Something to mention. I'm thinking the quickest way to get this done is HTTP only. So I hope most people would be okay with that. I'm not sure what protocol ngit uses for the git stuff.
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.
Discussion
Nostr
So, no SSH?
This does SSH and HTTP, apparently.
I was thinking, nsec-signing would be the third option.
need to make a credential helper for that
Or, will it be HTTP and nsec, only? No SSH?
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.
Like, use npub as the user.name and NIP-05 as the user.email.
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)
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.
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
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.
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
I for one would highly prefer no email at all if possible, but I know that is probably shooting for the stars as requests go.
We're going to probably start off with email notifications and then switch, to get it going faster.
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
Yeah, otherwise we'd have to delay the gitserver setup.
Someone could always choose to wait for the npub setup to finish, if they don't want to use email.
i'm fine with email option, you gotta do what can be done sooner to get a thing into a state of usability
let's be clear, this is beta, and early signups are beta participants, we are interested because we want it bad and are happy to have bugs and report them and get the thing working
Yeah, it's gonna be an ongoing construction site, for a few years, probably. 😂 But a useable one, promise!
Just setup the repo for the project and gave nostr:nprofile1qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcpr9mhxue69uhkzafwwp6hyurvv4ex2mrp0yhxxmmd9uqzqqm9x092su3hd9rdfe8aafxp5pzpak3cegkem9qhhvmqqm96406ct9x0dz a ticket, listing the guinea pigs -- errr... I mean, customers.
Already so many feature requests, that I made the ticket into an epic, rather than a story.
if you guys make this thing work so i can have hosting i'll redirect realy.lol to the gitcitadel when i can make my repo public
i hate github, always did, and that went 100000x when microsoft bought it to feed their AIs to try and build skynet
Yeah, I've been using it for a year, now, and I'm grateful that I soon won't need to rely on it. And other "free" versions are weirdly political or have terrible performance and stuff.
I only got on it to respond to NIP stuff and write issues, and that's turned out to be a bit of a nothingburger.
there is nothing important going on, on github, per se, i mean, yes, many great software projects there but the freedom minded people are getting pretty mad at this situation being under the control of the most malicious software company in the world, who, as you have observed, seem to be trying to build the codebase for skynet
Yeah, whole thing is getting creepy.
We want to publish our stuff, but I really chafe at basically being forced to publish on there. I also just hate email and logins and etc.
You always have other options. As a Catholic you know how to make the hard decisions in order to defend yourself from evil in all its forms. Sometimes you need to make the hard decisions and use alternatives. There are other ones out there. You can do it. I have faith in you.
we are building it, stay tuned
and as soon as you have replication i'll fling that thing onto my VPS
I mean, it probably doesn't matter, if we don't setup email, since git hardly uses it. Don't know, if it really matters.
making nostr or lightning based auth for login is the most important i think
email notifications are of little value, but nostr based notifications are kinda useful but i don't think there is any model for how to do that properly either so...
email as 2fa is fine, and as an account ID is fine
Yeah, I'm just thinking about which capabilities the gitserver should have. 🤔
I'll take a look at this. The issue I keep running into is that every guide assumes you are running a private server for yourself, or a completely public server. We need a protected public server, the most complext thread model of course XD
SaaS model is what we need XD
we have some disagreements but someone more familiar with C will have a much easier time of getting proper git servers running... i had one built on a Go git library but it started having some problems when there was a new version of git, some encoding change or idk what... anyway, bravo to nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7