-
Notifications
You must be signed in to change notification settings - Fork 10
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
DropURL length should be fixed #151
Comments
I am in favor of letting the user decide. Because users who use a mobile device would decide different than users who only use the desktop version. But instead of "less" and "much" I would write "little traffic and low anonymity" and "much traffic and high anonymity" and add a description for interested users below. |
yes a description is imho needed. maybe a ''button" until the user can change to traffic.... 'whats this' or 'more infos'. iam send you @audax a pm with a wording example |
In my current android version (from last Thursday) the description is actually wrong: questions: "how paranoid are you" and "how much traffic would you accept" -> answer: "less" should mean that many URL bits are used (=> few collisions => few users use one URL => little traffic) but it is implemented the other way around: "less" indicates few bits are used. |
what is the state of this ticket |
From my point of view if we fix the length to a certain value we (have to) answer the big question nobody ever answered regarding Qabel Drop: (when) will Qabel Drop scale (on mobile devices)? |
By allowing the user to chose the length of the DropURL, we reduce the chance for collisions and we have to explain what all that stuff actually means.
Is it really worth it or should we just use a reasonable default value?
The text was updated successfully, but these errors were encountered: