- cross-posted to:
- foss@beehaw.org
- cross-posted to:
- foss@beehaw.org
Rip. Time to delete all my standard notes.
Not surprising. Proton seems to be exploiting the niche of “privacy” . I haven’t seen anything to the contrary other than turning over metadata due to court order.
exploiting
Yes, that’s the right word for it. :)
Proton’s alternative to Google Docs getting closer? 👀
It will really hard or impossible to reach the level of development that ms and google have in their cloud collaborative products. They don’t have the resources like the mentioned two monsters.
A single coder made photopea which is near feature parity of photoshop. I think the Proton team can figure out a docs suite
It may require intense passion and a manic episode to do something like that with one coder or a small team, which is hard to arrange bureaucratically.
Or a burning hatred of proprietary systems
So… this was the plan of the Standard Notes guys all along? Now it makes sense why they never made open-source and self-hosting a true priority.
Let’s see what Proton does with this, but I personally believe they’ll just integrate it in Proton and further close things even more. The current subscription-based model, docker container and whatnot might disappear as well. Proton is a greedy company that doesn’t like interoperability and likes to add features designed in a way to keep people locked their Web UI and applications.
Standard Notes for self-hosting was already mostly dead due to the obnoxious subscription price, but it is a well designed App with good cross-platform support and I just wish the Joplin guy would take a clue on how to design UIs from them instead of whatever they’re doing now that is ugly and barely usable.
Doesn’t proton open source everything they do? Iirc, proton mail, calendar, vpn, drive, and simplelogin are open source under GPL v3 on github.
Yes the clients are open source but the server part is closed and it’s a big missing part
Now, better to be 50% oss than 0%, but it’s not a community effort. Most commits are done behind the scenes and then published when app is released. This causes most pull releases to be rejected as the problem was already fixed internally months before. It’s more like “source available”
Ah ok, yeah they should definitely be more transparent then.