Thread

🛡️
Grasp is Blossom for git repositories. You can host your repositories in multiple servers and their state is attested by Nostr events you publish that tells people where to fetch from and what is the latest head and branches, so the servers don't have to be trusted and it's easy to switch servers while keeping your repository identifiers immutable (they're essentially your pubkey + an arbitrary identifier). Grasp servers can be self-hosted, paid, or ran for free by some community benefactor, and you can mix and use all these at the same time. The existence of grasp servers also makes it easy for people to clone repositories, create branches and make them available to be merged by others, all without leaving the terminal (but of course there can also be all kinds of clients), which is the GitHub "pull request" UX people are familiar with.

Replies (5)

🛡️
pull requests are bullshit. i have made a dozen to various projects that were perfectly valid. one of them i had to merge, merge, merge, and then merge some more, and it's still probably sitting there on the lnd repository. if you are so unfriendly you won't give privilege to a contributor to make new branches and push them, you aren't the kind of project participant i have any time for.
🛡️
Full Grasp support coming to BudaBit soon, the primitives are already implemented. 1. What we struggled with is the creation flow where we first post the repo announcement then the newly created git repo, but that must be done with an arbitrary sleep(X ms) wait time so that's not really ideal. You guys have ideas to improve this flow? 2. I think it this was discussed before but want to get a fresh opinion of yall: Unified grasp api for file browsing and perhaps diffs and really data-heavy ops? Cloning repos via git smart http can still be a fallback but this would benefit performance a lot. Blossom has an api as well so I guess this would make sense, especially in a browser context. @fiatjaf @DanConwayDev