10,712 karma · joined September 6, 2019
[ my public key: https://keybase.io/miked; my proof: https://keybase.io/miked/sigs/NDka9SDMYHUI-gYuU6qG7FGLznGEAAZU0I15VdBAjAc ]
With a myoptic view of the battlefield it is easy to convince yourself that the distractions launched to keep the military busy were the primary objectives.
If you read the bottom of the page they plan to sell it. Not sure how that works when all the software/data is open.
95 good, NT 4 bad, 98 good, 98 SE bad, 2000 good, Me bad, XP good, Vista bad, 7 good...
The plan with Windows 10 was to light their desktop market share on fire in the hopes they could see iPads in the distance and try to chase them. Windows 11 was codenamed "give your toxic ex a second chance."
There is a heck of a Dunning–Kruger joke to be made here.
Header processing and alignment were an issue in the 90s when routers repurposed generic components. Now we have modern custom ASICs that can handle IPv4 inside of a GRE tunnel on a VLAN over MPLS at line rate. I have switches in my house that do 780 Gbps.
> There was no way to move from 32-bits to >32-bits without every network stack of every device element (host, gateway, firewall, application, etc) getting new code. Anything that changed the type and size of sockaddr->sa_family (plus things like new DNS resource record types: A is 32-bit only; see addrinfo->ai_family) would require new code.
That is simply not true. We had one bit left (the reserved/"evil" bit) in IPv4 headers that could have been used to flag that the first N bytes of the payload were an additional IPv4.1 header indicating additional routing information. Packets would continue to transit existing networks and "4.1" capable boxes at edges could read the additional information to make further routing decisions inside of a network. It would have effectively used IPv4 as the core transport network and each connected network (think ASN) having a handful of routed /32s.
Overlay networks are widely deployed and have very minor technical issues.
But that would have only addressed the numbering exhaustion issues. Engineers often get caught in the "well if I am changing this code anyway" trap.
IPv6 was designed by political process. Go around the room to each engineer and solve for their pet peeve to in turn rally enough support to move the proposal forward. As a bunch of computer people realized how hard politics were they swore never to do it again and made the address size so laughably large that it was "solved" once and for all.
I firmly believe that if they had adopted any other strategy where addresses could be meaningfully understood and worked with by the least skilled network operators, we would have had "IPv6" adoption 10 years ago.
My personal preference would have been to open up class E space (240-255.*) and claw back the 6 /8s Amazon is hoarding, be smarter about allocations going forward, and make fees logarithmic based on the number of addresses you hold.
Apple's "shelf space" is not free. There are constant R&D expenses involved in introducing new sensors and screens that make the underlying apps better. They take on the support load of on-boarding users, managing the relationship, and dealing with any problems. Advertising, carrier validation, third party hardware ecosystem, etc.
Epic wants to sidestep all of the costs of building a platform, and offload support costs onto Apple.
It is not fair to me as a merchant that everyone who wants to buy a phone case goes to Best Buy. That's where all the foot traffic is. It's clearly anti-competitive that they expect me to pay for shelf space I benefit from.
And now they want to charge me to verify that the USB-C cables I'm selling actually work? How is that remotely reasonable? Just because most of my cables are faulty and customers will inevitably go complain to their customer service desk, why should I bear that cost?
Consumers deserve the right to choose accessories from multiple independent merchants inside Best Buy. Suggesting otherwise is anti-consumer, anti-choice, and proof that you hate open and accessible ecosystems.
If you know demand will go up because Microsoft announced that each new Xbox will have 2TB of RAM, that is perfectly fine. Or if OpenAI issues a press release that they intend to buy half the worlds RAM.
If you know demand will go up because you learn the volume your customer intends to purchase from your competitor during confidential negotiations, that is not ok.
NVIDIA recently told their board partners that they will need to source their own RAM and will not be bundling it with chips anymore.
If there is a supply crunch on DRAM, commercial GPU production lines will start having idle downtime. That is literally the worst possible thing that can happen to a company that has invested heavily in tooling and they will negotiate at or below cost production runs to fill the gaps if a customer can bring their own DRAM to the table.
It is already getting dangerously close to the duration of holiday freeze windows, compliance/audit enforced windows, etc.
Not to mention the undue bloat of CT logs.
If you find yourself caring about data types or actually writing a query, you should probably setup an actual database server.
I don't believe you are very familiar with LA airspace, but it will be one of the last places drones ever make sense.
LA Sheriffs are responsible for an area larger than Delaware and Rhode Island combined.
They also assist in rescue operations, transporting SWAT and crisis negotiators to scenes, flying snake venom antidotes from the airport to the hospital, and dozens of other things.
I'd say 17 helicopters and 90 employees is pretty lean given that they have a crew ready to go within 5 minutes 24/7.
Even if they "usually" start from a minor traffic violation (which they do not), the majority of individuals who run have outstanding felony warrants or are engaged in committing another crime.
At best they identify the family of browser, and spoofing it is table stakes for bad actors. https://github.com/lwthiker/curl-impersonate
If you want to avoid being uniquely identifiable stick to Chrome, signed into a Google account, running on a PC from Best Buy.
It's fun to call this a waste of taxpayer dollars until you watch a carjacked vehicle recovered with kids inside.
There is an hourglass shape to emerging technologies. Everyone uses commodity hardware and duct tape to try to win the race to the bottleneck, where everyone save 2 companies goes bankrupt. As it narrows companies have learned enough about the problem to start developing purpose built solutions. Once you pass the bottleneck enough of your engineers go to other companies that the custom solution becomes mainstream and competition grows again.
Google was working on custom chips for AI before we knew it was AI. They are going to survive either as the dominant player in AI or as the underlying platform everyone else builds on.
That leaves one other spot for everyone else racing to the eye of the needle. Anyone betting on Oracle to win on technology is silly, betting on Oracle with a bunch of generic GPUs that anyone can get is down right dumb.
Google later decided to come up with a completely different implementation called RCS to deal with the same problems. Rather than work with Apple on bringing an iMessage app to Android or licensing it, they instead tried to pressure Apple with a public advertising campaign to adopt what is frankly an inferior solution that doesn't even have reliable end-to-end encryption.
Your complaint is basically that you bought a Toyota and it does not have BMW's laser headlights that adjust brightness and angle automatically. You still have headlights, you just didn't spend the money to get the good ones.
I was a small part of the original team that built OpenDNS. I also operate a less well known public resolver now.
DNS is extremely latency sensitive. You have basically a 20ms budget to work with, which includes the time the request and response traverse the internet. It is also extremely high volume, a large public service like Quad9 could easily see single digit millions of requests per second.
There is nothing that technically prevents you from doing geofencing. Cisco has the money to absorb the costs of the additional overhead - but I could not. My first stab at the problem would be to simply shut down my servers in France to try to get out of the legal jurisdiction. I don't know if that would be sufficient without paying for a lawyer.
Quad9 absolutely has a valid argument here and it pushes more of our public infrastructure into the centralized hands of a small number of players because people like me can't afford to just run free shit on the internet anymore.