Replying to Avatar fiatjaf

nostr:nevent1qqsgj29telj4jstnkppvjysvvg7salac6cuw3edynu72w2ngl7vacvcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhszgthwden5te0wfjkccte9ehx7um5wghxyctwvshhyetnw3exjcm5v4jqz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszrnhwden5te0dehhxtnvdakz7ds2yrp

Once upon a time I started hosting my small projects on a self-hosted Gitea (I think this was it) server. The problem was that once someone showed up and wanted to make a contribution they were totally unable to. They had to create an account on that stupid server, then the ssh access didn't work for them, then they lost their password on my server and I didn't have SMTP configured to send them a password reset, it was all very very painful.

It would have been beautiful if they could have done

- git nostr send-patch

And then I would do

- git nostr list-patches

- git nostr apply-patch

Or my repositories could have webpages that would list pending patches found on relays and also allow people to comment on them from their browsers.

Actually even a nostr login plugin for gitlab would be a nice interim that would solve a lot of the painpoints you just mentioned. You could host your own gitlab, fire up the nostr login plugin and every nostr user can use nostr connect to login. Could even store basic profile settings in a app specific nostr note. Then when you login to another gitlab instance it will just ask you "do you want to use your 'fiatjaf' profile here?".

Reply to this note

Please Login to reply.

Discussion

No replies yet.