Oddbean new post about login | logout Nostr often feels like being stuck in Beta Testing Hell because you can confirm that things don't work, but nobody cares that they don't work, so things don't get fixed and you just go from one thing to the next, like Yup, this doesn't work. This also. Oh, this is cool! Oh, nevermind. Doesn't work. That doesn't work, either, and.... yeah, this never worked, and it now it crashes my browser. There goes my cell phone battery, geez. Deinstall that... Actualize... actualize... yeah, doesn't actualize. Moving on... This doesn't work and the developer either died or moved to Timbuktu or has been abducted by aliens...
it's umm... well... the spinner might go away too soon and no response message. But it'll probably work. Takes quite a while because of rate limits and req limits. It reqs 100 events at a time and then tries again for since with the timestamp of the last event form the previous req. It does work. It will get most of them. But it's kind of scuffed and not great. Frontend is not the priority right now. I just have the framework in there build it up later.
should be now
But I think broadcasting doesn't work. Throws an error.
Broadcasting is a client action though right? It's just resending the event to your relay list. What error are you getting?
Timeout
What client are you using to broadcast it? It should just be sending the event back to the relay and it should handle it the same way as always. I just checked and it seems to be running. Wheat I still running a slightly older version from the current. I thought about nuking the database and starting fresh since it's the same DB from one of the way earlier versions and has some bad events in it.
Nostrudel
hm I just broadcast a global note to my local running relay and it worked fine. Inserted kind 1 in the database. Where are you seeing the timeout?
hm I just broadcast a global note to my local running relay and it worked fine. Inserted kind 1 in the database. Where are you seeing the timeout?
