manton
manton

Threads starting opt-in for the fediverse is fine. In fact, it’s what we did in Micro.blog too back in 2018, because I wanted to focus on personal domain names and that requires a little more configuration. However, I do hope that Threads expands to enable federation by default for all users.

|
Embed
Progress spinner
Ciantic@twit.social
Ciantic@twit.social

@manton We hope that, but given that @mosseri was explicit on opt-in, I doubt that.

This is starting to look a lot like a one-sided street, where #Threads get most if not all content from Fediverse, but Fediverse only gets the posts from a selected few who ever bother to look at options for opt-in.

Also, we here at the Fediverse will not be able to follow discussions in Threads if that is the case. Suppose 'A' who has opted in replies to 'B' who hasn't, we won't get that discussion.

|
Embed
Progress spinner
manton
manton

@Ciantic I think Meta is going to find that it gets weird when only some accounts are enabled. For example, what happens when someone sees replies from the fediverse that they can’t reply to because they haven’t opted-in? So I’m hoping they’ll come around.

|
Embed
Progress spinner
rom
rom

@manton is there a plan to include a feature to block certain domains (on the user level) from following the ActivityPub endpoint here on Micro.blog? This would be great for people like me who would rather not have my data easily siphoned off my Meta (yeah, I know it is public, but a little friction would do wonders). :)

|
Embed
Progress spinner
In reply to
manton
manton

@rom Yes, that is planned. Shouldn't be too long.

|
Embed
Progress spinner
rom
rom

@manton yay!!!! Thanks in advance!

|
Embed
Progress spinner
lukemperez
lukemperez

@rom can you walk me through a use case? I’m afraid I don’t understand Activity Pub deeply, and so I’m not sure I understand what you want; but I understand just enough that I might want that feature one day (for Threads or anyone else for that matter).

|
Embed
Progress spinner
rom
rom

@lukemperez mastodon has this feature that allows users to block domain/instance but the host instance does not need to defederate said user-blocked domain.

Micro.blog might allow this in the future - users to opt not to be seen by other AcitivityPub instances/users. Not sure how this will be implemented by @manton and team, though. :)

I know posts are public, but as I have said, a little friction for those instances can help prevent abuse.

|
Embed
Progress spinner
lukemperez
lukemperez

@rom oh that’s rad. I can see how that could be helpful. Thanks for the explanation.

|
Embed
Progress spinner