150

A Step Towards Full Bluesky Federation? | Self Host a Bluesky Atproto Network (github.com)

submitted 1 day ago by ericjmorey@discuss.online to c/fediverse@lemmy.world

49 comments fedilink hide all child comments

This is the first time I'm seeing a way to host a full Bluesky network, I think. It seems like a big step towards full federation beyond appviews and personal data servers.

you are viewing a single comment's thread
view the rest of the comments

[-] originalucifer@moist.catsweat.com 8 points 14 hours ago

the short is, bluesky is only designed to 'federate' with itself and will never be truely decentralized as it will never interact with 'foreign' servers.

all they really built is a twitter where a user can control their own node of information (pds) but it will never interact with another bluesky instance.

in the real fediverse, servers interact as they come on-line and are subscribed to each other by users. this causes some security issues, and portability issues but at least its actual federation creating webs of content by fully independent peeps.

[-] aeshna_cyanea@lemm.ee 4 points 14 hours ago* (last edited 14 hours ago)

The entire point is that your pds can interact with multiple "instances" of bluesky or whatever other apps people build on the protocol.

For example there is a reddit/hn clone that people can post on (keeping their same identity) when the official bluesky service goes down. The reddit clone is fully independent from the twitter clone, but they use the same protocol and (unlike AP) the same hosting and authentication infrastructure.

Whereas on Lemmy and mastodon, my accounts are totally separate. And unlike AP, your data lives on your own pds and is never hostage to the owner of the instance that actually runs the load bearing interactivity. If they become compromised or shut down you can switch to another. No cooperation from the old owner required (unlike activitypub).

[-] supersquirrel@sopuli.xyz 2 points 9 hours ago

Yeah but unlike activity pub, atproto/bluesky demands each self hosted relay process a massive amount of data to participate, it is incredibly impractical and costly to envision scaling up, bluesky's self hosting is essentially made to be a curiousity rich developers with access to powerful hardware try out as a hobbiest project and write a blog post about, not a serious general use case for everyone.

The idea of course is make it so nerds can technically do it, but the bulk of users can't and won't.

The strategy is convince the nerds you are giving them access to the future and that average people aren't ready for it, and than never actually provide that future since nerds stop advocating for it because a corporation handed them a tiny scrap and that was enough to write a good techy diy blog post about.

Bluesky is the past desperately trying to convince you it is the future, don't fall for it.

[-] originalucifer@moist.catsweat.com 5 points 13 hours ago

in other words, if bluesky goes titsup you can take your pds, and set it to another relay. but then when the original bluesky comes back up you are dark on that instance. thats not decentralization. thats islands of twitter that you can switch between.

you will not be able to interact with multiple bluesky instances simultaneously.