from what I can tell, when a server is spun up there’s the option to subscribe to an existing blocklist on a piefed server.
This means blocklists can propagate transitively:
If instance A blocks lemmy.ml, and instance B subscribes to A’s blocklist, and instance C subscribes to B’s blocklist, then whatever instance is blocked on A will also end up blocked on C (unless filtered out manually).
quoting the developer of piefed, hexbear and lemmygrad are blocked by default:
Piefed just seems like it’s going to be a social chauvanist echo chamber, most people like Lemmy because even though the devs have their own ideological principles, it doesn’t pre-configure the user experience based on those principles.
It used to be hard coded, not even in the database but in Lemmy code itself and couldn’t be changed without forking. If I read the issue https://github.com/LemmyNet/lemmy/issues/622 correct, this has changed though.
Thanks. That’s unfortunate. But everyone running an instance will know about blocked instances sooner or later and can get them if the list of they like.
The blocklist subscription would be super useful on mastodon but I think the threadiverse is a bit different. However I’m on my single user instance and am subscribed to communities on other instances only, so I already get a pre-moderated experience even if I don’t block any instances myself so far so is experience doesn’t match that of the admin of an instance with more users and own communities.
Where is that code? Does it block some specific instances or how does it work?
For hexbear + lemmygrad it’s by default
from what I can tell, when a server is spun up there’s the option to subscribe to an existing blocklist on a piefed server.
This means blocklists can propagate transitively:
If instance A blocks lemmy.ml, and instance B subscribes to A’s blocklist, and instance C subscribes to B’s blocklist, then whatever instance is blocked on A will also end up blocked on C (unless filtered out manually).
quoting the developer of piefed, hexbear and lemmygrad are blocked by default:
This is why piefed is so popular with centrist extremists.
Piefed just seems like it’s going to be a social chauvanist echo chamber, most people like Lemmy because even though the devs have their own ideological principles, it doesn’t pre-configure the user experience based on those principles.
Does it not have that slur filter still? Not sure that’s really the reason people use lemmy
I don’t think the slur filter is something enabled by default, or if it is, is a widely known setting.
It used to be hard coded, not even in the database but in Lemmy code itself and couldn’t be changed without forking. If I read the issue https://github.com/LemmyNet/lemmy/issues/622 correct, this has changed though.
Ah, gotcha.
Harcoded block lists in your software? Gross.
Thanks. That’s unfortunate. But everyone running an instance will know about blocked instances sooner or later and can get them if the list of they like.
The blocklist subscription would be super useful on mastodon but I think the threadiverse is a bit different. However I’m on my single user instance and am subscribed to communities on other instances only, so I already get a pre-moderated experience even if I don’t block any instances myself so far so is experience doesn’t match that of the admin of an instance with more users and own communities.