- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Code for people interested https://codeberg.org/rimu/pyfedi/src/branch/main/app/admin/routes.py#L373
I commented it out, rebuild the Docker containers and it works now 👍
Code for people interested https://codeberg.org/rimu/pyfedi/src/branch/main/app/admin/routes.py#L373
I commented it out, rebuild the Docker containers and it works now 👍
Well, it seems specifically 196 just got removed: https://codeberg.org/rimu/pyfedi/commit/b7a9ea0eea3a80f710e0b5b63cf0bbecde60f8bf
Actually, they only removed it from 2 places. It’s still there https://codeberg.org/rimu/pyfedi/src/branch/main/app/cli.py#L1026
I wonder why the dev had an issue with 196
Because it’s an enormous flood of content that overwhelms trying to browse All otherwise, especially by New. Or at least that was the case a couple years ago, maybe it’s changed now that the community has split up into 3 parts.
It was particularly a concern back before Lemmy had implemented the Scaled sort function and changed how Hot worked. Perhaps PieFed, back upon tinkering with its own sort functions, similarly tried to make that process easier to see content other than from 196 and memes?
If I had to guess, 196 is more queer positive.
You’re wrong. Rimu has never expressed any objection to pro-LGBT sentiment and has even done interviews in regards to that. I have seen him ban people for anti-LGBT bigotry. This particular ruleset looks like a copy and paste from the retention rules that piefed.social currently has that doesn’t save data from communities after 6 months. (RImu doesn’t have a high opinion of meme-themed content and believes it to be a drain on server storage).
I agree all of it should be optional, and I believe it currently is anyway as instance owners can revert this.
That still makes no sense
It does if your a bigoted shit face.
Correct, it doesn’t. But some people find a way to be bothered by it.