nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g on the nostr:npub1tr0va8lk35pp4lnk64ymneywdjmmq6juznxlg5ejerkhxgwk7ggsw5qqpx
A deep dive by nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9 into how GitNestr code repositories will be stored on relays as scionic merkle DAGs.
Interesting stuff!
it's quite technical, i'm working on a tiny part of the cryptography for this project, but this is a technology that will enable fully decentralised git hosting, with the metadata broadcast over nostr and available to any nostr relay running HORNET storage, watches the blockchain and can automatically detect updates for the files knowing what to ask for by the signed merkle root from peers, get the tree of parts and inventory each part one by one.
as well as enabling decentralised, distributed git hosting, it will also be applicable to nostr profiles as well, where you will be able to periodically snapshot updates to your profile and then all subscribers can quickly learn about a new batch of updates and get every single one of them.
this is the most exciting thing in my opinion, because it means that user data can be easily gathered for followers, and stuff like being able to enable paid relays to fully sync their users' subscriptions proactively.
(just re-bumping to get this looking better in preview)
it's quite technical, i'm working on a tiny part of the cryptography for
this project, but this is a technology that will enable fully
decentralised git hosting, with the metadata broadcast over nostr and
available to any nostr relay running HORNET storage, watches the
blockchain and can automatically detect updates for the files knowing
what to ask for by the signed merkle root from peers, get the tree of
parts and inventory each part one by one.
as well as enabling
decentralised, distributed git hosting, it will also be applicable to
nostr profiles as well, where you will be able to periodically snapshot
updates to your profile and then all subscribers can quickly learn about
a new batch of updates and get every single one of them.
this is the most exciting thing in my opinion, because it means that
user data can be easily gathered for followers, and stuff like being
able to enable paid relays to fully sync their users' subscriptions
proactively.
haha, l0k1 is me... changing the handle with the move to madeira and all the new things...
i'm just finishing off a last piece of signr, the tooling/CLI that does the signatures to support taproot, i think this will finally mean i can move to another part of the work next - specifically it will be a minimal to start with, with commits, tags, staging, stashing, etc, configuration, but the main point of the exercise is that to include schnorr signatures into git as it stands is not very easy. the reason is that the way they included ssh signing, was by gpg supporting ssh. so either way, you have needing to dig into the official git, or the official gnupg, both of these are very rigid, old, C language code, whereas go-git has got all but the more esoteric features of the official git, so it is simple to insert the nostr/taproot signatures and we can also simplify the UX a little and make it easier in the more common use cases.
just wanna point out also, gitea is much much faster than github, it has issues and wiki, and it would be easy to layer in the nostr social layer to add forums and discussions and it would be simple to turn issues into nostr threads and so on.
Things have changed a bit since the pod. Not using GitTea, found a way to leverage Git in the browser without GitTea.
Also, Loki/Mleku is just working on the CLI Signr/Wallet and Adam is taking care of the rest of the GitNestr backend now — if anything, we need more hands working on the frontend with nostr:npub1u9e887ad8pl49cxgzqkuljxcxy89dtac7jkyuajnukxg6hu2hufqdjdsp7. Although, Loki/Mleku optimizing BTCD could be useful for nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g in the future!
Creating a #nostr version of Discord/Slack or making a SimpleX relay in Go would also be neat to see, maybe Loki/Mleku will take a shot at those soon. Excited for the future!
yeah, one step at a time...
haha, maybe i should just change my display name back...
today i will have the function built that properly provides all the necessary bits of information to enable creating on-chain anchors for HORNETS nodes to be notified of updates to relevant NPUBs they cache for.
Sounds all very smart but hard to follow as to where GitNestr is at.
Also I can't find any repository or demo or so for GitNestr neither.
I hate to say it but we are still at early stages. The foundations are there but integrating Hornets into the GitNestr UI has not started yet. So there is no demo yet. The conventional startup wisdom says "publish alpha when you're 80% there" and that's probably what we'll do.
