Ah shit, I thought it had reverb but it doesn't seem to :(, my bad.

Get any equalizer app (e.g. Poweramp Equalizer).

There's only incentive to do that if the mempool is empty. If the mempool is full, there will be plenty of transactions for both the first miner and the next miner.

Wait... This entire paper only makes sense if the mempool is near empty. If the mempool is full, then there is no reason to mine an empty/partial block because there will always be transactions left for future miners.

So basically:

• Mempool full = miner would mine full blocks just like intended.
• Mempool empty = miner would mine empty blocks but that isn't a problem because there are no transactions to process in the mempool.

What's wrong with that though? BTC handles forks just fine. Eventually one fork will win out and life will continue on as usual.

The bigger issue this paper presents is that miners become incentivized to mine empty blocks. But can't you just enforce a minimum transaction count on blocks?

I think we generally agree but I just want to clarify anyways. I'm not saying we should use PNG to store frames from videos.

What I am saying however, is that we should replace PNG with a modern lossless image format that is more flexible so users don't have to deal with these issues. All this colorspace stuff should be automatically handled and I shouldn't have to worry about it not being lossless. If I want to save a frame of video, I should be able to do it using an image format that everybody recognizes and accepts, it should not be a huge hassle and it should be fully lossless.

There's no real reason why you shouldn't use PNG for a frame of video. I'm not talking about using it as a video format, I'm talking about extracting a frame from a video and sending it off to an editor for inclusion in another video or image.

As a user, I would expect that I could use the most popular lossless image format if I want to losslessly share a frame from a movie with someone.

Of course I do agree that we need adoption of other image formats. We really should not still be cramming everything in PNGs or JPGs in 2023.

BTW that still uses Google's proprietary gesture typing library internally: https://github.com/wordmage/openboard/commit/46fdf2b550035ca69299ce312fa158e7ade36967

There's still no good FOSS alternative to Google's library though so it is what it is.

It's still bad compared to modern lossless algorithms. PNG is very old and even though PNG encoders have evolved, it is still fundamentally a decade behind modern lossless compression algorithms.

For example: JPEG XL in lossless mode compresses at least 30% better than PNG.

Also, PNG is not actually lossless in many cases. PNG only supports RGB colorspaces. If you try to store anything that's not in an RGB colorspace (e.g. a frame of a video) in a PNG, you will lose some color information as colorspace conversion is not lossless. Example of someone running into this issue: https://stackoverflow.com/q/35399677

JPEG XL supports non-RGB colorspaces so you don't have this problem.

JPEG XL came after WebP. It's more of a successor and less of a competitor.

That said, in the world of standards, a successor is still a competitor.

A significant number of subreddits shifting to private caused some expected stability issues, and we’ve been working on resolving the anticipated issue.

How in the world does setting a bunch of subs to private crash the website?