iiinova — where your digital self keeps evolving

hydrant now verifies CIDs by default! 🎊

yep. was on my list to open the issue but it's just need basic CID check with iroh-car like: tangled.org/microcosm.bl... jacquard firehose validation is i think also missing a length check: tangled.org/microcosm.bl...

000

fig (aka:[phil]) @bad-example.com · 16h

just tried to load a pull request page 🙃🙃

000

fig (aka:[phil]) @bad-example.com · 17h

er, maybe not for general consumers. but who knows.

010

fig (aka:[phil]) @bad-example.com · 19h

new gateway is in dns rotation. tomorrow will update the secondary, then remove the digitalocean one and close my account there.

010

Reposted by fig (aka:[phil])

Cat Hicks @grimalkina.bsky.social · 29/09/2026

Badasses can do badass public speaking and still be very comfy masking on the floor just in case you didn't know or get nervous about it and needed to see it 🫶

A selfie of Cat on an escalator wearing a maroon blazer and a white n95 mask. Behind her is a massive banner that reads work like never before, talent connect summit

3621

fig (aka:[phil]) @bad-example.com · 23h

restructured the repo a bit, took i think pretty much all suggestions, and split out the application profile and changelog bits. it's now a short spec! (yay!)

tangled.org

/star/v1-star at main · microcosm.blue/star

STreaming ARchive format: simpler, stricter, smaller than CARs for a subset of use-cases.

060

Reposted by fig (aka:[phil])

PolyWolf @wolf.girl.technology · 29/09/2026

New blog post: "Pining for Arc Downcasting in Rust" wolfgirl.dev/blog/2026-09-29-pining… #programming #rust

6243

fig (aka:[phil]) @bad-example.com · 29/09/2026

fixing ecosystem handling of CARs has begun! atcute stays undefeated in quality and maintenance ✨

2330

fig (aka:[phil]) @bad-example.com · 29/09/2026

a little delayed but got the groundwork in for the new gateway (and fixed a bunch on the way), should be able to get it live tomorrow went with linode (/akamai now) since they’ve been fine for me before and have a toronto location. (plz don’t tell me they also donates to omarchy or something)

160

fig (aka:[phil]) @bad-example.com · 28/09/2026

ah nice. if you ever need the maximally official-legit one, we could work something out for plc.wtf

0100

fig (aka:[phil]) @bad-example.com · 28/09/2026

fantastic update to start the week!

0170

Reposted by fig (aka:[phil])

AT Protocol Developers @atproto.com · 28/09/2026

The organization that governs the PLC Directory now formally exists as a registered Swiss Association and has taken the first steps towards being able to independently operate the directory. blog.plcred.org/3mwlphq42d227

blog.plcred.org

First steps of the PLC organization

213432

Reposted by fig (aka:[phil])

Filippo Valsorda @filippo.abyssdomain.expert · 28/09/2026

I'm excited to announce that the PLC Organization now has a statute! And a bank account! And a @standard.site publication! All the important stuff. The PLC Org is an independent Swiss Association meant to operate the PLC directory, which collects and distributes signed updates to atproto accounts.

blog.plcred.org

First steps of the PLC organization - Public Ledger of Credentials Organization

One year ago, Bluesky Social PBC announced their intention to facilitate the creation of an independent organization to operate the Public Ledger of Credenti…

425157

fig (aka:[phil]) @bad-example.com · 28/09/2026

adding the record’s sentry to that lthash state should give you the trusted hash back er,,,, no im wrong this is not right at all, you can “remove” any item from lthash state even if it’s not a real member of the set oops. oops oops.

120

fig (aka:[phil]) @bad-example.com · 28/09/2026

yeah, it’s a loss (for something i’ve come around to thinking worth it) for inclusion proofs though, *kindddda*, in a limited way? if you have a current lthash state that you trust for a repo (big if), then you can receive (lthash with record removed) along with the recordl

130

fig (aka:[phil]) @bad-example.com · 28/09/2026

(doodled a bit on public repo covering proofs and partial exports in star-lite, and found myself wishing i could insert non-ordered keys for gap CID stubs, so maybe working my way toward accepting relaxed key order at the format level)

010

Reposted by fig (aka:[phil])

Jaz @jaz.sh · 27/09/2026

Okay so I've built a new Atlas, this time it lets you explore the conversations on Bluesky over the past 7 days graphically. It should update every ~6 hours and help you navigate the information environment that exists on here. I've learned a LOT about what people do here today... atlas.jazco.dev

atlas.jazco.dev

Atlas

A living map of what Bluesky is talking about: the past week's conversations, grouped into topics and regions and rebuilt every six hours.

1161389407

fig (aka:[phil]) @bad-example.com · 27/09/2026

i still can’t believe feature unification works the way it does with cargo still some old crates i need to go back and clean up not to have switched behaviour

1120

fig (aka:[phil]) @bad-example.com · 27/09/2026

- still not closed to dropping lex order on keys but also not convinced yet - still a bit bothered by the fact that there isn’t a terminator to explicitly end a star-lite archive currently

120

fig (aka:[phil]) @bad-example.com · 27/09/2026

after a few sleeps: - dropping my objection to high limits for meta/key-length/value-size at the format level. seems like it would make it useful in more places, and maybe embedding whole archives in values could be neat. no reason a reader can’t expose a steam for reading values

120

fig (aka:[phil]) @bad-example.com · 26/09/2026

i think star probably embeds inside other formats better than the other way around.

010

fig (aka:[phil]) @bad-example.com · 26/09/2026

*parse error. i was trying to think of how to have the data section explicitly terminate, to make eg a car-like or key-less trailer section for blobs possible, living separate from the streamed kvs. only thing i came up with was a byte tag before every kv block. idk.

100

fig (aka:[phil]) @bad-example.com · 26/09/2026

strict lex key ordering does nice things for LSM and BTree and even MST data loading (though some of those systems allow custom comparators), and it makes duplicate keys a parse order which i like. could be app-layer enforced (even elements as k-v pairs could be hoisted up), i’m not closed to it

110

fig (aka:[phil]) @bad-example.com · 26/09/2026

i’m leaning a lot on iroh-car’s hard-coded 4MiB max block size a lot to justify this but i do kinda feel like a non-huge value size max keeps this as a streaming-oriented format. it also keeps it probably record-oriented and not great for blobs. very yes to bumping meta + key length limits

230

fig (aka:[phil]) @bad-example.com · 25/09/2026

only if you need that guaranteed 💅

120

fig (aka:[phil]) @bad-example.com · 25/09/2026

wheeee (i have nightmares about people depending on slingshot’s bi-di guarantee in some critical way(??) and then becoming vulnerable(???) after switching to use something else)

130

fig (aka:[phil]) @bad-example.com · 25/09/2026

yeah was thinking unspecified bytes for star vals and the application restricts further if they want. i think this is still easy-ish to do zero-copy with a generic streaming archive reader. not opposed to drisl-only vals or other restrictions in v1 if it’s an easier path for spaces though!

020

fig (aka:[phil]) @bad-example.com · 25/09/2026

ohhhhh my bad for apple-assuming! i think you’re good then! apple is the problem

210

fig (aka:[phil]) @bad-example.com · 25/09/2026

if it’s web notifications, they might stop getting delivered shortly. i went through a long cycle of disappointment with the spacedust notifications demo :( (or maybe apple fixed it?)

130

fig (aka:[phil]) @bad-example.com · 25/09/2026

commitment/integrity separate: og star-lite legacy that we should definitely drop!

020

fig (aka:[phil]) @bad-example.com · 25/09/2026

yeah i forget why i didnt want to use “S” for space, but “L” was meant to mean “space” just keyed off the hash type for some reason (i have zero attachment to this!) four magic bytes was to have public and space repos under the same version byte. also not attached, and that goes away if we do

150

fig (aka:[phil]) @bad-example.com · 25/09/2026

yeah interesting! could almost do like a CAR trailer bit heh hmm

010

fig (aka:[phil]) @bad-example.com · 25/09/2026

the separated-out commitment from the original STAR-lite was because the rest of the the commit is technically optional, because i thought i’d need to be able to archive sub-trees for hubble in hindsight, those could have just been another $type (and also i didn’t go that route with hubble)

140

fig (aka:[phil]) @bad-example.com · 25/09/2026

yeah i was reaching this same place after i pushed this! original star-lite was very coupled to public repos, but it’s a short move to make a separation so header metadata is an app-level concern, which feels nicer and more useful.

140

Reposted by fig (aka:[phil])

DASL @dasl.ing · 24/09/2026

Hey fam! We've been shaping a governance model for DASL, pretty lightweight, in line with the project's philosophy. You know what we'd love? We'd *love* to hear from you (yes, specifically *you* right there) about what you think about it. See: dasl.ing/governance.h...

dasl.ing

DASL: Governance of the DASL Project

The goal of the DASL Project is to develop content-addressing primitives and the technologies that build on them, with a view towards enabling unbundled software and protocol architect...

0176

fig (aka:[phil]) @bad-example.com · 24/09/2026

o no app name? (do ittttt, i’ll find another name for a thing)

120