@arch
Yeah I was a long time Gentoo user before switching to nixos

Today it will be Gentoo Linux with systemd

Hm yes it is once again time to hop Linux distros

@puniko
Naja den Mauerfall konnte man nicht nehmen und die Wiedervereinigung unter den Konditionen zu dem Zeitpunkt gab es ja auch nur weil der kohl wiedergewählt werden wollte, und die UdSSR Kohle brauchte

@fiore @dangerdyke @ben atproto is designed around the cryptobro idea that everything should be public, unlike fedi which had some access control pretty early on. and authorized fetch to enforce blocks and the like. this makes it impossible to restrict visibility of posts beyond stupid client side restrictions like loginwalls

this also means that blocks are shared. also not learned from activitypub where it federating out blocks to remote instances is a harassment vector. and we don’t even get people’s whole blocklists here!

certain minor things are also limited. for example on twitter and on here it is possible to make someone unfollow you by “soft blocking”, i.e. blocking then unblocking. however blocked users stay following you on bluesky because you don’t have the authority to change their profile.

however bluesky does have better effective reply management than fedi, outside certain implementations like gotosocial

and posts and user identities being intrinsically linked with a practically ephemeral server identity on fedi is kind of annoying

@ben @fiore @dangerdyke i can understand a clean break from the fediverse and it could have been better but they did not in fact make it better

i suppose relays is what you end up with if you want a global view like centralized social media networks with multiple nodes in the system. in a way centralized social media networks have something similar to said “relay” internally

@fiore @ben @dangerdyke lots of tradeoffs that are unexplained and undefensible if you are doing a centralized social media network like bluesky effectively is. lots of lessions not learnt from the fediverse which predates it and does certain things better to begin with

@fiore @dangerdyke @ben there are loads of problems don’t get me wrong and if it wasn’t started by jack dorsey bluesky would probably have a significantly better albeit likely not decentralized protocol

@dangerdyke @ben @fiore if you wanted a bluesky 2 then doing that would be necessary would be my guess

but you don’t have to have a global view of everything to have a social networking service. you could for example limit the scope of your relay to just posts by your users and people they follow

@dangerdyke
@ben that is a different point from "basically the same thing as just a twitter client let's ignore that twitter clients do not host your account profile"

@ben
Idk if there is a proper website but https://github.com/blacksky-algorithms

@ben
Like I'd point at blacksky here which has replicated the entire stack for their Userbase. You can also reach their users from bluesky and vice versa

@ben
If being able to be completely separate from the main bluesky servers (with your own apps, appview, relay, moderation, and pdses) is the same as just a twitter client, then we are also just using our own custom twitter clients

@ben
Which can also access the same pdses as regular bluesky and vice versa

@ben
Like the entire discussion surrounding bluesky decentralization boils down to "it doesn't work exactly like the fediverse which is the only decentralized design apparently" while the real argument to make is "everyone uses the bluesky equivalent of mastodon.social"

@ben
The pds is where the data is stored. You can also host the relay server yourself

@ben
You can host each of the components of bluesky yourself (data storage, post aggregation, content filtering/moderation, and the app), it's just that basically nobody does any of that

And it allows you to have an effective disconnect of the main bluesky servers but practically you do not want that

@TerrorBite
@stilgherrian tbf someone would have to report it and also they'd greatly prefer if your neighbors and you agreed on a solution without getting them involved

@pyrex
Yeah the actual Future plumbing is kind of arcane but honestly the main time I have to write it is with 3rd party async primitives like `AsyncRead`