Okay, here's a new note
Discussion
Yep, it's not showing up yet.. π€ nadar said the same thing to me... Unresponsive, so I'm doing some latency checks, doesn't seem like the relay takes anywhere near 15 seconds to respond though. Looking into latency too. Nostr.watch says all good too..
check this out, at least for nadar mystery, it dies from too many connections looks like..
So, could it be that my relay is just too far down everyone's list?
OMG, that could actually be it. Ingwie is closer to the top of the list and forest is closer to the bottom.
The list is really long now and they all probably start writing from the top and slow down halfway. Good grief.
It explains it for the nadar tool yeah, the developer console spews a ton of errors meaning it's overwhelming the browser with too many reqs..
but that doesn't explain why the blast is not reaching as much as you'd expect it to right? I'm also not sure blastr can deliver reliably to all relays, or if it has errors at times or what it's relay list currently is.. I had never really tried to track what it's doing before. π€
Yeah, I was wondering about NADAR because he says he marks as unresponsive after 15 seconds, but it only ran for 4 seconds. What happened to the other 11 seconds? π€
nostr:npub1cuyfg04rf9gemn6kk2juzw8anmgxftt9mhk2ucu5a27c0f30zacqggzw8d that's your tool, right?
Seems to work sort of sporadically. I wanted to try it out because I've been thinking about turning theforest into a private blaster (among other things, I have a list LOL), so I've been researching how they work.
Note to self: don't use the nostr.watch list. π
Is it possible for me to program something for it?
It could also be maybe blastr detects that our relays don't accept all messages so it penalizes them or removes them from a list after too many rejections.. I'll read it's code some more to see if it has back off logic like this.. (cause I don't think it's blasting to nostr21 either since I switched to paid)
That could also be true. π€
I only noticed this issue because I connected the blaster and it started out writing.... and then stopped.
I read the code for blastr, I'm not a rust programmer yet or anything, I couldn't quite understand what happens when blastr fails to deliver a message. I wanted to know if it would cause the message queue for that relay to stall out or not..
If I could see the logs, then I'd know a lot more about how it is working, but I'd have to run it and it requires cloud flare (ick). π
I'm working on getting around using it. Makes me sort of uncomfortable to think of my shitposts landing all over the globe. π
Ya haha, it's not the best really.. cause the messages go out to 600+ relays and if someone responds or reacts on a relay you're not on you won't see it ..
It's original purpose was for zapping I think.. and supporting NWC.
I don't really hate on blasting anymore, I used to not like it because it seemed lame and inefficient.. but clients have been slow to find a different paradigm. I do use relayable still, and those relays send their feed to blastr as well because they're an aggregator feed. δΉβ ΰΌΌβ β―β βΏβ β―β βΏβ ΰΌ½β γ
Yes, very messy.
I looked over the relay server(s) last night and today. As far as I can tell they're operating nominally, working decently hard(er) compared to a few months ago but not fully loaded yet. Any delays you're having could just be from international ping /network delay.
I've been working on getting monthly billing sorted out and that will free up some server resources I think once some of the relays disappear because they've been abandoned or taken over by rogue botswarms..
That and I want to have a support chat, so I've been messing with coracle's groups and stuff like that.
soon soon soon ππ
Cool! π₯°