Post ATGzoapoPLFm4iYtUm by d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c@mostr.pub
 (DIR) More posts by d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c@mostr.pub
 (DIR) Post #ATGzoapoPLFm4iYtUm by d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c@mostr.pub
       2023-03-02T00:21:42.000Z
       
       0 likes, 0 repeats
       
       This 1.23 BTC bounty for a nostr Github replacement looks really yummy ๐Ÿ˜‹:https://bountsr.org/code/2023/01/19/nostr-based-github.htmlHere's my plan:1 - Propose a NIP introducing 3 new event kinds (repo, issue, PR). Each event has an eventID and has a "parent" field pointing to another event. The root event in the tree is the "repo" event kind.2 - Fork gitea/gitlab3 - Add a nostr client library that can talk to 4 - Remove all server side code that queries a centralized database5 - Replace it with event queries6 - Cache it so it is not super slow7 - Replace user database with a nostr login8 - Self host a demo client9 - Claim bounty to @82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2 10 - profit?
       
 (DIR) Post #ATGzobGknAnvQHAPUO by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
       2023-03-04T13:21:12.000Z
       
       0 likes, 0 repeats
       
       Not sure I like this approach, I would build a proper client
       
 (DIR) Post #ATH0J0CgeQaLRWlHM0 by d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c@mostr.pub
       2023-03-04T13:23:34.000Z
       
       0 likes, 0 repeats
       
       Why reinvent the wheel when it comes to UI?
       
 (DIR) Post #ATH0J0wPuPAHjM9ndI by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
       2023-03-04T13:26:42.000Z
       
       0 likes, 0 repeats
       
       This is always proposed (fork an app and add nostr to it) and is almost always a bad idea. It would deserve its own clients and web uis without a centralized DB. The goal is to not just rebuild another github, but instead to do it right on top of nostr.
       
 (DIR) Post #ATHPNvXZugSbHayimm by 7560e065bdfe91872a336b4b15dacd2445257f429364c10efc38e6e7d8ffc1ff@mostr.pub
       2023-03-04T18:07:14.000Z
       
       0 likes, 0 repeats
       
       No the plan is the keep git. So itโ€™s not clear to me what nostr adds?
       
 (DIR) Post #ATHPNwADb1MvDR3a0u by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
       2023-03-04T18:08:13.000Z
       
       0 likes, 0 repeats
       
       The other stuff. Code review, issues, pull requests, patches, etc
       
 (DIR) Post #ATHPnn7pp6w8iFGoLo by 7560e065bdfe91872a336b4b15dacd2445257f429364c10efc38e6e7d8ffc1ff@mostr.pub
       2023-03-04T18:09:35.000Z
       
       0 likes, 0 repeats
       
       Why so much resistance to just doing it all in nostr?Seems 100x easier than combining git + nostr.
       
 (DIR) Post #ATHPnnsH2S5F2Gztjc by 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub
       2023-03-04T18:12:54.000Z
       
       0 likes, 0 repeats
       
       git is much better for storing git data. Makes more sense to use nostr for the other stuff and is easier not harder