Serious answer, I’m not sure why someone would run a VM to run just a container inside the VM, aside from the VM providing volumes (directories) to the VM. That said, VMs are perfectly capable of running containers, and can run multiple containers without issue. For work, our Gitlab instance has runners that are VMs that just run containers.

Fun answer, have you heard of Docker in Docker?

You should just be able to go into the comment section, then click the image from there. Doesn’t matter if it’s empty, but it’s currently the only workaround other than what you mentioned.

I absolutely appreciate all the work done recently, but I was wondering if there was any chance we could get thumbnails that, when clicked, don’t have ?thumbnail=1500&format=webp appended to them. For some posts, it doesn’t make a difference, but for longer posts, or posts with smaller text, it makes the image blurry unless you click into the post comments, and select the image there. It feels like a needless extra step when trying to open an image.

I’d love it if clicking on the thumbnail of an image opened the raw image, instead of the compressed view, so instead I have to go into the post and click the image there for full resolution. It’s especially noticeable for larger images with small text.

I’m guessing it’s the same thing on the backend, but the issue is the exact opposite of what I have. The left drawer works fine for me, but the top is the problem. Could be with something I’ve set differently for layout, but I’m sure if he fixes it one way it’ll fix it all.

The only bot option you can control through Sync is to hide PipedLinkBot. Actual bot hiding needs to be done through a website. The Sync settings provide hiding bots in the search, but it doesn’t appear to be an implemented toggle yet.

I’ve heard that and decided to look myself. According to their fundraising report for fiscal year 2021/22, they received $165.2m from 13m people. Removing “major gifts,” $20.8m (only 18,000 people), it comes out to a bit over $11 per person. Additionally, they got $13.5m to their trust, the Wikimedia Endowment (average donation of $13.91/person). So definitely, most of their income comes from small donations.

As to whether they need it, according to their FY 21/22 financials statement, they’re sitting on $198m in assets ($51m of which is cash), with an additional $52m they can’t touch because they’re long-term investments. However, their expenditures made up $154m. In total, they’re reporting they netted $8m last year for additional assets, but assuming that everyone stopped donating, Wikipedia would probably die in a year, even with liquidation of short-term assets.

Yeah, that’s the exact behavior. Thanks for pointing it out.

After clearing the cache, this works. However, while I did mess around with the settings, I didn’t for this specific post because I had done so before, and just didn’t have time to submit a bug report on it. This means that even if you have the correct settings, it may decide to serve you the compressed version anyway, and the only way to get the uncompressed is to manually clear the cache, restart the app, hope you can find the post again, and roll the dice on the settings taking again. I don’t have this issue with every long image, just enough to make me report it.

Edit: On closer look, clicking on an image from your feed gives you the pixelated version. Clicking from inside the post, aka the link I gave everyone, gives you the uncompressed image. You can test this by clearing your cache, restarting the app, going to [email protected], and then clicking the image, not the post. Then click in the post, then the image, and magically it will be uncompressed.