All Proton Drive apps are now open source | Proton
proton.meProton Drive’s desktop apps are open source, meaning you can review the code of any Proton Drive app for yourself.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 3K Posts
- 75.4K Comments
- Modlog
What does this mean practically
gpl v3 you can do pretty much anything but you have to put it the same license but it has like drm protections and Anti-Tivoization and also has some patent protections people find this license too strict
Its actually more restrictive, in a good way.
You can’t, for example, fork it, make changes, and sell that derivative software without releasing the source code
yeah but drm is too strict for some people and anti tivozation this is why linux did not do gpl 3.0 or later
It’s pretty much not reversible and the code is free to use, modify, and distribute forever. And if you do modify it you also must make those changes open source.
Very good news
It means it can’t ever become proprietary closed-source software (not without a major lawsuit).
deleted by creator
Any GPL violations would be reported to the Software Freedom Conservacy, who would go to court on the dev’s behalf.
There was a major lawsuit back in 2022 between the SFC and Vizio, and the SFC won.
Any new open source software is always a net positive.
But, there are a few small caveats (depending on how cynical/cautious you are):
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:
Alternatively:
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).
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. :)
IANAL, but AFAIK that’s incorrect. If you’re the only copyright holder, you can issue multiple licenses for your work. GPL doesn’t allow you to rescind previous issues, so anyone in possession of your GPL code can still modify and release it under the GPL freely. But it doesn’t prevent you from issuing your own work under a different license.
There isn’t usually much economic sense for most applications to do that because anyone can fork the project and distribute it for free. For Proton, since they still hold the server as closed source, they could simply introduce a breaking protocol change and all the forks would be useless.
The way I understand it is that they can relicense it and then publish it if they want, but the GPL would still fully apply to the previous versions.
The first question you cited seems to refer to any different organisation/individual making changes to the source code. And the second seems to refer to revoking the GPL for an already released version, which they would of course not be allowed to do.
This would make sense as ownership of the copyright would supersede a license.
“releasing the modified version to the public” would cover them re-closing the source and then subsequently releasing that newly closed source, so they can’t relicense it and then release the built version of the code.
At least not easily, this is where court history would likely need to be visited because the way it’s worded the interpretability of “modified” in this context would need to be examined.
Not a lawyer but in the scenario where proton closed the source but kept offering the build, even if gpl3 still applies since they’re the only copyright holder (no contributions) it’d only give them grounds to sue themselves?
From gnu.org:
Oh, yes but the DRM exemption clause means that you can backwards engineer the changes and continue releasing them under GPL
Edit: as an example we should probably be looking at the duckststion situation evolving right now:
https://vimuser.org/duckstation.html
Oh that is a SHAME.
DuckStation is such a wonderful piece of software too. :(
deleted by creator