• 0 Posts
  • 40 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle



  • You’re approaching a relevant part (that big corporations have an overwhelming power advantage in this “negotiation”), but “small artists never use copyright law” is just wrong:

    Without copyright law they couldn’t even sell their content (or more accurately: they could sell it, but the big corp could simply copy it and sell it better/cheaper due to the economics of scale).

    So without copyright the smaller artists would be even more boned than they are right now.




  • IMO copyright as a concept makes sense, but it’s duration should be significantly shortened. In todays short-lived world most works lose the majority of their financial value after a few years (let’s say ~10) anyways. So to allow artists to benefit from their creations while still allowing remixing or reasonably recent content I’d say some sane compromise is necessary.

    Either that or massively expand (and codify) what qualifies as fair use: let anyone reinterpret anything, but don’t allow verbatim copying.







  • I was answering under the assumption/the context of of “Amazon wants to release an Android-based OS that doesn’t contact any of Googles services”.

    So, when I said “easy enough to remove” that was relative to releasing any commercial OS based on AOSP, as in: this will be one of the smallest tasks involved in this whole venture.

    They will need an (at least semi-automated) way to keep up with changes from upstream and still apply their own code-changes on top of that anyway and once that is set up, a small set of 10-ish 3-line patches is not a lot of effort. For an individual getting started and trying to keep that all up to do date individually it’s a bit more of an effort, granted.

    The list you linked is very interesting, but I suspect that much of that isn’t in AOSP, my suspicion is that at most the things up to and excluding the Updater even exist in AOSP.





  • I just checked it out. That licensing documentation is a mess. They say that it’s released under the AGPL, but not all of it? So what they are saying is that the whole product is not actually under the AGPL. I wonder if their “freeware” part can actually be removed without major loss of functionality. Because if that’s possible, then you could simply rebundle that one.

    But I suspect it exists exactly to “taint” the open source nature of the product.


  • Note that they said “not intended” and not “not allowed”. you are perfectly within your right to use the program under the GPL without licensing it otherwise.

    But the company would prefer if you paid for a license (and support). If you weren’t allowed the use you do, they would have said as much, but they didn’t.

    This is a common business practice with open source software and I don’t particularly think it s “wrong”, but the fact that they are apparently trying to use confusion to make it look like you have to buy a license for commercial use is very icky in my opinion (but is unfortunately also very common).