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! π₯°
