e0qdk

joined 2 years ago
[–] e0qdk@reddthat.com 3 points 1 day 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 3 days 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 3 days 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 4 days 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 4 days ago

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

[–] e0qdk@reddthat.com 3 points 6 days 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 6 days ago (5 children)

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

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

Factorio - Every so often I still get a craving for this even if the space age release really took a lot of the shine off it for me personally.

I played it about six months ago and sometimes get the craving too. Does Satisfactory scratch that itch or is it too different? (Haven't played it but was thinking of picking it up next time it's on sale -- or the itch gets itchy enough...)

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

!! We're not friends? 😭️

(Image Src: pixiv - danbooru -- by rui tamachi)

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

Tornado-kun, no! I'm not ready to go to Oz yet! πŸŒͺ️

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

I believe the intention of DMs is that they are supposed to be accessible only to the sending/receiving server admins and sending/receiving users -- but given the many ways that distributed systems which are not built specifically for secure comms can go wrong, you should simply assume anything you transmit through Lemmy is or will eventually be public, period.

If you are concerned that some information you transmit through Lemmy may be exposed the correct security stance is simply: DO NOT SEND IT.

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

Kiki and Bouba

 

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 β€Ί