wat. it seems to be abusing nostr relays for proxying traffic via ephemeral events. this is an attack on nostr, adds unnecessary load to already bandwidth-constrained public relays and makes them harder to run. I will have to add ephemeral note blocking to noteguard and strfry now =/
There's a similar problem with draft events. I would say this problem is not about ephemeral events specifically.
The main issue is I don't think I can block ephemeral events with strfry's write policies, but I could be wrong. I might need to update strfry. Draft spam is at least handled by rate limiting?
It's just a kind range, so you should be able to block it. Rate limiting should work the same.
I'm not sure it would fall into the write policy because the event is not persisted
maybe I'm wrong. will test...
I think it will work, but strfry is still forced to parse and process each message to some extent before it can reach the policy filter.
I may need to finish proxy mode in noteguard: https://github.com/damus-io/noteguard/issues/9 then I can do more advanced stuff like this... 🤔
Draft spam on every single character or keystroke seems a bit much.
Maybe we have specific dedicated relays for NWS events moving forward if this type of service seems to take off and be useful and used?
Oh noes here he comes, nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gprpmhxw309akk7mnpvshx5c34x5hxxmmd8gurqwpsqyxhwumn8ghj7mn0wvhxcmmvqyvhwumn8ghj7urewfsk66ty9enxjct5dfskvtnrdaks7vj9m5 the little fucker, ruining your grand vision with practical concerns. nostr:nevent1qqst7d3atqe26dfpx2zntks32vtqh59ccvsysxr98cnef92zfkqnd5qppemhxue69uhkummn9ekx7mp0qgsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3grqsqqqqqp9crp4u