>> The encrypted chunks of the file are stored, without any user-identifying information, using third-party storage services, such as S3 and Google Cloud Platform.
There must a misunderstanding. I was asking supporting evidence that Apple ran its own storage. This is evidence that Apple is using storage service from other companies.
This! When I was on a cheap shared and hosted solution the idea of LE was waaayyy above me.
But, I moved over everything to AWS, for the same amount of money (OK, ~$0.60 more than what I was paying before - relatively nothing), and it became a piece of cake.
That initial time commitment to the move, though, will never be recouped. I do however look at it as a career-expanding experience (fairly confident in how AWS works for projects/companies), so I got that going for it.
That's really not relevant to this article. The author is not talking about crawling and indexing the entire web (although he mentions the "whole web" once, that's clearly not what he means). He is wondering why old pages -- pages that used to be in Google's index -- are no longer showing up in SERPs even when using appropriately-targeted long-tail queries.
For the same reason 'Joe Infinity page 1234567' would not be found anymore. Google thinks its not relevant enough to keep it indexed. Yes, it is debatable what is relevant enough and what isn't. But everyone who indexes 'the web' has to decide what to keep and what not. Nobody can store 'everything'.
Also it's not as easy as just keeping everything that ever was in the index in there. Then searchengines would link to noexisting urls most of the time. Most URLs have a short lifespan. Links rot pretty fast.
I completely agree with you, but your initial argument was that "Joe Infinity page ∞" wouldn't be indexed because Google cannot index every viable page on the internet. That is true, and Google will certainly set limits on what pages is crawls and what pages it indexes. However, in this instance the articles were crawled and they were indexed and they were relevant at one point in time. But google decided to remove them from SERPs for some reason or another (age, lack of traffic, etc).
Sure, but that's just more reason to use HTTPS across their entire domain and would help prevent users from being phished as easily. If I enter "apple.com" I expect all links on that page to point me to the correct location. A MITM attack from a non-HTTP page could easily alter the page and link me to https://www.xn--80ak6aa92e.com/login instead.
I do the same and it really helps my productivity. I have no clue why it actually works, but I've been using the strategy successfully for a few years now. I always suggest the idea to a coworker if they're stuck on a problem or find themselves unmotivated.
They randomise the AZ letters, because humans tend to shove things in 'a' before anywhere else - it's a psychological load-balancer.
If you want to figure out which of your AZs corresponds to another account's AZs, you can compare spot-prices, which are individual per AZ. Also, for some reason, my account doesn't have a 'b', just a-c-d-e. Weird.
Interesting that the idea is to distribute load across the zones (because people default to using A), but Google Cloud zones are uniform across all accounts and it seems to work for Google.
I heard that aws actually scrambled availability zones... so your 1a might be my 1c, etc.. Haven't confirmed it, but the comments seem to bear that out.
