Laeserin @Laeserin - 1d
GM ☀️ Okay, the current sign-up list, for the public git server is: nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub18pudjhdhhp2v8gxnkttt00um729nv93tuepjda2jrwn3eua5tf5s80a699 nostr:npub15pr6xlz88e2wfs2d2drdy5a56fl60t9kn9h65e07k6ecmh7tgvkqdz5uyf nostr:npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4 nostr:npub1useke4f9maul5nf67dj0m9sq6jcsmnjzzk4ycvldwl4qss35fvgqjdk5ks nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr nostr:npub176gqu66z4qax6ejcju2dujdvs6gecerys47eu9jtj5aul8r7jwwsnqq836 nostr:npub14agjgx6a67trjefrvllewlju2l92pyttuud2pfhydjguc63zvehs88dadk nostr:npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tyc Last call today, and then nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 gets a task ticket from me, to start pricing out possible setups.
Here 😁 I'll add you in.
Paid in Lightning, of course.
Silberengel @Silberengel - 1d
Nostr
So, no SSH?
This does SSH and HTTP, apparently. https://git-scm.com/book/en/v2/Git-on-the-Server-Smart-HTTP
I was thinking, nsec-signing would be the third option.
Or, will it be HTTP and nsec, only? No SSH?
mleku @mleku - 1d
need to make a credential helper for that
We just need nip-98 for auth and basta. Adding nostr signatures would be gravy
Would be kinda neat to have the option to use a NIP-05 in commits, instead of email. One npub can have multiple NIP-05s and we could switch notifications from email to some sort of note.
Yeah, I'm just thinking about which capabilities the gitserver should have. 🤔
Silberengel @Silberengel - 24h
Like, use npub as the user.name and NIP-05 as the user.email.
mleku @mleku - 24h
the need for a consistent registry of name<->npub is pretty clear, nip-05 is not really quite the solution, because it has no reverse lookup (you can't find the nip-05 from the npub)
Silberengel @Silberengel - 23h
We're going to probably start off with email notifications and then switch, to get it going faster.
Well, the gitserver itself has a registry. I just know that git requires both a name and something containing an @, and we'd like to eventually not need to ask for an e-mail. And that adds something human-readable to the commit text. We can always use current nprofile data in the display.
mleku @mleku - 22h
there is such things as non-network identities using the user@location format, but anyway, the thing is that there is no consensus mechanism for tying names to nostr:npubs anyway... this would actually be a sane use of op_return then you could have the "location" being some code meaning "bitcoin blockchain" i'd sure be fine with spending a transaction to anchor my npub onchain to a name, just needs a scheme for superseding identifiers
i think this is the right way, it's a bit of a pain setting up email send on servers but a lot easier than building a new protocol
Silberengel @Silberengel - 22h
Would it be possible to include that in the registration Lightning zap? nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszdthwden5te0xgekzumyveshxe3jwgengvt8de38yungdf58wem8v9jxven8v9ekvumpv3nxzumpvesju7re0ghszrnhwden5te0v9j8yefwwd6j7qpq8pudjhdhhp2v8gxnkttt00um729nv93tuepjda2jrwn3eua5tf5sz3h4k8 would probably know a clever way to do something like that.
I'm not wedded to the NIP-05 address. Just seemed like one that most npubs would have or we could give them.
lightning LNURLs would be even better, yes! multi-purpose - identifying and enabling payment
yeah, it is a way to associate a DNS and a name to an npub, that is correct, the LNURL option lacks the npub association, but it has the ability to auth with it
