Thread

Replies (69)

I agree that a large bounty doesn't put the right incentives in place. I'd love to work full time on this problem. Would you consider sponsoring a lead developer? I outline the key challenges as I see them here: https://blogstack.io/naddr1qqyxxdmyvsmrqdn9qywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wspzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqvzqqqr4guzzjrgj And the bull case for this here: https://blogstack.io/naddr1qqyr2wt9xfsk2wp3qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsyg9qpr00z4uklw56p4h6kp8gl4ts3y59m874qhd94ql732k40g6kf5psgqqqw4rsd8v7ng
This is exactly what I do and recommend. Everyone writing code should be handling their primary/authoritative git served in house, and use GitHub, GitLab, Bitbucket, AWS Code, Sourceforge,Launchpad etc as mirrors only. Gitea works ok at small scale. One caveat is when pushing commits to mirrors the refs to issues won't line up and this can be confusing in GitHub and others that render links The bigger challenge is projects that are intended to be open and decentralized like Bitcoin. They need a publicly accessible authoritative home without risk of a single corporate or gov organization controlling, or being rugpulled. I periodically fetch and backup projects I deem important, and recommend also running local maven and npm registries as needed
Which specific projects do you want to see move? The issue is usually somewhere between “people don’t have an account at the alternative” plus “self hosting means finding someone to host”. The first can be solved with software, the second can’t (modulo some decentralized thing but that makes the first problem 100x worse - “install software X to report an issue or open a pr, and if you have issues with X good luck”). It’s really more of a motivation question - can you convince the devs of a project it’s worth the pain to move.
Bounty is the last apple that quenches my hunger. We need user base that depends on this piece of tech. Looking at that user base developers feel interest on the platform. A user base closer to the bottom of the pyramid better for the purpose. Let’s fund such user base first so that bounty begins to work it’s magick.
Why not organize and lead a fully open source team to create what you want to see? Your vision is so strong and your such a great leader! Lots of folks would absolutely love to work with you on this 💚 You've got the sats as a bounty, but I wonder if you'd get more traction if you could start to describe some journeys and perhaps rough requirements as a starting structure? You could always use the sats as fuel for the fire then, instead of a tool to start the fire to begin with. 🔥
Self-hosting a Git instance can be relatively straightforward. There are several options available, such as Gitea, Gogs, and GitLab, with Gitea currently being a top choice. Migrating the Bitcoin repository to a self-hosted instance would be manageable, although transferring issues and other related content might require some effort. Developers would need to transition to a new domain and register, which may take about 5 minutes. While this could be a minor inconvenience, it's still feasible. Nostr could play a role in this process as well. By having all developers on Nostr with a keypair, it's possible to verify their identities on another instance. An app could be developed for this purpose, or developers could simply include their npub in their profiles and sign something. This can also be done with ssh keys, and the new git verification mechanism. Setting up mirrors as contingency plans could be a proactive approach to address potential concerns.
Your proposal has merit and could be worth exploring further. However, it's important to carefully consider the potential benefits and drawbacks of any major changes to the development process. it's worth noting that there may be some potential challenges and trade-offs to consider. For example, self-hosting a Git instance may require more resources and maintenance compared to using a hosted service like GitHub. Additionally, transitioning to a new domain and registering on a new instance may require some coordination and communication with developers, and could result in some initial disruption or confusion.
May I suggest to break out smaller bounties. It's $290k to fulfill a seemingly herculean task that requires to assemble a team and work out many details that you have not defined and neither does anybody know what others are working on. How about awarding $10k of that money for the 3 best proposals (5k, 3k, 2k) to tackle the big task in time and budget. These proposals have to detail sub-tasks that again can be accomplished in short sprints. Pay out +$10k every week or two so people see it's real and in reach.
On the gitea repo there is doubt about the goals of the bounty and I would appreciate clarification from you @jack Is the bounty only for a solution on nostr or could at least part of it go to contributions that do not use nostr but ActivityPub? The issue if you want to reply there yourself instead of here: