received almost immediately.

(as a devops/security minded engineer) ...and companies wonder how supply chain attacks are possible

I recall there was an outage 6 years ago. And many companies migrated to dot com over night.

https://hackernoon.com/stop-using-io-domain-names-for-produc...

My previous company used Cloudinary for the purpose and amazingly lot of time was saved.

Most Indian Banking services, Payment endpoints, OTT platforms have adapted phone numbers as identity.

Your phone number is your identity. You can receive or send money only through your phone if the SIM is installed and validated by sending an SMS.

Getting a replacement SIM card requires physical verification using Aadhar (Identity service) with One Time Password validation (Email/SMS). Once the new SIM is active, you will not receive any SMS for the first 24 hours after getting a replacement SIM card. This is to reduce the attack surface of SIM Swap attacks.

AWS and their billions in IPv4 addresses - https://news.ycombinator.com/item?id=24839887

https://gist.github.com/atoonk/b749305012ae5b86bacba9b01160d...

AWS adds an extra 5.5M IPv4 addresses(https://github.com/seligman/aws-ip-ranges) - https://news.ycombinator.com/item?id=28177807

With all that investment in addresses I'm surprised AWS is still the first cloud provider to charge for them. (As far as I know.) It will be interesting to see if other cloud providers will follow, and if the cloud providers compete over the price or just match AWS. It kind of feels like AWS charging for V4s will "give permission" to other providers to charge.

I'm also curious if the price will come down over time as addresses are yielded back. I guess it depends on if their goal is to recoup all the money they spent on addresses, or just to avoid running out.

AWS is the last major cloud to start charging, not the first.

Ah, should have googled. I stand corrected.

GCP and Azure have always charged for IPv4 addresses. If anything, AWS was the last of the public cloud providers to provide them for free.

I've even seen small VPS hosts have discount plans if you turn off the v4 address.

Wait! Why not bitcoin?

Pointing to cloudflare dns circumvents the issue for now.

move away from ISP DNS to 1.1.1.1 to temporarily solve the issue.

Some ISPs still tamper with DNS traffic irrespective of which DNS server they're to/from. githubusercontent.com has no DNSSEC, so it's not tamperproof.

It wouldn't be tamperproof even with DNSSEC for most of that ISP's customers, because DNSSEC is server-to-server, and collapses down to a single "yep, we checked DNSSEC" bit in the response header. This is a big part of why nobody does DNSSEC, and why the browsers adopted DNS-over-HTTP to solve this particular problem.

Through what mechanism is it possible for them do bypass custom DNS servers? Does DNS over other protocols prevent this tampering?

DNS traffic is plaintext. MITM is all that's needed to be able to bypass custom DNS servers. An ISP, obviously, has to be in an MITM position to be able to provide internet service.

Here's an example: https://jeff.vtkellers.com/posts/technology/force-all-dns-qu...

cloudfare + OpenDNS .

works like a charm

Standard marketing page for improving SEO.

Short answer: it depends

Subscriptions lock you in on various levels. It’s very similar to renting a house. You can get kicked out by the owner.

Subscriptions for individuals is different from subscriptions for companies. Companies want to optimise time, individuals may want to optimise cost

personally, I am inclined to pay for IDEs as I spend more than 50% of the time on it, but not so much similar amounts when I use tools no more than 5-10 times a day.

Agreed. I liked 1Password a lot more when it was not subscription-based. The client is worse, the reliability is worse, the subscription is painful. The value is not there.

But it's a password manager and I use it. Perhaps I will bother to investigate alternatives and switch before my next renewal.