While researching business models that could work on atproto there are some obvious ones that won’t work on a technical/architectural level. Like you can’t really monetize the data in the PDS because it’s all completely open (as long as there’s no permissioned data, but probably not even after that). That in itself already takes away a lot of room/incentive for enshittification (which is great), since when you do users can create or move to another app. But still, I kept encountering models/ta...
not to get too ahead of some other stuff i'm working on but i think every news org should be able to build experiences like this that they own via atproto. once permissioned data lands you can tie in business models really well. "substack on atproto" is too narrow, we can do better.
nilay patel
Was just scrolling our homepage revchron feed and caught the same vibe as when I was myself a hardcore Engadget reader in 2006ish. So happy with this, so much more to come
Hot take but I think it’s problematic for atproto that lots of developers i see talking about making stuff focus mostly on things absolutely no end user gives a shit about to fuel their protocols and architecture fetish, and it’s a failure there isn’t another app with like 100k+ users active even.
An underappreciated #atproto feature is that whenever apps want to update your data: 1. they ask your PDS for permission, 2. your PDS asks you, 3. you can say no, + 4. your PDS enforces your wishes As of today, the @tranquil.farm PDS UX lets you give "partial no" answers to question 3. Bravo!
Trezy
This is awesome. I made a PR last week to add better support and display for permission-sets to the OAuth consent screen for @tranquil.farm. Now every time I log in to my Atmosphere account, I can actually see my fingerprints on Tranquil. 😍 #atproto
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgThe key questions: how much power will apps be given to determine and enforce what data is permissioned? What incentives will apps have to make any data public? So far the protocol has been a forcing function for (adversarial) interop. We need to be intentional about not recreating app silos.
daniel holmgren 🫠
hey we're really working on permissioned data! read the first in a series of posts i'll be doing about our design decisions along the way. this one is about our decision to not do an e2ee system
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”
the 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.
