Nostr Web Client

So, how would I build gittr (git transmitted by relays)?

Event kind R = repository root. Replaceable (by author). Points to git url(s). Everything related to that repo points to this with a 'repo' tag, except the 'repo' tag is searchable so some single letter we have not used yet.

Event kind I = repository issue. Long-form note that starts an 'issue'. Normal nostr threads proceed from here.

Event Kind PR = pull request. Points to a url and branch. Points to the repository root.

I would then make some web client that drives this so that the web client looks similar to gitea (which looks remarkably similar to github).

... but I'm building gossip, so please steal these ideas.

Reply to this note

Please Login to reply.

Discussion

average_bitcoiner 2y ago

https://github.com/nostr-protocol/nips/pull/223

₿logging₿itcoin 2y ago

Pairing gitea and nostr somehow makes sense to me. I run Gitea on yunohost and it's on Umbrel too.

average_bitcoiner 2y ago

Was just looking at the source code. It’s in an unfamiliar language. 😞

But still going to check it out!

₿logging₿itcoin 2y ago

I''m just afraid if we add all that code to relays, they will either be ephemeral or centralized.

If we want to enhance the decentralization of bitcoin, it makes sense to decentralize where we put the code much like the thousands of bitcoin nodes.

Bitcoin core devs can sign these with their nos tr keys instead of PGP.

Putting it all on nostr relays and creating clients that read the Git kind would be easier for non developers, but at the cost of eventual centralization, but I could be wrong.

I don't think I have a deep enough understanding of the protocol yet to make definite statements. Besides, I'm like a NPC coder. I hardly know what I'm doing.

average_bitcoiner 2y ago

Gitea is open source. Hrm...

Nunya Bidness 2y ago

Zappid!

#Plebzap

Nunya Bidness 2y ago

"Please steal these ideas." - #[0]

This is how we win. Nobody working on the most important, world changing code like Bitcoin and nostr is knocking on the Federal Reserve's door begging for a $120K a year job. Or at the Treasury. Or at the ECB. Or at the DoJ. Or at Twitter, FaceBag, IG . . .

No. They are here, spittin' ideas, building code, and getting feedback on implementations from actual users, real-time, and while in production for a fucking pittance or worse; burning through savings and the best years of their lives.

We win with sacrifice.

We win with companionship.

We win by eschewing lambos and other bullshit and hangining ourselves out there warts and all for nothing more than reaching for something better.

#[1]

$elfish gene 2y ago

Delta, Dirac 2y ago

Idk exactly what this means, but yes, put everything on Nostr ⚡⚡⚡

#[0]

Delta, Dirac 2y ago

#[1]

3j2009 2y ago

Happy help with the UI design

Ignatio 2y ago

To handle the "context" around a git repo is far more of a specialized nostr client problem than a nostr protocol problem. Or it should be.

A git-specialized nostr client can work with that context (PR's, issues, etc) on nostr - using standard relay implementations - and kind 1 events, NIP-79 (custom) events, and possibly parameterized replaceable events (for issues, to update their status).

If every niche application of the nostr protocol requires a protocol amendment, that is certainly not sustainable. If the protocol does not handle arbitrary and specialized applications, then that needs to be fixed preemptively with a NIP or two.

As it stands with the current 35 NIPS, 25% of them concerns the protocol essentials. Another 25% concerns optional protocol-level features. 40% of them concerns content-only stuff, and the remaining 2 covers peripheral things (browser extensions, URL schemes).

By analogy, if UDP had to care about whether it was transporting syslog, SNMP or VOIP packets, no one would use UDP for anything.