Only so I don't have to turn down the volume, and turn it back up when the episode starts.

Same for me. You can bypass it if you read in a "private browsing" window.

Cockpit is great.

It's pretty simplistic. It gives you an overview of your system ressources and handles libvirt VMs and Docker (i think. I used it with Podman, but in this context both should work).

My impression was that the container and VM interfaces were pretty simple, and I wouldn't have liked it as my main interface for those services, but it would be perfect for getting an overview and restarting them!

Grounded danish plugs don't fit Schuko sockets, but Schuko plugs fit danish sockets (but aren't grounded).

This leads to a staggering amount of ungrounded devices in Denmark, as most are imported and making a variant for such a tiny country isn't profitable.

Fun fact: the danish power plug was created by Lauritz Knudsen, a Danish company who had a monopoly. They are the reason Denmark uses this plug as the only country in the world, and Schuko only became legal to install in houses quite recently, so 99% of houses still use their standard.

LK has since been bought out by Schneider Electric but we are still stuck with our special plug and most imported devices are still ungrounded.

Thanks for listening to my Ted Talk.

I only tried running rootless when i set them up several years ago and i was completely green, so it was probably me who was the problem.

Regarding podman-compose, Fedora repos has a a package that aliases podman -> docker and the regular docker-compose package, which i used before migrating to podman+systemd. It worked flawlessly unless i did networking shenanigans because Podman and Docker differs (/differed?) in so some thing simply couldn't be brought over.

Edit: i found the docker-compose and Podman alias thingies in a Fedora Magazine post.

However, unless you use docker-compose a lot for other stuff, learning to use Podmans systemd integration (also called quadlet) is very much worth it. They're just a really powerful combo and systemd has a ton of nice features for making stuff run and keep running.

Oh, i did not know. Thanks!

I barely use a calculator, but you could try SageMath if you like the thought of writing you math in Python.

I mean inserting the pause gcode command in the slicer. The idea is that this command is very basic, so every printer supports it, as opposed to a filament change command.

I used Cura and IIRC you could add "move away from the print and move back when unpaused" commands.

I haven't 3d printed for far too long, so my memory is very blurry. You might be better off looking for a Youtube video or googling for a tutorial, but it wasn't rocket science once someone on the internet explained it to me.

Edit: maybe try searching for something like "3d printer filament change pause"

I believe we are reffering to two different, but related things.

As i understand your comment, you are reffering to "the platform is responsible for what the users upload to it", or rather whether they are responsible and i am reffering to "(eg.) Torrent sites don't host copyrighted content, they only link to it".

My knowledge about the latter is from many years ago, so i might be wholly or partly wrong.

The former i think is a really interesting balancing act, since i believe that huge platforms that earns billions on hosting user content should be forced to use some of that profit to remove dangerous content, but if that obligation was put on small platforms like Lemmy instances or even the initial Twitter or Facebook, right when they lanched, they would be never be able to get up and running, which would cement the current Big Tech monopolies.

I am not very knowledgable about this specific topic, but i believe the European Unions attempts at solving this is distinguishing between the giants and everybody else, which again, is a great balancing act.

Base64 encoding is not a legal loophole, it's a method to avoid automated content filters on platforms like Reddit and Discord. Encoding a link in base64 offers no legal protections.

Thank you for correcting me. It makes a lot more sense that you can't just encode something to make it legal.

Not OP but, consider using something like a YubiKey or similar hardware key for your second factor authentication.

They usually support multiple protocols so you only need to carry one around - and storing your second factor with your passwords is like putting all your eggs in one basket.

Print out recovery codes or get an ekstra hardware key for backup and you get great security for surprisingly little effort.

Have you tried the MicroG fork of LineageOS?

It has an open source implementation of Play Services. It works for a lot of apps, but not every app.

But looking at what Rocky Linux is saying publicly. It's not impossible that Red Hat won't levy their right to remove access to the sources to non-commercial forks of RHEL.

I think this is a good theory. I would be surprised if Red Hat hadn't realized the value of clones and the community (and contributions) they bring.

I hope, but also honestly believe, that this is targeted at Oracle and that publicly saying "Don't worry we're only gonna use this against this company" would be make Red Hat liable to a lawsuit.