Rebranding without a particular purpose really only serves to make everything more confusing. See X.com

If an opinion poll is needed to validate the rebrand, after the rebrand, then it’s probably not the right choice.

The CLI has more functionality than the API, so you might have better luck listing all entries that way then looping through the details of each entry if the list doesn’t contain the datetime.

Server admin here, you can do this in a way that avoids lemmy even knowing anything has changed. Read through all of this and do some googling first if you don’t know the specific commands to use!

First, you need to set the remote volume to automatically mount correctly on system restarts. On Linux, this is done by adding an entry for it to /etc/fstab if one does not exist already. Once done, ‘mount -a’ will mount the volume.

Mount your remote volume to the filesystem and rsync the folder you want to migrate off-server to it. Take the lemmy service offline, rsync again to catch any changes from when you started.

Now, you can move the old folder that lemmy has been using elsewhere - I recommend renaming it by appending “.old” or something.

Next, you need to make a symbolic link. This link should point from the old folder’s original path and point to your remote volume. Once done, make sure everything is there and that file permissions match the ones in your .old folder - file permissions are important and you may need to recursively set them if your lemmy service runs on a different user than you were making these changes with.

Finally, say a prayer to the machine spirit, waft the holy incense, perform the ritual whack with a wrench, and start the lemmy service. Make sure everything is running properly before you walk away!

The only issue you’re likely to run into is that remote volumes are constrained by network bandwidth. This may slow down load speeds, so some kind of CDN caching solution is recommended.

Assuming any dynamically loaded module will fail, why does KernelCare exist and why is it used so prevalently in web hosting environments? It costs money, so buying it when it doesn’t work seems odd.

This triggers geometry memories with right triangles.

Angle Side Angle

I’ve never had to interact with system updates in Linux distros beyond saying “yes I want to update” in the last decade. If I didn’t want to, there’s usually a force update flag available to skip the asking part. Would I do this for a server without backups? Absolutely not. For home use? I’ll roll the dice; I have backups even if there’s a couple days of shipping time to get all 12TB mailed to me.

Of course, major distribution releases are a different monster. Fortunately, I don’t deal with those often and when I do, I migrate instead of upgrade.

Only to activate the new kernel! You can just leave the current one running with minimal issues, even less if you have something like KernelCare live patching security bugs

You can set up a Cron job or systemd timer for the root account to run that command regularly, if it is a non-interactive command!