 | Aegis Authenticator | 395 Members |
| Discussion surrounding the development of Aegis Authenticator | 48 Servers |
| Aegis Authenticator | 395 Members |
| Discussion surrounding the development of Aegis Authenticator | 48 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 Jul 2024 | ||
 Bald Dev joined the room. | 20:11:20 | |
| Bald Dev | Hi all Would like to know about #923. Showing past/ future totp along with current one. I think, the proposal should be accepted. | 20:29:14 |
 michaelschattgen | In reply to @blackbaal:matrix.org It's been a while since we've discussed this internally so I'm open to have another look at this. I'm still leaning towards our initial thought about this issue; most services have a 90 second time window in which your codes will work. Meaning the previous, current and next codes are being accepted. I've never had any issues with the codes from Aegis not working (I tap to freeze the code). Is there any situation where you really need to see codes other than the current one? In my opinion the UI will look extremely messy with 3 codes per entry. | 20:37:39 |
| Bald Dev | Yes, 3 codes per entry would be messy. I got the idea from ente and thought to raise a issue. Few of the services have 30s period only, for which I wait for progress bar to finish and enter the new code. Hence I was expecting if we could add next code like ente. Maybe we can make it flexible, 1. to hide 2. Show next 3. Show previous for user to choose | 20:50:04 |
| 31 Jul 2024 | ||
| michaelschattgen | Download qemu-system-x86_64_faWgxMiKr0 - Trim.mp4 | 00:32:53 |
| michaelschattgen | In reply to @blackbaal:matrix.orgI've been trying a few solutions to this issue this evening and just finished this prototype. Would swiping an entry be sufficient enough for you? We still have to discuss this issue internally but in my opinion this might be a good solution without cluttering up our UI. Please let me know! | 00:34:36 |
| michaelschattgen | So swiping an entry temporarily increases or decreases the window offset. This allows you to see any code of the future or the past. | 00:35:30 |
| Bald Dev | In reply to @michaelschattgen:matrix.orgSeems a plausible solution, but it might create a confusion that which code is this? From UX perspective, it should have a state indicator too. | 13:10:21 |
| Bald Dev | Just noticed +-2 as part of indicator, but doesn't seem intuitive. | 13:13:25 |
| michaelschattgen | In reply to @blackbaal:matrix.orgThis was just a prototype so I'm sure there are things that could use some improvement, however I fail to see how it isn't intuitive. The animation clearly shows which direction the code is shifting towards and the +-1 pops up as soon as you swipe the code, showing you the offset of the window. I'm not saying we will implement this solution, but I think it's a step in the right direction without cluttering up the UI too much. | 13:19:02 |
| Bald Dev | In reply to @michaelschattgen:matrix.orgYes the prototype is in right direction. I am just suggesting that explicit is better for a normal user. As a dev, UI like +-1 and swipe action makes sense but not in general | 13:27:13 |
| Bald Dev | https://f-droid.org/packages/io.ente.auth/ Reference images doesn't look cluttered to me. I think a Poll can clarify user's intent. | 13:31:18 |
| michaelschattgen | We definitely could spend some time on this issue figuring out what the best way to handle this issue could be but in my opinion this definitely looks cluttered | 13:45:55 |
| michaelschattgen |  Download image.png | 13:46:00 |
| michaelschattgen | Besides that, we have take into account that we have 3 other view modes which we don't want to exclude from features like these. | 13:47:03 |
| michaelschattgen |  Download image.png | 13:48:47 |
| michaelschattgen | It would look worse on this smaller viewmode for example. Thus why I came up with the idea of swiping the code to see the next/previous ones, it would work in every viewmode without cluttering up the UI. | 13:49:26 |
| michaelschattgen | Then we also have users that have their devices font size set to a bigger font than default, the code is already spread out on multiple rows for these users | 13:50:28 |
| Bald Dev | Will swipe work properly for tiles view? 🤔 | 13:52:10 |
| michaelschattgen | Yes. | 13:52:32 |
| Bald Dev | Ohk | 13:52:53 |
| michaelschattgen | There are just so many complications and obstacles for something that we don't see have an issue with. We never ran into the issue ourselves that we want to use old/newer codes, which is why I initially asked why people feel the need to see codes other than the current ones and to be honest I'm still not really convinced we need to incorporate this. | 13:54:08 |
| michaelschattgen | * There are just so many complications and obstacles for something that we don't have an issue with. We never ran into the issue ourselves that we want to use old/newer codes, which is why I initially asked why people feel the need to see codes other than the current ones and to be honest I'm still not really convinced we need to incorporate this. | 13:54:16 |
| michaelschattgen | * There are just so many complications and obstacles for something that we don't have an issue with. We never run into the issue ourselves that we want to use old/newer codes, which is why I initially asked why people feel the need to see codes other than the current ones and to be honest I'm still not really convinced we need to incorporate this. | 13:54:22 |
| Bald Dev | Reasons - Main : to handle 2FA expiry duration of all sites. 1. few sites have 30s period or longer codes, which finishes as we type the code. So, by showing new code one can type ahead of expiry. 2. Some allow for past codes, so showing those codes without any user intervention. | 14:04:26 |
| michaelschattgen | Aegis allows you to freeze codes upon tapping which basically solves this, right? 🤔 | 14:07:47 |
| Bald Dev | In short, users expecting minor convenience improvement. | 14:08:11 |
| Bald Dev | Freezing won't show new code. | 14:08:43 |
| 1 Aug 2024 | ||
 Mr_Spade joined the room. | 12:37:44 | |
| 2 Aug 2024 | ||
 @lantizia:mozilla.org joined the room. | 15:23:09 | |