deleted by creator
It would be a great feature. If a comrade would like to volunteer to build it, please check out our guides in: !hexbear@hexbear.net.
Until then, we work with what we have, which is bans.
deleted by creator
This is an easy decision to make. We'll be adding this word to our slur filter when a dev comrade is able to. This may take a while to implement, so please be patient in the meantime.
This word was not included at launch based on feedback from fem comrades during beta testing. Clearly something that needs to be adjusted based on the strange reactionary responses to comrades even suggesting it. We'll be locking this thread now.
@Kanna, @Arahnya , and @Bayonetta - thank you for bringing this to our attention and holding your ground.
We are going to lock this thread since admins have responded and to force anyone still arguing to disengage.
deleted by creator
deleted by creator
deleted by creator
Do you have a link to your !feedback@hexbear.net bug report for this? We fixed an issue in the past with some pdf sites and iframely (lemmy's default library for embeds). We do have a ticket for a site blacklist / whitelist as well, but need someone to pick it up.
Hey comrade, totally valid question. The Hexbear Manifesto covers the reasoning for shifting from Vanilla Lemmy pretty well. Returning to vanilla lemmy would involve building a completely new site and the loss of all custom developed features like pronouns, sitemods, reports, custom emojis, and more.
There also isn't an interest from the core dev volunteers in continuing to work with Rust. When we previously did try to contribute upstream, the turnaround times of having our PRs approved + number of rewrites requested unfortunately made keeping up with the vanilla project untenable. That was for totally valid reasons since the core Lemmy team has other priorities, but did result in the code drift that eventually created a de facto fork even with the legacy rust codebase.
The vanilla lemmy devs are comrades and we 100% support their efforts. This project just has different priorities. A version of the lemmy effort in a different language more folks are familiar with also helps benefit the project since it will eventually allow for more people to contribute to building out a federated ecosystem.
We're currently focused on the back-end rewrite and will be able to look at federation + other new features following that. For comrades familiar with typescript, please take a look at our getting started guide for how to contribute to Hexbear.
Correct. It allows for someone to self host an image and skim the ip addresses of everyone who views the embedded image.
This may have changed with the vanilla project since we were beta testing the site before launch, but is why we disable the feature for our site. Only allowing images uploaded to this site is an option, but like with any open source project, requires a volunteer interested in that feature to build it.
When someone pitches in and builds it! :owl-wink:
Obligatory plug for !hexbear@hexbear.net. The cool thing about open-source projects is that the whole community makes new features happen together. :halal:
Thank you for the troubleshooting session, this is a known issue. We are aware there are things to fix with the active sort algorithm. While it is not at the top of our priorities right now, if others would like to chip in to address this, please go to https://hexbear.net/c/hexbear
:chavez-salute: