La dernière version de FerretDB (1.18.0) vient de sortir, avec une gestion basique d'OpLog ainsi que d'autres fonctionnalités intéressantes. FerretDB se donne pour mission d'ajouter la compatibilité MongoDB à d'autres bases de données, dont Postgres et SQLite. Les nouveautés de cette version rendent FerretDB compatible avec davantage d'applications et de cas d'utilisation. https://blog.ferretdb.io/new-ferretdb-v118-support-oplog-functionality/
@alex i guess its affero like requirement is too broad. It requires the code of separate software (e.g. automation) on the server to be conveyed, even if the server operator should have the right to keep it private.
@dragestil@fsf I've heard people say "it's what people incorrectly believe the GPL already is"
The main issue I see with it is that they could try to sue for having binary blobs in your kernel or something. But I think later revisions clarified it.
I don't really have a problem with forcing Amazon to open source their SaaS as a contingency of the license. In fact I would prefer it.
@alex I think it is a optimisation problem of maximising meaningful copyleft requirement subjecting to it still respecting the 4 freedoms. I wish there's a mathematical proof that (a)gplv3 is the solution to this optimisation problem (if that is the case). Then we can use this proof to prove that sspl has gone too far. @fsf
@alex >Is MongoDB's SSPL license really that bad? Yes.
>I kind of like it. Of course you would.
>I don't really have a problem with forcing Amazon to open source their SaaS as a contingency of the license. In fact I would prefer it. No, the SSPL doesn't require that, it doesn't even say "open" in it.
If you want amazon to release their SaaSS modifications as free software for your free software, the AGPLv3-or-later is the license you want.
amazon just stopped using mongodb and wrote their own after it became proprietary.
>But I wish he would remember his youth for a second and then think again. Same, I wish he would remember his youth and call a proprietary license, a proprietary license without holding back.
"13. Offering the Program as a Service.
If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge, under the terms of this License. Making the functionality of the Program or modified version available to third parties as a service includes, without limitation, enabling third parties to interact with the functionality of the Program or modified version remotely through a computer network, offering a service the value of which entirely or primarily derives from the value of the Program or modified version, or offering a service that accomplishes for users the primary purpose of the Program or modified version.
“Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available."
Part of freedom is being able to use software privately (using software as part of SaaSS to do other peoples computing is not private usage) - the SSPL badly violates this principle by demanding that you provide the source code of your own private editor that you've only ever used yourself to edit some config files (or any other kind of software that falls under the broad range of software defined).
@dragestil >Then we can use this proof to prove that sspl has gone too far. The SSPL isn't written with freedom in mind.
The whole idea of the license is to be impossible to comply with, to allow MongoDB to demand money for exceptions off any business that uses the software.
Previously MongoDB was licensed under the AGPLv3, but too many businesses were just complying with the license terms, or pointed out their existing compliance and telling them to sue if they had a problem, rather than forking over money for a license exception.
In order to resolve these rent-seeking failings, MongoDB added an impossible to comply with proprietary clause to the AGPLv3 and removed the parts about GNU as required and as a result, every attacked business has no choice but to pay the license exception rent.
It saddens me that people can't see through such moderate level of proprietary trick.
@Suiseiseki Engaging in bad faith and then writing huge walls of text you expect me to read after your negativity. Your autism has gone too far sir. So outside.
@dragestil I can't find any concrete details, but I believe amazon just complied with the AGPLv3's requirements, as it's really not that hard to make it so that the DB and some software that merely inputs and outputs records to that database are separate.
amazon has now developed their own proprietary DB that is mostly compatible with mongodb now.
@Suiseiseki Can you remind me what amazon did to the agplv3 mongodb? Did they manage to offer a modified version as a service without conveying the source to its users? If so did they pull some trick to do it legally? @alex