Hi,is MeshMB just 1 to all messaging? Does it support n to all? For example I have a feed "first-responder" and all first responders will publish messages to this feed? Or has every identity an own feed? Or is the feed name the identifier?
--
You received this message because you are subscribed to the Google Groups "Serval Project Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.
To post to this group, send email to serval-project-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/d/optout.
The identifier we use is the same as the public key in your keyring.You *could* share the same public key between users, but there are a couple of edge cases that will trip you up eventually.We have considered how to handle private messaging between group members, or how to handle users who wish to use multiple devices. But we haven't found a design for the underlying encryption and transport layers that we think will work well.
On Fri, Sep 15, 2017 at 2:13 AM, Artur Sterz <goo...@artursterz.de> wrote:
Hi,is MeshMB just 1 to all messaging? Does it support n to all? For example I have a feed "first-responder" and all first responders will publish messages to this feed? Or has every identity an own feed? Or is the feed name the identifier?
--
You received this message because you are subscribed to the Google Groups "Serval Project Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.
To post to this group, send email to serval-proje...@googlegroups.com.