at://rude1.blacksky.team/app.bsky.feed.post/3mdtaccp33s2a
Back to Collection
Record JSON
{
"$type": "app.bsky.feed.post",
"createdAt": "2026-02-01T21:05:22.512Z",
"embed": {
"$type": "app.bsky.embed.recordWithMedia",
"media": {
"$type": "app.bsky.embed.images",
"images": [
{
"alt": "Mike Masnick\n(profile)\nsays:\nJanuary 27, 2026 at 11:50 am\nRe:\n\nIn ATproto, it’s not set up as “instances” like in ActivityPub. In ActivityPub, you have each service sits on its own server, so you’re at the whims of whoever runs which server you’re on. With ATproto, there are different layers to the stack. You have the PDS, the relay, the AppView, and the client. And so different people can take control over different parts of the stack and mix and match.\n\nThe article above is really just discussing the PDS layer, but we’re seeing different relays, appviews, and clients all the time.\n\nI take your meaning to be: “if i have a Bluesky account, can I still communicate with people on Bluesky without touching any Bluesky hardware” which is a bit of a different question. But the answer to that is also yes.\n\nBlacksky is the most obvious one, that now runs its own PDS hosting, its own relay, its own appview, and its own client. So you can absolutely move elsewhere and tons of people have.\n\nNorthsky is working on a similar setup for Canadians. EuroSky will soon be online for Europeans. Others are building out their own offerings as well.\n\nBut that’s all for microblogging. The whole point of this post is that atproto does way more than that.\n",
"aspectRatio": {
"height": 567,
"width": 695
},
"image": {
"$type": "blob",
"ref": {
"$link": "bafkreiaw5xlh6o7ui5tzva5n4qrqylbm74dxjypslg36vq7kbq43tk4el4"
},
"mimeType": "image/jpeg",
"size": 279731
}
}
]
},
"record": {
"$type": "app.bsky.embed.record",
"record": {
"cid": "bafyreievdfx3avdlabzoo6xrbdfj6jvxbqtfvnrswd4memb6bltvyeapl4",
"uri": "at://did:plc:l4edfel22exejp7mewt6f3ky/app.bsky.feed.post/3mdgfw53gey2s"
}
}
},
"langs": [
"en"
],
"text": "Blacksky is the only* one."
}