moomoomoo309

If they're on android, try revanced. It's a patched YouTube apk, so the interface is the same (unless you change stuff, like, for example, disabling shorts - but by default, it's the same).

It's C, NaN is never equal to itself in floating point, that's not just a JS thing.

Or a wireless winch, if I were to hazard a guess.

"Creates a whole game in assembly" is probably referring to roller coaster tycoon, which was written by a man. (lots of other games were written in asm, like many NES games, but I'd wager RCT was what they were alluding to)

And you think there's not bias in those rules that's notable, and that the edge cases I mentioned won't be an issue, or what?

You seem to have sidestepped what I've said to rant about how OpenAI sucks when that was just meant to be an example of how even those best informed about AI in the world right now don't really understand it.

Sure, who will it impersonate if you don't? That's where the bias comes in.

And yes, they do need a guide, because the way chatbots behave is not intuitive or clear, there's lots of weird emergent behavior in them even experts don't fully understand (see OpenAI's 4o sycophancy articles today). Chatbots' behavior looks obvious, and in many cases it is...until it isn't. There's lots of edge cases.

Oh, I know this one! Make sure you're using pipewire and use HDAJackRetask. You can reassign the ports to whatever, you can even swap mic and headphone if you want.

I was thinking not only about the finicky drivers, but also the different audio backends, like ALSA and OSS, Pulse would have just come out at the time, so it was definitely getting better, but it was fresh off the presses back then, so it wasn't good enough yet either. Nowadays, Pulse works pretty well, pipewire works pretty well, things more or less just work, Bluetooth can be a little weird, but usually you just need to change the settings on pulse/pipewire to your preference.

Audio and networking were a shitshow back then, nowadays almost everything just works on those two fronts. Also, having to edit your Xorg.conf is not what I'd call user friendly...

Check rocm's supported cards, oh and after you install rocm, restart your computer - made that mistake when I was doing it and couldn't figure out why it wasn't working.

Your M.2 port can probably fit an M.2 to PCIe adapter and you can use a GPU with that - ollama supports AMD GPUs just fine nowadays (well, as well as it can, rocm is still very hit or miss)

That is for a circle that's not filled in, that's what the outline operation does.