@strypey >But this kind of architecture has its place, for those who want to use it.
I agree and bsky is that place in my opinion. There is one large difference between what ATProto users want and what AP users (at least those than been here for a few years) want. AP leans a lot on user-level moderation where the user has almost absolute control over what their view of the network is. There is only one exception and that is the instance administrator who can force moderation on users of that instance. And even then a user can simply make their own instance and put the administrator out of the equation. ATProto is very different in that regard and uses almost centralized content labelers to first filter content, then allows users to subscribe to blocklists not managed by the user (a dumb idea that Mastodon will likely copy soon) and only after that allows user-level moderation. And users of the respective networks expect and want this difference. AP user mostly wants to moderate their own view with small exceptions done by the admnistrator, meanwhile ATProto users expect the moderation to be mostly done for them. That is the incompatibility in how they operate I talked about; you can interoperate between the two networks, just like Nostr, but the expected way of moderation is the polar opposite.
>The fediverse is for facilitating connections between any 2 people who want to interact, regardless of where they choose to host their accounts. Like email.
I agree and adding bsky-esque moderation centralization into AP throws a wrench into this mostly working system. At that point it no longer is about facilitating connections between users, but facilitating connections between users only if an overseer and some amount of instance administrators all agree. It is no longer email.
>This has been the pitch since Evan and the
Identi.ca folks launched Status.Net to encourage community-hosting.
And I agree with that pitch, but Evan either lost his plot in the last few years, got paid to loose his plot or simply doesn't understand yet what the consequences of what he wants are. He may have create Status.Net, created OStatus(2), co-created GS and co-authored ActivityPub, but what he wants now removed a lot of the credibility he accumulated over the years at least for me.
>I don't think we want protocol engineers and software devs to be making decisions about who "should" be able to talk to each other. For reasons explained in some detail here;
>https://disintermedia.net.nz/ethical-technology-and-political/
Since I contribute to Pleroma and also am a Fediverse user for more than 5 years now, I have two hats that I wear depending on what the topic and context in question is.
I agree with what you wrote in that article, mostly, which was a good read. Software should stay apolitical and impartial to who uses it and that is my stance and has been for a very long time. And that's the mentality I will always put ActivityPub to, I'm in no place to dictate who should use the Fediverse or who is allowed to use Pleroma. Neither do I want to have that power, I'm not interested in it. My stance on gatekeeping bsky users away isn't a stance on the software dev or protocol engineer side, but on the user side as a long time user of the Fediverse. I've seen the effects of similar users joining in en masse and don't want it to happen again.
>But we absolutely need to enable people to control what they see at account *and* instance level. To control spam, if nothing else.
My stance is, users should control almost all of this and administrators should only get involved in controlling spam or getting rid of illegal content from their server and making sure it doesn't come again from the same source. That is what instance-level moderation should be used for in my opinion. Software devs and protocol engineers shouldn't have control over who uses the Fediverse, nor should administrators have intrusive control over what users of an instance see unless its for the above.
@icedquinn @fish @sampler @p @light @silverpill