Ext4 does not have CoW.
That's the only true part of this comment.
As for everything else:
Ext4 uses journaling to ensure consistency.
btrfs' CoW makes it resistant to that issue by its nature; writes go elsewhere anyways, so you can delay the "commit" until everything is truly written and only then update the metadata (using a similar scheme again).
Please read https://en.wikipedia.org/wiki/Journaling_file_system.
Made by one of the people who made Lemmy btw ;)
Reverse proxy can mean different things in different contexts. What kind are we talking?
Don’t have to re-upload every image from my phone as my network is 100/30 mbps
Is your immich server in a different network? But your photos are already on that server, right?
It's used in many cases where the machine may not be on the LAN and LAN is a technical term. "Internal" is not and to me signifies that it's "not public" aswell as probably managed by someone, well, internally at the entity you're with.
That could be Cloudflare or any number of DNS providers out there.
I can highly recommend desec.io for this purpose.
Get yourself a domain name. It doesn't cost a whole lot and also allows you to complete DNS-01 challenges for SSL certs. It's also, like, your own. That's also a requirement for owning your email address.
(If you really don't want to pay and don't care about email, you can also use a shared domain DNS such as dedyn.io.)
You then simply set records to the Tailscale IP addresses of the hosts and you're good to go. Alternatively, you can also set them to the hosts' LAN subnet addresses and forward your subnet via a single subnet router; that's how I do it.
That has nothing to do with Jellyfin itself. Any comparable service will have the exact same issue because the root cause are browsers not supporting the container.
Yeah, I've noticed the PayPal issue aswell.
One "hammer" mitigation to most threats could conceivably face when self-hosting is to never expose your services to the internet using a firewall. "Securing" your services against a small circle of guests/friends/family members in your home network is a lot simpler than securing against the entire world.
If you need to access your services remotely, there are ways to achieve that without permanently opening a single port to the internet such as Tailscale or ZeroTier.
Otherwise, commonly used tools in self-hosting such as Docker or VMs usually offer quite decent separation even if a service is compromised.
Nothing replaces good security hygiene though. Keep your stuff up-to-date. Use secure methods of authentication such as hard to guess passwords or better. Make frequent backups (3-2-1). The usual.
copy your bank card nfc
From what I've been able to find, this is not possible with modern cards: https://android.stackexchange.com/a/21986/283347
At around 70%, fragmentation issues start becoming apparent with ZFS IIRC. Though they shouldn't be this apparent.