Email or username:

Password:

Forgot your password?
Top-level
L. Rhodes

To be clear, I don't know if you'll actually be able to restore an account from an indexing server. The protocol doc assumes you'll do it from your CLIENT. Which means that the app you post from is expected to make a persistent backup of your entire account—"contingent on the disk space available." So if the idea of being able to port your entire post history around is a big selling point for Bluesky, expect to eventually have dozens of gigs of account data riding around on your phone.

7 comments
L. Rhodes

Let's assume space isn't an issue. You connect to Bluesky from your desktop computer, and its got storage enough to handle decades worth of image-and video-heavy account backups. Your account is safe, right? Maybe. To recover an account hosted by a failed PDS you'll need your recovery key, so make sure you don't lose that. And there's a 72-hour window in which it can override the signing key, so make sure none of this happens while you're taking a week-long break from social media.

L. Rhodes replied to L.

To summarize: Bluesky makes accounts portable by taking everything important about them off of the servers that handle posting. Identity goes to a registry. Post history goes into an ever-growing backup on your own device. And most other functions are provided by services that crawl and index the entire network. To take full advantage of account portability, then, you'll have to shoulder some of the technical burden yourself, and make a few privacy tradeoffs.

L. Rhodes replied to L.

The technical burdens include (but may not be limited to): making sure your DID is registered with a secure and sustainable registry that's not operated by your PDS; managing backups of your entire account history on your own devices; and keeping track of the registry key you need in order to restore an account in an emergency.

The privacy tradeoff is that everything you do on the service will be indexed by third parties for use in their algorithms and (presumably) for their profit.

L. Rhodes replied to L.

All of this speaks to the issue of decentralization, btw. Ostensibly, Bluesky is built for federation between multiple PDS, the protocol's version of instances. AFAICT, though, PDS only communicate with one another when you @ a specific user on another server. Most of the time, they're just middlemen between your client and the indexing servers. The indexing servers are making most of the real decisions about what shows up in your timeline.

Bluesky is centralized around indexers.

L. Rhodes replied to L.

In theory, there can be multiple indexers, and you (or, at least, your PDS) would be able to choose between them. In practice, though, it's going to be incredibly costly to run an indexer, so expect corporations and VC-backed orgs to dominate. Bluesky has the first-to-market advantage, so they'll be the big one. Twitter could well pivot to indexing on the BS protocol. Maybe a few others will pop up. That's what decentralization really means here: Your choice of corporate-run indexers.

L. Rhodes replied to L.

I'm sure there are people on the fediverse for whom that use-case is a good fit. They put a premium on account portability, can shoulder the technical burden, aren't concerned about the privacy implications, and aren't particularly invested in the more thorough-going decentralization. To them I say, good luck and God speed.

I just don't want anyone making that jump without recognizing that one choice they're being asked to make is between account portability and genuine decentralization.
/end

I'm sure there are people on the fediverse for whom that use-case is a good fit. They put a premium on account portability, can shoulder the technical burden, aren't concerned about the privacy implications, and aren't particularly invested in the more thorough-going decentralization. To them I say, good luck and God speed.

Jon replied to L.
Go Up