Yes, but only for 2.4 ghz since I live in a small apartment and there’s no benefit to high transmit power in those cases. 5 ghz is another story since it doesn’t penetrate walls easily anyway, so no harm to others.

I’ll add that it’s a meta-search engine rather than something that does the actual searching itself. That’s still useful, but you’re limited by the quality of the upstream search engines (including google, duckduckgo, qwant, etc).

The gain from self-hosting is that you have more control over the results, and can do things like redirect social media sites to privacy friendly alternatives, and create your own bangs (or even add your own custom search engines).

Probably not a massive privacy gain though, although if you host the instance behind a privacy VPN queries won’t be associated with your IP at least.

AMDGPU virtio native context is somewhat of an equivalent to the other options, although the pieces are not all available yet. Linux guest only as well.

And there’s Venus but that’s for Vulkan only (but a lot can be done with that alone on Linux guests).

One issue I could see is using it not as a second opinion, but the only opinion. That doesn’t mean this shouldn’t be pursued, but the incentives toward laziness and cost-cutting are obvious.

EDIT: One another potential issue is the AI detection being more accurate with certain groups (i.e. White Europeans), which could result in underdiagnosis in minority groups if the training data set doesn’t include sufficient data for those groups. I’m not sure if that’s likely with breast cancer detection, however.

There’s also calibre-web for a self-hosted option with a web interface.

btrbk works that way essentially. Takes read-only snapshots on a schedule, and uses btrfs send/receive to create backups.

There’s also snapraid-btrfs which uses snapshots to help minimise write hole issues with snapraid, by creating parity data from snapshots, rather than the raw filesystem.

Putin and Trump are best friends so you might expect Russia to follow. But perhaps Putin wants to show he’s the dominant one in said relationship.

The official Forgejo instance, to be clear (Codeberg are the organisation that forked Gitea and created Forgejo).

Not the modern X.com to be clear; Musk just has a weird fetish for the letter X like an edgy teenager.

I’m not arguing in the slightest that FLAC shows an audible difference in most cases for most tracks. However, it just makes sense as an archival format given it’s lossless which means you can transcode to any other format without generational loss.

This means if there is a massive breakthrough in lossy compression in the future, I can use it for mobile purposes. If you store as lossy, you’re stuck with whatever losses have been incurred, forever.

Could be useful for web articles and scientific papers too (if it could be configured to ignore reading out all of the boiler plate and citations).

Store the original library as FLAC, then transcode on-the-fly (or once if you don’t want to use something like Navidrome or Jellyfin).

The main benefit to lossless is for archival purposes. I can transcode to any format (such as on mobile) without generational quality loss.

And it means if a better lossy format comes out in the future, I can use that without issue.

There are better lossy formats, like opus.

But MP3 still has its place as it’s supported everywhere.

There’s likely a firewall on the system that hosts the docker services, and docker’s default bridge rules bypass it when publishing a port. And since the docker rules are prioritised, it can be quite difficult to override them in a reliable way. I personally wish that the default rules would just open a rule to the host, but there might be some complexity that I’m missing that makes that challenging.

I personally use host networking to avoid the whole mess, but be aware you’ll have to change the internal ports for a bunch of services most likely, and that’s not always well-documented. And using the container name as the host name won’t work when referencing other containers, you’ll have to use e.g. localhost:<port number> even inside the network.

You can do the bind to localhost thing that others have mentioned, as long as the reverse proxy itself is inside the docker network (likely there are workarounds if not).

Kind of fits as a general philosophy though. Exclude items based on some criteria, limiting the choices you have to make. This makes your life simpler, and your actions align with your beliefs.

The older versions will still stick around for many years; it just means apps specifically targeting GTK5 won’t support X11.

In any case, X11 has all but been abandoned already so the writing is on the wall.

My desktop PC idles quite high as well. The semi high-end consumer motherboards on the AMD side tend to use a lot of power at idle, so I think that’s a big part of it (at least the x570 series, can’t speak for later). And as others have said, high refresh rate and multiple monitors can make things worse.

I’ll add though that people’s perception of how much power there system is using can be skewed by software based monitoring tools. People may think there system is using only 50W because that’s what software reports but it’s actually drawing a 100W at the wall.

It has never occured to me my whole life to not suspend

Reliability issues with suspend-to-ram are rather common. Shutting down is an option, but session save and restore is a relatively recent thing and not supported by all desktop environments. I.e. it’s the post startup part that takes the longest.

I use NixOS so if an update breaks, I just roll back. And since it’s effectively a rolling release distribution there isn’t any risk of being left behind on an outdated version.