Realtime messaging is what we take for granted on the internet, but we’ve learned about the flaws of the centralized architectures used to implement this functionality. So I’m wondering, whether Safe Network (SN) is capable of providing the same service (w/o the flaws)?
I heard quite some time ago that SN would have (realtime) communication, in addition to the existing data storage/management capabilities, but I’m not sure what was exactly meant by “communication”, and as a newbie, I’m unable to find such APIs in the code, e.g. something that allows one to send a text directly to a user by their ID on SN (would this be “SafeID”?).
I did briefly check if there were existing examples/demos on the forum, and I’m aware of Patter. Without going through them thoroughly (e.g. I don’t know React), I could only get a very rough idea, but it seems to me that, so far, the demos are implementing communication or chatting via data storage and retrieval, basically. E.g. the receiver has to periodically fetch the data, after the sender puts the data on SN, is that right? Again because I’m new to all this, I’d appreciate it if you guys could correct any of my misunderstandings here.
Although I don’t know anything about the technical aspects of distributed, realtime messaging, I think the “UX” we would want is something more intuitive than the current approach (which in a sense seems to only “emulate” chatting via sort of “publishing”, with access control). Conceptually, we would prefer something more straightforward, like sending a text over SN to some destination ID, where the receiver just “gets it” without having to actively retrieve it periodically. I guess another way to put it is, can SN “push” messages to a specific set of targets? (I know I’m probably abusing the terms. But I guess that’s the point, please correct me.)