this post was submitted on 18 Dec 2023
31 points (89.7% liked)
Lemmy
12535 readers
3 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mastodon instance blocks are already bidirectional AFAIK: if you block an instance your content does not get federated with them. I was actually surprised that this does not seem to be the case for Lemmy. I don't think this break any core abstraction of AP...
I'm no expert that sounds like limited federation mode? Seems it's supported for truly private instances (ie. Universities) but discouraged? At the similar server level I thought lemmy had bidirectional defederation too, but nothing that would be at the user level like the new instance blocking feature.
Can you share more info on how mastodon blocks function? Their documentation list the user action as "Hiding an entire server", which seems in line with lemmy
More info I found:
This post from Eugen Rochko mentions that blocking Threads at the user level "stops your posts from being delivered to or fetched by Threads". Basically, the user-level instance block is bidirectional.
Limited federation mode is a different feature, at the admin level. It doesn't really affect the delivery of posts in either direction, it just hides the blocked instance's content from the global feed. Defederation on the other hand is indeed bidirectional, but again it's on the admin level rather than users'.
I don't know but the mastodon documentation does not mention this: https://docs.joinmastodon.org/user/moderating/#block-domain
Personally I'd expect that anything I post on social media is being public and freely accessible by anyone if they want to. If you don't want the information to be used by others you probably should not share it with the world.
Lol well hey, fair enough. That's much more recent than anything I found, too. I'd be interested in seeing this feature implemented as well. It would be nice to not directly contribute to anything Meta..
There is an interesting thread here showing the "block" behavior is operating as described in the documentation (Hiding), this raises some questions of a true block or just a client filter: https://mastodon.online/@NatureMC/111590515879528415
I'm curious for additional clarity now!
Other people in that thread have pointed out that it isn't showing posts being delivered to Threads despite the block. That should be testable with other instances, but not Threads since it's not receiving any content from Mastodon at the moment. The concerning thing there is the user still being able to view content from people they've blocked, but that seems to be a bug if it's reproducible.