fiatjaf on Nostr: #[3] I think the way this bounty is stated is put is not the ideal. I think most ...
Still believe it’s critical we have a credible permissionless alternative to GutHub (ideally based on nostr). One that bitcoin-core and all nostr devs would trust.
Moving my bounty up from 120 million sats to 1 billion sats.
https://bountsr.org/code/2023/01/19/nostr-based-github.html
I think the way this bounty is stated is put is not the ideal. I think most people will read this and think we need a big website that is just like GitHub but using Nostr somehow. I think that is not what we should see (and hopefully that's not what
jack (npub1sg6…f63m) wants either).
What I would want to see are multiple apps that can interoperate and are able to perform separate functions:
- browse code
- comment on code (referenced by a commit)
- create issues and comment on issues
- send patches
- comment on patches
And how these should be done? I am not sure, but here's what I have in mind:
- most of the comment things should probably be kind:1 events, I don't know, with some extra tags (so they could be interacted with from the normal "social" Nostr clients? or not?)
- code should probably be hosted by standalone dedicated git servers -- and there could be centralized providers offering these services but they should interoperate seamlessly between themselves and with standalone personal servers
- sending patches should probably be done using something like this approach by
jb55 (npub1xts…kk5s):
http://git.jb55.com/git-nostr-tools/file/README.txt.htmlAVERAGE_GARY (npub160t…yjc9) has opened a discussion on this topic on the NIPs repository that could possibly be used to coordinate the efforts:
https://github.com/nostr-protocol/nips/pull/223I think we could have multiple different smallish webapps, native apps and specially command-line tools that implement one or multiple of the separate functions described above, and with that we can achieve a much better result both in terms of quality and of decentralization than if someone or some big team decides to tackle the entire cake and come up with some centralizing architecture on their own.
Published at
2023-03-04 12:09:48Event JSON
{
"id": "048f5e74bbb7e6b8019655ae45a42e93e4b028be31ebcf5aadcea6028c4fd3ec",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1677931788,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"
],
[
"p",
"d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d"
],
[
"e",
"f213b7d9f083aa0c2c28cc54d0c67cff0bea6e416fcb306c70f1f700e94a695e",
"wss://eden.nostr.land",
"mention"
]
],
"content": "#[3]\n\nI think the way this bounty is stated is put is not the ideal. I think most people will read this and think we need a big website that is just like GitHub but using Nostr somehow. I think that is not what we should see (and hopefully that's not what #[1] wants either).\n\nWhat I would want to see are multiple apps that can interoperate and are able to perform separate functions:\n- browse code\n- comment on code (referenced by a commit)\n- create issues and comment on issues\n- send patches\n- comment on patches\n\nAnd how these should be done? I am not sure, but here's what I have in mind:\n- most of the comment things should probably be kind:1 events, I don't know, with some extra tags (so they could be interacted with from the normal \"social\" Nostr clients? or not?)\n- code should probably be hosted by standalone dedicated git servers -- and there could be centralized providers offering these services but they should interoperate seamlessly between themselves and with standalone personal servers\n- sending patches should probably be done using something like this approach by #[0]: http://git.jb55.com/git-nostr-tools/file/README.txt.html\n\n#[2] has opened a discussion on this topic on the NIPs repository that could possibly be used to coordinate the efforts: https://github.com/nostr-protocol/nips/pull/223\n\nI think we could have multiple different smallish webapps, native apps and specially command-line tools that implement one or multiple of the separate functions described above, and with that we can achieve a much better result both in terms of quality and of decentralization than if someone or some big team decides to tackle the entire cake and come up with some centralizing architecture on their own.",
"sig": "6de2936d8a96a170a80f00e0b9377264c330404dbb544d1938b780f92b00a6ab05ebd3fe37b11cfadc39a58dc78b6628919374e044c291730ae61a4d4c815bcb"
}
