Damus
Open in Damus

Recent Notes

Arjen · 4d
Yes! We're redesigning for a mesh structure rather than a tree structure (though that will still work) FIPS is the model we hope to move towards.
Renaud Lifchitz · 1w
Actually it's a implementation (firmware) of LXMF...
PixelBob profile picture
So ngit/grasp basically stores git repos on your own (and other) servers, but indexes them all on nostr. Hashtree uploads the repos to blossom servers but uses the same nostr events to index.

ngit/grasp easy to reason about, easy to implement, easy to setup locally.

Hashtree.cc interface is very nice, maybe hard to setup locally? A lot of technical implementation details to replicate across platforms. Free Blossom servers about to receive a lot more content/bandwidth usage.

@DanConwayDev

@Sirius Business Ltd
PixelBob profile picture
Hashtree.cc looks interesting. And a clean ui for managing git. But ngit and grasp seem to be working well. Hashtree looks like a lot of techinical debt there to reproduce
Johnathan Corgan · 2w
In theory, yes. In practice, there would likely be some tradeoffs involved regarding the need for fragmentation, protocol timer adjustments, etc.
PixelBob profile picture
PixelBob @PixelBob
I ask because meshcore has a lot of people deploying hardware and investing time growing the network, if fips could be an additional overlay you might get a boost to adoption. But yeah, its a very slow transport, and any system spamming hundreds of packets to send a cat pic might upset some.
2:fire:1
Juraj · 2w
It would not just upset, it would completely break the network. Especially the country-wide ones.
Johnathan Corgan · 2w
Right. FIPS is a general purpose datagram service between npubs, designed and optimized for the traffic scale typical of Internet applications. So adding LoRa or other low bandwidth / low MTU / high latency transports would be possible, but would need specific engineering for rate limiting and traff...