- cross-posted to:
- opensource@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
Hello everyone,
I’ve been using Standard Notes on the recommendation of Privacy Guides since the beginning of this year, I believe, and it has truly been a fantastic experience. It serves my purpose perfectly, is truly cross-platform, open source, and lightweight. It was a real find, and I couldn’t be happier to have it installed. However, it seems that they are planning to change the licensing to one that restricts companies from abusing their code (which makes sense), but I wanted to know if this goes against the guidelines in terms of considering it recommendable.
I don’t really understand licenses, so correct me if I’m wrong, but with this change if the project becomes private, a fork couldn’t be created for all users who want to continue having the software format but not the backend… Is that correct?
Thanks
I did too, but because I’m broke lol.
That is true, but for the front end applications, if that is open source and has sound encryption then the server could even be proprietary, it won’t be able to break the encryption, so your data would be safe, maybe not so much for some metadata though.
In this case the apps were changed to be all AGPL as I understand, so that should be ok.Agree with all the rest, don’t like the maintainer’s attitude.
Edit: I was wrong, even the app is source available now (CC Noncommercial), not exactly good, but better than proprietary I guess