-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/04/14 18:45, Ben Laurie wrote:
If it is delayed for all recipients, then causality cannot be
violated :-)
Here's a crazy idea.
Each client maintains a list of messages it knows each other
client has seen (because that client has told
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I've never come across a good way to display threaded conversations on
a small screen. Have you? Please share.
On a large screen, the best example I've come across is Reddit: clear
nesting, plus a parent link in every message in case the
On 29 April 2014 09:24, Michael Rogers mich...@briarproject.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I've never come across a good way to display threaded conversations on
a small screen. Have you? Please share.
On a large screen, the best example I've come
On 29/04/14 09:24, Michael Rogers wrote:
Hi all,
I've never come across a good way to display threaded conversations on
a small screen. Have you? Please share.
On a large screen, the best example I've come across is Reddit: clear
nesting, plus a parent link in every message in case the
On 29/04/14 09:15, Michael Rogers wrote:
On 27/04/14 18:45, Ben Laurie wrote:
If it is delayed for all recipients, then causality cannot be
violated :-)
Here's a crazy idea.
Each client maintains a list of messages it knows each other
client has seen (because that client has told it so).
On 21/04/14 16:22, Trevor Perrin wrote:
On Mon, Apr 21, 2014 at 6:24 AM, Ximin Luo infini...@pwned.gg wrote:
Suppose a simpler policy: a member-delete message takes priority over
member-add even if they're siblings. Since siblings only arise in the
simultaneous send case, where it's sort of
From my experience with mobile phones, the issues are that due to the screen's
small size, things like delineating the depth of a message in a thread or
providing ways to collapse/expand a thread have to happen within barely any
space to clarify the necessary UI elements.
What could be helpful
