It also depends on the domain name itself. I registered a domain recently, and it was much cheaper to go with .io than with .com.

Correct. Unfortunately, it’s something that each desktop environment or window manager has to implement themselves. But all the button is doing is moving some config files around, so you can probably do some digging to figure out what it’s copying to where.

This is the system settings application for the KDE desktop environment.

Literally yes. And you don’t even need to know the exact pixel resolution of the TV.

Edit: Here are the problems with you “Wayland isn’t good enough” people.

First, you don’t use Wayland, so you don’t even know if it’s fixed whatever weird issue you encountered with it before or if it supports a niche use case, for example.

Second, Wayland won’t get good enough for you until you start using it and reporting bugs. You think X11 was a bed of roses when it first started? Or do you think they bumped the version number 11 times for fun?

Not sure if you’re a troll, but if you’re serious, nothing I say is going to change your mind, so I won’t bother.

If you’re using Wayland, you can go to Settings -> Colors & Themes -> Login Screen (SDDM) and click “Apply Plasma Settings…”

If you’re using X11, it looks like you’ll have to resort to hacky scripts, unfortunately.

Source: https://discuss.kde.org/t/how-to-change-monitor-layout-and-orientation-in-sddm/3377

Oh nice! I just use Lutris, but options are always good.

I mean. I can’t because I defederated from Threads. But neat, I guess.

I could go in-depth, but really, the best way I can describe my docker usage is as a simple and agnostic service manager. Let me explain.

Docker is a container system. A container is essentially an operating system installation in a box. It’s not really a full installation, but it’s close enough that understanding it like that is fine.

So what the service devs do is build a container (operating system image) with their service and all the required dependencies - and essentially nothing else (in order to keep the image as small as possible). A user can then use Docker to run this image on their system and have a running service in just a few terminal commands. It works the same across all distributions. So I can install whatever distro I need on the server for whatever purpose and not have to worry that it won’t run my Docker services. This also means I can test services locally on my desktop without messing with my server environment. If it works on my local Docker, it will work on my server Docker.

There are a lot of other uses for it, like isolated development environments and testing applications using other Linux distro libraries, to name a couple, but again, I personally mostly just use it as a simple service manager.

tldr + eli5 - App devs said “works on my machine”, so Docker lets them ship their machine.

That sounds like the default GitHub boilerplate message, to be fair.

I haven’t had a deletion request come around yet, but I’ve had the pict-rs documentation in my back pocket just in case. My instance allows NSFW, so I made sure I knew how to do this before deploying.

I agree with the author, though, it definitely shouldn’t be so hard to delete images. Hopefully the Lemmy devs tackle these issues quickly.

Text is copied to your instance’s database, but any images are hosted on the other instances and simply linked to. Worst case scenario, you get told to delete something that’s illegal in the country in which you host the instance, you comply, and everything’s peachy.

Edit: That being said, I’m currently hosting an instance for myself and a few friends, and it’s been smooth-sailing. Just make sure to require email verification or admin approval for new sign-ups (or disable them entirely) if you don’t want to be overrun with bots.