Skip to content
This repository has been archived by the owner on Jun 14, 2022. It is now read-only.

Clarify default parameters #85

Closed
l0b0 opened this issue Dec 11, 2017 · 2 comments
Closed

Clarify default parameters #85

l0b0 opened this issue Dec 11, 2017 · 2 comments
Assignees
Milestone

Comments

@l0b0
Copy link

l0b0 commented Dec 11, 2017

The form to manually add new entries comes up with the default algorithm options already selected (TOTP, 30 second period, 6 digits, SHA-1 hashing). This is great, but I think the form can still be improved a bit:

  • TOTP is a selection list even though there are no other selections, so it would be better if it was static text until and unless someone implements other options.
  • I've used a few OTP providers, and I don't think any of them mentioned the period, digits or algorithm settings in their manual instructions. I assume this is because virtually everyone use the same parameters for now. If so, then to avoid confusing users it would be better to hide these options behind an "Advanced options" thingie (deliberately left vague) until some other set of options become the norm. For example, after a few minutes' web searching I was only somewhat sure that these were indeed the correct parameters, and re-entering a 32-character string plus label (for example if I had thought that TOTP would use the now common SHA-256) is not fun.
  • I know someone must have put a lot of effort into the tagging feature, but it very much feels like overkill. I would bet not one in 100 users have more than a screenful of entries, at which point the tagging starts to be useful.
@RichyHBM
Copy link
Contributor

There is also a steam guard implementation hidden behind the secret features which is why the algorithm is a drop down.

I for one have about 30 entries and the tagging is basically what made me switch to andotp (I was the one that implemented it). If you activate 2FA on every site that supports it (which I recommend you do) they soon build up

@flocke
Copy link
Member

flocke commented Dec 11, 2017

  • As @RichyHBM already mentioned I added support for SteamGuard tokens hidden under the "Special features" (since there are certain limitations when only using andOTP and not the official Steam app). Also I plan to add HOTP support in the future (I currently don't have a lot of time but maybe over the holidays).

  • I don't dislike the idea of hiding the more advanced options. That would also clean up the dialog a little bit. I will try to get that in for the next release as it shouldn't be to hard.

  • The tagging feature was a much requested one and @RichyHBM spend a lot of time implementing it. It will definitely stay. By now I also have a lot of 2FA-enabled accounts and it is very nice to have a quick way of filtering them.

@flocke flocke self-assigned this Dec 11, 2017
@flocke flocke added this to the v0.3.2 milestone Dec 11, 2017
@flocke flocke closed this as completed in 11b9042 Dec 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants