Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QSS: User should be able to opt-in/out #2443

Open
holmesworcester opened this issue Apr 15, 2024 · 4 comments
Open

QSS: User should be able to opt-in/out #2443

holmesworcester opened this issue Apr 15, 2024 · 4 comments

Comments

@holmesworcester
Copy link
Contributor

holmesworcester commented Apr 15, 2024

UPDATED

We are adding QSS (Quiet Storage Service) to support iOS notifications, speed up joining, and provide an alternative mechanism to Tor for moving community data.

For community creators:

  • Community creators should be: prompted to add a server when they invite members.
  • This prompt should explain the benefits of the server, explain that Quiet will not work well on iOS without it
  • They should be able to use their own server, not use a server, or use ours.
  • The prompt should appear until they add a server or until they choose "don't show this again".
  • Community creators should also be able to add a server in settings.
  • We should never contact QSS if they don't choose to use a server.
  • They should have to create an account.

For invitees joining:

  • Invitees should see a clear notice that a server is being used. (For now, we will not allow non-Quiet servers to be used. In the future we will also want a clear warning when a server is being used that is not Quiet.)
  • It should be clear that Tor isn't being used
  • If a server is being used that is not Quiet's server, they should see a clear warning of this.
  • They should see links to terms of service and a privacy policy, and be able to agree to them.
  • If a community uses a server, they should not be able to not use the server, since this will make the community unreliable for iOS users.
@holmesworcester
Copy link
Contributor Author

Another optional thing we can do here is to consider #2442

@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Next Sprint in Quiet Apr 19, 2024
@holmesworcester holmesworcester changed the title User should be able to opt-in/out of Quiet Storage Service QSS: User should be able to opt-in/out Apr 19, 2024
@holmesworcester
Copy link
Contributor Author

holmesworcester commented Apr 19, 2024

Here's some work in progress:

https://www.figma.com/file/y8h6w8PYR9jyI3zjYHL9Cl/Mobile-%2B-desktop-%2B-prototypes?type=design&node-id=1427-34497&mode=design&t=qxsYkljhpdNnRgwz-0

... But in the course of that work I had a better idea:

When people join the community, we can tell them on the username screen, before they start the network or connect to anything, what the "network approach" is of the community they are joining. That way only the community creator has to choose.

@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Design - Awaiting External Feedback in Quiet Dec 2, 2024
@holmesworcester holmesworcester moved this from Design - Awaiting External Feedback to Design In Progress in Quiet Dec 4, 2024
@holmesworcester holmesworcester moved this from Design In Progress to Design Backlog in Quiet Dec 4, 2024
@jgaylor
Copy link
Collaborator

jgaylor commented Dec 23, 2024

@holmesworcester unclear what's next on this, it's at the top of the design backlog. I'm skipping for now until I get more definition on next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Design Backlog
Development

No branches or pull requests

2 participants