bryan newbold
@bnewbold.net
oscilloscopes, cycling, snow, big cities, wiki. I like speculating about found objects.
protocol engineer @bsky.app. formerly archive.org
elsewhere: bnewbold.net / @bnewbold@social.coop
protocol engineer @bsky.app. formerly archive.org
elsewhere: bnewbold.net / @bnewbold@social.coop
Pinned
bryan newbold
@bnewbold.net
· Dec 19
M̴̥̋r̶͈̄.̶̧̚ ̶͙̀W̵͇͝à̶̯ţ̶̾š̸̯ȍ̸̩n̸̪͘ ̴̨͊-̴͇́ ̷̞̈́c̸̹̈́ō̴ͅm̴̗̆e̷̮̽ ̶̯̚h̷̡̎ḛ̷͒r̴̞̈́e̶̦̐ ̵̲̑-̷̬͠ ̷̧̑I̸͚͋ ̴̹̊w̴͕̎ȃ̷̭ǹ̴̟ť̶͈ ̷̱̂t̷̲̓ó̸̱ ̶̹́ș̸͋e̸̹͗e̷̾ͅ ̸̻͌ỵ̵́ö̶̯́u̷̳͝
Soft launching my Keybase on atproto alpha: @keytrace.dev
Basically the identity verification system from keybase/keyoxide but storing the identity claims on your registry and signing them based on keys in mine.
It is not focused on PGP, but on making it possible for social apps to handle identity
Basically the identity verification system from keybase/keyoxide but storing the identity claims on your registry and signing them based on keys in mine.
It is not focused on PGP, but on making it possible for social apps to handle identity
February 9, 2026 at 11:16 PM
bsky API bump due to a bad deploy. rolling back and should resolve in a couple minutes...
February 9, 2026 at 10:46 PM
bsky API bump due to a bad deploy. rolling back and should resolve in a couple minutes...
Reposted by bryan newbold
In 2026, @bsky.app is focused on what’s next for open social: bringing together users for conversations around live events, creator and platform monetization, and private state, giving users truly private data while preserving ownership and portability at the protocol level.
February 9, 2026 at 6:46 PM
In 2026, @bsky.app is focused on what’s next for open social: bringing together users for conversations around live events, creator and platform monetization, and private state, giving users truly private data while preserving ownership and portability at the protocol level.
Reposted by bryan newbold
In 2025, PL portfolio company @bsky.app grew from 25M to 40M+ users and shipped major progress on verification and decentralization, with 270K+ users self-verifying and 2,000+ community-run servers live - moving core infrastructure forward at scale.
February 9, 2026 at 3:31 PM
In 2025, PL portfolio company @bsky.app grew from 25M to 40M+ users and shipped major progress on verification and decentralization, with 270K+ users self-verifying and 2,000+ community-run servers live - moving core infrastructure forward at scale.
pretty huge spike in atproto firehose during Bad Bunny superbowl half-time show; much larger than overall superbowl coverage.
also more 2x API request rate on bsky services
also more 2x API request rate on bsky services
February 9, 2026 at 1:51 AM
pretty huge spike in atproto firehose during Bad Bunny superbowl half-time show; much larger than overall superbowl coverage.
also more 2x API request rate on bsky services
also more 2x API request rate on bsky services
Reposted by bryan newbold
when you get the chip to the physical layer 😋
February 8, 2026 at 6:37 AM
when you get the chip to the physical layer 😋
what are the seven layers of dip
February 8, 2026 at 5:49 AM
what are the seven layers of dip
finally gave this a deeper read and it is great.
super relevant when thinking about permissioned access data in atproto, but a lot of this applies to fully-public spaces as well.
endorse "organizer" as terminology
super relevant when thinking about permissioned access data in atproto, but a lot of this applies to fully-public spaces as well.
endorse "organizer" as terminology
Been mulling over @bnewbold.net's recent post on community spaces and atproto's next frontiers. I wrote about why building for organizers (not just users) might be the key to making it all work.
Building for Organizers - The People Layer
The most enduring social networks aren’t the prettiest or the most addictive – it’s the ones that empower organizers.
mosh.leaflet.pub
February 8, 2026 at 5:04 AM
finally gave this a deeper read and it is great.
super relevant when thinking about permissioned access data in atproto, but a lot of this applies to fully-public spaces as well.
endorse "organizer" as terminology
super relevant when thinking about permissioned access data in atproto, but a lot of this applies to fully-public spaces as well.
endorse "organizer" as terminology
this didn't come out worded good:
I meant that folks should *increase* the account limit for the eurosky.social PDS
I meant that folks should *increase* the account limit for the eurosky.social PDS
if you run an atproto relay, it's worth giving this PDS instance an account limit. the hostname is 'eurosky.social'
We sent the first ~100 invites for @eurosky.social. We might send some more on the weekend, then start sending 100s daily if everything holds up well.
February 7, 2026 at 12:30 AM
this didn't come out worded good:
I meant that folks should *increase* the account limit for the eurosky.social PDS
I meant that folks should *increase* the account limit for the eurosky.social PDS
Reposted by bryan newbold
There is as giant dancing coffee press!
February 6, 2026 at 7:25 PM
There is as giant dancing coffee press!
Reposted by bryan newbold
THERE IS ANOTHER SOLUTION TO THE ATPROTO CAPITALIZATION DEBATE BUT I PERSONALLY DO NOT LIKE IT VERY MUCH
February 6, 2026 at 11:30 PM
THERE IS ANOTHER SOLUTION TO THE ATPROTO CAPITALIZATION DEBATE BUT I PERSONALLY DO NOT LIKE IT VERY MUCH
if you run an atproto relay, it's worth giving this PDS instance an account limit. the hostname is 'eurosky.social'
We sent the first ~100 invites for @eurosky.social. We might send some more on the weekend, then start sending 100s daily if everything holds up well.
February 6, 2026 at 11:28 PM
if you run an atproto relay, it's worth giving this PDS instance an account limit. the hostname is 'eurosky.social'
the simple solution to the atproto capitalization debate is to not capitalize any other words in the sentence either
February 6, 2026 at 11:23 PM
the simple solution to the atproto capitalization debate is to not capitalize any other words in the sentence either
huh that is a pretty cool reuse of network data
this one is pretty good
February 6, 2026 at 11:12 PM
huh that is a pretty cool reuse of network data
Reposted by bryan newbold
Here’s a quick recap of yesterday’s Summit. The @greens-efa.eu & @alexandrageese.bsky.social had invited myself and several other technologists, including @robin.berjon.com, to speak in the EU parliament as part of the „EU Tech Stars Summit“ www.greens-efa.eu/en/article/event/eu-tech-stars-summit.
February 6, 2026 at 8:18 PM
Here’s a quick recap of yesterday’s Summit. The @greens-efa.eu & @alexandrageese.bsky.social had invited myself and several other technologists, including @robin.berjon.com, to speak in the EU parliament as part of the „EU Tech Stars Summit“ www.greens-efa.eu/en/article/event/eu-tech-stars-summit.
great to see folks building new and meaningful social features on their own timelines. especially guided by community feedback and prioritization.
the future of this atmosphere thing should be shaped by many hands
the future of this atmosphere thing should be shaped by many hands
February 6, 2026 at 10:38 PM
great to see folks building new and meaningful social features on their own timelines. especially guided by community feedback and prioritization.
the future of this atmosphere thing should be shaped by many hands
the future of this atmosphere thing should be shaped by many hands
Reposted by bryan newbold
The other goal of going to museums is to build a collection of eyeballs
February 6, 2026 at 7:41 PM
The other goal of going to museums is to build a collection of eyeballs
updated the atproto specs to reference dasl.ing, a simpler variation/subset of IPLD.
hope this is more accessible for folks digging in to atproto-from-scratch implementations. the core primitives in IPLD (DAG-CBOR, CIDs, CAR) are great, but the fully flexible/general system can be overwhelming
hope this is more accessible for folks digging in to atproto-from-scratch implementations. the core primitives in IPLD (DAG-CBOR, CIDs, CAR) are great, but the fully flexible/general system can be overwhelming
specs: update many IPLD references to DASL/DRISL references by bnewbold · Pull Request #496 · bluesky-social/atproto-website
The DASL specifications are simpler and align with what we use in atproto.
This updates most references to the IPLD docs to reference the DASL docs instead. It still discusses the lineage in some p...
github.com
February 6, 2026 at 8:14 PM
updated the atproto specs to reference dasl.ing, a simpler variation/subset of IPLD.
hope this is more accessible for folks digging in to atproto-from-scratch implementations. the core primitives in IPLD (DAG-CBOR, CIDs, CAR) are great, but the fully flexible/general system can be overwhelming
hope this is more accessible for folks digging in to atproto-from-scratch implementations. the core primitives in IPLD (DAG-CBOR, CIDs, CAR) are great, but the fully flexible/general system can be overwhelming
some thoughts on how to implement public community spaces in atproto.
I think it is important for us to stretch what the protocol can do; and there are some great opportunities for self-hosting, moderation, customization, etc
I think it is important for us to stretch what the protocol can do; and there are some great opportunities for self-hosting, moderation, customization, etc
February 5, 2026 at 2:50 AM
some thoughts on how to implement public community spaces in atproto.
I think it is important for us to stretch what the protocol can do; and there are some great opportunities for self-hosting, moderation, customization, etc
I think it is important for us to stretch what the protocol can do; and there are some great opportunities for self-hosting, moderation, customization, etc
it's pizza time
Community Spaces on AT Protocol
Scaled-down design patterns
bnewbold.leaflet.pub
February 5, 2026 at 2:37 AM
it's pizza time
go devs using indigo:
going to push out some more small breaking API changes. in this case, returning pointers from constructors to avoid accidental copies, and improve ergonomics.
feels like we are getting close to a milestone where we start to formalize SDK changes (git tags, etc)
going to push out some more small breaking API changes. in this case, returning pointers from constructors to avoid accidental copies, and improve ergonomics.
feels like we are getting close to a milestone where we start to formalize SDK changes (git tags, etc)
atproto: some constructors return uncopyable values · Issue #1313 · bluesky-social/indigo
As originally observed here #1306, atproto/identity.NewCacheDirectory returns CacheDirectory. The issue is CacheDirectory contains several sync.Map fields which are marked nocopy. In practice all u...
github.com
February 3, 2026 at 8:13 PM
go devs using indigo:
going to push out some more small breaking API changes. in this case, returning pointers from constructors to avoid accidental copies, and improve ergonomics.
feels like we are getting close to a milestone where we start to formalize SDK changes (git tags, etc)
going to push out some more small breaking API changes. in this case, returning pointers from constructors to avoid accidental copies, and improve ergonomics.
feels like we are getting close to a milestone where we start to formalize SDK changes (git tags, etc)
Reposted by bryan newbold
every so often, when the conditions are just right, the veil between two different worlds grows thin.
February 2, 2026 at 7:03 PM
every so often, when the conditions are just right, the veil between two different worlds grows thin.
2026 word of the year is going to be "psychosis"
February 3, 2026 at 3:44 AM
2026 word of the year is going to be "psychosis"