Oddbean

not agree, they are the third parties in that case, ipleak should be technically addressed, not mitigated by social protection. No serius dev would based any choice on the fact that someone is doing something without consent.

i have been working for most of this year so far on projects involved in offloading event storage to publicly accessible databases i see events as a public data, and unless the relay is specifically offering to restrict access to the events it stores, they are public, and not being propagated is more of a problem for users than not being propagated you know the saying "better to be talked about than to not be talked about" there is also the matter of public interest in the case of technical and journalistic event content obviously DMs and app specific data should not be broadcast but ... and yeah, i've talked about this and i hope eventually someone will get it, there needs to be a distinction in event kinds where they can and should be broadcast notable event kinds that should be propagated are nip-65 in/outboxes and kind 0 user metadata, these two combined make it possible to find people's notes without requiring distribution at all, but they themselves should be broadcast