I suppose then, for any child born around 00:10 on 1 January, there might be some pressure to encourage the doctor to write the birth certificate as something more like 23:50 on 31 December? Because of the social prestige with being older?

Or maybe the opposite, since being physically older than your peers is correlated with better academic and sporting performance?

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.

A few years ago, iirc, the Korean government instructed people to stop using the traditional system and to use the international system instead. Has that had much of an effect in practice, or are people largely ignoring it? Or do you think it’s something that younger generations will pick up more over time while older people continue using the traditional system? (This last option being sort of what happened in Australia when we transitioned to metric through the '70s.)

Also, what happens to someone born on 1 January? Are they born du sal, and thus the youngest of their sal, or born han sal and remain han sal for a whole year?

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?

Really interesting! Thanks!

Part of the reason I ask: I bought a Synology (4-bay, 1 TB each in Synology’s RAID 5–like format) a while back with the intention of using it as a hybrid NAS & server. But have been repeatedly struggling to get it to do actually run the applications I wanted to run. And then started trying to get some of the things I wanted to run on my Synology to instead run on a Raspberry Pi…same problem. The weird architecture and distro makes some things not work smoothly. So have been thinking about getting a Mini PC with a standing x86_64 processor running a standard Linux distro to be a proper server, and using the Synology more exclusively for file storage & sharing.

Some of the things you listed there are definitely things that were on my radar to get around to running myself anyway (e.g. Immich, Watchtower). Others I had never heard of, but was already considering looking for an equivalent (Affine, Jotta—though for notesI was hoping Nextcloud would have a suitable app), and others I didn’t even think of (Linkwarden looks very interesting).

Since you’ve got a Synology already, I’m curious what value you see in the Mini PC running a Samba server? I’m also curious why you go with the Synology as your reverse proxy. Just the ease of the included tool? Does it also handle TLS termination, or how does that work in your setup?

I clicked into the comments for one fucking reason. And was left very disappointed.

What do you run on your home server? What sort of hardware is it running on?

Also Republicans:

But look, there was a shooting in Australia two weeks ago, so clearly gun laws don’t work!!1!11!!1!

On the nation-state

Then I think it’s really important that you are clear about that, mainly with yourself, but also any time you talk about the issue in public. Conflating Israel with all Jewish people is a deliberate attempt by the Israeli government and its supporters to make it easier for them to brush off criticism of their actions as “antisemitism”, and is itself an antisemitic act.

It’s also a major factor in increasing genuine antisemitism, because some people see the atrocities the Israel government is committing, see that Israel claims to be acting on behalf of all Jews, and then they turn around and blame all Jews for the actions of Israel. Which only serves to help Israel’s case, which is why it’s so important we be clear about the distinction whenever possible.

that’s kinda harsh on jewish people

Harsh on Jewish people as a whole, or harsh on the nation-state of Israel and its supporters, many of whom are Jewish?

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.

Software very rarely has an individual’s vision behind it in the same way movies do. At least publicly. There are a small handful of game developers you could say that about, but outside of games the only time a single creator’s vision is relevant in that way is when they also do have creative control over it, and so the need for such a pseudonym doesn’t exist.

Age of Empires is a bit different, because I don’t think they’ve moved the same game around between different studios in the midst of development. ES got shut down in 2009, with all existing Age of Empires games having long since ceased development. Then in 2013 Microsoft decided to release an HD remaster of the 1999 Age of Empires 2, and they brought Hidden Path on to do that. And then with the 2019 Definitive Edition they brought on board Forgotten Empires (who had also developed the official expansions in HD). The new development team in each case was being brought on to create a completely new release.

The KSP2 and Bloodlines 2 examples above both involved unreleased in-development games being given by the publisher to a different development team, and Skylines 2 is a still-supported game being given a different developer for future updates.

Bloodlines 2 came to my mind. And it even has the same publisher as Skylines.

We can just do this.

outlaws anonymous communication by requiring every citizen to verify their age before accessing a service

This is likely to be the case in practice, but technologically, it does not have to be the case.

If the age verifiers (which IMO should be the governments themselves^[1], but could also be a private third-party, as long as it’s not the same as the social media company) only ever receive a blinded token representing the user, verify the user’s age, and then the user brings that token back to the social media site, unblind it, and present them the signed token, there is no way for the age verifier to track which sites a person visits, and no way for the sites to have any detail about who their users are (other than what they already have).