Ephemeral message scope
acurrieclark opened this issue · comments
Ephemeral messages are currently emitted with a channelId which is not used to scope messages in any way.
My understanding of the current setup is that this means that 2 independent peers connected via (for example) a central server, would receive any ephemeral messages that the other sent, even if they were accessing a completely different set of documents.
If this is the case, would it be useful to be able to scope messages to a specific document, such that it is only sent to peers with whom the document is already being synced?
Are there any other scenarios?
Scope to documentId for now.
Need to include a test to check that you still get broadcast messages even when no doc sync has occurred