Avatar
hazeycode
bfbd26dc75540c5ee8be08f0ffaf2191a90c63e37ce066412d25ccfa5104e730

Could be simplified. Some good stuff in there though

The RIPs are the most coherent and well formed thing I’ve read on the problem in general. The architecture is interesting in that it leverages the proven distributed consensus qualities of git (not just storage).

Compatibility with existing workflows ie gradual migration from centralised services via bridges I still feel is critical for success and perhaps overlooked.

Thanks for sharing! I’m going to test it out.

Some thoughts on replacing GitHub: https://github.com/NostrGit/NostrGit/issues/115#issuecomment-1561512746 #[0]​ #[1]​ #[2]​ #[3]​ #[4]​ #[5]

👀 get your Zaps out ⚡️⚡️ nostr:note1devmc990xa2xv0ndn0g630qqrsw2k3au8nffve8w0jse9pz29ycsa4qvt4

Isn’t every private messaging system working on top of a public routing protocol? Are they all leaky to some extent?

Shout out to everyone’s mother for developing them nostr:note13qc8jc60va4x6xs65m40xvvlks03qzewss8lrdesrxmdjgy0jp9saphg33

Note previews (ie pasting a note id in another note) should just work right? Or did i hallucinate that feature? #[0]

My memory came back: note1u66xnz0yurdv6raa6kksyqeunkqe4v49mawz4nr56yylc7xj4r4sk4zm9z

Another possibility is that it is not a race condition and that the log is causing a memory allocation which in turn changes the location of subsequent allocations.

That is to say; *any* work can affect a race condition outcome. But that work may not be happening where you think it is, for all sorts of reasons.

Hard to make suggestions with no context but generated code and strace are good tools. Tricky if working within many layers of abstraction.

Not necessarily. Does the log write direct or is there flushing, batched kernel io, etc? (Just pulling shit out of thin air without knowing context)

I can’t think of a single time that a heisenbug was not due to a race condition.