• 0 Posts
  • 25 Comments
Joined 3 months ago
cake
Cake day: June 5th, 2025

help-circle







  • I had a similar setup to this awhile back. You have to port the number to your VoIP provider of choice and then decide on what client you are going to run (no need for SIM card). I was wanting voice service and only needed limited SMS, so I went with linphone (and played around with zoiper too). If you are needing good SMS support, then JMP is probably the best. It supports both SMS and MMS. You won’t get E911 access I believe, but as data only its a good solution.

    Free wifi is all over the place and if you wire up a mobile hotspot in your car (yes it somewhat defeats the purpose), you can get some pretty decent coverage.


  • I think the idea of an IP address (IPv6 or not) providing anyone a semblance of privacy is wishful thinking in this age. Google ad revenue in the EU is estimated to be lower because the power in GPDR areas isn’t in PII obfuscation, its in the consent model. Positive opt-in to Legitimate Vendor Interest makes tracking difficult, not whether your IP is generic. You have to remember companies like Google are still able to monetize off of users in mobile CG-NAT environments in the US/EU. Given the roughly 150 other metrics Google (or any publisher/SSP would have access to), removing one doesn’t really stem the tide.

    What’s also interesting is how IPs become anonymized. For IPv4, the industry standard I kid you not is to take the 4th octet and mark it zero. That’s it. It just assumes carriers use /24 CIDRs like someone’s home network might. The funny part is what if that was 50.50.0.0/22? A publisher could in practice replace one user’s IP with another user’s IP which means that they still would be passing PII unanonymized which could violate GDPR.

    IPv6 uses the same basic system. 2001:db8:85a3:8d3:1319:8a2e:370:7348 becomes 2001:db8:85a3::. You just truncate at the 64th bit. Rolling through available host bits doesn’t really matter then. IPv6/IPv4 really aren’t ever used for Google user syncing.



  • I would only expose a port to the Internet if users other than myself would be needing access to it. Otherwise, I just keep everything inside a tailscale network so I can access remotely. Usually I believe people put a reverse proxy in front of the Jellyfin server and configure your certificates from there. So Jellyfin to proxy is insecure and then proxy to internet is secure. Lets Encrypt is an easy way to do that. And if you are going to expose a port you definitely want fail2ban monitoring that port.

    If using tailscale funnels, you can technically skip the certificate part as that’s done for you, but that would take away from the learning experience of setting up a proxy.





  • One other thing I didn’t mention is it depends on the backup tool you use. Not all of them are filesystem aware. What that means is if you have hardlinks present those will not be preserved.

    That can be important to remember as it will bork things down the road with the restoring. If you aren’t familiar with linking: Hard links point to actual data (think of it like a pointer in C). Soft links (symbolic) point to file path.


  • Have any other distros been tried on this box and do the same issues present with them? I think the recommended PSU combined with an RX580 is 600W, so you might try swapping PSUs. Another option if you don’t have a spare to test with is to undervolt the GPU. If it stabilizes at that point, it would suggest the PSU needs replacement. At least that way you wouldn’t be dropping money on a hunch.

    Another good indicator of that being GPU/PSU issues is the fact you mention not being able to get past the login screen. Both X11 and Wayland (especially Wayland) crank up the VRAM usage at that point due to compositors caching and whatnot


  • For me, I tend to focus on specific directories I know I’d need data from (or that will just be a hassle to rewrite config for). I have a scripts folder that gets backed up, Books, .mozilla, etc. A lot of things I just know I won’t need like .cache. That folder is 7GB and mostly just the cache from yay needing to be cleared out.

    I don’t backup my entire home directory because I’m worried ACLs may change or other little issues that will take more time than its worth to correct. That said, you could. You worried about something like that, you could pull the existing ACLs: find ~/ -type f -exec getfacl --absolute-names {} + > home_acls_backup.txt and then restore them: setfacl --restore=home_acls_backup.txt

    I haven’t really used KDE much, but I know it has a theme data in .local/share that you’d want (and probably the .cache folder as well). GNOME keeps theme data in .themes, .icons, .fonts. They might just be defaults, but if you have anything custom, you’d want those folders too.