Vitor Pamplona2d agoHey nostr:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uqkvamnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hkuur4vgchvdt4veuksdrvddjhxmr80puxxcmvvuuxvvrg0fsh56rpwumhyumjdpmxvut40pax6vnxdvmrgcehxf58que5x4hrqa348a38ymmpv33kzum58468yat9qywhwumn8ghj7mn0wd68ytfsxyhxymmvwshx7cnnv4e8vetj9udmam06 nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppysprpmhxue69uhhyetvv9ujuen0w4h8gctfdchxvmf0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj754rj0e, there is a bug on relay.fountain.fm where the relay returns 500-1000 random events every time the filter has a `q` tag, like this. ["REQ","test", { "kinds":[1], "#q":["123412341234"] } ] We do this all the time when searching for quotes of the events the user is seeing at the moment. Which means, as the user scrolls, a new note shows up, fountain gets a query and returns 500 unrelated events. Huge data usage for nothing.
Replies (0)
No replies yet.