Thoughts on update UX: maybe options should be "update now", "update later", "I don't use that functionality, remove it now".
-
-
Replying to @RichFelker
"FooBarBobblerService requires an update for critical RCE." "Um, just nuke that shit from orbit. And all services while you're at it."
1 reply 0 retweets 3 likes -
Replying to @RichFelker
"Cannot nuke FooBarBobblerService, which you think you never use, but is actually a core system component"
2 replies 0 retweets 0 likes -
-
Replying to @RichFelker
A failure at HCI, sure - the connection to system design is ever so slight.
1 reply 0 retweets 0 likes -
Replying to @mfukar
The system design to HCI connection is that bad design makes it impossible for users to make informed decisions about security tradeoffs.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @mfukar
Users should be taught "uninstall any background cruft you don't need to reduce attack surface". Doesn't work with spaghetti service crap.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
No need for spaghetti deps - systems aren't designed so all their components are self-contained.
1 reply 0 retweets 0 likes -
Replying to @mfukar @RichFelker
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.
1 reply 0 retweets 0 likes -
Replying to @mfukar @RichFelker
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?
1 reply 0 retweets 0 likes
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.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.