atproto made simple: granular permissions - underreacted
Permissioned data on atproto — pick your depth
A private room in a place with no walls: how engineers are adding permissioned data to atproto. Read it plain-language or technical.
Early Permission Sets · bluesky-social atproto · Discussion #4437
Progress is coming along on "Permission Sets", as part of the atproto OAuth and permission system. As with other parts of the protocol, seeing how this functionality gets implemented for ...
atproto made simple: granular permissions - underreacted
you're working on an atproto app that needs to write some records to your own collection like app.example.post or app.example.like. you're already using OAu…
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgthe point of atproto is to make locked-open apps. apps which are constrained such that they cannot be e.g. bought by billionaires and ruined. yes, doing non-atproto things "enables app developers to do more". yes, non-atproto is "more intuitive" and "it sucks" when you hit atproto's limits.
related: for a number of use cases on atproto, the challenge has shifted from 'how do i get people to use my app' to 'how do i get people to use my lexicon' this also shifts what prototype apps even are
dame
in my experience there is now room to “vibecode” a prototype, evolve it into a more serious app, and then down the road refactor it into something that is more professional, organized, and sustainable previous AI models couldn’t handle large refactors like this, but they now can with human aide
looking for feedback on the first pass of permissioned data protocol lexicons! hop in & let me know your thoughts! discourse.atprotocol.community/t/permissioned-data-pds-lexic…
Permissioned Data PDS Lexicons
discourse.atprotocol.communityatproto offers an fascinating example of what it means to restructure this relationship. End-users get to choose who and how much trust they delegate to software producers, the delegation of trust becomes tangible and revokable.
𝕮
Networked computing, in a fundamental way, changed the producer-consumer relationship we have with corporations. In the material world that relationship ends with the transfer of material and money; I buy a pencil and some paper, and the producer is out of the picture while I use them to write.
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}"
dame
i would like to see more atproto apps that aren’t just “already popular app, but on atproto”
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
