randy408

You mean half a dozen add-ons are available

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.

https://support.google.com/maps/thread/152846276?hl=en

original post was deleted

https://support.google.com/maps/thread/152809911/terrorists-...

https://old.reddit.com/r/ukraine/comments/t4copf/they_are_us...

Someone with a line to the Maps team should contact them immediately

Google does not own .lol either.

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.

Obvious trademark infringement.

This needs more detail, what is the body of the mail supposed to show?

Did you run an experiment? How was it run?

Is this between protonmail addresses?

Obviously you haven't played online video games.

Based on my experience Microsoft Store will kill the app to update it.

FizzBuzzCoin?

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?

Doesn't USB4 also introduce its own optional PCIe tunneling spec which isn't exactly the same as Thunderbolt?

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.

[1] https://sourceforge.net/p/png-mng/mailman/png-mng-implement/...

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=428045

[3] https://searchfox.org/mozilla-central/source/image/decoders/...

[4] https://libspng.org/

> bKGD overflow, tRNS overflow

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.

This reminds me of Google hiding ProtonMail from their search results: https://protonmail.com/blog/search-risk-google/

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.

Moral rights are unalienable in Europe, I'm not gonna quote a full paragraph from Wikipedia[1] here.

https://en.wikipedia.org/wiki/Moral_rights

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.

Could this method be used to image exoplanets or is that still in the theoretical realm of the Solar gravitational lens[1]?

[1]: https://en.wikipedia.org/wiki/Solar_gravitational_lens

The RPi 400 only has 4GB but the board is integrated into a keyboard with a power button and a big heatsink, if you go for a (m)SATA SSD + USB3 adapter you still have a second USB3 port, those things can easily push 300MB/s with UASP, the official power supply should be enough in this case.

Dual-license typically means (A)GPLv3 with the option for a commercial license.

Writing a naive PNG parser is easy, but handling all the corner cases is harder than it should be, e.g. text chunk fields can be variable- and even zero-length:

1. https://github.com/randy408/libspng/blob/3439bf5c173421b1af4...

2. https://www.w3.org/TR/2003/REC-PNG-20031110/#11iTXt

I'm using 1.6.36, the most obvious speedups should come from RGBA 8-bit PNG's, that codepath doesn't rely on compiler optimizations.

> Is there a way to disable this multiple-pass approach to get a slightly larger image that is generated faster?

Use png_set_filter() with PNG_NO_FILTERS.

> This one makes it look nearly equivalent to zlib

I don't know how squash is set up, but decompression performance depends on which library created the DEFLATE stream (see https://github.com/zlib-ng/zlib-ng/issues/326#issuecomment-4...).

A 3-byte layout can be worse for performance, I think the simplest solution would be to add a special format that always matches the PNG's format, that way you always get RGB from RGB images, grayscale from grayscale images, etc. This wouldn't require a conversion step.

This is what I use for benchmarking: https://github.com/libspng/spngt, my platform is Debian 10, GCC 8.3.0 with -O3 on an i5-4670. I use -SPNG_SSE=2 because that targets SSE2 instead of SSSE3, this matches the Debian build of libpng, both are linked against zlib-ng. The results I get for medium_rgb(a)8.png and large_palette.png are the results on the charts.

For now it's either 8- or 16-bit RGBA, adding more output formats adds complexity and requires more test cases. What's your use case for a 3-byte layout?

No, the letters are spelled out, the "s" stands for simple.