fiatjaf on Nostr: ...
Which specific projects do you want to see move? The issue is usually somewhere between “people don’t have an account at the alternative” plus “self hosting means finding someone to host”.
The first can be solved with software, the second can’t (modulo some decentralized thing but that makes the first problem 100x worse - “install software X to report an issue or open a pr, and if you have issues with X good luck”).
It’s really more of a motivation question - can you convince the devs of a project it’s worth the pain to move.
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 <branch>
And then I would do
- git nostr list-patches
- git nostr apply-patch <event id>
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.
Published at
2023-04-27 02:38:47Event JSON
{
"id": "a784c897f898a127dadd9516f491ef1f0a8e50f16ca377ca7c218e166fa35385",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1682563127,
"kind": 1,
"tags": [
[
"e",
"8928abcfe5594173b042c9120c623d0effb8d638e8e5a49f3ca72a68ff99dc33",
"wss://nostr-pub.wellorder.net/",
"mention"
]
],
"content": "nostr:nevent1qqsgj29telj4jstnkppvjysvvg7salac6cuw3edynu72w2ngl7vacvcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhszgthwden5te0wfjkccte9ehx7um5wghxyctwvshhyetnw3exjcm5v4jqz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszrnhwden5te0dehhxtnvdakz7ds2yrp\n\nOnce 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.\n\nIt would have been beautiful if they could have done\n\n- git nostr send-patch \u003cbranch\u003e\n\nAnd then I would do\n\n- git nostr list-patches\n- git nostr apply-patch \u003cevent id\u003e\n\nOr my repositories could have webpages that would list pending patches found on relays and also allow people to comment on them from their browsers.",
"sig": "9eefdfbd556fe48434b0f3f94a61e6a1bc50b2ec5fe99c137e3dbb767e8753f0a00ffdf620acbb810f55c068e391136e6be8120f24f017e21cfcd7e81077b291"
}
