

The name Google TV returned, except now Google TV is a UI running on top of Android TV.


The name Google TV returned, except now Google TV is a UI running on top of Android TV.


You can get a lot done when you’ve got 29 months in a year


RCE from integer overflow (not possible by default in Rust
It is possible. Rust will check for overflow and panic in debug builds, but will silently wrap integers in release builds.


It’s mostly Windows of course. But some people in those companies may prefer to use Linux, and this gives a them a higher chance of being allowed to do so. I for one am running Linux in a company that’s increasingly pushing for Microsoft stuff.


On their own machine, maybe not. On their employer’s machine, maybe if the employer demands it.


This isn’t quite following the format. The “And X, of course.” line in the original is an example that’s more well known than the preceding examples, something that ponytail thinks is so obvious that it doesn’t even need to be mentioned (yet still something that the average person doesn’t know about).
OK, bad examples. On the other hand e.g. X, GitHub, Pornhub, PSN, Steam or Discord do not support IPv6.
I know this is humor, but for the record this wouldn’t work. Each simultaneous TCP connection needs a unique four-tuple (source address, source port, destination address, destination port). If a lot the people behind the NAT try to connect to the same place (destination address and port) at the same time (something popular like Google, YouTube or Netflix), and their source address is the same, the source port needs to be different for each connection. So after at most 65535 connections within a short time the NAT would run out of ports and no one behind the same NAT would be able to open new connections to the same place until the NAT mapping expiries.
So you could have at most tens of thousands of people behind the same NAT, maybe even fewer to make it reliable.
The dates below the graph