Michiel de Jong

@michielbdejong.com

Working on personal data stores and decentralisation with Unhosted, remoteStorage, Solid Pods, OAuth, OpenAPI extensions, and Federated Sharing. Freshly diving into the Atmosphere and liking what I see so far!

Me: how do Atproto firehose seqs relate to repo commit revs? Claude: "across accounts your question doesn't even typecheck" Poetic in a nerdy way. Reminds me of when I used to write code myself.

has it been enough time since the last time? YUP, repost, follow all, you know the drill! for anyone new to the atmosphere and specifically the atproto dev side of things, welcome home.

Post nicht verfügbar.

While reading RFC 9518 "Centralization, Decentralization, and Internet Standards" by @mnot.net I agree that equal opportunities for human agents is an egalitarian goal in itself. But it also suddenly occurred to me the moral design principles for AI and automated companies may be totally different.

Product categories in the software industry are falling like dominoes against the competition of one-shot. Nobody I know has used Keynote or Powerpoint anymore since last month! Dashboards become part of the harness. Which software product do you think people will still use in 5 years from now?

the increasingly-obvious precarity of even "skilled" or "white collar" labor erodes the plausibility of the narrative that material security is in reach for the sufficiently-diligent & part of me (maybe naively) assumes that narrative is actually important societal glue for the united states

🧾 Introducing npm.tax Estimate the probability of being impacted by a breach in your npm supply chain. Adjust the knobs to see how slimming your node_modules lowers your risk. Look up a package to see its own risk profile, then share the report, e.g. npm.tax?direct=59&tr.... What's your npm tax?

npm.tax: npm supply-chain risk explorer

Explore how your code, npm dependency count, breach probability, and time horizon combine into cumulative supply-chain risk.

npm.tax

I wrote up my talk at @localfirstconf.com as a blogpost The AT Protocol is a high-scale network by design. It works by codifying proven architectures into a protocol. If you've ever used kafka to connect some backend services, then you basically know how atproto works.

Starting from scale in the design of the AT Protocol

Bluesky was founded in 2022 to produce a protocol which Twitter could adopt. The product goals changed, but the requirements didn't.

pfrazee.leaflet.pub

Freshly diving into the Atmosphere. :) I just updated my handle from @michielbdejong.bsky.social to @michielbdejong.com and it Just Worked, even easier than on GitHub Pages. This is the sort of detail that we always talk about but you rarely see it actually implemented. Liking what I see so far! <3