4 ms·
And if only developers understood UX. The "lie" the author was complaining about was that Firefox is miscommunicating what it did: It warned that a concrete fi
by xg15 8y ago
And if only developers understood UX.
The "lie" the author was complaining about was that Firefox is miscommunicating what it did: It warned that a concrete file was containing malware when it actually found a suspicious domain.
Depending on context, that might make a huge difference - e.g., if a user got such a warning for a file they uploaded themselves, they might get the wrong impression that their system is compromised.
As the author noted, simply describing the actual threat would clear this up.
> Sure, there are some costs to false positives, but they are dwarfed by the cost of false negatives.
This strategy has blown up a number of times already. If you present too many false positives, users might lose trust in you and ignore your predictions altogether.
- deathanatos 8y ago> And if only developers understood UX. I've upvoted you, since I think your point is good, I'd just add that as a developer, I've found myself on more than one occasion pushing for the type of UX being advocated here, and getting pushback from designers/PMs. Typically, the issue I run into is a desire for the UX to be "simple", sometimes simpler than the system underlying it actually is (or is even capable of being), and so instead of clear and correct messaging, you get simplified and incorrect messaging. (My current example of this would be ZIP codes. People like to simplify them to a geographic area in their heads, and then think of them as polygons, and then from there, think you can ask "is this lat/lng inside this ZIP?"; ZIP aren't polygons (they're defined as segments of roads) so answering that question requires approximations; those approximations are sometimes wrong.)
- ssivark 8y agoIMHO, the most reasonable solution is to have a link for “More details” for the interested/advanced users to dig into. It’s hostile for software to fail because of incorrect assumptions and then give them no way for the sensible user to handle the collateral damage.
- ryandrake 8y agoYea, that s happens all the time in software. It’s the developer’s job to push back and explain the probability distribution of the results to the designers/PM so they understand the algorithm’s limitations, and everyone’s job to fight for the user. It needs to be a conversation, not a contract. Designer: This label is required to say what store the user is at given his location. Developer: the location sensor is imprecise. We could have 20m of precision or worse. The store location data is also known to be inaccurate and incomplete. We can provide top 10 candidate stores with their probabilities. The “top” one we return could be 95% likely or 35% likely. Your move! Bad Designer: Too much numbers for my brain. We’ll just show the top result. YOLO! Better designer: We could only show a result if it’s above a certain threshold. Or we could show top 3. Or maybe we need to talk about changing the requirement. Better developer: There may be other signals and inputs we could use to help make the results more confident...
- xg15 8y agoI generally agree, though in this case, I'd agree with the yolo designer. If I consulted Google Maps and it told me I'm with 48.25% likelihood at address A, with 39.81% likelihood at address B and with 11.94% at another location, what exactly am I to do with this information? I think Google Maps actually shows a good design to communicate the uncertanity: They show the uncertanity as a blue circle of varying size. It's visual but (more importantly) gives you as a user the ability to reduce the uncertanity with their own information. E.g., if you know you're at an intersection and the circle covers only one, you now have a precise location. In general, I'd say, it's important to know which context the information is used.
- ozim 8y agoUnderstand security, if there is malware in one file on your server you burn down the server and set up new one. If your machine gets infected you format all because it is insecure by definition. You might even need to throw out physical machine... If you get one it downloads ten other and you don't know which one will pass your virus scanner. It is not fun and games anymore, silly nerds having fun are not doing it. It is actual crime and really bad guys that would kill you without blinkink an eye are doing malware. If there is one infected file on your domain you consider whole domain compromised.
- tomsmeding 8y agoWhat you say is true, but how is this relevant to the discussion at hand?
- yodon 8y agoIt speaks to the argument that “if this site is serving up infected files, all files it serves should be treated as potentially infected”
- sammoth 8y agoThat would include domains like dropbox.com or drive.google.com then?
- yodon 8y agoSecurity is always complex, and simple rules always have flaws. That doesn’t mean simple rules are always bad, it just means people who build systems around them do need to understand they need to do more than just blindly follow simple rules. I’m pretty sure you’ll find FF doesn’t alert on those sites, because they are being handled by a more complex rule than a vanilla low or medium traffic site.
- ozim 8y agoFunny thing is article is saying "Unfortunately, this message isn’t always accurate. Apparently, sometimes this message is an outright lie.". So it is not like this domain hosts one bad file and it got flagged, it is apparently more often if it "sometimes .. is .. lie".