Kostis Maninakis 妙祇

In the Phaedrus, which dates to the fourth century B.C., Socrates recounts a myth in which the Egyptian god Thoth offers King Thamus the gift of writing—“a recipe for memory and for wisdom.” Thamus is unmoved. Writing, he warns, will do the opposite:

Ah yes, genuinely beautiful. A Grove's rad clone: the network lane trickling in at the top, pack-io grinding through the middle, the eight pack-resolver workers firing their staggered shard bursts, the SharedWorker's verifying, telemetry bars. 👨‍🍳👌

At some point I need to write a blog post titled "Performance As the Default". Every web experience needs it to feel engaging, smooth and foster a reassuring feeling when using a web app. Performance must be a requirement hitching along every new feature, not an afterthought.

Totally usable, @AnthropicAI

@radicle Favorite detail: some nodes announce only over Tor. And on the flip side, ~120 repos currently live on a single node. Seed something obscure today and you're literally the backup.

The average public repo on the @radicle network is replicated on ~13 independent nodes, spread across 28 countries. No hosting company, no single point of failure. It's just how the protocol works. Measured it from a live seed and built a dashboard: stats.radicle.at

Yo, how did I not know about `git history fixup` and `git history rename`? lalitm.com/post/git-histo…

0m12s

0m18s - 0m27s

Honestly, I came close to giving up. 66h of gruel grind to get repo cloning to work failing -> failing less -> tiny repo clones -> disaster after disaster then suddenly one hour ago -> 10m47s for heartwood then 10 minutes later -> 4m27s 🚀 I'm not done.

If I only knew that one can't spawn Web Worker from inside a SharedWorker I'd have a couple of days of my life back... Hey, at least I won't ever forget that now. We learned something. 🌈

@bordumbb @Ableton The loops are fruity 🍓

@maninak_ Reminds me of a really complex track produced on @Ableton 😂

You know shit's about to go down then the profiler is out.

And that's not even half of it...

Sure let's reimplement half of heartwood in TS. Sure let's run it in a Web Worker, signing with radicle-crypto wasm, interop'ed with a typed RCP, storing on a tab-shared OPFS protected by write locks, a SharedWorker and electioning to handle co-running tabs with updated workers.

Grove's tech and architecture is boggling my mind. So many moving parts that reach so deep.

Having a complex web app fully work offline is hard. Setting up Content Security Policy a complex web app is hard. Fulfilling both is harder than the sum of its parts and for Grove I must have both.

That's a damn fine looking bundle you got there, babe.

@emil_priver LGTM👍

just wanted to share some ai slop