daniel holmgren 🫠
@dholms.at
just trying to build a little network we can all hang out in head of protocol @ bsky 🌅
ATProto builders, I've been having some really positive conversations with multiple funders who want to invest in the ecosystem. The tides are shifting, the interest is here. But, we need to talk. 👇
pretty successful first working group session I think! thanks to the chairs and everyone who participated. excited to get this thing really rolling!
If you weren't able to tune in live, the recording from the IETF 126 session on Authenticated Transfer featuring @dholms.at and @bnewbold.net is now available www.youtube.com/watch?v=1xsN...
Felt genuinely nervous hitting publish, it's impossible to overstate how much @kissane.myatproto.social's writing and thinking has been an influence on my own over [redacted] years. It was such a pleasure to get to chat with her, I hope y'all love this one as much as I did putting it together.
For the latest Off Protocol conversation, @jimray.bsky.team had a delightfully wide-ranging talk with @kissane.myatproto.social about so many things and ultimately a desire to make better mistakes atproto.com/off-protocol...
just got an email from @dholms.at that just said "do a breakthrough" ?
We know developing OAuth clients locally has been harder than it could be, partly because `localhost` isn't allowed as a `redirect_uri`. Please chime in on this discussion if you have any concerns about relaxing that particular rule.
Proposal: allow `localhost` redirect URIs in the localhost dev exception in the OAuth spec · bluesky-social atproto · Discussion #5255
This is a proposal carrying on discussion from this closed PR: bluesky-social/atproto-website#709. There is also a corresponding open issue, bluesky-social/atproto-website#699. Currently, http://12...
github.com
check out this post on the forum if you're curious how to participate in the atproto working group at the IETF this week Thursday, July 23rd from 4-6pm CET
Wrote up a version with updated links, inspired by @chadkoh.com's Montreal post: discourse.atprotocol.community/t/support-fo...
the thing i love most about decentralised socials is that it continually surprises its most active proponents of how radical and disruptive it actually is
new data diary! (and i think final in the main series) this gets into the permissioned repository itself. how it's structured, signed & synced. give it a read & as always, lmk your thoughts!
Permissioned Data Diary 7: Off the Record
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
dholms.leaflet.pub
ugh web is so complicated. that certificate authority looks quite centralized to me. and that CDN might end up expensive to run at scale. and do we really need another standard? just use email
exhaustion from traveling/conferencing for a week and a half vs 6 club mates who will win?
A selection of the meetup crew tonight in Berlin, with some travellers passing through.
My dream open and local setup for playing with computers: @pi.dev as the harness, @tonk.xyz as the database, @atproto.com for identity, and @iroh.computer for sync 👾👾👾👾
late to the party cause i've been conferencing but this is very welcome & very exciting news. @toni.bsky.team has been awesome to work with & i'm stoked for this next phase of building out the atmosphere with him
Staying in the game I'm four months into my interim CEO role at Bluesky, and it's time for an update. Most importantly, as of today, the interim part of the title is gone. I'm... https://toni.org/2026/07/10/staying-in-the-game/
Thursday at @getdweb.net camp started off with a great conversation about distributed protocols @dholms.at ATProto & @dustyweb.bsky.social ActivityPub moderated by @bmann.ca Later @brewster.kahle.org debuted @onionpress.org There were so many awesome talks and presentations & chill forest baths.
come hear me talk about atmoq! you’ll all be using it in a year or two anyway, might as well learn what’s up
reminder that IETF 126 is coming up in a few weeks! the atp working group is scheduled for July 23 at 4:30pm CET we want this to be a good one! so if you're interested in the standardization of the protocol, make sure you sign up & participate a few notes in thread:
reminder that IETF 126 is coming up in a few weeks! the atp working group is scheduled for July 23 at 4:30pm CET we want this to be a good one! so if you're interested in the standardization of the protocol, make sure you sign up & participate a few notes in thread:
IETF 126 Meeting Agenda
datatracker.ietf.org
Daniel's permissioned data proposal just dropped!! This will be a major upgrade for atproto that enables private groups & communities. Really hope this technical design resonates with people so we can keep moving fast, but please do get your comments in
just in the nick of time! github.com/bluesky-soci...
how the holiday weekend's looking at me after publishing the permissioned data proposal that i've been working on for the last 5 months straight
just in the nick of time! github.com/bluesky-soci...
proposals/0016-permissioned-data at main · bluesky-social/proposals
Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.
github.com
gonna get this permissioned data protocol proposal out at some point within the first 250 years of this nation's founding
We just had another Atmospheric Group working group meeting. Doing something in #ATProto is like working on a group project with all the people that always had to do all the work for their group projects 😂 It's lovely to see how much folks put into it.
continuing to wrestle with the uri scheme for permissioned data i'm currently leaning back towards `at://`. get in here and let me know what you think! discourse.atprotocol.community/t/bringing-b...
Bringing back at://
The biggest complaint that I’ve heard about the permissioned data protocol design is that it feels like a totally separate thing from the existing public broadcast protocol. While many of the things t...
discourse.atprotocol.community
they're saying the entire AT Protocol is an elaborate ploy by @pfrazee.com and @dholms.at to trick innocent programmers into writing databases
they're calling it the ecosystem with the most nih syndrome databases in history
one benefit of the rise of ai writing is that i feel more personal liberty to let my voice come through in my writing. colloquialisms, asides, jokes, mixing of registers, etc
folks, don't use claude for slides. the style's immediately recognizable, it looks good, but it slides right over people's brains. in an era where sounding professional doesn't cost nothing to nobody, just some tokens, we're entirely free to be non-professional . embrace dreamcore wordart or smth