Thread - Nostr Hypermedia

arbadacarba abracadabra@nostr.com 5 months ago

Jo, I include https://git.gittr.space/... as the primary clone tag on push by a new endpoint to the bridge so theres a guaranteed HTTPS source while it’s processing. Once other relays pick up the NIP‑34 event, the nostr:// URLs are broadcasted and should work.

gittr

gittr - Decentralized Git Hosting on Nostr

A truly censorship-resistant alternative to GitHub built on Nostr.

↑ Parent

Replies (5)

arbadacarba abracadabra@nostr.com 5 months ago

Repo read is still done on the client for the events and the bridge fetch, so thats due to the storage/cache + binary fallback, not SSR. Flow is described here https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g5tu7dhftfpueajf4rpxqfjhzmc/gittr?file=README.md

2 replies ↓

arbadacarba abracadabra@nostr.com 5 months ago

if you open the clone-url section theyre shown on each repopage

npub15qyd...yejr 5 months ago

I don't understand how a bridge is a decentralised git server. Do you mean they are stored on grasp and access via a bridge for efficency?

1 replies ↓

npub15qyd...yejr 5 months ago

I dont understand your recommended option. how can you use ssh? Are you offering a centralised git server permissioned via ssh keys?

1 replies ↓

npub15qyd...yejr 5 months ago

Option C links to a repository that doesnt exist. ngit has the git-remote-nostr plugin that enables cloning via `nostr://` see ngit.dev/install

1 replies ↓