Let's not kid ourselves, if there was such cryptocurrency the sanctions would have been drafted differently and the end result would have been the same.
There has been a response in another ticket that they're harmless markers that have been around for a while, but it's hard to tell if they actually went through the data to confirm it.
An average user would download "Eurovision GP" expecting the voting functionality everyone and their dog knows is a major part of the experience and instead they get a gallery app.
OP's highly rated app was more than likely listed higher than the official app rated 2.8 stars hence user reports and its subsequent removal.
Trademark infringement is never a good idea, those other apps could get pulled for the same reason at any time.
Surely you know by now that Elon/SpaceX will get its fuel no matter what, even if it means trucking the fuel there, seems to me your best case scenario will increase net emissions.
Protecting the environment is not the point of this stunt, is it?
It makes sense to treat it as an error but the ISO standard is too vague on this and the libpng developers never "fixed" this[1], it issues a warning but otherwise just masks off the high bits. Firefox has a workaround[2][3], Chrome doesn't.
FWIW I do the same in my library[4], handling it as an error is problematic because it would mean the chunk gets discarded and then you can't even retrieve the values.
This is one of those awkward parts of the standard, the samples always take up 16 bits and decoders are expected to mask off the extra high bits, any 16-bit value was supposed to be considered valid. In the real world trash values are often written for transparency (tRNS) chunks that inadvertently match samples in the image when the extra bits are masked off, which leads to random holes in the image. In practice those chunks have to be ignored when the values are out-of-range for the given bit depth.
Moral rights are part of the Berne Convention, it's not limited to Europe.
This is only an issue when someone 1. is very negligent with redistribution 2. has enough negative implications for the author to take issue with it.
NixOS is a big, funded project, what's wrong with holding them to a standard? If they package it right then moral rights wouldn't be an issue for them, it's not exactly a legal minefield.
Not a lawyer, but I _highly_ doubt the MIT license makes any difference when it comes to the author's demands in this situation, he has moral rights (legal term) to the software.
You can't just make a mess of packaging someone's work and assume there's no legal avenue for the author, that's just naive.