Ironic timing…

Basically, the way Lemmy is designed, each instance has to tell each other instance what its users did (where relevant—no need to send to aussie.zone a post made in a community that there are 0 aussie.zone subscribers, for example). That includes posts, comments, and upvotes. And the way it’s designed, the originating server (in this case, LW) has to send it to the receiving server (AZ), then the receiving server sends a confirmation back, and then the originating server can send the next one.

Because LW is hosted in Germany, and AZ in Australia, there’s a minimum amount of time thanks to the physical constraints of sending signals over that long distance. And double that because it’s a return trip, and a small amount more for processing time. It ends up measuring in the hundreds of milliseconds. Which leaves you with a maximum of a few hundred thousand actions sent from LW to AZ per day. If LW users are doing more than this, then the delay will slowly grow. If they send less, the delay will shrink, or remain at near 0.

Now, the most recent version of Lemmy actually lets you set it so that instead of sending just one at a time, you can have multiple threads, so you’re sending multiple at a time. But LW only upgraded to this version a few days ago, and they didn’t turn on this feature when they did so.

If you’re asking for money to fix bugs, that incentivises writing code with bugs, as if you write perfect code first time nobody will pay you to fix it

There’s certainly potential for that to be a problem. But it’s not necessarily insurmountable. For starters, I think the idea is you’re not paying to have your thing fixed, you’re paying to have your thing prioritised. The same amount of work is getting done either way, but bugs reported by people who paid will be prioritised over bugs reported by people who don’t pay. If there are no bugs reported by paid users, then unpaid bugs will still be worked on.

Any web page can be printed. Any print can be sent to a PDF generator. It might not look super pretty, but it’ll get the job done. I recommend making sure you’re on light mode before you print though, because dark mode has grey text instead of black.

Young Democrats…didn’t vote

In 4 of the 7 key states, Harris received more votes than Biden did in 2020. In the 3 where she received less, Trump still would have won based on how many more votes he got even if Harris’s vote count was unchanged compared to Biden in 2020.

This “Democrats lost because of Gaza” angle is convenient. Both sides like it use it. “Moderates” like to blame the “far left” for discouraging voters by calling out the inaction on the genocide. Leftists blame the moderates because they refused to actually denounce the genocide or commit to stopping it. Both side’s arguments are based in assumptions that do not bear out once you look at the actual votes.

It’s the 4th bullet point that gets me. “We should spend more time going to right-wing-dominated spaces (and also restaurants)”. Because only right-wing communities are “real”. Anything lefties do is elitist.

To be fair to JavaScript (I feel gross just saying that), it does have the ability to do some more functional-like programming as well. For example, many of its more recent array methods like filter, map, and reduce are pure functions.

Nothing wrong with classes in functional programming though. Just return a new instance of the class from your method, rather than mutating an existing instance.

Honestly I can’t even figure out how to get that alpine-chrome image to work. I edited my Dockerfile to say

FROM zenika/alpine-chrome:with-puppeteer

instead of

FROM node:22

I tried changing USER node to USER chrome. I removed all the apt-get dependencies that were needed to get Puppeteer working in Docker on my PC in the first instance, and added --chown=chrome to my COPY package.json line, all as described in the with-puppeteer example. I also added the ENV lines from that. (I also tried various combinations of some of the aforementioned changes but not others.) Now I get an error with the npm install step.

15.44 npm ERR! code 1
15.44 npm ERR! path /usr/src/app/node_modules/canvas
15.44 npm ERR! command failed
15.44 npm ERR! command sh -c prebuild-install -r napi || node-gyp rebuild
15.45 npm ERR! prebuild-install warn install No prebuilt binaries found (target=7 runtime=napi arch=x64 libc=musl platform=linux)
15.45 npm ERR! gyp info it worked if it ends with ok
15.45 npm ERR! gyp info using node-gyp@8.4.1
15.45 npm ERR! gyp info using node@20.15.1 | linux | x64
15.45 npm ERR! gyp info find Python using Python version 3.11.10 found at "/usr/bin/python3"
15.45 npm ERR! gyp http GET https://nodejs.org/download/release/v20.15.1/node-v20.15.1-headers.tar.gz
15.45 npm ERR! gyp http 200 https://nodejs.org/download/release/v20.15.1/node-v20.15.1-headers.tar.gz
15.45 npm ERR! gyp http GET https://nodejs.org/download/release/v20.15.1/SHASUMS256.txt
15.45 npm ERR! gyp http 200 https://nodejs.org/download/release/v20.15.1/SHASUMS256.txt
15.45 npm ERR! gyp info spawn /usr/bin/python3
15.45 npm ERR! gyp info spawn args [
15.45 npm ERR! gyp info spawn args   '/usr/src/app/node_modules/node-gyp/gyp/gyp_main.py',
15.45 npm ERR! gyp info spawn args   'binding.gyp',
15.45 npm ERR! gyp info spawn args   '-f',
15.45 npm ERR! gyp info spawn args   'make',
15.45 npm ERR! gyp info spawn args   '-I',
15.45 npm ERR! gyp info spawn args   '/usr/src/app/node_modules/canvas/build/config.gypi',
15.45 npm ERR! gyp info spawn args   '-I',
15.45 npm ERR! gyp info spawn args   '/usr/src/app/node_modules/node-gyp/addon.gypi',
15.45 npm ERR! gyp info spawn args   '-I',
15.45 npm ERR! gyp info spawn args   '/home/chrome/.cache/node-gyp/20.15.1/include/node/common.gypi',
15.45 npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
15.45 npm ERR! gyp info spawn args   '-Dvisibility=default',
15.45 npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/chrome/.cache/node-gyp/20.15.1',
15.45 npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/src/app/node_modules/node-gyp',
15.45 npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/chrome/.cache/node-gyp/20.15.1/<(target_arch)/node.lib',
15.45 npm ERR! gyp info spawn args   '-Dmodule_root_dir=/usr/src/app/node_modules/canvas',
15.45 npm ERR! gyp info spawn args   '-Dnode_engine=v8',
15.45 npm ERR! gyp info spawn args   '--depth=.',
15.45 npm ERR! gyp info spawn args   '--no-parallel',
15.45 npm ERR! gyp info spawn args   '--generator-output',
15.45 npm ERR! gyp info spawn args   'build',
15.45 npm ERR! gyp info spawn args   '-Goutput_dir=.'
15.45 npm ERR! gyp info spawn args ]
15.45 npm ERR! Package pixman-1 was not found in the pkg-config search path.
15.45 npm ERR! Perhaps you should add the directory containing `pixman-1.pc'
15.45 npm ERR! to the PKG_CONFIG_PATH environment variable
15.45 npm ERR! Package 'pixman-1', required by 'virtual:world', not found
15.45 npm ERR! gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
15.45 npm ERR! gyp ERR! configure error
15.45 npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
15.45 npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/usr/src/app/node_modules/node-gyp/lib/configure.js:259:16)
15.45 npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:519:28)
15.45 npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
15.45 npm ERR! gyp ERR! System Linux 6.10.14-linuxkit
15.45 npm ERR! gyp ERR! command "/usr/bin/node" "/usr/src/app/node_modules/.bin/node-gyp" "rebuild"
15.45 npm ERR! gyp ERR! cwd /usr/src/app/node_modules/canvas
15.45 npm ERR! gyp ERR! node -v v20.15.1
15.45 npm ERR! gyp ERR! node-gyp -v v8.4.1
15.45 npm ERR! gyp ERR! not ok
15.45
[+] Running 0/1A complete log of this run can be found in: /home/chrome/.npm/_logs/2025-02-18T01_04_35_846Z-debug-0.log
 - Service node  Building                                                                                         18.9s
failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1

Which I just now (after posting) noticed was already mentioned in a different comment. Sorry!

I’m guessing the user who made that other comment is on lemmy.world? I can’t see any comment other than yours, and LW has known issues with federation (issues that would be fixed if the instance weren’t 5 version behind…) that mean I probably won’t be able to see it for about 2 days right now. So thanks!

I haven’t looked into the suggestion in great detail yet, but I will say I’m already running as a non-root user (USER node is a line in my Dockerfile). I’m not sure what a seccomp profile is, but in case it wasn’t clear from the original post, I just want to emphasise that the current configuration works in Docker on my Windows PC. It’s only on the Synology NAS that it fails.

Personally I’m not enormously worried about SSH, because I’m behind NAT anyway, but yeah it’s definitely still something I’d rather keep off if not in use.

Is there a way to get a terminal on the Synology itself, or is SSH from my PC the only way?

I would love to containerise it. I worked with Docker in a previous job, but honestly I’ve forgotten most of how to work with it. Would be a nice refresher to try and relearn how to create Dockerfiles and docker-compose.yamls.

Unfortunately I currently have two problems. First: I seem to be completely unable to test this on my desktop. When I open Docker on my PC, it complains that I need to run wsl --shutdown, but despite doing that many times, it still complains, before immediately closing.

So I was going to try doing it entirely on the Synology. And then I ran into the issue that…I have no idea how to even start with that. When I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

Yeah I’m pretty sure my Synology should be able to run containers. It’s a DS923+. But unfortunately when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

How do you run a docker container on Synology? I have a DS923+ which AFAIK should be able to run it, but when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

How do you run a docker container on Synology? I have a DS923+ which AFAIK should be able to run it, but when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

How do you run a docker container on Synology? I have a DS923+ which AFAIK should be able to run it, but when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

I can, but that would require manually starting it up every time I restart my computer—which is daily, for the most part. And there are times when I don’t even turn on my computer for the day, or don’t do so before the 2pm time the bot needs to run. It would be better to have it running on a system that’s always online.

Yeah it’s a very fun name, isn’t it?