Thoughts on update UX: maybe options should be "update now", "update later", "I don't use that functionality, remove it now".
-
-
I used *Service example because an end-user client machine should require approximately zero services running.
-
For things that are arguably needed, provide concrete simple language description of what will break if you remove it. Not vague bs.
-
For whom? Customer who can assess the risk and take informed decision? Not possible.
End of conversation
New conversation -
-
-
A failure at HCI, sure - the connection to system design is ever so slight.
-
The system design to HCI connection is that bad design makes it impossible for users to make informed decisions about security tradeoffs.
-
Users should be taught "uninstall any background cruft you don't need to reduce attack surface". Doesn't work with spaghetti service crap.
-
No need for spaghetti deps - systems aren't designed so all their components are self-contained.
-
This is what we teach people to create: abstract the common stuff of A and B into C. You don't use B, great. Want to nuke C? Sorry, nope.
-
Will the customer ever understand what C is needed for? Why do they need to, in the first place? Is that a good use of their time?
-
No. Rather it's a good use of the system designer's time to ensure they don't have to do that in order to keep themselves safe.
-
I completely agree
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.