Messaging systems

Hi

I am looking for some technical explanation of how various messaging systems will work. Would secure messaging between an app and an iot device work using the same infrastructure as secure text messaging. Would data be sent, stored in a vault then relayed or is it a direct relay between clients.cant seem to find any info on this. Thanks in advance.

Hello,

Data, which can be used as messages, is stored in vaults. As I understand it, the clients must ‘poll’ the SAFE network to detect the new ‘messages’, stored in these vaults. See for example the Safe Mail Tutorial Application.

2 Likes

Thanks. Do you know of any literature to read about messaging and polling?

I hope the documentation contains the info you are looking for:

2 Likes

Yes, this should not be the case for long though. A logged in client has a group that knows it and they should eventually push messages to that client. It’s just not been prioritised yet, but I feel this will happen.

14 Likes

Thanks. I ve read a lot of these already but some I haven’t yet so I will be thorough and re read all. Looks like there is a messaging module in client library but maybe it’s not confirmed yet. I will check the white papers tomorrow. Thanks.

1 Like

I am wondering what the limits of this system are though. What will messages cost and can it be used for anything with a relatively high throughput,an Iot device constantly streaming data for example?

3 Likes

I suspect that there will be a lot of temp data, not stored but held in quorum of peers for as long as they are alive. This temp dat should then be actually stored and paid for, or deleted. The trick will be the app devs picking up on that delete point and deciding to store (at cost) or not. Again we need to take care of spammers and flood attacks, but I feel that is a simple fix.

12 Likes

Found some useful info regarding messaging in the “peer to peer public key infrastructure” whitepaper if anyone eles is ever looking.

3 Likes

This temp dat should then be actually stored and paid for, or deleted. The trick will be the app devs picking up on that delete point and deciding to store (at cost) or not.

Ahoy, me again…

This does make sense, it seems messages should have a format than normal data to not overload the network with messages. Am I right in thinking it would then be up to the recipient device to reupload the message?

If so, heres a couple of questions:

  • What if one device is running and receives the message, but I’m away from that device and want to receive the message on my phone when I turn that on? Setting the first device to automatically reupload would solve that I guess.
  • If the recipient device receives the message, stores it in RAM, then crashes, how does the network know to resend the message?

Maybe there could be an opt-in/out scheme whereby user-selected types of message can be marked as important and therefore saved by the network in a file? I would happily pay to have my received messages stored that way (​: Edit for clarity: saved by the network as in, before it reaches my computer.

Also, I’m guessing eventually all this will be handled by apps running on the network through distributed computing rather than individual computers?

Hold on, here’s another one, sorry:

  • If the messages aren’t necessarily stored as normal data on the network, does that mean it would be plausible to build a character-by-character messaging app? It would be really cool to see incoming messages as they’re being typed — I feel this would help connect people and reduce social anxiety in some cases.