I'd like to announce github.com/MichaelMure/..., a go native @automerge.org implementation. It doesn't have all the bells and whistles of the rust version (no sync protocol/repos), but has the core CRDT logic and should be reasonably fast. It produces byte identical data, and has the same license.

I feel like there is a gradient of software engineer going from very controlling of the code structure, to more or less appending features however it comes up. Coding assistants are going to magnify this gradient like never before.

A tool that I wanted to have for a looong time: github.com/MichaelMure/...

One major distinction between software and woodworking: when you are tired/frustrated, it's way more important to stop for one of those. A computer can't take your hands but those machines definitely can.

Do you also think that the go crypto packages are a bit hard to use? What about my attempt at a thin ergonomic layer? github.com/MetaMask/go-... Details and rationals in the Readme.

I'm opening a new personal tech tree! Today, some CAD for a shoji (japanese sliding door). It's all parametric so I can adjust the global parameters (dimensions, kumiko counts, ...) and all the cuts, mortises, tenons are recomputed. Now the questions will be: can I make it for real?

For fun and giggles, I wrote an implementation of IBLTs, for set reconciliation: github.com/MichaelMure/... Feedback welcome.

Hey @expede.wtf @b5.bsky.social, I enjoyed the Rateless IBLT reconciliation paper. Any suggestion for a mind-bending christmas paper read?

I wrote maybe half of the decoding of an #automerge document in go, as an exercice in performance and database-like internals (column storage, RLE..). It's sitting in a private repo until I come back to it, but happy to share with a foss license if there is interest. Just ping me.

Another new thing: github.com/MetaMask/go-... It's a fast and simple (battery included) Decentralized Identifier implementation in go. Currently it supports did:key, did:web and did:plc.

It's time to announce properly some new things! I just published v1.0.0 of github.com/ucan-wg/go-v..., the multiformat for cryptographic signatures. It's notably used in UCAN.

Recursive hierarchical explainer for LLMs: starts with a high level concept ("explain database") and get a breakdown. From there you get an UX to expand as deep as you like on sub-topics ("LSM trees") in various ways: more explainers, implementation, connective question... Does that exists?

Random thought: full text search engine use word transformation, canonicalisation to map the input text to some internal index (my understanding). Could a LLM vector space be used instead? That would remove the need for the transformations, and make it work cross-language.

Don't tell anyone, but my secret endeavor is to one day teach something to @expede.wtf instead of being schooled every time (which I enjoy dearly).

> Excited to try this. > This is incredibly cool. I love seeing local first software starting to make a comeback. > I've been yelling 'omg why doesn't someone build [...] for YEARS. This is wildly exciting. More than coffee, those are what feed an open source project.

Hehe, git-bug making some waves again on hacker news: news.ycombinator.com/item?id=4397...

Any opinions around about what is or could be a good distributed social graph (aka: I know and can find other people) with reputation and DIDs? @bmann.ca maybe?

I am quite excited that our brand-new module "P79: Cryptography and Protocol Engineering" has its first lecture today! @martin.kleppmann.com and I designed the course to bridge the gap between mathematical ideas and the challenge of implementing secure cryptography in the real world. @cst.cam.ac.uk

It's a somewhat simple thing in the end, but I wrote my first ever proper spec, for a UCAN token container: github.com/ucan-wg/go-u... Thanks a lot to @hugomrdias.bsky.social and @expede.wtf for the help!