You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
If nothing else, pretending Bluesky is the only player is Blacksky erasure
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
@countablenewt The problem is that Bluesky Social PBC are the owners of ATProto. From Wikipedia:
Bluesky Social, officially named Bluesky Social PBC, is a privately owned for-profit corporation.
[...]
Bluesky unveiled open source code in May 2022 for an early version of its distributed social network protocol, Authenticated Data Experiment (ADX), since renamed the Authenticated Transfer (AT) Protocol.Note the wording: "...its distributed social network protocol..." ie, ATProto is owned by Bluesky Social PBC.
And, it's easy to see this ownership by just looking at the Github Repository for the ATProto reference implementation.
Compare that to ActivityPub:
ActivityPub is an official W3C recommended standard published by the W3C Social Web Working Group.
And, it has been a standard that has been developed under W3C going all the back to its beginnings around 2016.
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
how to, though?
-
how to, though?
@sirtao@social.sirtao.it the three general approaches I've seen are:
- use a different PDS, relay, and AppView than the Bluesky hosted ones - this is how Blacksky works (and I think wafrn uses its own sidecar PDS along with Blacksky's relay)
- disregard the AppView layer entirely and just talk to individual PDSes, along with external APIs like https://www.microcosm.blue for reverse lookup - this is how Red Dwarf works
- just use Bridgy Fed
My art gallery app Pandacap (which I really need to make a proper post about at some point) uses #2 to follow people and #3 to post stuff.
-
@countablenewt The problem is that Bluesky Social PBC are the owners of ATProto. From Wikipedia:
Bluesky Social, officially named Bluesky Social PBC, is a privately owned for-profit corporation.
[...]
Bluesky unveiled open source code in May 2022 for an early version of its distributed social network protocol, Authenticated Data Experiment (ADX), since renamed the Authenticated Transfer (AT) Protocol.Note the wording: "...its distributed social network protocol..." ie, ATProto is owned by Bluesky Social PBC.
And, it's easy to see this ownership by just looking at the Github Repository for the ATProto reference implementation.
Compare that to ActivityPub:
ActivityPub is an official W3C recommended standard published by the W3C Social Web Working Group.
And, it has been a standard that has been developed under W3C going all the back to its beginnings around 2016.
@unattributed@gotosocial.social AT Protocol may have initially been developed at Bluesky, but they are in the process of developing a standard for it: https://datatracker.ietf.org/wg/atp/about/
The IETF Working Group was only fully setup the other week, so you may have missed it.