6 ms·
I just wish I could convince them that specifying a monospace font is not the same as specifying an unambiguous font, and it matters because not everything is c
by Brian_K_White 7y ago
I just wish I could convince them that specifying a monospace font is not the same as specifying an unambiguous font, and it matters because not everything is cut & pastable.
In the password fields, I don't know how anyone either writing or using a password manager doesn't consider unambiguous glyphs to be critical. It's a password manager not a greeting card designer.
They think they have solved this by specifying the font to be monospace in the password fields (maybe notes too I don't remember).
I submitted an issue complete with pictures of passowords written in monospace fonts in KeePassXC where the characters are ambiguous.
It shouldn't even require pictures to convey the problem. Once someone says "the property "monospace" and the property "unambiguous" are two dufferent properties. It's an unsafe and in fact broken assumption.", you'd think that would shed all the light necessary.
But what more do you do when tbey don't see it even WITH pictures? Fork it yet again? Just to add a config option to let the user or desktop integrator select an arbitrary font for some display fields?
What really bugs me is, they didn't say "yeah that would be better but it's hard and we don't know when anyone might get to it" No, they think it's already done.
Failing to get that idea across really made me wonder about the parts of their work that aren't so visible.
- csande17 7y agoFor context, here's the issue report the parent's talking about: https://github.com/keepassxreboot/keepassxc/issues/1771 https://github.com/keepassxreboot/keepassxc/issues/1771
- Dreami 7y ago(to GP) I really have to say, this is not how you should ask someone else to fix a problem. Going at the developers on a personal level is NEVER a good thing. If it was my project, I probably would have closed the issue completely after you insulted me this personally.
- beart 7y agoRegardless of the conversation, it really bothers me when the person locking a thread also posts the "last word" before locking it, allowing no chance for rebuttal.
- phoerious 7y agoWe explicitly specified Menlo in the new release, because it is rather unambiguous (and monospace). I don't really understand your criticism.
- Jon_Lowtek 7y ago> I don't really understand your criticism. I think i understand what this is about. It starts with this code (inlined for brevity) > QFont passwordFont = QFontDatabase::systemFont(QFontDatabase::FixedFont); and this distinction of characteristics > "fixed" and "unambiguous" are different things (note: there is no QFontDatabase::UnambiguousFont) and an actual bug somewhere else as the root cause > broken in lubuntu 17.10: resulting font was neither fixed nor unambiguous. which finally resulted in: > this kind of utility needs the option to specify a specific font but things got heated between "not a bug: fix your system" and "this utility can be improved" ending in personal insults and everyone being annoyed by each other despite showing great love for the application (just foss things)
- politelemon 7y agoIt looks like you've got a bone to pick with them not having agreed with you. I had a look at your Github issue and I agree that this is down to your _system_ not the application; your screenshots don't demonstrate the problem either.
- thawaway1837 7y agoIt’s not a bug with the app, but the OP’s is a reasonable feature request. The ability to specify an unambiguous font for password fields, for example, makes absolute sense. And the app defaulting to the monospace font is not an appropriate solution, because a user may pick a monospace default which isn’t unambiguous. Not every app requires unambiguity the way a password field might, so to require the user to change their default font is not a great solution. There’s a reason emacs, vim, etc allow you to set your own fonts specific to the app that’s different from your DE defaults. That’s because they have very specific requirements that may be different from what you’re looking for in a general default font for your DE. The same is true for something like the password field of a password manager app. Honestly, certain devs in this case started insulting the OP well before the OP said anything unreasonable, probably because for some reason they came up with the idea that the OP thought this was a heinous bug when, as they clarified, that was an invention on the reader’s part with no grounding in anything the OP said, who was not calling it a bug, nor by any means calling it heinous. Of course the discussion went off the rails after that with the OP unnecessarily getting personal, but I can see where their frustration came from even if they shouldn’t really have acted on it.
- benhurmarcel 7y agoI just tried it, that's what it looks like on Ubuntu: https://imgur.com/a6s0QEB https://imgur.com/a6s0QEB I don't see how that's ambiguous.
- iszomer 7y agoIt's needed for smaller/lower resolution screens. I sometimes mistaken an O for a 0.
- m-p-3 7y agoAgreed, a an "unambiguous" option when generating a password would be nice, along with some colouring depending if it's a letter, a number or a special character would be nice.
- brewdad 7y agoThis might be my favorite feature in Bitwarden. Numbers are colored differently than letters. Red may not have been the best color choice but not being colorblind myself, I can't say whether it's an issue in practice.