LightNews — News, ranked by scholars

David Buchanan

@retr0.id

oh you use atproto? name every nsid

October 29, 2024 at 2:22 PM

Eli Mallon

@iame.li

I know this syntax isn't finalized yet but there's an elegance in going from `at://did/nsid/key` to `ats://did/nsid/key/did/nsid/key`

atproto permissioned data: atproto twice as hard as before

Eli Mallon @iame.li · Mar 21

Then the last three parts of the URL are just normal atproto: user, collection, tid. This gives us:

ats://did:plc:2zmxikig2sj7gqaezl5gntae/place.stream.webhookSpace/self/did:plc:2zmxikig2sj7gqaezl5gntae/place.stream.webhook/3jzfcijpj2z2a

Anything I missed?

March 22, 2026 at 12:46 AM

dan

@danabra.mov

first pieces of @inlay.at are now open source at tangled.org/danabra.mov/...

🔮 Inlay "browser" prototype (hono+htmx): inlay-proto.up.railway.app

📝 Inlay ProfilePage component from the above demo: pdsls.dev/at://did:plc...

📜 Tests describing the Inlay rendering model: tangled.org/danabra.mov/...

// ============================================================================
// inlay render — specification tests
// ============================================================================
//
// inlay is a UI component system on the AT Protocol.
//
// Elements reference components by NSID — <com.example.PostCard uri="...">
// is an element whose type is the NSID com.example.PostCard. An NSID is
// just a name; it says nothing about where the implementation lives.
//
// A pack (at.inlay.pack) maps NSIDs to concrete implementations. Each
// entry points an NSID at a component record URI (at://did/at.inlay.component/rkey),
// so the same NSID can resolve to different implementations depending on context.
//
// A component record (at.inlay.component) defines what happens when the
// element is rendered. It has one of three body kinds:
//
// - no body → a primitive; the host knows how to render this
// - bodyTemplate → a stored element tree with Binding placeholders
// - bodyExternal → an XRPC endpoint that returns an element tree
//
// Resolution algorithm:
//
// 1. Start with an element like <com.example.PostCard uri="at://...">.
// 2. Scan imported packs for a component that implements com.example.PostCard.
// 3. Resolve the component record and switch based on body kind:
// a. no body → done, it's a primitive.
// b. bodyTemplate → substitute Binding placeholders with the
// element's props (and optionally a fetched record when the
// component declares that it's a "view" for some records).
// c. bodyExternal → call the XRPC service, passing props.
// Children can be passed too, but they're opaque to the callee.
// 4. Recurse into the expanded tree until everything resolves to
// primitives. This can be done to completion or (better) streamingly.

February 25, 2026 at 5:30 AM

fig (aka:[phil])

@bad-example.com

oh, a real backlinks issue with tangled vouches: opposite meanings in the same NSID. the "kind" field is "vouch" or "denounce".

separate NSID convention (like "com.app.graph.follow" / "com.app.graph.block") are better for generic indexes like constellation, that you query by link-source.

May 2, 2026 at 3:15 PM

hailey

@hailey.at

the nsid would suck anyway

February 28, 2025 at 3:42 AM

bryan newbold

@bnewbold.net

atproto devs!

this is a small one: we are updating the NSID syntax to allow non-leading digits in the final 'name' segment. this makes 'com.example.postV2' a valid NSID (it wasn't before).

this will take a while to roll out everywhere, and will be "broken" until it works everywhere...

NSID: allow digits in 'name' segment by bnewbold · Pull Request #402 · bluesky-social/atproto-website

Closes: #391 indigo (golang) PR: bluesky-social/indigo#981 atproto (typescript) PR: bluesky-social/atproto#3633 interop tests PR: bluesky-social/atproto-interop-tests#3

github.com

March 12, 2025 at 12:58 AM

Scoiattolo

@scarnecchia.net

One thing I like to do is to check clickhouse to see what lexicons have been the most active over the last two months. That's how you learn that a Japanese study app (studynext.app) is the second most active Atproto application right now.

A markdown table showing the current top 25 top-level NSIDs:

A dark-themed table ranking namespace ID roots by activity. The columns are “#,” “nsid root,” “events,” “distinct lexicons,” and “share.”

Visible rows:

| # | nsid root | events | distinct lexicons | share |
| -- | -------------------------- | ----------: | ----------------: | -----: |
| 1 | app.bsky | 338,480,884 | 24 | 96.29% |
| 2 | app.studynext | 2,156,118 | 23 | 0.61% |
| 3 | cx.vmx | 1,151,099 | 2 | 0.33% |
| 4 | site.standard | 1,113,465 | 5 | 0.32% |
| 11 | link.bridgebeats | 392,316 | 1 | 0.11% |
| 14 | community.lexicon | 245,161 | 16 | 0.07% |
| 15 | games.gamesgamesgamesgames | 244,932 | 11 | 0.07% |
| 16 | team.sigint | 156,514 | 3 | 0.04% |
| 17 | net.anisota | 131,988 | 34 | 0.04% |
| 18 | org.titlegraph | 105,841 | 6 | 0.03% |
| 19 | is.currents | 96,942 | 5 | 0.03% |
| 20 | com.nsc | 96,855 | 1 | 0.03% |
| 21 | org.hypercerts | 92,294 | 20 | 0.03% |
| 22 | ai.afrilingua | 86,710 | 15 | 0.02% |
| 23 | com.puzzmo | 83,180 | 3 | 0.02% |
| 24 | jp.5leaf | 66,824 | 1 | 0.02% |
| 25 | app.qte | 53,658 | 14 | 0.02% |

July 14, 2026 at 12:03 PM

fig (aka:[phil])

@bad-example.com

(you can query it for recent records by collection nsid. *any* nsid. and it collects total record and unique user statistics about every nsid over time)

May 7, 2025 at 10:12 PM

Ms Boba (rebuilding community era)

@essentialrandom.bsky.social

What!?! Since when!?!

If an endpoint is experimental, unstable, or not intended for interoperability, indicate that in the NSID name
eg, include .temp. or .unspecced. in the NSID hierarchy

September 14, 2026 at 9:06 PM

Lexicon Garden

@lexicon.garden

👀 Beautiful

lexicon.garden/nsid/site.st...

January 9, 2026 at 6:12 PM

dan

@danabra.mov

i'm pretty excited about this — with HTTP imports, you get typed lexicon codegen from nsid directly in your @val.town vals

dan @danabra.mov · Feb 4

demo www.val.town/x/gaearon/le...

i think this is very cool actually

import * as Post from "https://lex.val.run/app.bsky.feed.post.ts";

const examplePost: Post.Main = {
"$type": "app.bsky.feed.post",
text: "Hello from lex.val.run!",
createdAt: new Date().toISOString(),
};

export default async function (req: Request): Promise<Response> {
const result = Post.$safeParse(examplePost);
return Response.json({
valid: result.success,
lexicon: Post.$nsid,
example: examplePost,
});
}

February 4, 2026 at 6:11 PM

bryan newbold

@bnewbold.net

probably need to write tutorial on how to publish Lexicons with the new lex resolution stuff. here is the short version!

say you have new lexicon record type with NSID 'dev.example.drink.tea', and you control the 'example.dev' domain name

February 20, 2025 at 8:32 PM

dan

@danabra.mov

ok this is looking way better than what i had before

component collection with interface nsid as rkey

March 27, 2026 at 7:11 AM

Eli Mallon

@iame.li

#atproto: let's do personal-private data right now

second repo adjacent to the public one with the same semantics but not published

oauth scopes for read/write access to various NSID namespaces

ezpz

October 22, 2025 at 5:00 AM

Bailey Townsend 🦀

@pds.dad

every song i've listen to since about fridayish has been tracked on my atproto repo btw

Picture of PDIs showing the NSID fm.teal.alpha.feed.play and 521 records

May 22, 2025 at 2:04 AM

Eric

@edavis.dev

NSIDDD: NSID driven development

Eric @edavis.dev · Jan 11

heartbreaking: I thought of a really cool NSID but the domain is taken

January 11, 2026 at 5:12 PM

Nelind

@nel.pet

yayyy

pub const NSID: Nsid = unsafe { Nsid::from_static_unchecked("com.atproto.identity.resolveHandle") };

Nelind @nel.pet · Oct 19

aaaah no!! const_box was abandoned :( how am i gonna construct a Box<str> wrapping newtype in const context then ...

ig i could make them wrap ByteStr instead ... acquiring a new dep just for const contruction is annoying tho ... but ig it works. i do really want that const contruction for NSIDs

October 19, 2025 at 7:33 PM

fig (aka:[phil])

@bad-example.com

Launching: 🛸 UFOs, a global ATProto lexicon explorer! 🛸

Find sample records for every collection NSID ever published!

+timeseries stats, unique user counts, and more!

🛸 App: ufos.microcosm.blue
👾 API: ufos-api.microcosm.blue

🛸 UFOs: Explore atproto lexicons

Sample records and timeseries statistics for *every* collection seen in the ATmosphere.

ufos.microcosm.blue

June 12, 2025 at 7:23 PM

fig (aka:[phil])

@bad-example.com

it's future me's problem now

some rust code that i'm very sure i will not understand when i come back to it later. it has triple nested `.map`.

// with apologies
let mut iters: Vec<_> = iters
.into_iter()
.map(|it| it
.map(|bla| bla.map(|(nsid, v)| (Child::from_prefix(&nsid, &prefix), v)))
.peekable())
.collect();

June 4, 2025 at 9:11 PM

fig (aka:[phil])

@bad-example.com

Constellation "link sources" are currently(ish):

`<NSID>:<RecordPath>`
like "app.bsky.feed.like:subject"

soooo
`<NSID>^rkey`
like "sh.tangled.graph.vouch^rkey"?

or just "sh.tangled.graph.vouch^"?

May 2, 2026 at 3:22 PM