|
|
|
|
|
by dozzie
2899 days ago
|
|
> It's an important distinction because if the software isn't at fault, [...] Though the software is at fault. It created a false sense of security,
misleading the users. What else in Arch just feels secure, but in fact is not? And then, if the users around the software generally exhibit a jockey
attitude, you get the whole environment built in a similar manner, not
a robust one. The software may technically not be at fault and technically
could be used in a safe manner, but you won't get much exposure to that, any
such use will be cumbersome and difficult (because nobody uses it this way),
so you still should stay clear of the software. So no, you don't get to
separate the users and the OS/distribution. |
|
AUR never tried to pass false sense of security, it is explicitly declared as not supported everywhere.
> And then, if the users around the software generally exhibit a jockey attitude, you get the whole environment built in a similar manner, not a robust one. The software may technically not be at fault and technically could be used in a safe manner, but you won't get much exposure to that, any such use will be cumbersome and difficult (because nobody uses it this way), so you still should stay clear of the software. So no, you don't get to separate the users and the OS/distribution.
Except it is not, experienced users of Arch community vocally recommends new users to not blindly trust AUR, and the dangers of AUR is also documented everywhere. This is also one of the reasons that yaourt is shamed in public Arch communities like /r/archlinux, since it defaults to poor security behavior.