All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Why Bluesky Has No "Instances": Explaining atproto's Architecture

By

danabramov

8d ago· 160 min readenInsight

Summary

The article explains why people asking "where are the Bluesky instances?" are making a category error. Unlike Mastodon's federated model with distinct instances/servers, atproto (the protocol powering Bluesky) uses a different architecture where accounts are portable across providers and there are no separate "instances" in the Mastodon sense. The author draws a comparison to RSS and Google Reader to illustrate the conceptual difference.

Source

Hacker NewsWhy Bluesky Has No "Instances": Explaining atproto's Architectureoverreacted.io

Key quotes

· 3 pulled
Every single time a post about atproto hits Hacker News, somebody asks in the comments: 'But where are all the Bluesky instances?'
The problem is, there are no instances in atproto! The question is a category error.
Instances are a Mastodon-brained concept, and I wanted something I can link to that explains this clearly.
Snippet from the RSS feed
Like RSS and Google Reader.

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.