That should be the guiding principle for all atproto "alternatives"

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

As far as i understand the #atproto ecosystem has 3 great problems: 1) the main huge relay is under control of #bluesky 2) The #PLC (identity register) is under control of the same company 3) also the protocol itself is developed and at the moment under control of bluesky.

ATProto explainer thread from a non-Bluesky app/service’s perspective

What I am learning from this outage is that if you were naive enough to believe that the atproto overview docs and architecture diagrams presented a true view of how bits of software rely on each other (🤚) you have a very distorted view of how how the network actually works.

#atproto is there anything we can do to solve the issues plaguing the lexicon specification right now I don't think it's good that the reference TS and Go SDK do not agree with each other on how lexicons should be interpreted