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.
Ignatio
npub1r2x…6rtn
2023-03-06 06:23:24
in reply to nevent1q…jze7
Author Public Key
npub1r2x8j028pdjdlrtu65z4y99xre09dcuyu7cct49gfhcmz93t00eqzq6rtnPublished at
2023-03-06 06:23:24Event JSON
{
"id": "b2c94da29b07a6c776248a2974ec0cdee17fb10b0f23b970c22d10a9d32804bb",
"pubkey": "1a8c793d470b64df8d7cd5055214a61e5e56e384e7b185d4a84df1b1162b7bf2",
"created_at": 1678080204,
"kind": 1,
"tags": [
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"wss://at.nostrworks.com"
],
[
"e",
"00006780e1cc6d35fced77a1752ac182ac33b8f2b580bb13d6ec66645606657a",
"wss://at.nostrworks.com",
"reply"
],
[
"e",
"00006780e1cc6d35fced77a1752ac182ac33b8f2b580bb13d6ec66645606657a",
"wss://at.nostrworks.com",
"root"
]
],
"content": "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.\nA 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).\nIf 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.\nAs 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).\nBy analogy, if UDP had to care about whether it was transporting syslog, SNMP or VOIP packets, no one would use UDP for anything.",
"sig": "615ada8d9948bd843716fc6bbb7108a928d75f774eef0b77a8dad9febce0ecc5744542beec9a77d47af65a1dbd5b4a23200c1f269c753eafe43b86adba941a29"
}