Hacker News Reader

Comment by ninjagoo | Hacker News Reader

Not trustworthy. The providers mentioned in the article, blacksky and bluesky, presumably the most visible ones, do not allow signups with anonymous email providers even though they make you pass a human verification step.

The link in the article for Blacksky (blackskyweb.xyz) has a dark pattern that attempts to get you sign up for bluesky instead of blacksky. Odd.

The bigger issue is funding - currently appears to be VC funded (seed round 2023, Series A 2024), so they'll want a return at some point. Voilà, enshittification.

The biggest selling point - portable identity - is a mirage because the current providers do not give you the cryptographic keys to your identity. So they can simply lock you down, and your 'identity' is done.

View on HN

> The biggest selling point - portable identity - is a mirage because the current providers do not give you the cryptographic keys to your identity. So they can simply lock you down, and your 'identity' is done.

Here is one of many sites that help users de-risk, backup, and migrate: https://pdsmoover.com/

> Here is one of many sites that help users de-risk, backup, and migrate

Unfortunately, doesn't work if you're already locked out ...

And, you have to give this 3rd party site your username and password. Ouch.

You can use `goat` for a CLI version: https://whtwnd.com/bnewbold.net/3lj7jmt2ct72r

I'm not sure if OAuth gives access to the account management APIs. Certainly much could be improved. Nudging users would be a good notification within the Bluesky app, like one of those on boarding task lists that doesn't have to be completed to get started, but remains visible until you complete or discard them.

goat has since moved to a dedicated repository: https://github.com/bluesky-social/goat

There is also an adversarial path (when the PDS will not play nice), but it requires setting up a rotation key and having a repo backup ahead of time.

https://www.da.vidbuchanan.co.uk/blog/adversarial-pds-migrat...

This is also my take and I feel like we've seen this play out enough times to see where it's going. The protocol seems to allow decentralization, but that hasn't happened enough to protect against enshitification. If bsky decided to disconnect their main instance from the others, most bsky users wouldn't even notice, but third-party instances would likely implode.

The happy developer relations is to encourage people to develop on top of this "open" platform, but it's hard to imagine that's not just growth hacking.

Why not build on top of protocols that are actually open and will still have decentralized usage in a decade?

Reply on news.ycombinator.com