@oliphant
@HistoPol @snarfed
@snarfed.org @luca @PCOWandre @fedidevs @fediversenews @chronohart @activitypubblueskybridge
I’m wondering if that means there may be a functional difference between blocking the bridge vs adding the #nobridge tag?
@oliphant
@HistoPol @snarfed
@snarfed.org @luca @PCOWandre @fedidevs @fediversenews @chronohart @activitypubblueskybridge
I’m wondering if that means there may be a functional difference between blocking the bridge vs adding the #nobridge tag?
@scott@authorship.studio In short, it’s just like blocking one-by-one but as batch-action. Admins can also block domains using wildcards, I think.
However, either would not work to block specific software. You would indeed have to use an instance in limited federation mode, where each connection is checked one-by-one, to avoid federating with Friendica and Hubzilla instances that could copy your posts over.
@Qazm There are other options, like using a platform that has privacy, access lists, permissions, and better moderation tools. Mastodon only has block lists, which limits user’s control over their own posts.
For example, on Mastodon you can block someone so you can’t see their posts, but you can’t stop them from replying to posts they have already seen. On Hubzilla, you can actually turn off commenting on your posts so no one can reply or so that specific people can’t reply, and can even delete other people’s replies to your thread. You control the conversation in your thread. You can’t do that on platforms like Mastodon.
Also, on Hubzilla, it is all about user choice. So if Hubzilla implements the Bluesky protocol, both the admin AND the user would have to opt-in. Users would have to actively turn on the Bluesky addon to federate with Bluesky. Otherwise none of their posts will ever be sent to Bluesky. I am pretty sure Friendica will work the same way.
So Hubzilla and Friendica would actually do a better job at blocking Bluesky than the bridge does. And the bridge actually has a lot of options for blocking Bluesky.
So instead of blocking Hubzilla and Friendica, you probably want to start using it instead, since it gives you better protection against Threads and Bluesky than Mastodon does.
@scott I don’t think so. Other Hubzilla or Friendica instances that receive a Hubzilla post over AP can still boost it over there, right?
The reply control from your instance won’t stop Mastodon users from replying either (though it will stop you seeing those replies, and to some extent will reduce the visibility of replies).
I think it all comes down to what’s outlined in https://foggyminds.com/display/c6ef095f-1165-ce77-d6de-73f618365846 (saw that post a little after my reply above) and open federated social media in general being built around own-access-choices rather than data control, outside of posting modes with very limited reach which should be implemented with more privacy than they are.
@Qazm That was sort of my point. If you want to have more control over who can see and respond to your posts, you probably should stop using Mastodon and switch to a platform that supports privacy, access control, permissions, and moderation.