At Protocol for Agents
davidgasquez.com
At Protocol for Agents
1–5 of 5 posts
Re: At Protocol for Agents
#2AT Proto's fundamental issue is that the data is open and every dev thinks they should have access to every user's data.
People want privacy, and def don't want AI touching it, nor likely want their chat sessions to be public.
Re: At Protocol for Agents
#3AT Proto's fundamental issue is that the data is open and every dev thinks they should have access to every user's data. People want privacy, and def don't want AI touching it, nor likely want their chat sessions to be public.
No disagreement there. If you want to keep updated on the permissioned data protocol you can follow daniel's leaflets https://dholms.leaflet.pub/ (https://dholms.leaflet.pub/rss)
The public side is extremely important for agents though. Agents need up to date public information to do their job. Every other service is going closed. Public information and activity should be a commons.
Re: At Protocol for Agents
#4AT Proto's fundamental issue is that the data is open and every dev thinks they should have access to every user's data. People want privacy, and def don't want AI touching it, nor likely want their chat sessions to be public.
Chat sessions on atproto apps are not generally public. For example, the Bluesky app has private chat and Germ (https://germnetwork.com/) is an E2EE messaging app built on atproto as its identity system.
Regarding the open data— we do believe that anyone should be able to publish in the open, and building should be permissionless much like the web. But we don't think all data should be public, and clearly there is strong demand in the world for private spaces.
The community is working intently on bringing permissioned data to AT Protocol, and there are already several working examples out there illustrating different approaches. The head of protocol at Bluesky, where I also work, has been publishing his views on where permissioned data is heading: https://dholms.leaflet.pub/3mhj6bcqats2o
Re: At Protocol for Agents
#5AT Proto's fundamental issue is that the data is open and every dev thinks they should have access to every user's data. People want privacy, and def don't want AI touching it, nor likely want their chat sessions to be public.
Chat sessions on atproto apps are not generally public. For example, the Bluesky app has private chat and Germ ( https://germnetwork.com/ ) is an E2EE messaging app built on atproto as its identity system. Regarding the open data— we do believe that anyone should be able to publish in the open, and building should be permissionless much like the web. But we don't think all data should be public, and clearly there is…
It continues to amaze me that you (multiple members of the bsky team, not you specifically) are unaware that I was very actively involved in the community effort around private data for atproto, and developer tooling in general. Boris gave me a slot in the first private data working group call to present Zanzibar and my PDS fork with a prototype implementation.
That no one from Bsky was there was telling. That I don't think the diary is a sufficient implementation, and Paul's comment on HN attempting to get under my skin about it (saying "sorry we didn't pick yours", before any formal proposal had been made), the near zero Bsky presence in the private data forum discussions. The impression I take from this is that Bsky team doesn't actually care about what's going on in the community around private data, Bsky will do what Bsky wants to do.
Between the poor leadership, community snuffing, toxicity within the community, bain capital crypto y'all hid from us for nearly a year, and general misalignment in several areas... I've left atproto permanently. A successor will come along that takes privacy seriously from the get go.