There is no good outage. But, it is great to see that when their portal/admin/webmail is down, DNS, SMTP, IMAP/POP3, SSL, Network is not affected by this.
Some of it seems to be down. I use Gandi for my DNS, I can still access my site at www.example.com but the redirection I have from example.com to www.example.com doesn't work.
That would make sense, but then tym0's reply to edvinasbartkus doesn't make any sense. It would be like saying: "It seems that DNS is not affected, only hosting." and the reply being: "Yeah, but it seems that hosting is affected as well"
Web redirects are usually not called web hosting in the dns industry, even if it technically operate just like any website. It is more like an attached service for a customers dns.
It is similar how the web interface for email has technically nothing to do with the email infrastructure and email protocols, but as a service it is packaged together with email.
It's not DNS alone. In the Gandi UI you can set up a so called "web redirect" which results in an A record pointing to one of their http servers that does the actual 301 redirecting. If that http server is down, the redirect won't work.
Yes it was badly phrased from my part, I should have said:
"My DNS record for www.example.com works but the web redirection I have from example.com to www.example.com doesn't work."
Maybe that is what the issue is? Some, well many, DNS providers provide value add transparent additional features like redirect and email. If their web infrastructure is down then that might not work even though the core DNS shit does.
CNAME is aliasing, not redirecting. If www.$domain.com is CNAME for $domain.com, loading www.$domain.com will make you remain on www.$domain.com, not redirect you.
When the app is removed from the App Store, does it mean that it disappears from all phones, or it means that the new sales of the app are not possible?
In my understanding, this depends on what action Apple exactly takes. If it just removes it from the App Store, all existing installations on devices would remain and continue to work. If Apple revokes the developer's certificate, then the app would likely fail to launch sometime soon and would be removed.
I'm sure there are gaps in my understanding. Corrections are welcome.
I believe these are the different levels they have at their disposal:
- Remotely delete from everyone's devices (Apple has never used this capability, they say the ability is there in the case of malware)
- Remove from the App Store completely (keeps running if you had it installed, you can back it up to iTunes and reinstall from there, can't download from the store. I think they did this with apps that worked their way around AT&T tethering restrictions back in the day when that was a thing)
- Removed from sale (if you installed it before, you can still re-download it from your App Store purchase history)
I don't think certificate revocation is applicable to app store apps - e.g. I can revoke my own dev distribution certificate and it only kills self-hosted Ad Hoc builds. They may have per-developer app store certs only available internally as well but I think they'd use one of the capabilities above instead
When Apple removes an app from the App Store, you cannot download it anymore but it will continue to run on your device if you had it already. Apple also has the power to "blacklist" applications and prevent them from running on your device even if you've installed them (https://iphone-services.apple.com/clbl/unauthorizedApps), but this list looks empty for now. Usually what happens in the latter case is that the violation is so egregious that they will instead terminate the developer's Apple Developer account, which will have the same effect.
Eventually, they'll have a version of the file for each minute in the day. After that, the hash should ensure that no additional space is used to store the content. (I think, I don't know much about git internals.)
After that, if you assume 128 bytes per commit (timestamp, and maybe a hash or two saved?) then probably around 14 years.
Every commit will need a new tree object, containing the names, hashes, and chmod of each file/folder in the root (LICENSE, README.md, _config.yml, index.html, and bin).
I modified the script to commit as fast as possible (cycling the minutes between 1 and 60), and after 600 commits, doing "git gc --aggressive" before and after, the .git directory grows by around 460 bytes per commit.
Actually, we could just run `git commit --amend` every time and then force push. That brings troubles if I ever make other changes on another pooter though
But no other company is selling the promise of an autopilot car. For example, Audi is expected to launch renewed Audi A8 this year with Level 3 autonomous driving but it's called "Traffic Jam Pilot". Level 2 was called "Traffic Jam Assist".
Maybe bdash is more advanced with drawing graphs. In our small start-up, we love using blazer: https://github.com/ankane/blazer. Everyone can write queries, we can share it with each other, it has cashing layer for fast results, it provides basic charts, it even has maps representation. Thumbs for the team at Instacart for this OSS product.
