the article makes some good points on why not though, also they offer anyone that wants to help to first ask them.

in the end its "their" property that you're trying to fix, with them responsible for it when you do it wrong

8bitdo Ultimate 2, do really watch the product name though, because a lot of their similar named controllers are completely different (8bitdo Ultimate 2C for example)

lemmy loop you in: https://infosec.exchange/@ifin/116735279416101129

TL;DR; lots of aur packages got hijacked and install a infostealer, if you updated today/yday, there is a reasonable chance you got hit by it :(

also: the info stealer is installed by aur via npm

Gotta give a shoutout to SourceGit

Its the first git GUI that is actually clear and comfortable to use for me and makes relatively complicated git actions like interactive rebase easy.

I'm slowly growing support for it at work and trying to get it in the pool of projects we donate to at work. (Have not checked if they allow donations, I probably should)

printing to a console could enforce a flush, sync thread or other shenanigans.

usually setting a breakpoint would have the same effect and gives me the suggestion of a threading issue.

with a car the other person has a licence for it, which comes with the assumption of at least some basic skills operating the device.

Users with computers? Some people really shouldn't even approach one.

Back when starting your computer and launching programs took a good chunk of your first hour at work (this was about 10-15 years ago for me), having startup programs meant you could just

• hit the button
• get coffee
• chat with colleagues
• login
• get coffee
• review the incoming paperwork
• get coffee
• start the one program that didn't autolaunch
• get coffee
• actually start doing something on your pc

those people in sitcoms chilling at coffee machines were probably waiting for their PC to start. Launching corporate software took ages, having them started neatly by windows saved you from having to start the next program when the previous was finally launched after a few minutes.

The biggest bump in computer performance in history wasn't getting more memory or a faster CPU, it was switching from a HDD to a SSD.

I've got a serverrack on the attic, what is spare solar power? ;)

I've been considering getting a battery, but until I'm actually going to any meaningful surplus in power its not really worth the investment for me.

I'm from the EU and got 6 panels for a total of about 2kW on my roof, my house isn't on a optimal angle though, so I'm not often tapping the max capacity.

wiggle it until it's the size of a monitor, and if you're brave, it'll take over EVERYTHING.

I love it that KDE didn't limit the growing of it :)

the last part is one of my biggest annoyances. People just clicking away the dialogs that almost exactly tell what is wrong and at most just say: "yeah of gave me an error but I just clicked it away and it still didn't work".

As a software developer, pretty much every error you see I made there for you to either read or screenshot and send to IT, because I had to pretty much implement each one of them. (usually with a standard library, but it's still a deliberate choice to show it to the user)

Real unexpected errors are hopefully written to logfiles, but that's not always possible (try logging an error when your system disk is no longer available).

addendum: please also include the gibberish at the end of the error, because its likely there for IT or me to find more details of this specific error in the thousands to millions of things that are logged for the software or website.

the issue is that things like the DHT and PeX can leak your own home ip address, and local peer discovery can leak the torrents you're seeding to local network devices.

Mullvad is very privacy oriented, hence it giving this advice.

on my normal desktop I use the flavor of the day DE, gnome is only used on my 40 inch touchscreen, because its the only one I could imagine being good on a touchscreen