skilltheamps

Additionally, if you where to drop a clamp or touch something by accident, it is most likely to contact negative, as that is the whole chassis. If you adhere to this order and drop the negative clamp, it will most likely just reconnect to negative. If you drop the positive clamp on the negative chassis nothing happens anymore, as you broke the circuit beforehand.

If you do it before every print, you also get rid of the dust that settles inbetween prints

I bet worst schmoo is grease from fingers tho. Either way alcohol or soapy water does the trick

What issues do you have running it via firefox? It seems fine for me, although I didn't try with chrome

As many other stated, its nozzle ooze. When you travel the same path repeatedly, it will catch on previous ooze and build these diagonal structures.

Besides what other wrote, I can recommend:

• Try out how fast you can make your printer move, and travel as fast as possible. That gives your filament less time to ooze, and therefore you minimize the amount.
• When travelling, do a very small Z-hop. Something like .1mm. That helps a bit to not deposit the oozed material along the way, but where you touch down again. If you make the Z-hop too high, it will start to create strings. So you'll have to try and tune this value.
• Generally try to slice in a way that minimizes travels. Even stuff like choosing an infill that doesn't cross lines, and connecting those lines so that you print long and steady can help to keep your nozzle clean (I like gyroid with connected ends for that matter).
• What also helps is to convert your printer do direct drive. That gives more precise retractions. What works well for me is direct drive with small retractions. I believe, not shoving the filament back and forth so much yields better quality. Maybe, because retracting a large amount pulls air into the hot-end, and I imagine it might not all come out perfectly again when continuing with the next perimeter.

it's not that important if you know what you're doing and don't break your distro.

That may be true for intermediate level users.

Let's go about it this way: Arch for sure is the mutable distro that requires the least fiddling when using it for many years. Much less than any distro that doesn't roll and/or relies on 3rd party repos could ever achieve. Arch only ever has very small hiccups, almost never actually breaks. And yet, after the hundredst time of upgrading the keyring first, recompiling some AUR package because some library changed under its butt or whatever tiniest annoyance, you grow tired of it.

After a decade of usage you know all these things, you have explored every nook and cranny of your OS, the excitement for messing about is over. You just want your computer to take care of itself, because there's nothing entertaining/surprising/interesting in it anymore.

An then an immutable distro becomes very attractive. You get an OS that does its thing, no manual intervention required at all. You can concentrate on the stuff you want/need to do. The OS is not the joyful toy with productivity benefits anymore, just a plain tool. Also here and there you may finally discover some interesting new kinds of bugs or challenges that arise from the new paradigma of containerizing literally everything.

You want so isolate the things you host from one another (security, making updates easier etc). So if you host just one thing you can do so on the host directly. If you host multiple services you may seek some separation method.

VMs is one method, but it wastes a lot of resources, especially RAM. A more elegant way is containers. Both the docker/podman route as well as the LXC way are quite polular.

Same thing with Silverblue. I just created aliases for the hoping into the containers