Skull giver

Revanced has that, as well as a load of other features. Can be used without root access these days.

They’re teachers, they already have a full time job, they don’t need a side job of syadminning their own laptops.

Upvoted for actually posting an unpopular opinion. I disagree with your reasoning, but at least your opinion has some arguments backing it.

Fuck Github for refusing to set up some kind of IPv6 proxy is all I’ll say on the topic.

I know several companies that, because of bad network planning, have ended up using public address ranges as internal IP addresses. IPv6 would’ve solved this easily, but I don’t think the relevant network admins ever bothered to learn network configuration beyond 1990. But hey, who needs that arbitrary /8 anyway, right? Not like anyone’s going to host DNS on 1.0.0.0/8!

A factor in favour of jet fuel is that as the plane burns fuel if becomes lighter, thus consuming less fuel. Batteries stay the same weight. The difference between a full plane and an empty plane can be 18 metric tonnes. Super cheap operators tend to carry only a small extra margin of fuel over the amount technically necessary to make a trip, because it makes a real difference.

That means the energy density you need in this comparison isn’t really linear. If you’re doing Taylor Swift flights to the couch and back, you can save a lot of weight by having a minimal amount of fuel in the tank, but with an electric plane you’ll always have to have the full battery in case you need to go somewhere further away.

In the instance of UDP handshakes yes, you need local software to initiate the connection on one of your devices somewhere (I highly doubt that your home router verifies the origin of those packets, so a hacked printer or IoT crap can open ports to your desktop no problem). Other problems are harder to solve.

NAT is great at what it does, but it does not guarantee security. It blocks straightforward attacks, but brings in tons of edge cases and complexity that sophisticated attacks can abuse. At the same time, the same security can be achieved using IPv6 and a firewall without all the complexity.

It’s a neat workaround that means you don’t need to mess with subnetting and routing tables when you do stuff like run virtual machines and when your ISP doesn’t offer IPv6. It was designed so larger businesses with 10 machines could access the internet without spending a lot of money on a /30, not to replace firewalls, and it still works well for what it’s designed to do.

Not really, though. It was never designed as a security boundary. You can “open” a UDP port by sending UDP packets to another host, and then that host can send UDP packets to you, for instance. Usually the IP addresses of the two hosts are exchanged through a third party, and that’s how STUN/TURN works in essence. Without this, you’d need to port forward every UDP connection manually, both incoming and outgoing.

NAT only protects you when you have hosts that only communicate along preset routes, but then a normal firewall will also work fine. It’s not like having a public IP means any traffic will actually go through, every modern consumer router has a standard deny all firewall. At best, it sort of hides what devices are sending the traffic.

Meanwhile, NAT has flaws breaking traffic (causing NAT slipstreaming risks, like I linked elsewhere). It also has companies like Nintendo instruct you to forward every single port to their device if you have connectivity issues. If that forward is not towards a MAC address, and your PC gets the IP your Nintendo Switch used to have, you’ve just disabled your firewall to play Animal Crossing.

If you want to, you can do NAT on IPv6. Every operating system supports it, even if it’s a stupid idea.

Actually, the Dutch government has mandated that all of its services need to be IPv6 compatible.

The longer you try to avoid IPv6, the harder you’ll make your life when you eventually need to use it.

It’s really not that hard, especially compared to the kludge of protocols that make up IPv4. I know change is scary and difficult, but if you can do IPv4, you can do IPv6.