e0qdk

joined 2 years ago
[–] e0qdk@reddthat.com 5 points 6 hours ago (1 children)

I liked the UI when I first encountered it, but it being invite-only killed what interest I had in it pretty quick during the 2023 reddit exodus. Seems to still be invite only in 2026.

[–] e0qdk@reddthat.com 4 points 10 hours ago

I use container tabs for that. Makes it easy to keep two logged in accounts side-by-side.

[–] e0qdk@reddthat.com 2 points 22 hours ago (1 children)

I wonder how they'd take to being called "morbidly rich"? 🤔️

[–] e0qdk@reddthat.com 3 points 2 days ago

I talk to my Dad about once a week or so for maybe 20 or 30 mins. Usually just "How's it going?" kind of small talk. Work. Health issues. Sometimes about food or hobbies. Commiserating about politics. Updates about relatives moving/getting jobs/etc. Things like that. Helps us both stay sane in this crazy world.

Once a month or so, I talk to my uncle. He's more chatty, so those calls go on for longer. He likes to tell me bits of family lore, about his interests in detail, about food and his pet and what's going on with his friends and neighbors -- like trips he's taken with them to go out shopping and such.

My other relatives don't talk to me very often, so those are more of life catch-up talks every couple months/years or conversations about specific things that I have skills in that they'd like help learning.

Maybe try asking your mom what's on her mind lately -- other than you -- and take it from there? Most people love to talk about themselves if given a chance. Ask questions about what she says and try to find a topic of mutual interest.

[–] e0qdk@reddthat.com 2 points 5 days ago

No, we are communicating. People can coordinate their actions to achieve things that are impossible for an individual. We obviously don't have perfect shared understanding, and miscommunications are not uncommon (as others have already pointed out) but we can exchange enough information to do useful things.

Also, we can make jokes. The fact that it's possible to craft a joke and make someone laugh by setting up and intentionally subverting expectations through language is pretty good evidence that we have shared understanding and similar processing.

[–] e0qdk@reddthat.com 56 points 6 days ago (1 children)

Looking back through your history, that's a post by a user local to your instance. You can see it because you're on the same instance.

If I understand how federation works correctly, posts don't go directly to the instance a community is on when they are made. They are created locally on your own instance, and then federate out if/when they can. Since you're both on the same instance, you can see the post and interact with it, but the post and your comments are (presumably) stuck in a queue trying to federate to the now defunct instance. Since lemm.ee is gone, it can't federate out, so other people don't see the post/comment on their instance.

I think that's what's going on.

[–] e0qdk@reddthat.com 3 points 6 days ago (6 children)

@FireWire400@lemmy.world, @BoozeOrWater@piefed.social: FYI -- possible automoderation issue in this thread. Can you please take a look?

@whaleross@lemmy.world -- if there's a better option for getting moderator help, I don't know what it is. Hopefully one of them is online and can help figure out what's going on and get it sorted. For what it's worth, I didn't see a problem with what you wrote in that comment. Cheers.

[–] e0qdk@reddthat.com 2 points 6 days ago (8 children)

Modlog says "Automatic deletion due to block". So, it seems like a bot removed it? Not really sure why though. This comment came through fine.

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

if anyone knows a better solution to sharing videos that doesn't involve making accounts, please let me know!

You can upload small files (under 200MB) to https://catbox.moe/

I don't know how to fix your trackpad issue though. Sorry.

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

$0.33 per avocado

Damn. You made out like a bandit!

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

BlueSky uses AT Protocol which is similar to how you break things down: https://en.wikipedia.org/wiki/AT_Protocol

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

Should be trivial to set up something like that if you've got parts you want to work with. Any desktop with an automatic background switcher should be able to cycle through images in a directory you specify on a timer. Set up your favorite remote access software (SSH, Samba, NFS ...) and you're done. If you want more control over the behavior, you could script up something custom with a little more effort -- but it's still not particularly hard to implement something like that.

Watch out for burn in on the screen if you're leaving it on all the time.

 

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 ›