It uses other signals too, like what other sites you’ve visited with that checkbox on it, what CloudFlare has seen your IP address doing in the past, etc.

The google one is able to see if you’re logged into a google account and take that into account.

There’s even a new variant of the Google captcha that is invisible and doesn’t even bother to show a checkbox.

I’m running on 0.19.3 without any issues on Linux arm64. I built my own docker image though.

Manjaro and Antergos are just asking for trouble. If you want Arch, use Arch. Otherwise Ubuntu, Debian, Linux Mint, and Fedora are popular.

I don’t think the full Radeon suite is on Linux but there are tools for screen recording like simple screen recorder and OBS.

There is lots of 3rd party software available on all of these distros in their respective package managers, but Ubuntu has the advantage with PPAs allowing for more 3rd party repos to be easily added to the package manager.

HDR support is still very early/basic right now: https://wiki.archlinux.org/title/HDR_monitor_support

Good Girl by Aquilo. It brings up a lot of relatable feelings around growing up Christian and ultimately is quite sweet.

True, you’re correct. I’m just not sure how you did it without corrupting the sled db. Maybe I’m just unlucky

Interesting, when I tried a while back it broke all images (not visible on the website due to service worker caching but visible if you put any pictrs url into postman or something)

I wrote a patch for Lemmy a week or so ago if you want to skip the caching: https://github.com/LemmyNet/lemmy/pull/3897

I think deleting images from the pictrs storage can corrupt the pictrs sled db so I would not advise it, you should go via the purge endpoint on the pictrs API.

Just a note that my PR there doesn’t disable pictrs for your own instance’s users. It just disables the caching of remote content.

The Lemmy instance I’m speaking from right now is running in my k8s cluster.

Yes, there are a few issues in the lemmy-ui including this PR with a temp fix: https://github.com/LemmyNet/lemmy-ui/pull/2058

I ran this query:

select distinct thumbnail_url as url from post where not local and thumbnail_url like 'https://campfyre.nickwebster.dev/pictrs%'

(replace with your instance’s url)

I then sent delete requests to /internal/purge on pictrs to delete all of those old thumbnails, which cleared out a lot of space. After deleting the thumbnails I ran an UPDATE query to set all of those old thumbnail URLs to null in the DB. I also patched the version of lemmy that I run to stop caching thumbnails in the future. Hope this helps!

Haha yes, that configuration flag PR is mine

100% agreed. I don’t have the time to make a change that complex right now, so I did a fairly blunt approach with the hope that larger instances will keep caching on to reduce load.

Agreed, I sadly don’t have the time to implement that.

I don’t think anything in lemmy is currently clearing that. There are community scripts around that do some clearing but I have not tried them.

go to https://campfyre.nickwebster.dev, sort by “new”

Thumbnails still seem to work.

That’s why I made it a config option that defaults to true (defaults to caching on).

I think big instances should cache, but for smaller instances with less funding and resources it makes sense to skip the caching.

Yep! There’s a pretty rapid growth of pictrs data that’s never going to go away from all the images being cached for thumbnails on my instance.

It’s starting to get to ~1GB per week at this point.

I pulled this PR into the version of lemmy I run on my instance and it looks promising.