Judges don’t prosecute people. Prosecutors do. She literally has nothing to do with the charges being brought against defendants in her court. It’s up to the prosecutors to file charges and persue cases like this.

If the pollution bothered them so much, why do they building nests in it? That sounds like their problem ¯\_(ツ)_/¯

Have you tried increasing your first layer extrusion width? A wider first layer will squish the filament into the build plate more, which might help. I use a 140% first layer width.

I’ve been using FolderSync. It let’s you sync to/from a remote server through a bunch of different protocols like SMB, SFTP, and WebDAV. You can schedule it to run automatically.

I haven’t tried it myself, but I think there is a way you can get Tasker to run scripts in Termux. You could set up your own rsync scripts that way.

If you’re worried enough to encrypt the drive, you shouldn’t be auto mounting it.

This really depends on your threat model. If you are only concerned about the drive getting stolen, or wanting to keep the data on it private if you need to RMA the drive, mounting it automatically on boot with a key stored on the rootfs can be perfectly fine. If you are a journalist in a hostile country and protecting your sources from state level actors is a matter of life and death, then yeah, this would be woefully insufficient.

You can leave it.

As long as you ran systemctl daemon-reload, you should be able to try sleeping without needing to reboot.

It might be due to https://github.com/systemd/systemd/issues/33083.

Try disabling user session freezing when sleeping:

sudo systemctl edit systemd-suspend.service

Add the following to the file:

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

Reload systemd:

sudo systemctl daemon-reload

After that, try sleeping and waking again.

What filesystem are you using on the external drive? If it is NTFS or FAT, they won’t store permissions on the filesystem, which would explain why the owner/group changes are not persistent. To fix that, you can set the uid/gid on mount in your fstab.

/dev/mapper/YOUR_DRIVE /path/to/mnt <fstype> rw,uid=<jellyfin_uid>,gid=<jellyfin_gid>,dmask=0002,fmask=0113

Are you using the default bridge? I have a similar setup (with Traefik instead of NPM), and for each compose file am using separate networks for the internet, proxy, and backend services.

services:
  some_service:
    ...
    networks:
      - frontend_network
      - proxy_network
      - backend_network
  backend_service:
    ...
    networks:
      - backend_network
networks:
  frontend_network:
    driver: "bridge"
  proxy_network:
    driver: "bridge"
    internal: true
  backend_network:
    driver: "bridge"
    internal: true

Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot.

Just use nofail in the fstab.

Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.

If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn’t change this.