Avatar
aldum
399d85b6034a4d0ee221a8497a09f5be78c97422548a1f3f0d70d4905c6bcb2b

I'm a 30-year-old boomer who's not lightning-ready yet :P

Dang it, you made me test my max, which I haven't done in 2 years. 33 it is. Stay humble, stack reps!

Yes, if we use the interpretation that 'code is law'. Making the smart contract bulletproof is on you. However, breaking into a server is like sneaking into your house: just because you left the backdoor open, it doesn't mean they are welcome inside.

Not CGI, film tricks. Very different argument.

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.

The login part could be solved with SSO, gitea already has some support for that.

Great stuff. Is there a forum one could/should frequent as a developer, to see where is help most needed?

He said "mother asshole".