Oddbean

▲ ▼

 NIP-11 does have an "icon" URL, i think it might be meant for a bigger logo and is separate from the small favicon that e.g. nostrudel will show in overviews, but i'm also not 100% how things work here

▲ ▼

 getting a new error on some event pushes:

invalid: must be greater than or equal to 1 tagValues at "[3].#a"

▲ ▼

 Thanks. Is they for any specific kind or tag? Or search queries?

If yes, I would be happy to have the detail of the event or query.

Also, sometimes Jellyfish errors are due the hardware, network and devops issues, we are actively working on them.

But code issues may take more time to fix since we are working on our own implementation.

▲ ▼

 i managed to interecept it, this is the request/response:

["REQ","OJ957lpN",{"#e":["d8318134bc5f45280e9e88f413972733b7684f18e12d995f2c791db7f46bdd8c","4eb0e2b8d2b496ead92bb58cdf38baba9cfc2ed95c2ec83fbe880b3ac26cede6"],"kinds":[9735]},{"#a":[],"kinds":[9735]}]

["NOTICE","invalid: must be greater than or equal to 1 tagValues at \"[3].#a\""]

(it could very well be nostrudel making an invalid request, but can't remember seeing it from other relays)

▲ ▼

 Ops, #a tags requested to relay is empty and error is valid. I think other relays ignore invalid requests and focus on other fields instead of making errors for better UX. Robustness principle!

We will consider that. Thank you soo much. 🔥🧪

▲ ▼

 i think this can be useful to debug client problems, though i agree the errors could be confusing for "normal users"
i'll look into reporting this as a nostrudel issue, thankyou !

▲ ▼

 fyi https://github.com/hzrd149/nostrudel/issues/213

▲ ▼

 Yes. We will fix it to handle this small mistakes from clients. But that's good to report them.

▲ ▼

 Me too, soon I'll check client codes to find out how exactly they obtain these informations.😵‍💫