mleku on Nostr: i have some fixing to do in client code that i have not used before the current work ...
i have some fixing to do in client code that i have not used before
the current work i'm doing is a spider, which is searching systematically through the relays listed in relay list events in order to try and get as many of the relay list event (kind 10002, mainly, but also 10050 the dm relay event kind) for every user who has been automatically allowed read/write access to #realy when my pubkey is the owner
and i'm looking at this client code and 🤦♂️ damn you fiatjaf and your loony unnecessary concurrency
the current work i'm doing is a spider, which is searching systematically through the relays listed in relay list events in order to try and get as many of the relay list event (kind 10002, mainly, but also 10050 the dm relay event kind) for every user who has been automatically allowed read/write access to #realy when my pubkey is the owner
and i'm looking at this client code and 🤦♂️ damn you fiatjaf and your loony unnecessary concurrency
quoting nevent1q…wxl6BLAT BLAT BLAT
yeah but lol so i find one example and when i use the envelope unmarshal as i expect it's fine, everything is decoded correctly, so there is something wrong with something else that is being used
probably a good moment to find these bugs before i start using said code, it seems to be client code, and i cannot see for the life of me what is triggering it except for that there does seem to be a feature that this involves the value of a "r" tag having a terminal `/`
i kinda was hoping to find some obscure bug in relay code but i think i'm now just debugging hardly tested client code