personally, i’d have pretty big benefits for my homelab if i could use my own ipv6 range for everything. having only a singe public IP is just very limiting.

sadly, my ISP does give out ipv6 for home networks, but i cannot connect to any of them from my mobile phone with the same carrier. so that’s fun. they talked about rolling out ipv6 on mobile networks years ago, but i guess it’ll take a few more…

i’m thinking long term - sure, right now google knowing everything about me isn’t dangerous. but if a massive political slide to the right happens in countries that host services, suddenly all the saved data from many years ago can be used against me. and don’t fall for the “end to end encrypted” bullshit either - all these services can flip a switch and have your encryption keys instantly. (or, if its an open source app that ACTUALLY keeps keys on the device only, which is extremely rare, it’s one update away from happening, and you better read the whole diff every update and compile the app yourself.)

that’s why i choose to self host everything. yes there’s a risk of being hacked, or installing something malicious because i don’t read every diff on every update. but i feel more confortable with it being my own responsibility, and my services are also all on seperate virtual machines to hopefully isolate any breaches.

using dd for that is outdated info that everyone keeps blindly parroting with zero understanding why. cat is simpler and works fine.

note: both cat and dd only work for this when the image is made in a compatible way, my linux isos always work fine but a windows iso didnt and needs a more specific tool.