571–580 of 623 posts
Earlier quoted context omitted.
I still mourn the loss of Google Reader.
This is the most hilarious meme on HN
Earlier quoted context omitted.
Exposure Notifications was designed to be deprecated, though? It was a pandemic thing.
The pandemic is ongoing, we've just started calling the disease "endemic" but that doesn't make it less dangerous. We have however wound down most of the protective measures. Germany has retired the official bluetooth contact tracing app earlier this year. I wouldn't be surprised if Google retires theirs this year or the next.
Google does not have their own app. Exposure Notifications is the cross-vendor low-level API which apps like Germany's is (...was) using.
Who do you use as a registrar? Why do you like them? Do you recommend them?
Earlier quoted context omitted.
I have a conspiracy theory that a lot of domain registration companies like GoDaddy sell the domain name searches to squatters (sometimes themselves). The larger cloud companies don't have so much incentive do this. I always look up domains from the terminal.
>The larger cloud companies don't have so much incentive do this. I always look up domains from the terminal. somebody runs those whois servers. verisign runs .com and they like money just as much as the next guy - i wouldn't expect your lookups of unregistered domains to be unsold no matter how you do them.
Earlier quoted context omitted.
Having any sort of code on python 2.7, means you don't give a rat's ass about security. It also immediately means your code should be assumed to have back doors, vulnerabilities, because python 2.7 almost certainly does! This is what happens, when no one is maintaining software. Security is more important that anything, certainly than having time or not to update your code. You're 100% in the wrong here, and Google i…
Not all code is a website or publicly accessible…
Earlier quoted context omitted.
The problem with the logical conclusion of this argument is that it’s networks all the way down. Remember verisign site finder? https://en.m.wikipedia.org/wiki/Site_Finder That’s the sort of crap you end up with when every network operator asserts their “right” to modify traffic. Don’t get me wrong I do dns filtering on my home network and block public dns over http endpoints, but there is some balance to be had here…
Let's Encrypt is just the carrot (and to be clear, Google is not just a top sponsor, but two of Let's Encrypt's other top sponsors are organizations themselves sponsored by Google). Let's Encrypt is not Google but absolutely is downstream from that money flow. Meanwhile Google itself is the stick. Google has used it's policy control over Chrome to effectively mandate using Let's Encrypt, by making using certificates…
You can still have "classic" certificates - if exchanging certificates is enough of a nightmare that you can't even do it once a year, it's a clear indicator your tech stack is brittle beyond belief and should be updated anyway. Meanwhile if you're using a modern cloud-based stack the provider (e.g. AWS ACM) does the work for you, and acme.sh makes it a breeze on on-prem/bare-metal stacks as well.
> DoH, QUIC, and ECH are where it really begins to go "too far", where we're obliterating norms to ensure nobody can tamper with ad delivery.
What? Browser extensions still exist and DoH doesn't impact whatever you're putting in /etc/hosts, that one works just fine.
Earlier quoted context omitted.
Google once tried to setup a 'smart' community in Toronto, including wanting control over police and laws and all sorts of other absurd blather. Can you imagine living in such a community? I can't believe people rely upon gmail for anything . Integrate anything . When I see a business using gmail for a backend, I question their entire business model, because I question their judgement .
What do you mean "gmail for a backend"?
Earlier quoted context omitted.
Unless it is air gapped, it is accessible.
at the point that would matter you have more pressing things to worry about then old code.
If you think security is an afterthought, you're doing it wrong.
Earlier quoted context omitted.
at the point that would matter you have more pressing things to worry about then old code.
It's not just old code, it's an old compiler too. One with security issues well known, unpatched. If you think security is an afterthought, you're doing it wrong.
this also really highlights the problem with python's 2 vs 3 split: there is a large body of work that will never be updated and will forever run 2 including actual web/publicly facing code. And saying "just upgrade because security" isn't going get much of that code upgraded.