That's not even a dig, it's more an aspect of time spent and size of team.
The largest Nostr team (#GitCitadel) can produce the same sort of things, in the same time, in the same quality, as two devs working in full time. Or, as we do it, we can produce twice as many things, in parallel, in twice the time, because the efforts heavily overlap.
So, we can produce _and maintain_:
* Alexandria
* Sybil
* Aedile
* GitRepublic
for those who saw my messages about the sysop of #gitcitadel yesterday
the problem, as i saw it, was he doesn't understand that NIP-42 specifies that the client has to put the relay address, eg wss://realy.mleku.dev in the auth message, and when the relay is behind a reverse proxy, the reverse proxy has to tell the relay what address the client reached the reverse proxy through
i already have PTSD about how byzantine nostr protocol is in general, and retarded, and MY reverse proxy correctly works as you can see by simply using the one in the address i just named
i don't appreciate being treated like i don't know my subject matter by someone who thinks they are some kind of fancy fucking ops tech who clearly does not understand the nostr protocol and has never deployed a nostr relay that requires auth
and i especially don't appreciate it when i explained it all in detail, repeatedly, for the last month, and the dude doesn't even click the link to the http API docs, and nearest i can tell is because the dude has a phobia against #golang
he doesn't read the code, he doesn't read my instructions, and he doesn't run any of the NECESSARY tools that i stipulated were necessary, in order to do configurations like dynamically changing the logging in order to see what address the relay is receiving from the reverse proxy and why the auth is being rejected
it's not just "working on my side", it's how nostr fucking auth works, ok?
i refuse to work with this guy any further after he has repeatedly shown that he seems to be lacking respect for the person who builds the software he has been asked to deploy
if gitcitadel want to use my relay, they are on their own, at this point, unless they can persuade this guy to fucking pull his head in and actually follow SIMPLE instructions
https://theforest.nostr1.com (a community relay) and https://thecitadel.nostr1.com (a document relay), from #GitCitadel, are two of the Top-30 liveliest #relays, now. No spam, no porn, no scammers. Just real Nostriches interacting.
We are getting two more sets of mirrors, as well, hosted on different providers and run by different admins. And both relays also stream to different sets of relays, as well as to each other.
Together with your local relay (I recommend #Citrine 🍋 on Android), subscribers don't really need anything else. I only use theforest (inbox and outbox) and thecitadel (inbox), as my relays, now. This has caused my bandwidth usage to go waaaaay down.
https://image.nostr.build/16121dd755642ed1fbdfe64e9965ced7a5539fa0a56e1c8867a8afd15b4a5a0e.png
nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhkx6rjd9ehgurfd3kzumn0wd68yvfwvdhk6tcqypprj6m7h8z74maqe7jcnxd5cc8k9svzrvutnd0d3jlal9vakdn5yyupskm
As someone more specialized on test and UX, it saves me a lot of stackoverflow searching, which is nice, but I really have to sort of inch forward and constantly test because it occasionally breaks stuff or generates wrong solutions. The more time I spend writing the scenarios and tests, beforehand, the better the coding part is. The resulting code is better than what I usually write, but there's lots of room for patterns, tighter algorithms, and other architectural improvements.
Someone specialized on coding, probably feels that way about tests.
TL;DR -- It can leverage your current talent stack and even out your weaknesses, but a specialist would get better results. Since nobody is a specialist in everything, it's good that we at #GitCitadel can cross-pollinate the same codebase. Leverage upon leverage.
I'm now more convinced than ever, that this is going to have a bigger impact in making programmers faster and better, than in making them obsolete.
Showing page 1 of
3 pages
