The reason you can't see it isn't that the drop isn't significant. It's because it's only been a week, and on a 10 year scale, it's just that last pixel on the graph. Meanwhile, it has shifted the entire graph upwards.
Today's announcement is simply the inevitable switch from "Search and Rescue" to a "Recovery" effort. It's been 2 weeks, someone had to make the call that the possibility of finding people alive has diminished to the point beyond hope.
As a "Recovery" effort, the pace will continue, but they will no longer risk lives to find the wreckage.
If they get rid of the service and the data pre-emptively, they can safely destroy the data. Once they've recieved an NSL, they have to comply with the order and provide the data (or at least the metadata) or be in contempt of court.
In a statement to TechCrunch about whether the shut down was only because Silent Circle felt email was insecure, CEO Michael Janke tells us
“It goes deeper than that. There are some very high profile people on Silent Circle- and I mean very targeted people- as well as heads of state, human rights groups, reporters, special operations units from many countries. We wanted to be proactive because we knew USG would come after us due to the sheer amount of people who use us- let alone the “highly targeted high profile people”. They are completely secure and clean on Silent Phone, Silent Text and Silent Eyes, but email is broken because govt can force us to turn over what we have. So to protect everyone and to drive them to use the other three peer to peer products- we made the decision to do this before men on [SIC] suits show up. Now- they are completely shut down- nothing they can get from us or try and force from us- we literally have nothing anywhere.”
Interesting strategy. So, while they were not able to store the content of the emails, they still retained the metadata. That metadata could be subject to subpoena, and if they destroyed the data after a request, they'd be in contempt of court. Dropping the service pre-emptively lets them delete all the data before they are asked for it.
Would be great to be able to deploy to multiple locations with one button. Even better, to deploy to an arbitrary number of locations based on how many cloud instances are running at the moment.
Also, maybe a multi-stage deployment.. One button to push from Dev to Staging, another from Staging to Production.
> Since the 1890s, U.S. customary units (the mile, pound, teaspoon, etc.) have all been defined in terms of their metric equivalents.
I don't know what the "official" definition is, but pounds are most often defined as 0.45359 kg. The problem is, pounds and kilograms are fundamentally different.
A pound is a measurement of weight (or the force that gravity exerts on an object), while kilograms are measures of mass. When you are measuring different things, we run into all kinds of issues of translation. You almost never hear of a pound being converted to "newtons" which would probably be more accurate.
If you know someone who was running the marathon and haven’t heard from them, you can see if they logged times here:
http://raceday.baa.org/individual.html
Google admitted the mistake:
“We’re sorry about the inconvenience this morning to people trying to search for Digg. In the process of removing a spammy link on Digg.com, we inadvertently applied the webspam action to the whole site. We’re correcting this, and the fix should be deployed shortly.”
Full memo from Andrew Mason (his jottit.com link isn't working):
People of Groupon,
After four and a half intense and wonderful years as CEO of Groupon, I’ve decided that I’d like to spend more time with my family. Just kidding - I was fired today. If you’re wondering why… you haven’t been paying attention. From controversial metrics in our S1 to our material weakness to two quarters of missing our own expectations and a stock price that’s hovering around one quarter of our listing price, the events of the last year and a half speak for themselves. As CEO, I am accountable.
You are doing amazing things at Groupon, and you deserve the outside world to give you a second chance. I’m getting in the way of that. A fresh CEO earns you that chance. The board is aligned behind the strategy we’ve shared over the last few months, and I’ve never seen you working together more effectively as a global company - it’s time to give Groupon a relief valve from the public noise.
For those who are concerned about me, please don’t be - I love Groupon, and I’m terribly proud of what we’ve created. I’m OK with having failed at this part of the journey. If Groupon was Battletoads, it would be like I made it all the way to the Terra Tubes without dying on my first ever play through. I am so lucky to have had the opportunity to take the company this far with all of you. I’ll now take some time to decompress (FYI I’m looking for a good fat camp to lose my Groupon 40, if anyone has a suggestion), and then maybe I’ll figure out how to channel this experience into something productive.
If there’s one piece of wisdom that this simple pilgrim would like to impart upon you: have the courage to start with the customer. My biggest regrets are the moments that I let a lack of data override my intuition on what’s best for our customers. This leadership change gives you some breathing room to break bad habits and deliver sustainable customer happiness - don’t waste the opportunity!
its an interesting academic investigation. In theory, you could do 10M pv/day with a relatively small archive. I bet some recently launched sites that take off quickly (PandoDaily for example) probably do decent traffic levels with a pretty small number of posts, that would probably fit into a small cache.
But that's all theoretical. There's no way someone running a site with that kind of traffic should be running on shared resources without an infrastructure. When that $15 server needs a reboot, the site is offline, and that would be a significant amount of lost traffic.
Capacity, speed, redundancy and cost of downtime... You really shouldn't run on this kind of architecture.
"At the time Yahoo had fired all the staff working on Delicious"... "However it looks like nobody wrote down the blog password, or got it from the departing staff. So nobody can put new posts there"
Looks like they're running Wordpress 3.0.1 on the blog. If they have access to the database, should be easy to gain access...