- cross-posted to:
- lobsters@lemmy.bestiver.se
- cross-posted to:
- lobsters@lemmy.bestiver.se
You must log in or register to comment.
Wait, is it required to mirror the entire Bluesky history? Can’t you just store only new messages? Because the storage requirements (4.5TB according to the article) make it almost impossible to self-host.
This is for if you want to host parallel infrastructure. If you only want to self-host your own data, the instructions create a PDS are here, and the instructions to migrate an existing Bluesky account to that PDS are here.
Okay, that makes much more sense.
Is there any public third party BlueSky storage server yet? Last time I tried setting up an account there it only showed the main instance despite all the fuss about decentralization. Or am I grossly misunderstanding how different it is from the fediverse?
theres also a critical ‘relay’ component required that so far only Bluesky runs, so not-so-federated.
there is no such thing as a 100% independent bluesky install to which people can attach also independent nodes (PDS).
- As far as I know, there aren’t any yet. Even if there were, I personally wouldn’t trust them for the same reason I wouldn’t use any Mastodon instance besides mastodon.social: if the PDS shuts down abruptly, your account is gone forever.
- Bluesky and ATProto are designed specifically to hide the ways in which it’s decentralized.
- I think this post does a good job visualizing how AtProto is different from ActivityPub.
Well, that diagram brings up an interesting point. In fediverse if the host dies the federated content can still live on (theoretically, I haven’t checked to see if they cull content from dead hosts) but ATProto would dictate that the host is missing and therefore all content associated with the host is now immediately 404.
Edit: I stand corrected https://social.coop/@cwebber/113527531906508036
you runnin your own relay or is it all ‘except the relay and appview’?
