Post ATH2NJnxuq7tImNsOG by d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d@mostr.pub
(DIR) More posts by d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d@mostr.pub
(DIR) Post #ATGwsVYRgIdSzkc7cW by 3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub
2023-03-04T12:09:48.000Z
0 likes, 0 repeats
#[3]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 @82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2 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 patchesAnd 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 @32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245: http://git.jb55.com/git-nostr-tools/file/README.txt.html@d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d 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.
(DIR) Post #ATGwsW3HpdJ0XP2kgy by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
2023-03-04T12:48:18.000Z
1 likes, 0 repeats
I would extend the feature set from just sending patches to pull requests (git endpoint + branch + target branch). git has this for email but it’s pretty janky and nostr apps could do it better.
(DIR) Post #ATH2NJIPo8tBivcgDI by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T12:56:48.000Z
0 likes, 0 repeats
Does the author of that bounty really know how git works and realize that git is already decentralized?Emailing patches is one of the main features that Linus wanted when he wrote git. Replacing email with nostr is already being done with git-nostr.The problem of who gets to decide what to merge into Bitcoin core is not going to be solved by putting it on nostr.
(DIR) Post #ATH2NJnxuq7tImNsOG by d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d@mostr.pub
2023-03-04T13:21:50.000Z
0 likes, 0 repeats
Link to git-nostr?
(DIR) Post #ATH2NKVZIj0LU0mhM0 by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T13:46:46.000Z
0 likes, 0 repeats
http://git.jb55.com/git-nostr-tools/file/README.txt.html
(DIR) Post #ATH2NLCohvbDe91ElU by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
2023-03-04T13:49:51.000Z
0 likes, 0 repeats
Yeah this is just a hack though. I think to fulfill the bounty it would need a really good UX, pull request support, code review, etc. web UI for managing issues for users, cli clients for devs. Lots of work to do! I’m tempted to do it but want to give other people a shot first. If I’m not happy with the solutions I will consider it.
(DIR) Post #ATH2ijYdMYw9FnQNrk by d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d@mostr.pub
2023-03-04T13:21:39.000Z
1 likes, 0 repeats
It’s the seamless experience that is capturing. Why do so many people use GitHub? I would argue it’s because of the friction it removes from the many git related tasks. Emailing patches is fine but not something everyone is comfortable with due to the “extra” steps needed to compare/diff, and discuss the patch. There’s user friction involved. GitHub and other git context providers have greatly reduced the friction for these processes as well as consolidated them into one place with other tooling. This value add cannot be understated. I can email you a patch, but that does not provide visibility into any CI/CD I’m running. Nor does it connect the patch to an outstanding issue.
(DIR) Post #ATH4Exdwd0OoA0q7DU by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T13:41:06.000Z
0 likes, 0 repeats
Linus wrote git to be distributed (decentralized) and his workflow with email patches was a core design feature.Github projected a centralized workflow onto git (branch permissions and all that jazz are not a part of git). This has its place especially in the enterprise world. So why do we want branch permissions for open source projects?I think it comes down to trusted reviewers. There are those rare combinations of talent, common sense and OCD that make excellent master branch guardians.So all I think we need is1. the feature of broadcasting merge requests on nostr2. the feature of trusted reviewers signing their approval to this request3. the feature of cryptographically coming up with a deterministic merge outcome and commit hash so every distributed client would have an identical merge4. a git client/client extension to automatically merge based on preconfigured sign eventsEvery developer could still hold the code local, plus there could be X public repository servers.
(DIR) Post #ATH4EyNfsyykRqEdUm by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
2023-03-04T14:10:47.000Z
0 likes, 0 repeats
Yes emailed patches are a core workflow for Linus/linux as it makes it easy to contribute code without needing a public repo and branch. You would still probably want git-request-pull like functionality for maintainers.The reason I mention this is that bitcoin-core doesn’t support patch workflows that well, as they rely on a signed chain of commit hashes and ACKs on specific commits.
(DIR) Post #ATHEbSuG4Xhz29q7d2 by 82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub
2023-03-04T16:07:24.000Z
0 likes, 0 repeats
💯I was lazy with my description and overly used GitHub as a shortcut. Either approach works (many small apps to achieve tool set, or one cohesive project). I’m a fan of the former as well, as each can probably be used for other things too, and it would move faster.
(DIR) Post #ATHF6TxyBKI3IXMjtQ by 82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub
2023-03-04T16:13:01.000Z
0 likes, 0 repeats
Yes I def know it’s already decentralized and how it works. However, bitcoin core has a current dependency on GitHub collection of tools and interfaces. This seems fixable. I think fiatjaf lays out the most critical needs much better than I did.
(DIR) Post #ATHbkAhnPVSg8W8Bpw by e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411@mostr.pub
2023-03-04T12:21:28.000Z
1 likes, 0 repeats
@82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2, I know you may not pigeonhole the offer. But you might want to spec it out a bit, ppl get scared of very open ended projects. Feel free to make PR or reply here and we can update the site https://github.com/coinkite/bountsr.org.pub/blob/main/2023-01-19-nostr-based-github.md
(DIR) Post #ATHbkBJ1B7EfzxXur2 by 82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub
2023-03-04T20:26:42.000Z
0 likes, 0 repeats
i don’t have a GitHub account 😬commit 4134343b3b3a63a4d2ff0c6542704b80505458ec (HEAD -> main)Author: jack <jack@freecpu.localdomain>Date: Sat Mar 4 14:14:01 2023 -0600 cleaning up and pointing to fiatjaf's postdiff --git a/2023-01-19-nostr-based-github.md b/2023-01-19-nostr-based-github.mdindex d8ffb2b..f88ba16 100644--- a/2023-01-19-nostr-based-github.md+++ b/2023-01-19-nostr-based-github.md@@ -4,28 +4,18 @@ title: "Nostr-based GitHub replacement" date: 2023-01-19 10:43:00 -0500 categories: code author: jack-value: 10.5+value: 10.05 currency: BTC-contact: nostr:note17gfm0k0ssw4qctpge32dp3nulu975mjpdl9nqmrs78msp622d90qvdral4+contact: nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m status: New --- -"will pay 120,000,000 sat (at least) bounty for best nostr-based GitHub replacement. “Best” as determined by this community."+Create a "complete" Nostr-based suite of git tools, such that projects like bitcoin-core are sufficiently confident to move away from GitHub. Best thread on this is here: -https://brb.io/n/0b2642fe0cf4a3c4daf315bedd5382266747b92d909c60f753f9160cba3d21f5+https://snort.social/e/note1qj84ua9mklntsqvk2khytfpwj0jtq297x84u7k4de6nq9rz060kq9zt84j --- "Eric pledges another 5,000,000 sats if the best product is selected." https://t.me/takechiyoe-------2023-03-03 update:--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. --note17gfm0k0ssw4qctpge32dp3nulu975mjpdl9nqmrs78msp622d90qvdral4
(DIR) Post #ATHcWLWOV2AFa8llGS by e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411@mostr.pub
2023-03-04T20:34:22.000Z
0 likes, 0 repeats
Just download, commit locally and drop the commit here. Or give meSome text and I will put it there.
(DIR) Post #ATHcWMBA3Sm3cZqJo8 by 82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub
2023-03-04T20:35:25.000Z
0 likes, 0 repeats
I think I did that?
(DIR) Post #ATHeqIhIuOyCWVVzs0 by e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411@mostr.pub
2023-03-04T20:47:00.000Z
0 likes, 0 repeats
I see the changes/diff now. Will put up when I’m back at a computer
(DIR) Post #ATHeqJDux93e9em2hk by 82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub
2023-03-04T21:01:26.000Z
0 likes, 0 repeats
Understood they took time to reach you