Same.
EveryMuffinIsNowEncrypted
Oh that is a SHAME.
DuckStation is such a wonderful piece of software too. :(
I...can't tell if you're serious or making a joke. Lol.
There's another comment that mentioned a landlord that was published exactly 30 seconds before yours. :P
^(Please^ ^keep^ ^in^ ^mind^ ^that^ ^I'm^ ^just^ ^teasing^ ^you.^ ^Obviously,^ ^there's^ ^no^ ^way^ ^you^ ^could^ ^have^ ^known.)^
What is "big iron"?
- "Because Proton are not accepting contributions, they own all the copyright, so can make the code closed source again if they want to (that wouldn’t affect the already released versions, but future versions)"
They can't do that actually. They can close the source, yes, but if they do they can't then release the new closed-source version to the public.
From the GPL FAQ page:
Does the GPL require that source code of modified versions be posted to the public?
The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.
But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL. [Emboldened by me.]
Can the developer of a program who distributed it under the GPL later license it to another party for exclusive use?
No, because the public already has the right to use the program under the GPL, and this right cannot be withdrawn.
- "They could likely take down any derivative on iOS, since Apple will always take instruction from the copyright holder, for GPL’d code"
Does the license prohibit this? Definitely. Could they get away with it? Probably. Though I'm uncertain Proton would go that far. I mean, if they wanted to prevent forks, they wouldn't have released the source, let alone with the GPL3 license, which requires the right to make modifications (as that's one of the Four Freedoms).
- "Since the builds are not reproducible, there’s no guarantee that the binaries they distribute are built from the source code"
Technically true, I suppose, though again why they would do that is beyond me. If they didn't want forks, they likely wouldn't have allowed forks.
Again, this is all assuming I'm understanding the GPL FAQ page correctly. If I'm wrong, I would welcome someone smarter than me to correct me. :)
Well yeah. I mean, computers back then weren't just spyware in a Scooby Doo mask.
That's how I see it, too.
First make it so you can eat. Then you can deal with any privacy holes you need to fill.
I wonder how these people sleep at night
With stacks of hundreds under the pillow.
Alternatively, pay a service (one that's actually reputable!!!*) to watch your shit for you. (Still keep an eye out, of course, but this at least takes a LOT of the load off.)
For example, I pay a 12.95 USD a month for a service provided by my credit union (way better than a bank) and I can input whatever information I want monitored. They do that and let me know as well if they detect any shit going down. They also give me an update email every month letting me know that something has changed (or, likewise, if nothing hasn't changed :) ).
I started doing this way back in 2018 when my wallet (containing my ID, debit card, social security card, everything) was stolen. (Gods, that was a fucking nightmare.)
*None of that LifeLock bullshit. AFAIK that's just marketing fluff mainly. (Somebody correct me if I'm wrong on that.) In any case, I don't trust any service that is provided by the same fucking company that owns Norton. shudder