And ncmpcpp, which makes sense as it’s about 2 or 3 different forks from the original so the name got increasingly out of hand.
Ah yes the ncm program. Used to give my brain half a stroke trying to remember the full name.
And ncmpcpp, which makes sense as it’s about 2 or 3 different forks from the original so the name got increasingly out of hand.
Ah yes the ncm program. Used to give my brain half a stroke trying to remember the full name.
A script kiddie
Or how about: don't shame anyone about how they prefer to pee, as long as they leave a clean toilet afterwards?
Overwriting a SSD is difficult as well,
Trim does a pretty good job actually. Secure erase as well.
https://rossmanngroup.com/technical-reference/what-trim-does-and-why-it-destroys-data
better encrypt the drive and trash the key when you decommission.
Absolutely.
I've had to RMA defective HDDs, and was glad I didn't have to think about what kind of data was still on the platters.
SSDs and HDDs don't always completely fail either. I've had a case where the drive could still be read, albeit very slowly. Writes were not working. Kinda sucks if you wanted to empty the drive before handing it in for repair/replacement.
Why does she look like a render from a 2010 era game? Took me a while to figure out it's an actual photograph.
I mean, that's basically how I find the root cause of problems that occur in one environment but not the other.
Most recently was when a plasma desktop of any newly created user wouldn't shut down properly, at logout it would hang for about a minute with an error in the logs stating that plasma-plasmashell.service was not responding to a sigterm, and was then ultimately force killed by systemd. On my main desktop, I didn't have this issue.
By meticulously diffing plasma related config files, I found that the culprit was in ~/.config/plasma-org.kde.plasma.desktop-appletsrc. Disabling a few system tray applets that I didn't need (and that I indeed had already disabled on my main desktop) fixed the issue.
It's not an ecosystem of one, though one is very dominant.
You can compare it to Linux. It's not the only Unix-like kernel, but it's similarly dominant. If you want to create a new distribution, it doesn't make any sense to spend a decade trying to write your own kernel rather than just using the Linux kernel (insert GNU Hurd jokes here).
Is that an unhealthy ecosystem then? I don't think it is.
What makes the chromium situation unhealthy is Google's ownership and control, not that it's the preferred engine for other browsers. I mean, even a company as large as Microsoft gave up trying to create their own engine.
Via is a very common tool to setup mechanical keyboards, customize the layout, the layers, the backlight,...
See: https://usevia.app/
Doesn't work in Firefox because it simply does not support webhid.
Tip: if you install Firefox from scratch frequently, you should build a custom user.js where you disable all the stuff you don't like, and then just drop the file in the profile directory with a script, instead of manually going through all the settings pages each time.
I mean, on a technical level chromium isn't a terrible browser engine. Building your own engine from scratch is Extremely Hard™ and it's entirely possible to build a decent browser on top of it, so I can understand why most alternative projects have done just that.
It's just... google's control over chromium is concerning.
Firefox doesn't support WebHID, so I can forget about configuring my custom keyboard with anything other than a Chromium based browser.
What's the original of this copypasta?
Edit: nvm, found it!
