0x0

How's Kagi?

Financially the right move. If what I read was correct, it would take approx. 8 years of steady Patreon income to get to the $2.4M figure anyway.

They must know they fucked up somewhere and decided to go this route rather than get exposed for potential shenanigans. From reading comments in other communities I was surprised to see a lot of people expected this outcome, although nobody was particularly specific about why (maybe someone here can give some insight.) For the record I've been on team "Fuck Nintendo" after the Gamecube, but I'd take the fact that other emulators haven't been targeted as possible hint that Nintendo got wind of something wacky going on. Who knows, maybe they're next?

An unfortunate part of the fediverse is that it attracts people who were too obnoxious for even the more annoying parts of Reddit/Twitter/etc. I've made plenty of attempts to "get into" Mastodon and can confidently say that's a miserable experience across the board if you aren't willing to do the work to curate your feed. Even if you do get a feed that is free of bad actors, conversations rarely veer off-course from Linux, programming, computers, tech, etc., at which point that's fine, I guess, but it's hardly diverse. Also, for all the complaining about "techbros" ruining the fediverse, it sure is full of them.

I have more faith in Bluesky currently. If they're able to achieve their own kind of federation then I'll gladly jump ship since their userbase is a lot friendlier and more diverse that Mastodon IMO.

I was just listening to a podcast recently where one of the (tech illiterate) hosts somehow stumbled upon ffmpeg and went direct to ChatGPT to get instructions on how to use it. They said after a bunch of time plugging different commands into the terminal they realized ChatGPT's output was just close enough to look right but was ultimately "complete gibberish" compared to the actual commands they found via some other resource.

I've already stumbled upon a few different help posts on various Linux-related forums where people have messed something up after following ChatGPT. I don't doubt that it can sometimes come up with useful output, but it's a real roll of the dice.

Check out Normcap.

His meltdown after he launched Rust on Linux and then found out his mouse wasn't supported by Ubuntu is one of the all-time greatest tweet threads. The fact that it was a mouse that ultimately sent him into the anti-Linux spiral that resulted in people being able to refund the game regardless of hours played is extremely funny to me.

If you give this guy money then I don't know what to tell you. He detests Linux users and has said as much while still taking money from them.

I had a rock solid AMD RX 580 up until the release of kernel version 6.7. Now I'm lucky to get a system that can remain up for longer than thirty minutes. Sticking to 6.6 has worked for me and definitely something you should try as well, but it's worth noting that any amount of time spent on the issue tracker for AMD GPU stuff will reveal tons of issues from 6.6 as well.

I did my first BTRFS setup over the weekend. I followed the Arch wiki to set up what I thought was RAID 1 only to find out nearly a TB of copying later that it was splitting the data between the drives, not mirroring them (only the metadata was in R1.) One command later and I'd converted the filesystem to true RAID 1. I feel like any other system would require a total redo of the entire FS, but BTRFS did it flawlessly.

I'm still confused, however, as it seems RAID 1 only works with two drives from what I've read. Is that true? Why?

I started doing this after my phone number got into some kind of crazy scam call database. At the height of it I was getting somewhere in the neighborhood of 30 calls a day, basically rendering the phone unusable.

So I started actually picking up and running these jokesters through the ringer. I'm talking 15+ minutes of pointless conversation, false info, tons of backtracking, and general bullshit. I refined my craft over a few months and would time how quickly I could make them scream at me for fucking with them. At the end of it my phone got taken off at least one of the bigger lists because the calls went to down only 10 or so a day. Now it's one or two a day at the most, probably from me not answering like I used to.

Favorite call was one guy who figured out I was messing with him and it turned into this general question and answer thing about life in the US. Dude wanted to know how easy it was to pick up chicks and whether or not I'd dated a lot/was married. Great guy, really into Counter-Strike.

I'm fresh off ruling out the RAM via memtest. I'll let it do a longer soak overnight to see if anything fails then, but I'm now on to bisecting the kernel from what I believe is the last release of 6.6 (6.6.13) to hopefully whatever the offending commit is. Been a while since I've had to mess around with manually building the kernel without the aid of linux-tkg, but I'm off to learn it anyway. Thanks for the help!

This is what I'll try next. I do think memory is the problem now that I've had a few more hours of research. Kernel 6.7 has issues with elevated RAM usage, so it's absolutely doing something funky with memory that might be exposing underlying hardware issues. I also realized my stable kernel was a version or two away from 6.6.13 (6.6.10), so I'm running it now to see if the issue was introduced late in the 6.6 release cycle, which would be easier to bisect than 6.7.