Today I released git-bug v0.11 with a brand new webUI and a fully featured code browser. This is a major step in the way of having the webUI be a public portal accepting external contribution and code review support. Release notes: github.com/git-bug/git-...

New thing I made: Benchspotter - github.com/MichaelMure/... It's a companion app to do performance work in go. It keeps track of benchmark/profile results and their full context, and gives you friendly and high level tools to exploit the data.

GitHub - MichaelMure/benchspotter: A developper assistant for go benchmarking and performance

A developper assistant for go benchmarking and performance - MichaelMure/benchspotter

github.com

So, 15 years ago in engineering school, a friend of mine made a Github account with a yopmail email. Those are public mailboxes you can use for throwaway account in annoying services. He used that to work on a common project. Today, Github action is disabled on my account for abuse.

I had a little fun after I realized you can track every single heap allocation and GC done by the go runtime, in real time: github.com/MichaelMure/...

I got some praise for my obscure github.com/MichaelMure/... tool from the official GitKraken account on reddit. If that feature is coming there, you know why ;-)

I just realized ... I want to use normal git signing keys so that git-bug naturally mesh with a normal dev worflow. But I can also publish those keys in the did:plc registry to have a centralized (vs one copy per repo) identity handling, with a key log, local key signing and everything!

I wish Github would expose each user's log of public key, not just the currently valid ones. Then I could anchor signed operations of a CRDT (git-bug) on those. DID:PLC does expose that, but what's the story for locally managed keys these days?

Ho hey, git-bug now has a brand new webui, complete with a code brower (ie, premise for pull-request support). As usual, everything is local and very fast.

ho hey, git-bug now has a formal spec: github.com/git-bug/git-...

git-bug/doc/spec at trunk · git-bug/git-bug

Distributed, offline-first bug tracker embedded in git - git-bug/git-bug

github.com

I wonder if having LLM personal assistants (safe bet at this point) will push businesses to expose standardized APIs: book an appointment or restaurant, product search ... Hopefully those don't get centralized into the same usual giants ...

I wonder if I'm doing annoyance driven development because it's the right thing to do or because I'm annoyed.

I wonder, if (big if) producing code get commoditized, the dimension that's left is the values of the author.

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/...

GitHub - MichaelMure/git-ownership: A tool to visualize code ownership over time, from the git history

A tool to visualize code ownership over time, from the git history - MichaelMure/git-ownership

github.com

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.

GitHub - MichaelMure/go-iblite: Invertible Bloom Lookup Tables in go

Invertible Bloom Lookup Tables in go. Contribute to MichaelMure/go-iblite development by creating an account on GitHub.

github.com

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.

GitHub - ucan-wg/go-varsig: Multiformat for cryptographic signatures

Multiformat for cryptographic signatures. Contribute to ucan-wg/go-varsig development by creating an account on GitHub.

github.com

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