Hi, to answer the second question:
The messaging service takes care of the order from messages in two different ways: 1.) All messages refer to the previous message logically to build up a graph structure which can be traversed. So you can theoretically use that to order all messages. However the problem is that different nodes can send messages in parallel, send messages while being disconnected and some other cases. So everything gets synchronized in a later stage. That means that there is no linear logical order of messages and messages arrive on receivement by your individual node. 2.) All messages contain a timestamp which can be used to sort them in a simplified way (when you know about the logical structure in the background). The applications I've implemented use this order because it is the most intuitive way for users to have their messages sorted. That means each application has to do that individually because it's a visual issue to solve. However keep in mind that given timestamps in messages could potentially be false when a user would modify the implementation of the service. Happy hacking Jacki On Thu, 2022-10-20 at 10:17 +0000, Lily wrote: > Hi! I've been evaluating gnunet for one of my personal projects and I > had a few questions: > > * I saw in the docs that gnunet uses proof-of-work in a couple > places (NSE and Revocation), would this work well on something like a > smartphone? If not, are there alternatives in the works? > * Does the messaging application guarantee consistent ordering of > messages across different nodes? > * I saw there was a social subsystem in the works, is there any > information about that public? > * How stable is gnunet, is it something that could be relied on to > build a stable p2p application on top of today? > > Thank you so much!
signature.asc
Description: This is a digitally signed message part
