this post was submitted on 15 Dec 2023
298 points (97.2% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54574 readers
423 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm going to go with the unpopular opinion, that all apps should have the subscription support model.
Especially open source apps!
Ideally the code is open, and under GPL or a GPL.
Unless you have a device completely disconnected from the internet, there needs to be constant development, to update libraries, to get security updates, to fix rare but critical bugs. Nobody, and I mean nobody, should be running a binary that never gets updates from 10 years ago, on a device connected to the internet.
I seen a variety of approaches to supporting app development, I think a lot of the pricing is targeted towards the richest people, ignoring the vast majority of the world. For open source apps having the app itself with a nag screen, or a supported version of the app that is just a recurring donation maybe a dollar a month.
All that being said, when the subscription ends, the app should still work at the last version, and the user just assumes the risk of running older software un maintained.
(I'm aware there's ways to mitigate the risk of unmaintained software, running in a very highly protected VM for example...)
Most users can't name a single reason why their programs should update.
They don't see risks in running unmaintained software. The developer does. I could get behind your all-subscriptions ideal, but if the user terminates the subscripition, he should be made unable to keep using the software. Hence why this cannot be the norm with Free software.
If the app doesn't have network access, though, the OS sandbox should be more than sufficient to keep it secure.
A calculator app should be safe to run without updates at least until the OS APIs undergo a breaking changes (which should take several years at least).
As long as somebody is maintaining the software, it really doesn't matter if it's the original developers. If somebody takes the code and rebuilds the software, they are de facto responsible / maintaining it.
Software such as signal, and Molly, mostly because they talk to a central server have minimum version requirements. So if you go too far without updating you can no longer participate.
I think from the internet health perspective, a nag pop up when a software hasn't been updated in it's a 6 months, saying this software is out of date and proposes a security risk, should be sufficient. This could be done by the app store, the operating system, or even the app itself