4 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The author details their frustrating experience setting up an ATProto account for Bluesky, highlighting documentation gaps and a problematic "burn" system. They argue that this centralization undermines the supposed decentralization of the platform, making it difficult to interact with others.
If you do, here's more
The author shares their experience setting up an ATProto account for Bluesky using did:web, highlighting significant challenges along the way. Initially, they managed to set up the PDS software on their server easily due to using NixOS. However, they encountered issues with the outdated tutorial for creating a did:web. After successfully creating the keypair and uploading the did.json document, they faced hurdles activating their account, which remained in a "deactivated" state. Despite seeking help in the ATProto community, they had to delete their account and start over, only to discover they were blacklisted due to this deletion.
The author’s main frustration lies in the centralized nature of the system, which seemingly punishes users for deleting accounts—even empty ones. They detail how their friend could not find their profile on Bluesky after deletion, while it appeared with limitations on other platforms. The lack of comprehensive documentation further complicates the process, making it difficult for new users. The author compares this situation to Mastodon, pointing out that while Mastodon has its own challenges, it wouldn't have led to such a complete inability to interact with others. They argue that ATProto and Bluesky’s claims of decentralization are undermined by this centralization, which ultimately restricts user interactions.
Questions about this article
No questions yet.