I joined Lemmy back in 2020 and have been using it as @qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.
- 10 Posts
- 5 Comments
- qaz@lemmy.worldtoBuy European@feddit.uk•How much of your money is invested in evil corporations? Some advice for ethical investingEnglish2·2 days ago
Do you know where I can find information about highly EU SFDR-rated index funds?
Mag ik vragen waarom je voor Signal hebt gekozen i.p.v. Matrix, aangezien dat vaak gebruikt wordt op Lemmy?
- qaz@lemmy.worldtoTechnology@lemmy.world•Linux Foundation says yes to NoSQL via DocumentDBEnglish1·6 days ago
Why would they do that?
- qaz@lemmy.worldtoOpensource@programming.dev•[Open question] Why are so many ~~rust~~ opensource projects MIT licensed?English1·3 months ago
…developing for a platform that doesn’t allow LGPL3 libraries to be used because users can’t replace the LGPL3-licensed binary (ios, android, game consoles, proprietary hardware)…
TIL. I didn’t know that LGPL would add any additional restrictions except for inside the library
Explanation from HN in case anyone else is wondering:
In the case of the App Store, Apple is the one doing distribution, so Apple must also comply with the terms of the license (in addition to the app developer). Apple has decided they will not do that (that is, people they distribute to will not have the ability to modify the LGPL code, relink the final executable, and run it on their devices), so Apple cannot legally distribute binaries that contain LGPL code.
It only makes sense, then, that Apple should preemptively reject apps that link in LGPL code, as they know that they will not abide by the licensing terms.
It is not. The source is linked in the post.