I just came across this old thread about public messaging and it raises some questions for me about messaging as a service/facility under the apps.
The discussion in that other thread seemed to indicate 1) that messaging was a “core thing” and 2) there would be direct interaction between users and core messaging, such as white/black-listing and applying filters and such.
I’m wondering if there is such an interaction, though. Aren’t all user interactions only with an app that then uses the core to accomplish the user’s wishes?
If that’s the case, then messaging is really between different running instances of the same app by different users – it’s never for direct user consumption. It’s up to the apps to wrap/send/unwrap their messages and present something (if anything) to the user.
If that’s reasonable, then it seems messaging should provide some kind of tagging capability for the app that created it. When a user logs in and runs the SAFEMail app, the app will find its waiting messages and possibly make a presentation to the user. This is where white/black-listing should happen, IMO. For the SAFEMail example, each message may consist of envelope information that is only enough to filter against while/black lists and possibly present an inbox to the user without accepting the mail payload until the user demands it.
Even if concepts such as white-listing are considered universal, they possibly mean different things in the context of different apps.
An app that is of a collaborative nature should be able to use core messaging to initiate updates across a group of collaborators that might not result in user interactions.
Very importantly, no app should be messing with messages for any other app.
Am I close?
EDIT for clarification: In referring to direct interaction between users and core messaging, I was referring to a design where the core messaging had features/API to suit direct user needs for particular use cases.