Conversation

Notices

1. Embed this notice
   jack (82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2@mostr.pub)'s status on Thursday, 27-Apr-2023 06:28:52 JST jack
   I’m growing more and more concerned about the reliance on GitHub.
   
   And starting to think a bounty isn’t the right way to fund this work.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Thursday, 27-Apr-2023 06:28:52 JST Alex Gleason

     in reply to

     @82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2 ForgeFed has already done a lot of work to build a decentralized git thing. It’s ActivityPub based, but worth looking at: https://forgefed.org/

   • Embed this notice
     Melvin Carvalho (de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645@mostr.pub)'s status on Friday, 28-Apr-2023 04:59:01 JST Melvin Carvalho

     in reply to
     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.
     Alex Gleason likes this.