nostr:nevent1qqsvl4vek90xl2ra6cta6u9ecqxgh9c060vv7k27wcthhr289p40gaqf7gn96

Reply to this note

Please Login to reply.

Discussion

The nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t team suggested displaying a repository nostr wiki page instead of the readme in the git repo.

We could definity do that or the `git push` thing but don't we ideally want to support display other files and potentially at other refs?

If we end up in a world where users of #GitViaNostr don't just rely on free (beer) and reliable hosting from big players like github, bitbucket, gitlab, etc. But instead use selfhost or #GitViaNostr hosted solutions like 'song' could be then the git servers could serve all files for all refs. That would provide the best UX.

We actually store our wiki pages as Asciidoc in the GitCitadel repo, so simply displaying the Asciidoc files gives us a similar result.

If GitWorkshop can deal with Nostr-style wiki links and other Nostr addresses, then it'd be added value.