Rich Felker
@alxlg @aks @thomholwerda We really need better user-facing communication/UX explaining this distinction, why it's important, and how users can make informed decisions about where to obtain software from, how to use permissions to their benefit, etc.
The existing platforms all purposefully make permissions look like a chore, ala cookie clickthrus, because the goal is enabling the platform's actual customers (malware app publishers) to bypass users' consent.
Rich Felker
@aks @thomholwerda If the premise is switching to getting apps directly from their publishers rather than a trusted distro, then sadly operating a permissions system is needed.
Arguably this is evidence that the premise is bad, and actually distros were a good idea.
Alex L 🕊 🇵🇸
Distros are a good idea but platforms are too, they are everywhere and we need an app platform for Linux, a distro can't package all the software out there and you would need a sanbox for proprietary apps anyway
Akseli :quake_verified: :kde:
@thomholwerda the problem IMO is the shoehorned "security first" approach. The usability has been pretty much an afterthought.
Nobody should need to open a permission setting to use an app.
Thom, King's Field speedrunner
If your response to Flatpak applications regularly requiring arcane, obscure terminal commands to make them usable is "it's just a terminal command, way less bad than systemd so who cares", you're basically admitting Flatpak was never designed for users to begin with.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.