Wow, really interesting, thanks!

It didn’t fix everything, or even fully fix my Redis container. But it did improve things a lot. This is now my full Redis logs:

2025-12-29T17:01:52.277109213Z Redis has started
2025-12-29T17:01:52.746857972Z 7:M 30 Dec 2025 03:01:52.746 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

Sorry, I’m not 100% sure I follow. Is this a quip about Nextcloud being difficult to run? If so, is it a loving one, or do you think it’s not worth the effort and I should try running something else?

The docker version says its API is on version 1.43. So I’ve fixed it by setting: DOCKER_API_VERSION: 1.43

Unfortunately I already tried this in my initial post, I’m pretty sure. It’s what I have with the errors shown in the OP.

Seems weird to me that there’s an AIO container that seems to contain other containers, but anyway I guess thats a synology thing.

No, that’s a Nextcloud thing. From what I can tell, it seems to be the preferred way of setting up Nextcloud these days. https://github.com/nextcloud/all-in-one

afaict it’s not that one container contains the containers, so much as one container is given control of the Docker socket so that it can create and control the other containers automatically.

all those containers are “starting” because theyre waiting for one other container to finish “starting” before starting up themselves

Apache and notify-push are waiting for Nextcloud. Nextcloud is waiting for Database. Whiteboard is waiting for Redis.

I have no idea what’s wrong with Database, Redis, or Collabora, but their errors aren’t obviously related to dependencies, to me. (Collabora’s could be, but it’s at least a different type of dependency since the logs are mostly [ remotefontconfig_poll ] ERR Remote config server has response status code: 502 (Bad Gateway)| wsd/RemoteConfig.cpp:133. I’ve not really started looking into it since it’s a rather downstream component and the core components failing is more important.)

Imaginary just says:

Imaginary has started

Is the 404 in the master container logs from you trying to access the instance in your browser?

Doesn’t seem to be. Seems to add a new log periodically even when I don’t try to load it up. I’m guessing the 404 comes from some kind of automated uptime checker?

Ditto

@non_burglar@lemmy.world is correct, but is perhaps not explaining it perfectly for the practical questions you seem to be asking.

If you have, say, two Docker containers for two different web servers (maybe one’s for your Wiki, and the other is for your portfolio site), you can have both listening on ports 80 and 443 of their container, but a third Docker container running a reverse proxy which has access to your machine’s ports 80 and 443. It then looks at the incoming request and decides which container to route the request to (e.g., http://192.168.1.2/wiki/%s requests go to the Wiki container, and all other requests go to portfolio site).

Now, reverse proxies can be run without Docker, but the isolation Docker adds makes it all a lot easier to manage, in part because you don’t need to configure loads of different ports.

I usually create new repos through GitHub or another central repo’s system, where it defaults to calling the main branch main. But I did recently create a new repo with my local Git’s git init, and had to deal with a master branch on a completely new repo for the first time in a while. It was actually kinda a weird experience.

My take is that everyone does it for their own posts, it’s not actually that much effort. And it’s an amount of effort that’s worth it, to make the threadiverse a more welcoming and accessible place. If even one post I transcribe is seen by one blind or vision-impaired user, I’ll consider the work worth it.

The fediverse broadly is already far better for accessibility than sites like Reddit and Twitter, with users in general far more likely to be aware of things they can do to promote access for users with special needs. But we can still do better, especially our threadiverse corner of the fediverse. Considering one of the reasons for outrage over Reddit dumping their API was the impact on users of blind-focused third-party apps, that’s particularly disappointing.

That’s a pretty good point. For these standard template memes I usually go to Know Your Meme and copy/paste the relevant section of their description. In this case it looks like they said “also landing on it”, which I think is supposed to get across the same idea, but it does seem easy to read that without getting the intended idea.

My ideal hope is that by modelling good behaviour, I can encourage more OPs to provide transcriptions themselves in the body or the alt-text field.

If OPs take my transcriptions and edit it into the body, that’s pretty good too. Especially if more people take up the work so transcriptions get posted on posts that I don’t do myself.

The algorithm is far too fickle for me to have even considered my comment getting upvoted to the top. Good if it happens I guess, but not in my consideration.

Yeah, it’s much, much better if OPs provide their own transcription. It’s much easier to see that way. Mastodon and Pixelfed both basically yell at you if you don’t do it, and it’s a shame that Lemmy isn’t the same.

For small transcriptions, there’s an “alt text” field in the post itself, and for longer ones, they can be placed into the body of the post.

Interestingly, the earliest example of this meme listed on Know Your Meme is “junior react developer”, “senior react developer”. So this meme seems to have come full circle.

Is archive mode the appropriate tool for this? I would assume that’s for when a repo is no longer receiving any updates from anyone, not just when the owner doesn’t want others contributing.

I’m not sure what “piece linked” you’re talking about, since none of the parent comments of this comment actually have a link in them.

This is the first time I’ve ever heard of FUTO, but I did read their statement about open source and it sounds pretty good to me. I actually think they’re capitulating a little bit too much by deciding not to call it open source anymore. As far as I’m concerned, if the source is available and anyone can contribute, that’s open source. I don’t particularly care whether or not it’s free for Google to incorporate it into their increasingly-enshitified products or not.

Creative Commons (an org to which FUTO says they have donated) doesn’t like their licences being used for software, presumably for finicky technical legal reasons. But if you imagine the broad spirit of their licences applying to software, all the main CC licences would be open source in my opinion. All combinations of Attribution, Non-Commercial, Share Alike, and No Derivatives, as well as CC0 respect the important elements of open source.

Visitors with UK IP addresses*

FTFY

while(true) { ... }

I understand the argument in favour of dangling commas, but oh gods I hate it. Aesthetically it’s just so awful.

Not even auto-update. Just auto detect updates. Then you go and download it yourself manually.

Auto-update-detection meant that the software was calling out to a remote server, so they updated the TOS to reflect that, and people got upset.