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

ICYMI, Chatto is now Open Source and available for self-hosting. It's still early days, with Chatto currently sitting at 0.4, but it's a good version that we're happily using in production, so have at it! Here's our social media manager @hmans.dev with all the deets:

Chatto is now Open Source!

The snappiest chat application you've ever used is now available for self-hosting.

hmans.dev

physical editions

Existing communities on Discord shouldn't have to choose between the critical mass of members they've built up on the legacy platform versus the agency afforded to them by @roomy.space Introducing Roomy's first premium feature: Discord-Roomy bridging! 🌉 (free for non-profits)

A bridge beyond Discord

Millions of digital communities have already made a home for themselves on Discord, and we'd rather not force them to make a binary choice between the critical mass of members they've built up on Disc...

blog.muni.town

NEW BLOG! After closely following atproto permissioned data, my take: what if an "atproto repository" is the base thing and there's more than one way to sync it? Based on @ipv.sx's take and grounded in a real-world Streamplace use case: how do I make a video private, then public?

What is an atproto repository?

One repo, multiple sync methods

iameli.leaflet.pub

OK, I wrote up a whole blog post with some more detailed thoughts on this. Curious if anything here resonates with other folks. Thanks to @iame.li, @dholms.at, and @bnewbold.net for helpful pointers and discussions! pckt.blog/b/bits-of-en...

All data should be permissioned data - Bits of Entropy

My post with vague complaints about the proposal that made for permissioned data got a bit of attention. Daniel was kind enough to take the time to chat with me...

pckt.blog

Richard Barnes@ipv.sx · last mo.

@dholms.at - What is the right venue for discussion on this Permissioned Data proposal you wrote up. atp@ietf.org or something else? I think it is wrong in some pretty fundamental ways. Or at least the motivations are poorly articulated.

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

daniel holmgren 🫠@dholms.at · 2mo ago

gonna get this permissioned data protocol proposal out at some point within the first 250 years of this nation's founding

hey so, @roomy.space is now generally available for real-world use! 🥳 make atmospheric group spaces for friends & community, chat in real-time, progressively structure emergent topics into evergreen threads and cultivate enduring knowledge.

Roomy is generally available

the door's open

blog.roomy.space

"but where are all the bluesky instances?" i've heard this so many times that i wrote an explainer

There Are No Instances in atproto — overreacted

Like RSS and Google Reader.

overreacted.io

We built Comail so your mail gets delivered instead of buried in spam. Next: a personal inbox tied to your atproto account. We're holding the full launch until Permissioned Data lands, so your mail is genuinely yours, not just sitting on someone's server. Join the waitlist: comail.at/inbox

comail

Cooperative email for atproto. Small self-hosters pool reputation through a shared relay so mail from their own domain reliably reaches the inbox.

comail.at

i'm starting a diary on atmospheric login as a way to explore the topic in some depth. our login experience is how everyday folks will form their understanding of what the atmosphere even is—and the design space is super rich. the web may also have some tricks up its sleeve for us...

Atmospheric Login Diary 1: On the Button - the divy zone

Atmospheric login is one of those topics that maintains a constant hum of discussion in our ecosystem, and for good reason: it's how everyday folks make their w...

divyzone.pckt.blog

Cooperative email reputation on AT Proto. You bring your domain. We pool the deliverability. comail.at

what if we made boring auth even more boring-er? if you're following along on permissioned data, give this a read & let me know your thoughts: discourse.atprotocol.community/t/removing-t...

Removing the member list?

I read this comment & this post from @jesseplusplus.com and they got me thinking. What if we could make our boring auth even more boring-er? Basically, I don’t think the members list is actually nec...

discourse.atprotocol.community

auth: it's just a list! authorization tends to bring out Strong Opinions ™️ so we decided to try to keep it as simple as possible in the protocol & let the applications build higher-level abstractions give it a read & let me know your thoughts!

Permissioned Data Diary 6: Boring Auth

In which we resist the temptation to invent a clever authorization model & pick the boring one instead.

dholms.leaflet.pub

Announcing the Streamplace VOD closed beta! We're ready for you to start hacking on it, but we're going to take things real slow to start. Check out the post for how to join the waitlist!

How Streamplace Works: VOD (Closed Beta)

blog.stream.place

Remote attestation is a heavily underdiscussed threat to computing freedom. People often mistakenly dismiss it with "I will run my own fork (of the OS or browser) / Magisk", not understanding that with hardware attestation, you're literally unable to 1/

GrapheneOS@grapheneos.org · 3mo ago

Apple and Google are gradually expanding their use of hardware-based attestation. They're convincing a growing number of services to adopt it. Google's Play Integrity API and Apple's App Attest API are very similar. Apple brought it to the web via Privacy Pass, which Google intends on doing too.

new data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)

Permissioned Data Diary 5: What’s in a Name?

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.

dholms.leaflet.pub

2nd chapter of Go! Go! Gris! is out now! ⭐️ Read it on my website for a better experience (and bonus content): gogogris.com/read Have fun reading! (1/5)

Modern DRAM is based on a brilliant design from IBM. But, we're still paying for a latency penalty that's existed since the 60s! In this video, I'm introducing my research project (Tailslayer) that immensely reduces p99.99 latency on traditional RAM!

VERY rough cut of VODS, these all need trimming, but the rough export looks like this: pdsls.dev/at://did:plc... I'm gonna go to sleep, more to come in the morning, but a cheeky link for the alpha testers because I love you all. Hey look, an HLS playlist! 😉 vod-beta.stream.place/xrpc/place.s...

We've got an updated protocol roadmap out, covering the next few months. Look forward to seeing folks at AtmosphereConf later this week!

AT Protocol Roadmap (Spring 2026) - AT Protocol

Updates to the AT Protocol roadmap, including Permissioned Data and Account Experience.

atproto.com

here it is folks! lots of details to still nail down, but this is roughly where our heads are at for the design of a permissioned data protocol give it a read and let me know your thoughts!

Permissioned Data Diary 4: The Big Picture

A special edition of the data diary that sketches out the rough shape of where we're heading.

dholms.leaflet.pub

continuing to build up our permissioned data protocol! this one asks what a bucket actually is and where the data that constitutes a bucket is stored. it argues for maintaining the atproto ethos in the permissioned data protocol as always, looking forward to hearing your thoughts!

Permissioned Data Diary 3: Your Bucket, My Data

The third in a series of posts building up a solution to permissioned data on atproto. We look at two different models for where buckets live and why the simpler-looking one doesn’t work out.

dholms.leaflet.pub

After years of work, the first chapter of my slice-of-life, gag manga Go! Go! Gris! is now available! ✨ Read it for free here: gogogris.com/read/chapter-1 Or check out some pages below 👇 (1/6)

Introducing Barazo: community forums where members own their data, by @gui.do gui.do/post/introdu...

Barazo: community forums where members own their data

I'm building an open source forum platform on the AT Protocol. Members log in with their Bluesky account, posts live on their own data server, and reputation follows them across communities.

gui.do

soft announcement for... at://news – collectively-sourced, weather reports of the atmosphere. Anyone can help contribute on the open @semble.so collection: semble.so/profile/chri... @leaflet.pub publication (starting end of this week): at-news.leaflet.pub

at://news (by 𝕮) — Semble

Collectively-sourced updates from across the atmosphere.

semble.so

𝕮@chrisshank.com · 6mo ago

Maybe the more interesting question is how this can be sourced collectively rather than relying on the good will of a single individual? Can we dogfood atproto to make this happen? (e.g. @semble.so open collections) This is a great example for the need of collective sensemaking.

I'm finally ready to show off the thing I've been working on: atBB (pre-alpha)! It's a forum platform built on top of atproto. I wrote up some thoughts about why I am interested in building forums: pckt.blog/b/mal-s-musi... 1/2

What the World Needs Now is Forums Sweet Forums - Mal’s Musings

and other thoughts from a forums purveyorI was seven years old when I got my first video game console. It was Christmas, and I actually got two! A GameBoy Po...

pckt.blog

Hey #GameDev and #ATProto! I'm working on tools to decentralize the ownership and management of video games by putting them (or at least their data... for now) on ATProto! I'm looking for feedback, so if you have any interest I'd love to hear your thoughts. ♥️ 🎮 ♥️

Introducing The Pentaract: A Comprehensive Set of Video Game Lexicons for ATProto

1. Dev mode I wanted to be able to iterate on my early lexicons, and I didn’t know how that would impact other lexicons in lexicon.community. TBF I didn’t do much research into it either, but I figure...

discourse.atprotocol.community

see: discourse.atprotocol.community/t/media-pds-... Basically it proposes that large media objects shouldn't be stored in your repo, but instead by a dedicated service that can correctly handle billing and distribution.

Media PDS / Service

So recently there’s been some discussion about video on demand and how that may work for AT Protocol. I’ve been thinking a bit about this topic recently, since solving video and larger media files wou...

discourse.atprotocol.community

full-network atproto relay on a $4.20/mo VPS demo.tiny.hose.cam still getting connected to PDSs, we'll see how long it survives...