• 4 Posts
  • 380 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle





  • ISP obviously don’t see the traffic inside your own network, regardless of the router used. But as soon as you open any kind of connection over the internet, incoming or outgoing, your ISP has to have some information about it to route the traffic. DNS over TLS doesn’t hide that your browser opens connections to servers, they can see if you use wireguard to access your services (not which ones, just in general that there’s traffic coming and going) and even if you use VPN for everything they can still see the encrypted VPN traffic and, at least technically, apply pattern recognitions on that to figure out what you’re doing. And if you use VPN then your VPN provider can do the same than your last-mile internet provider, so you’ll just move the goal by doing that.

    Last-mile ISP is going to be a middleman on your network usage no matter what you use and they’ll always have at least some information about your usage patterns.


  • ISP can see your traffic anyways regardless if their router is at your end or not. In here any kind of ‘user behavior monitoring’ or whatever they call it is illegal, but the routers ISPs generally give out are as cheap as you can get so they are generally not too reliable and they tend to have pretty limited features.

    Also, depending on ISP, they might roll out updates on your device which may or may not reset the configuration. That’s usually (at least around here) made with ISPs account on the router and if you disable/remove that their automation can’t access your router anymore.

    So, as a rule of thumb, your own router is likely better for any kind of self hosting or other tinkering, but there’s exceptions too.



  • You are on the right track. Installing Debian packages don’t require password to access shared libraries but to write into system wide directories. That way you don’t need to install every software separately for every user. Flatpacks are ‘self sufficient’ packages and thus often way bigger, since they don’t generally share resources.

    From security point of view there’s not much difference in every day use for average user. Sandboxed flatpacks can be more secure in a sense that if you harden your system properly they have limited access to the underlying system, but they can be equally unsafe if you just pull random software from a shady website and run it without any precautions.

    Flatpacks tend to have more recent versions of the software as they can ‘skip’ the official build chain and they don’t need to worry about system wide libraries. Tradeoff is that the installations are bigger and as flatpacks run on their own little sandbox you may need to tinker with flatpack environment to get access to files or devices. Also if you install flatpacks only for your user and you have multi-user setup other users of the machine can’t access your software, which might be exactly what you want, depends on your use case.

    Personally I stick with good old Debian packaging whenever possible, I don’t see benefits of containers like flatpack on my own workstation. Newer software releases or using software not included in official repository are pretty much the only exceptions when flatpacks make more sense to me.

    But there’s a ton of nuances on this, so someone might disagree with me and have perfectly valid resons to do so, but for me, on my personal computer, flatpacks just don’t offer much.




  • Age verification is one thing, but I routinely verify my id online. Banking, insurance, taxes, various other government things, car registrations, some of the kids school stuff and so on. We have pretty decent infrastructure in place here in Finland and the entities I identify myself online already has my info anyways. I can use either my banking app or mobile verification to securely prove I am who I claim to be and the systems have roughly the same user experience than MFA tokens.

    Each of those are roughly zero-knowledge, the website I log in receives just “User with login token xxx is IsoKiero with SSN 123456789” and the tokens expire after a while. Also there’s restrictions in place that my insurance company can’t just sell my data to whomever unless I opt-in for their “marketing” program (not going to happen) and even then there’s some limitations on how they can use the data.

    The same system could be adopted to age verification, but that’s a whole another can of worms.




  • Sound and power consumption. At least in my case those are important if I was going to store data at my mothers house. Power consumption might not matter that much, but HDD sound definetly does. And even with spinning rust hardware cost would be somewhere around 250€ compared to ~20€/month of cloud storage.

    YMMV, in my scenario it’s just easier to use a cloud provider.


  • That absolutely works, but when I built my offsite backup to hetzner I also thought about setting up own hardware and came to conclusion that for myself it doesn’t really make a ton of sense. New RPi + 4TB ssd/m.2 drive with accessories adds up to something around 400€ (if that’s even enough today), or few years worth of cloud backups. With own hardware there’s always need to maintain it and hardware failures are always an option, so for me it makes more sense to just rely on big players with offsite backups. Your case might be different for various reasons, but sometimes renting capacity just makes more sense in the big picture.




  • Wikipedia has a decent history lesson on Fedora. It’s not just sponsored by Red Hat, it practically replaced the open version of RHEL, so it’s pretty tightly tied to the Red Hat company. CentOS was a bit similar case, which is now discontinued and functionally replaced by AlmaLinux.

    Red Hat has already a lot of control over the project, but if they decided to do something stupid with it, something else would take Fedoras place pretty quickly, so I don’t see any ‘corporate threat’ to Fedora nor Linux community in general. That’s the way things have been for a long time and Red Hat has contributed quite a lot to the Linux development over the years which we all can enjoy.

    Fedora might get obsolete in the future, maybe because of changes in Red Hat or maybe for some other reason. New distributions raise and others pan out for multiple reasons. Mandrake (or later Mandriva) was somewhat popular at the time, but it’s now dead. Damn Small Linux had it’s userbase for a while, but it’s also now dead, like a handful of other somewhat decent sized projects.



  • In theory Canonical could lock down Ubuntu like that, but it would be the end of Ubuntu. Switching over to Mint or Debian is not a big deal for majority of the linux-users and also Ubuntu would lose all the advantages they can currently pull off from Debian package maintainers. Also I suppose it would bring a ton of headaches with licenses, but IANAL, so don’t quote me on that. And, obviously, that would kill snapcraft too as I don’t see any incentives for developers to support walled gardens for free, so it wouldn’t be all bad.