part of why things are broken is because devs dont test on relays where they can see the logs.. they are just guessing what is happening.
Discussion
wish i could show you the logs easier nostr:nprofile1qqstwf6d9r37nqalwgxmfd9p9gclt3l0yc3jp5zuyhkfqjy6extz3jcpz9mhxue69uhkummnw3ezuamfdejj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tcprdmhxue69uhhyetvv9ujucnjd9nksarzdak8gtnwv46z7273e59, i didnt anticipate nostr being this broken after this many years.. lol.
but, it does give me some ideas for trying to help debug where it wont just be me debuggin the relay side of things. 😁
there is an idiotic mentality amongst programmers that log printing is a "weak" method of debugging problems and so you see in most codebases, logging is an afterthought if it appears at all, and trace logging is nonexistent
my code often has bugs that happen on such short time scales that i MUST use log printing to get post mortems when my code fails, and i just use it most of the time, and then sometimes i remove some of the logs once i'm confident the code is working, because often the logging for the debugging process can be very noisy and crowd out the next thing i work on
Log debug is useful! 💯 with you on that. Trust your gut
#NAK wasn’t doing the job for me so i had the LLM write me a python script and it worked like a charm in a few minutes. The neural-nets sure love their py.
💯 the more we have client devs who are also relay devs the sooner we are going to see progress
https://realy.lol is a total replacement, not all drop-in but a lot is drop-in for go-nostr
it definitely has less bugs in it, but it probably has some other bugs that i haven't found yet
i was hoping that nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z had actually caught me a bug in my codebase but after testing, no, it's client side not authing correctly and ... yeah... i'm not opening my relay up to the spambots that have resumed in earnest, because they are not whitelisted to post on my relay and taht's how it is always going to be
oh yeah, and i am now confident to say that you can use https://realy.lol in your projects with confidence, in fact, it is at this point now where i know there is bugs in there somewhere, but i just haven't got the time or opportunity to ferret these bastard things out, so i would very much appreciate it if people would start trying to use it, and yes, documentation is pretty sparse, but there is some in there, i'm very much welcoming any PRs that fix documentation comments and add actual static markdown documentation texts for things that don't fit into the API docs side
Ah, was it Nak or my CLI? Two different libraries doing the AUTHing. Maybe I need to pull nostr:nprofile1qqsqvcu68pkfcyq5y9mz9n9u7sys33835rpnuglc6mtg7j4lv40c7ugpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyqyg8wumn8ghj7mn0wd68ytnhd9hx2erc6wa new bug-fix and retry. Wine was also having problems.
i'm not sure, i think nak's got an issue that it isn't properly retrying after getting an auth-required ok,false
Also found out that nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmgd9ehgtnwdaehgu3wd3skueqyluj3x was right and my router is fucked up.
yay
he's good people and i'm glad he isn't offended by me saying mean things sometimes, i had muted him for some time because of his pesimism but then i'm pretty caustic about some things so fair's fair
thick skin from hearing mean words from people that mean well is a good kind of thick skin that i can definitely praise
i lost a job because others didn't have it one time, and the shit this guy said was obscenely stupid
most routers in general fall under the category of dogshit
especially with defaults like not being able to route between especially wifi clients IP addresses, even better when you can't turn that shit off
what can you expect from mass produced low-cost crap meant for the average person trying to have basic internet service
datacenter networking equipment is where the good shit is at, really
VLANs, proper IPv6, good firewalling, etc
for APs I find that some mid/high end stuff can be repurposed to run OpenWrt and works mostly fine
Oma's house has an old Telekom Speedport, and we're going to exchange it for a new Fritzbox.
fritzbox sounds racist
I currently still have DSL service and use my router as a shitty bridge, that is it
when it gets replaced with fiber, I’ll most likely connect it to my switch and then the proper router/FW
Only DSL, out here, unfortunately. The newest neighborhood has fiber. Oh well.
it's all retardedly fast fiber here in madeira... in fact, the main trunk from brazil and north america lands just a few miles east of me... i have 500mbit down 100mbit up here in this little shack right next to the ocean
Well, none of us at nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t are relay devs, but we're all relay enthusiasts, which seems to also help. We consider the relay devs and admins as suppliers and I'm big on supplier relationship management from my logistics and production background.
Nostr documentation is in shambles. I can’t get an LLM to do anything because it doesn’t have at docs to chew on :(