652
fucking beautiful. almost a year into the 'verse and its starting to become more functional than that R place... better than i imagined.
(cdn.catsweat.com)
this post was submitted on 19 Apr 2024
652 points (96.3% liked)
Fediverse
28351 readers
585 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I was mistaken - lemmynsfw isn't bblocked. There are only 3 blocked: lemmy.one, lemmy.today, lemmy.froztbyte.dev. Are you proposing that lemmy.ml, lemmygrad, and hexbear get the block?
I personally wouldn't mind blocking those three specific ones but others obviously might disagree. I tried giving lemmy.ml the benefit of a doubt for a while but especially the worldnews community just seems disinformation & insults from the same accounts while the mods don't care or even actively work the same agenda.
I think what would be great is if we could block entire instances ourselves. Right now I am manually blocking all communities that pop up from those three instances, which is tedious. There is an URL for instances (Example: https://fedia.io/d/lemmy.ml), which even features the block button, but it simply does not work in blocking the actual content or even users of said instance. It would be cool if that was an actual feature and a link to the community's or user's instance available within the sidebar.
Just curious, what was the reason for blocking those first three instances?
lemmy.froztbyte.dev is/was sending malformed messages that caused this the queue runners to crap out. The others were for persistent harassment of one of our trans members.