Distinguish use cases, secret, private and public (outbox vs blastr)

[mleku]

I think the reason why there is confusion over the issues of these message propagation styles is the lack of distinction between message types

• Secret Kind 4, 1059, 1060 and Application Specific Data should be following NIP-65 relay inbox/outboxes -this greatly reduces metadata leakage as well
• Public Kind 0, Kind 1, and most other kinds of public lists all need to be broadcast far and wide, as quickly as possible
• Private Communities where the intent is for them to be private to the members, should also follow a scheme like NIP-65, except perhaps this list can be regulated by the community owners (such as so they can be relays run by community members only)

As an aside, a content addressing scheme like Blossom, IPFS, or any other public distributed database would be an even better place to put the Public messages.

Making a clear distinction between the message propagation strategy would help clients also evaluate which to use for a given case. Relay devs can also then start to look at how to share the cost of public relay data and relays themselves then become hot caches for the newest stuff that their users are posting or requesting.

[mleku]

i want to make a couple more distinctions as this continues to get more clear in my mind:

clients should have a configuration to stick to outbox or to do broadcast/wide search for public types of events (notes, articles, market, lists) - for two reasons:

• wanting to limit bandwidth usage with a small relay set (mobile devices - for also battery conservation)
• wanting to limit relays used to ones that are paid

as a consequence, paid relays really should be aiming to broadcast public types of events and to aggregate them so that paid relay users get all the events and never get stuck with a client unable to find a recent event