Eugen Rochko
AdventureTense@Gargron Even the term "Side loading", makes it sound non-standard and risky. Which of course, it doesnt have to be.
Joe W@adventure_tense @Gargron My best friend migrated his parents to Linux (20 y ago). The separation of admin and user accounts actually worked, software did not assume you were admin all the time, and he could let his parents only install software from trusted repositories. There is absolutely a case to be made for locking down the system. Don't forget, this is a pretty technically minded echo chamber we are in, what works for us is bad for others.
But I agree: It should be possible to do stuff!
But I agree: It should be possible to do stuff!
Ethan Black@drchaos @adventure_tense @Gargron I'm a believer in "locking" things down so that in order to install apps from unverified sources, you need to use the command line.
So, it indeed is unlocked, and rights are preserved; but, the system is built so that if you're savvy enough to know when it's safe to bypass the system's security checks, you need to be savvy enough to use the command line.
Best of both worlds in my opinion.
@golemwire @adventure_tense @Gargron ... and have the root password... Otherwise you get the new(?) "please use [win]+R and [Ctrl] + V to fix your computer" thing.
@drchaos @adventure_tense @Gargron I think that "PEBKAC" exploit existing is a neccesary evil that is possible when the user has rights and thus freedom. Removing their rights is just out of the picture in my opinion.
But truly it would be great if manual-control / command-prompt interfaces gave a warning when opened, saying that it gives them manual control and may be dangerous when in the hands of non-experts (+ a 'Don't show again next time' option).
Invoking sudo on #MacOSX comes to mind.