what about for bandwidth/load time optimization we add a "don't send me these event IDs" field tho
i don't think that's server side at all, that's just "i already got these" you wouldn't believe how many times nostr relays send the same events over and over again even when the client has cached them
That's a good point but would make REQs huge, no?
not with bloom filters, and they aren't that expensive to compute... you could make both options, most clients don't have to process the hex IDs they have them verbatim so it's only a memory cost, and a small bandwidth cost... average events are around 700bytes, so 32 bytes to avoid 700bytes is still worth it, also if the event type is a list, in some cases that can be an extraordinary saving
also, some reqs are already huge, only outdone by follow lists
