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

DropURL length should be fixed #151

Open
audax opened this issue Feb 19, 2016 · 5 comments
Open

DropURL length should be fixed #151

audax opened this issue Feb 19, 2016 · 5 comments
Labels

Comments

@audax
Copy link
Member

audax commented Feb 19, 2016

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?

@audax audax added the question label Feb 19, 2016
@roeslpa
Copy link
Collaborator

roeslpa commented Feb 19, 2016

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.

@hash13
Copy link

hash13 commented Feb 20, 2016

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

@roeslpa
Copy link
Collaborator

roeslpa commented Feb 23, 2016

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.

@jmt85
Copy link

jmt85 commented Mar 1, 2016

what is the state of this ticket

@roeslpa
Copy link
Collaborator

roeslpa commented Mar 1, 2016

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)?
If anybody can answer this, please set a default value. I belief nobody can answer this question because of the variable setting of mobile devices. Hence I would like to variably find out the answer by observing the behaviour (at least during the beta).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants