e0qdk

joined 2 years ago
[–] e0qdk@reddthat.com 2 points 8 hours ago

Try mixing 1 tbsp cocoa powder, 1 tbsp brown sugar, and 1 tbsp of peanut butter into 1/2 cup oats + 1 cup milk. Tastes like an energy bar.

[–] e0qdk@reddthat.com 95 points 1 week ago (1 children)

I don't know if the GUID Partition Table fuckery is better or worse than what I was originally expecting when I thought your title meant you'd replaced your filesystem with ChatGPT and just let it hallucinate files in and out of existence for you. 🫠️

[–] e0qdk@reddthat.com 5 points 1 week ago

Ctrl+Plus/Minus and Ctrl+Scrollwheel (on mouse) adjust the font size in Firefox on my system.

[–] e0qdk@reddthat.com 8 points 1 week ago (1 children)

LLMs don't really know the subject matter they talk about in the same way a person does. Whatever you feed as input biases the responses towards and away from certain sequences of words. If you put in something about Star Wars, it'll weigh its output in favor of saying things like "Luke Skywalker" and "Darth Vader" and away from things like "The best way to use a crockpot is...". When you're trying to get it to recall facts about things that aren't extremely famous, it will jumble some parts or just make things up that sound plausible.

As an example, I liked to prompt them with "Tell me about 'A Valiant Effort (1989)'" as a test -- it doesn't actually exist, but they'd often tell me it was a painting or a movie or an obscure book with hallucinated details until very recently; newer models seem more likely to say "I don't know what that is" or similar, but that's not guaranteed.

To get better results, try feeding it a passage you'd like it to work on directly in the input instead of assuming it just knows the story already, and you'll get output weighted by the actual text (and whatever else you put in context).

[–] e0qdk@reddthat.com 3 points 1 week ago

I ran a 3x3 grid configuration for a long time as well -- until I finally realized I needed more than that and upgraded to a 5x3 grid! 😅️

I use the center desktop for a maximized browser window and the most important stuff is usually in a plus shape immediately adjacent to that with less important things further away.

[–] e0qdk@reddthat.com 4 points 1 week ago

I have nuanced opinions about AI and, personally, I don't really care how you make your memes if they're interesting -- though I will strongly discourage you from paying anyone for AI as a service to do it...

The "in 10 seconds" bit makes it really easy to flood communities with slop though, and that's one of a number of reasons why people push back on it. There is a lot of boring AI generated stuff out there. Repetitive, same-y content is not fun -- novelty is fun. If you can figure out how to push AI to do something unusual or amusing, I say have at it... but the haters are going to hate here regardless.

We had a subculture here for a while back in 2023 or so that played with AI memes. Someone would come up with an amusing idea -- like Sailor Moon as a giant insect -- post an AI generated picture of it, and then people would riff off it with variations of the idea until it became stale. I think those comms are basically dead at this point -- and if you tried to revive them back you might get shouted off the platform given the amount of toxicity around AI now 😔️ -- but there was some genuinely entertaining stuff in there occasionally!

[–] e0qdk@reddthat.com 7 points 1 week ago (1 children)

RTX 3080-Ti Laptop AMD Ryzen 9 6900 HX

If I understand correctly, does that mean you had two GPUs in the system? (Integrated GPU in the AMD chip + a separate NVIDIA GPU?) If so, were you maybe running on the wrong GPU? Also, did you install the NVIDIA proprietary drivers or just use the out-of-the-box open stuff? For NVIDIA usually you want the proprietary ones, and for AMD open is fine, but the kernel you're running really matters in my experience...

[–] e0qdk@reddthat.com 3 points 2 weeks ago (1 children)

I've seen the word "shimeji" around a bit recently (e.g. fanart of Shimeji Simulation) but it hadn't connected in my head that shimeji is a mushroom until just now. Do these things pop up like mushrooms?

[–] e0qdk@reddthat.com 14 points 2 weeks ago

The narwhal bacons at midnight; the lemming beans at dawn.

[–] e0qdk@reddthat.com 3 points 2 weeks ago (3 children)

Seems like the easier option is to get another SD card and switch out cards depending on what set of games you want to play. A 256GB micro SD is ~$40 US right now.

[–] e0qdk@reddthat.com 6 points 2 weeks ago (5 children)

The Steam Deck already has a built-in microSD card slot -- are you having problems with it or something?

 

I had some free time this weekend and I've spent some of it trying to learn Go since mlmym seems to be unmaintained and I'd like to try to fix some issues in it. I ran into a stumbling block that took a while to solve and which I had trouble finding relevant search results for. I've got it solved now, but felt like writing this up in case it helps anyone else out.

When running most go commands I tried (e.g. go mod init example/hello or go run hello.go or even something as seemingly innocuous as go doc cmd/compile when a go.mod file exists) the command would hang for a rather long time. In most cases, that was about 20~30 seconds, but in one case -- trying to get it to output the docs about the compile tool -- it took 1 minute and 15 seconds! This was on a relatively fresh Linux Mint install on old, but fairly decent hardware using golang-1.23 (installed from apt).

After the long wait, it would print out go: RLock go.mod: no locks available -- and might or might not do anything else depending on the command. (I did get documentation out after the 1min+ wait, for example.)

Now, there's no good reason I could think of why printing out some documentation or running Hello World should take that long, so I tried looking at what was going on with strace --relative-timestamps go run hello.go > trace.txt 2>&1 and found this in the output file:

0.000045 flock(3, LOCK_SH)         = -1 ENOLCK (No locks available)
25.059805 clock_gettime(CLOCK_MONOTONIC, {tv_sec=3691, tv_nsec=443533733}) = 0

It was hanging on flock for 25 seconds (before calling clock_gettime).

The directory I was running in was from an NFS mount which was using NFSv3 unintentionally. File locking does not work on NFSv3 out of the box. In my case, changing the configuration to allow it to use NFSv4 was the fix I needed. After making the change a clean Hello World build takes ~5 seconds -- and a fraction of a second with cache.

After solving it, I've found out that there are some issues related to this open already (with a different error message -- cmd/go: "RLock …: Function not implemented") and a reply on an old StackOverflow about a similiar issue from one of the developers encouraging people to file a new issue if they can't find a workaround (like I did). For future reference, those links are:

view more: next ›