broadcast message must not reset ephemeral timer
broadcast messages should be ignored on ephemeral timer updates and must not reset the timer.
(reason is that they are sent as bulk message similar to BCC:, each recipient gets the same message and user-specific settings cannot be added that way)
How does the recipient recognize that it is a broadcast message?
good question, the sender can, but the receiver currently cannot afaik.
i think, we should consider to give up the idea that others recipients are hidden on the protocol level (this is the reason, we currently do not encrypt broadcast, which seems to be the wrong tradeoff, also after some one-to-one discussions the last years, it was changed here)
if we do not try to hide other recipients on the protocol level, we can encrypt, send sth. as is-broadcast and grpid along and also flag broadcast messages similar to "forwarded". that will also solve the multi-device issue (and this issue)
nb, for other readers: as that easily pops up, for "channel vs broadcasts", there are exhaustive discussion on github and at https://support.delta.chat/t/broadcast-group-distribution-list/1203/34
How does the recipient recognize that it is a broadcast message?
Replying my own question, with #4644 this issue will be fixed because broadcast messages will go to their own chat. Once it is merged we can close it.