holmesworcester

Let's revisit this after we upgrade libp2p.

I just saw hanging on leaving on Android too. No particularly special circumstances. Just testing an alpha.

If we take the approach proposed in simplification, QSS should block adding a sigchain with more than one user, because that user has not been opted in.

This should all be behind the "QSS enabled" feature flag env variable.

This prototype for the joining flow was missing from the epic, so I added it above: https://www.figma.com/proto/dSEZJr9crJjcV3ILogea9C/Join-from-invite-link---prototype?node-id=2811-2821&p=f&t=HxVuP1RPj5oW01TT-0&scaling=min-zoom&content-scaling=fixed&page-id=7%3A2510&starting-point-node-id=2811%3A2821

@anasouardini thank you for this request! > this app help me and other discuss our political issues without being arrested away from our families. Messages you send are encrypted end-to-end...

We definitely plan to support disappearing messages. Also, I recently learned of this paper that uses the phone's security module to limit password retries, for arbitrary passwords: https://eprint.iacr.org/2023/1792.pdf -- this...

@jgaylor this looks good to me and I don't think we need to do any of the things in #3 to start.

Let's try: 1. A version with "custom status", "recents", and "defaults" 2. A version with with just defaults and no custom or recent.

Another piece of custom status is prompting the user to update their status when they're back: https://www.figma.com/design/frxdNd42wV8kgXoiBExoqR/User-and-network-status?node-id=716-24251&node-type=canvas&t=2vRd0D6q7g50d2nJ-0 This can be broken out into a separate issue in the future.