pleroma.debian.social

pleroma.debian.social

Jonathan Dowland | @jmtd@pleroma.debian.social

Principal Software Engineer on #OpenJDK #RedHat. #Debian developer (dormant). Computer Science PhD student. Amateur Computing historian (Computer Science and H/W, esp. Commodore Amiga). Guerilla archivist.

Someone should write a ring-like movie that uses screen burn in as a plot device

Hypnospace Outlaw really captures the aesthetic of late-90s web

@mirabilos @venthur @Ganneff @wouter be gentle with Planet, folks. It’s been going for over twenty years!

Instead of storing my data in the cloud, I just store it in the bush. It's the same thing, only palette-swapped. More accessible, too.

A pair of Super Mario Brothers screenshots showing that the art for the clouds and the bushes is the same, just different colors and the bottom of the bush isn't displayed.

New blog post: Orbital https://jmtd.net/log/orbital/ #music

Actually - and this isn’t hyperbole - it’s worse. Instead of wrangling one app you now need at least three. One of which is Activity Monitor because you are required to terminate a bunch of processes beginning ams* from time to time.

can I report that syncing stuff onto ipods with Finder is JUST as awful as it was with iTunes.

@edwinb @plragde you’re making me want to play on my synth now

Today I took out an old pair of Bose on-ear headphones. The Bluetooth functionality is shot, possibly just the battery, but they work fine passively. I forgot how great they sounded. Bose don’t make them anymore and I haven’t seen any modern ones of this style. I think I’ll try to replace the battery.

@werdahias I recently completed a large LaTeX document. I had bound ',m' to rebuild my thesis (called Make which called make in a sub-process and watched it from a small split, and the make called latexmk, etc. etc., it was a hairy ball of glue) and that was really nice 90% of the time and a pain to fix the other 10%. I keep reading about LaTeX tools, packages etc that would have made my life easier after I'm done :-)

So the user actually found a memory leak in (using a fuzzer) and reported it correctly. All good.

Then, in a follow up comment the user makes the ugly choice of trying to "help" us with this bug by asking an AI for help and proposing that as a solution.

And again it broke horribly and the AI made up a broken patch that did not even fix the problem.

Now that reporter is banned.

@tizmic @guyjantic @david_chisnall @nixCraft @mwl pragmatic programmers? No starch press?

@jpmens I've done similar before and am not aware of a better way. You could try a cheaper checksum (MD5 or worse) to speed it up, if you were happy with that.

@pwaring I side-stepped this problem by having my containers be first-class citizens on the host machine's network. Then instead of connecting to "host:bignumport" I can connect to "somecontainer.local" directly. Might be worth considering: https://jmtd.net/log/podman_network/

@sxa @fred yeah, this appears to be a known issue. I wonder if Pleroma is still actively developed? https://git.pleroma.social/pleroma/pleroma/-/issues/2975

@fred @sxa It would seem so. This reply is from the Pleroma web UI on my laptop, rather than phone app. I couldn't find any setting for language, either in the web app preferences or the compose form as I write this.

@fred @sxa mastodon iOS app. It seems to think I’ve selected English
Screenshot of mastodon iOS app’s posting interface

@fred @sxa thanks for investigating! I might be able to set a user preference for my language, I’ll take a look

»