e0qdk

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

Linux Mint. No IDE -- I just use xed (a fork of gedit) + gnome-terminal, both of which ship with the distro. Only plugin I use regularly for xed is "Code Comment" which lets you comment/uncomment blocks of code quickly.

[–] e0qdk@reddthat.com 33 points 5 days ago (1 children)

My guess was that it was probably due to Hollywood, but some form of mass communication, almost certainly.

[–] e0qdk@reddthat.com 52 points 5 days ago (4 children)

I had a roommate from Manchester (UK) for a couple months back in college. I'm American (US). He seemed to have no trouble understanding me, but I usually couldn't understand what he said without him repeating it multiple times.

[–] e0qdk@reddthat.com 18 points 6 days ago

I haven't gotten around to playing either of them yet myself, but Nine Sols and Astro Bot also come to mind as titles that got a lot of attention.

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

Which sort of makes sense since the US has always had a huge agricultural / grain surplus.

米国 is because of ateji, not agriculture. 米 is the second character of 亜米利加 -- an old transliteration of "a-me-ri-ka" as kanji. 亜 is the shorthand for Asia (亜細亜); the second character 米 is used as the shorthand for America. 米 is both the country (USA) and the continents -- e.g. 北米 and 南米 are sometimes used for North and South America, respectively, while 米軍 is the US military.

Katakana has mostly replaced kanji transliteration of foreign words in modern Japanese, but some uses like the 米 shorthand persist.

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

I haven't tried Nostr, so have no opinions on what the experience of actually using it is like, but cryptographic identity seems like it'd be a better way (technically speaking) of doing things than AP; tying everything to domain names has worked rather poorly -- as we've seen repeatedly every time an instance goes offline...

I ended up on AP after jumping ship from reddit. I was on kbin first (since it was readable w/o JS and I liked the UI), and then later using the mlmym interface for lemmy as kbin because more unstable and eventually went offline.

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

reddthat is an instance hosted in Australia; so the answer to "how will the ban affect it" is "we already have an age limit in place". That's my point.

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

We discussed it in the community posts back in Dec 2024 when the law passed -- February is when the sign up change happened and March was when the announcement went up. The UK's bullshit may be what prompted the announcement happening then though.

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

On reddthat, we got this notice in an announcement back in March 2025:

Age Restriction

Effective immediately everyone on Reddthat needs to be 18 years old and futher interaction on the platform confirms you are over the age of 18 and agree with these terms.

If you are under the age of 18 you will need to delete your account under Settings

This has also been outlined in our signup form that has been updated around the start of February.

[–] e0qdk@reddthat.com 19 points 1 week ago* (last edited 1 week ago) (2 children)

It almost makes me wonder at the prospect of fully off-book unlicensed movie houses. How gangster to set up shop in an abandoned mall and host one-night screenings of pirated films on high end portable projectors? Maybe this already exists and I just don't know about it.

Students at my high school were doing that (with the science classrooms rather than in an abandoned mall) like ~20 years ago. They were watching fansubbed anime though, not Hollywood movies.

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

The 2013 government shutdown, maybe?

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

I was considering submitting a bid for 10% of that -- i.e. $3.50 -- but then I realized that Warner Bros is the goddamn Loch Ness monster...

 

Src: pixiv - danbooru

 

Src: pixiv - danbooru

 

Src: danbooru

 

Src: pixiv - danbooru

 

Src: pixiv - danbooru

 

Src: danbooru

 

Src: twitter - danbooru

 

The Stoosbahn, also known as the Schwyz–Stoos funicular or Standseilbahn Schwyz–Stoos, is a funicular railway in the Swiss canton of Schwyz. It connects the Hintere Schlattli in the municipalities of Muotatal, Morschach, and Schwyz with the village and mountain resort of Stoos, above Morschach. On a length of 1.7 kilometres (1.1 mi), it overcomes a height difference of 744 metres (2,441 ft).

The new line has a maximum gradient of 110% (47.7°-angle slope) and is the steepest funicular railway in Switzerland and Europe, superseding the Gelmerbahn. The Stoosbahn railway operator has claimed it to be the steepest funicular in the world and marketed it as such.

 

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: ‹ prev next ›