Lemmy

2172 readers

50 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

[email protected]

Instance blocks and Threads (feddit.it)

submitted 11 months ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

With debate raging in the Fedi about Threads' federation, I was having a discussion with another user about the recently implemented instance blocks. They pointed out that, blocking an instance simply hides their content from your feed but doesn't prevent your posts from being sent to them. Firstly, is this correct? Is this how instance blocks are implemented in Lemmy? If not, has this been discussed before? I couldn't find such a discussion in Github issues...

It seems that many people have concerns about Meta's use of their data, and would like to opt out of sharing their content with Threads. Is there any way to do this in Lemmy right now, or any plan to implement such a feature?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 11 months ago (1 children)

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...

[–] [email protected] 0 points 11 months ago* (last edited 11 months ago) (1 children)

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:

For Mastodon server admins, a bit more about the "authorized fetch" feature. It makes it more difficult for blocked accounts to interact with public posts on your server. It's not fool-proof as public posts can always be scraped by outsiders, but it makes life harder for trolls

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (3 children)

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'.

[–] PropaGandalf 3 points 11 months ago* (last edited 11 months ago)

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.

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago)

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..

[–] [email protected] 0 points 11 months ago* (last edited 11 months ago) (1 children)

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!

[–] [email protected] 2 points 11 months ago

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.