Should be groupchats, nip22 30023 for topics/subscription and nip22 1111 for comments

arbadacarba
Just a girl with ideas ⚡ gittr.space
Gittr.space has discussions tab per repo
Adding also better Nip05 support on the bridge.
On another front found that on gitworkshop the repo cannot be found with its dash in the name but only with hypermedia. https://image.nostr.build/8b19d2ccdbacfc18235991572241638… https://image.nostr.build/2053a040b466d50c1b923941d16e24c…
On another front found that on gitworkshop the repo cannot be found with its dash in the name but only with hypermedia. https://image.nostr.build/8b19d2ccdbacfc18235991572241638… https://image.nostr.build/2053a040b466d50c1b923941d16e24c…
Wut 😅 nevent1qqswagu7tdj…
Mat, the answer is in the posts comments
Happy Birthday 🎊
On the homepage you're shown recent repos of everyone using the nip on whatever client, it's not all yours 😆 your profilepage shows 2, lgtm https://image.nostr.build/0a8bcc64779595475d9a976e094f4ac… https://image.nostr.build/0a8bcc64779595475d9a976e094f4ac…
Sir, plz use nip07,npub or nip05 👾 Working on bunker, wanted to support the @lnbits remote signers but don't have one to test with 🐈⬛ it will come 🤣
https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g… needed the same plus confs plus bitcoin holidays 😜
Yes, that would be great. Doing this atm https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g…
Decentralizing repos to me is the coolest feature in nostrland atm. Waiting for you to add your apps to nostr gittr.space 👾🐈⬛
I use nowser on mobile. The UI is terrible but it works 😆
That’s why the repo view is stitched together from tiny helpers with clear in/output instead of a Franken-class you can’t test. If theres still a hidden coupling, point it out and Id happily erase it.
I keep repo data via StoredRepo snapshots. The file fetch, renderer, and UI are orchestrated through small utilities and not by inheritance
I keep repo data via StoredRepo snapshots. The file fetch, renderer, and UI are orchestrated through small utilities and not by inheritance
Id like to know what's too complex in this. You can just fork it and build upon or just face the complexity.
The result is very reliable & fast so i dont really get the problem here neither with complexity and sharing snippets on that nor PRing progress. Ive contributed to much older code than 2 years before..
https://blossom.primal.net/032e472c16fd15945080dcc295c0a6…
https://blossom.primal.net/7ede1947471fa01d5af24ca6c40138…
https://blossom.primal.net/032e472c16fd15945080dcc295c0a6…
https://blossom.primal.net/7ede1947471fa01d5af24ca6c40138…
Ist faster and working great, not sure what the problem is
Yes, thats what i am saying. Its about discoverability for me.
See nothing wrong in PRing changes so its up to date. Lost and left repos are a problem when ppl want to contribute.
See nothing wrong in PRing changes so its up to date. Lost and left repos are a problem when ppl want to contribute.
Issues and PRs (kinds 9803/9804) are automatically published to nostr on handled status changes (merged, closed and reopened).
I fetch them from source if possible on import of the repo and try to aggregate those by their timestamps with the nostr kinds.
If source is lets say Github im not upstreaming the edits additionally there so far.
Anyway still needs polish in finding these kinds better and flows are surely not the endgame, but what i went with so far 🤓
https://blossom.primal.net/98c2d54ff2b555c525ae66cf15b56a…
https://blossom.primal.net/b705890f9c15b80e8a05f4ec528405…
https://blossom.primal.net/d1d01ca7fe2f0fc0b0d00371208456…
https://blossom.primal.net/76ed21b82fbd9e2ee69018e765d51f…
https://blossom.primal.net/9c4d33065ce7aaf3b4c0f7ae2528a6…
I fetch them from source if possible on import of the repo and try to aggregate those by their timestamps with the nostr kinds.
If source is lets say Github im not upstreaming the edits additionally there so far.
Anyway still needs polish in finding these kinds better and flows are surely not the endgame, but what i went with so far 🤓
https://blossom.primal.net/98c2d54ff2b555c525ae66cf15b56a…
https://blossom.primal.net/b705890f9c15b80e8a05f4ec528405…
https://blossom.primal.net/d1d01ca7fe2f0fc0b0d00371208456…
https://blossom.primal.net/76ed21b82fbd9e2ee69018e765d51f…
https://blossom.primal.net/9c4d33065ce7aaf3b4c0f7ae2528a6…
Yep. An expanded git-nostr-bridge (similar to but not a GRASP server) that accepts SSH connections. When smo wants terminal/CI access, they publish their SSH public key as a Kind 52 event, and the bridge automatically pulls it into authorized_keys. That lets them git clone/push against git.gittr.space, just like hitting any GRASP server.
It isn’t the source of truth—every push still emits the NIP‑34 event and Blossom/nostr:// pointers—so anyone can ignore our bridge and sync the same repo via nostr:// or their own mirror. We just provide the SSH path for convenience and compatibility with stock git clients :
https://gittr.space/help#ssh-keys
In the DEPLOYMENT_GUIDE.md theres a “Bridge Explained” section that tells how i keep Strategy 4 metadata while layering an SSH/HTTPS bridge on top.
https://blossom.primal.net/f5637bed27a1b2e3c42a3d5132997b…
It isn’t the source of truth—every push still emits the NIP‑34 event and Blossom/nostr:// pointers—so anyone can ignore our bridge and sync the same repo via nostr:// or their own mirror. We just provide the SSH path for convenience and compatibility with stock git clients :
https://gittr.space/help#ssh-keys
In the DEPLOYMENT_GUIDE.md theres a “Bridge Explained” section that tells how i keep Strategy 4 metadata while layering an SSH/HTTPS bridge on top.
https://blossom.primal.net/f5637bed27a1b2e3c42a3d5132997b…
yes, “Blossom pack” here means the optional Strategy‑4/5 hybrid that publishes ["web","https://blossom…"] tags pointing at pack files, exactly like the approach you suggested afais
Yes, a lot. Pls check the docu files :P https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g…
Those are placeholders in the docs;. As said the real repo cards include the live nostr://npub… links, and they’re meant to be consumed via git-remote-nostr. https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g…
"Strategy 4 compliance: We never embed file blobs in the NIP‑34 event content. Every push still publishes the full tag set (clone URLs, nostr:// targets, r tags, etc.), and the bridge subscribes to all relays just like any other GRASP/bridge. Anyone can ignore our hosted URLs and pull directly from a nostr:// source or Blossom pack.
Why the bridge exposes /api/nostr/repo/files: That’s an extra convenience layer so the web UI (and other clients) can fetch file content faster while the data is still propagating. It’s not a proprietary format—just a REST wrapper around the bare repo the bridge synced from Nostr. Think of it as Strategy 5 (local caching) layered on top of Strategy 4.
Trusting state events (kind 30618): We do honor them. When a repo already has a 30618 “state” event, the bridge uses that to verify refs before falling back to the clone tags. If there isn’t one yet, we rely on the clone URLs so users aren’t blocked while waiting for the maintainer to publish the state event."
Why the bridge exposes /api/nostr/repo/files: That’s an extra convenience layer so the web UI (and other clients) can fetch file content faster while the data is still propagating. It’s not a proprietary format—just a REST wrapper around the bare repo the bridge synced from Nostr. Think of it as Strategy 5 (local caching) layered on top of Strategy 4.
Trusting state events (kind 30618): We do honor them. When a repo already has a 30618 “state” event, the bridge uses that to verify refs before falling back to the clone tags. If there isn’t one yet, we rely on the clone URLs so users aren’t blocked while waiting for the maintainer to publish the state event."
The “bridge” isn’t the source of truth, but i use it as accelerator. Repos are still announced and mirrored via NIP‑34 events (and, when needed, Blossom packs), so any relay-based client can fetch the same metadata/files straight from Nostr. I added some tags btw for docu-links to them etc. The git-nostr-bridge just watches those events, keeps a local bare repo for fast HTTPS clones, and exposes an API so the push ends without waiting period for relay propagation. Like a GRASP server but different :P










