Replying to Avatar OceanSlim

nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr I'm hosting a mirror of gitworkshop.dev at https://ngit.hapytavern.co (with a slight branding change) In case yours is ever unreachable. A decentralized git collaboration should have more than one front end for redundancy 😉

nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

(I'm self hosting so this is still in yarn dev atm, and since gitworkshop uses netlify I'll have to rethink production deployment when I get a minute but anyways)

Of course I misspelled my domain in the original note. It's edited now, but for those on clients that don't have edit: https://ngit.happytavern.co

Oh and we have a regular git server too...

https://git.happytavern.co

Stop depending on GitHub. Upgrading to forgejo soon. All nostr devs welcome 🫂

Reply to this note

Please Login to reply.

Discussion

gitworkshop can be a nice alternative frontend for gitea. how about emails accounts and webmail frontend? gitea require email to create an account, and we are all on nostr, now.

Yup. This is why I'm moving to hosting an instance myself so early.

Just use your NIP-05 or your zap address, for now. 🤷‍♀️

Probably just need something with an @ in it. Doubt it'll send you emails, or anything.

Most git services require account confirmation over email. There are solution like burner emails, but is complicated and github/gitlab reject accounts this this. It will be nice if can be done OpenID over nostr or use NIP07 , and use that create/use git service . Maybe nostr relay can support OpenID over nostr/NIP44.

Yes, I meant a self-hosted gitea or something. Git itself uses something-with-an-@ to identify people, but doesn't check authenticity, so NIP-05 seems like a good bug-fix, until we get full Nostr logins on gitservers.

We eventually need a note-writer to overwrite commands like git send-email, and we need a way to figure out who to send the note to, and NIP-05 could help with that and keep everything more human-readable. Could always offer npub as a fallback.

Or we could do

user.name = npubbunchofnumbers

user.email (optional, for a human-readable version) = NIP-05

This would also allow an npub to use the same user.email for multliple npubs.