• 23 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle
  • The only thing which F-Droid reports is that it uses jawg.io for visualising the map tiles and that is considered non-free is because it is… commercial?

    This is the quote from the Streetcomplete github:

    Since mid 2020, JawgMaps provides their vector map tiles service to StreetComplete for free, i.e. the background map displayed in the app.

    Personally I don’t care that much about FOSS/non-FOSS but IMO a reason like that is least of my concerns when looking at open source. If they’re providing a free (as in money) service to an open source app then that’s perfectly fine.














  • From what I’ve understood SSPL is a ridiculously ambiguous license, it’s extreme copyleft. It’s not just “open source the tooling you use to host the software”, it can also be interpreted to mean “open source all the hardware and firmware you use to host the software”. No one wants to risk going to court for that so corporate wants to use SSPL licensed software.

    AGPL is the best license you can go for IMO.



  • In very basic terms - GPL means that any modifications you make to a code base and distribute to public, you need to keep the license as GPL and open source all your modifications.

    Once cloud started becoming a thing, the cloud vendors went “Well ackchyually🤓, the code changes we’re making are hosted on OUR server so we’re not technically distributing them to the public. So fuck you we have no obligation to make them open source”.

    Which is why AGPL exists so even server side code needs to be public. Since the application in question here is a backend service, it’ll always be used server side and so any forks need to be open source.


  • Normally a breaking change means after you apply the change it’s not easy/straightforward to rollback to the older version if you want to do that for whatever reason.

    For example, a new version is released and underlying database table or structure changes. You upgrade properly, and find the new version has some bugs (or you simply don’t like it). If you want to use the older version again until the newer one is fixed it’s not a matter of simply point to old version.

    As the database structure has fundamentally changed underneath in the new version, when you put back the old version it simply doesn’t understand the new structure and might stop working. You need ways to be able to make the DB structure compatible with the older application.

    If the application is stable the devs might provide ways to do this. But since this is an alpha… You’re on your own.

    TL;DR it means the older and newer version of the application aren’t strictly compatible with each other


  • From what I understood the company who owns Nginx decided to give CVE ratings to experimental features, but those were for the stable branch. The dev disagreed because they were “experimental” but the company wanted to give them anyway because it was the stable branch used in production.

    I don’t understand what was so bad about this direction that the company wanted to take that the dev threw a hissy fit about corpos bad, decided to leave, and start his own fork. It’s an insane overreaction IMO, maybe I’ve misunderstood something so IDK which is why my opinion is that the dev is a moron.