Tag: google (page 1 of 6)

Awkward Moment For Google And Feedly

The Google Cloud Platform blog recently had a rather awkward moment posting about the success of Feedly, emphasis is mine:

In the middle of last year, our servers were overwhelmed with hundreds of thousands of new signups, and we experienced our first service outage. The first thing we did was move all of our static content to App Engine. Within an hour we were up and running again with 10 times the capacity we had before. This turned out to be a good thing – we added millions more users over the next few months and more than doubled in size.

I seem to recall Google telling millions of users to pack up their stuff and leave around the middle of last year. Feels strange to see Google excited to brag about their ability to send millions of users to a competitor. At least they used to be competitors, before Google decided to get out of the reader space.

Read Access on Google Servers with XXE

Detectify explains how they gained read access to production servers at Google:

One system caught our eyes. The Google Toolbar button gallery. We looked at each other and jokingly said “this looks vuln!”, not knowing how right we were.


They were able to leverage XML External Entity ( XXE ) processing to read local files on Google’s production servers. If you haven’t read up on XXE go watch Mike Adams talk at WordCamp SF 2013, the video is only 30 minutes.

Be very careful when processing XML, it can come back to bite you in very bad ways.

Export Gmail and Google Calendar Data

Great to see this news yesterday:

Starting today we’re rolling out the ability to export a copy of your Gmail and Google Calendar data, making it easy to back up your data or move to another service.

From Official Gmail Blog: Download a copy of your Gmail and Google Calendar data.

I’m not sure how well downloading 7GB of email is going to do in mbox format, exporting Gmail data hasn’t been enabled for my account yet. I like that Google is taking this step though, it is the right thing to do.

Opt Out Of Google’s Shared Endorsement Ads

Google recently announced that their ads are going Facebook style by including the image and name for your account as an endorsement on ads. This came as part of an update to their terms of service.

To opt out of this go to https://plus.google.com/settings/endorsements?hl=en.

Make sure that box stays unchecked.

Make sure that box stays unchecked.

You will need to make sure that the checkbox towards the bottom of that page remains unchecked.

I wonder how long until Google starts showing derived endorsements on ads. If you carry an Android device around they’ll be able to see what places your visit most frequently, which they might want to use as an implied endorsement. That could make Google Now a huge source of ad related data.

Google and Motorola

It has been more than two years since Google announced they were going to acquire Motorola Mobility. More than a year since the deal closed.

Yet it appears that Samsung is the top Android device vendor, by an enormous margin.

Did Google really pay $12.5B just to have Motorola Mobility fail as an Android device manufacturer?

Farewell Google Reader

The day has finally arrived, Google Reader is no more. You will be missed.

PageSpeed Online

Unfortunately the Chrome PageSpeed plugin hasn’t worked for me in a long time. WebPagetest.org appears to no longer include PageSpeed analysis in reports either.

That leaves PageSpeed Online has the only option for running a PageSpeed analysis on a site.

I really liked using the Chrome plugin (back when I could still get it to work), but I’m happy to see there is at least one place where you can still run a PageSpeed analysis.

Google Fiber in Provo Gets Even Stranger

Last week I mentioned the concerns over the $1 sale price of the iProvo fiber network to Google. Well, the Provo Google Fiber project continues to get even stranger than that. From the Daily Herald article on the Provo city council vote:

Curtis also introduced new information and obligations that had not been discussed during the initial excitement of last week. There will be a need to spend some money. For one, the map on where the fiber conduits are actually laid is not available and it may take some guessing at a few locations as to what side of the street the fiber backbone is under. There is also an agreement the city will have control of the fiber to the schools and the city operations. Money has already been set aside from the telecom fund to take care of those needs. An insurance policy will also be needed to protect the city from the unknown. The total cost for city outlay will be approximately $1.7 million.

Emphasis at the end is mine.

A more detailed breakdown was reported by The Salt Lake Tribune:

  • $722,000 “for equipment in order to continue using the gigabit service for government operations already using the network, such as the operation of traffic lights and police and fire services.”
  • $500,000 “to a civil engineering firm to determine exactly where the fiber optic cables are buried, a requirement by Google”
  • $500,000 “for an insurance policy to help mitigate any possible legal damages should Provo’s network not be presented to Google as promised”

Of course Google is paying Provo $1 for the network, so the real cost to Provo for selling their existing fiber network to Google is only $1,721,999. Still a fair bit money to pay someone to take an asset off your hands.

Then there is the issue of not even knowing where all of the fiber in the ground actually is. Didn’t they have to file permits with the city when they installed it in the first place? If they moved it later on, wouldn’t that require getting permits from the city as well? For something that they paid $39M for I would have thought they would keep a close eye on it.

The Salt Lake Tribune also reported numbers on how much is still due on the original $39M in bonds:

With interest, taxpayers still have to pay $3.3 million in bond payments per year for the next 12 years.

For a total of $39.6M that Provo will have paid out over the next 12 years.

This story may still have a happy ending. If Google Fiber in Provo blossoms into everything it could be, then all of this may have been worth it.

The money thing doesn’t really freak me out though. What really freaks me out is that the city of Provo has connected “operation of traffic lights and police and fire services” to the same fiber network that connects to the Internet. That strikes me as a really, really, really bad idea.

iProvo Sale Price to Google Fiber

Last week I mentioned that Google Fiber was coming to Provo. This process would be accelerated because they were purchasing the existing fiber network, iProvo, instead of having to built out a completely new one.

Turns out the sale price of iProvo fiber network to Google is $1. It should come as no surprise that some people are less than thrilled about this price.

The original cost to build out the iProvo fiber network is reported at $39 million. To fund this the city of Provo issued bonds. Those bonds have not yet been paid in full. The $1 in revenue from the sale isn’t going to pay off the bonds. In an effort to help pay off the bonds in 2011 a surcharge was added to the utility bills of every household in Provo.

While most people seem happy to have Google coming in to upgrade and run the fiber network in Provo, others are concerned that the sale of the network does nothing to address the remaining millions of dollars in bond obligations.

Both sides are benefiting from this, but the $1 sale does feel a bit odd. I’d assume the existing fiber network has some value, less than the original $39 million and more than $1. Perhaps something on the order of $5 to $10 million would have been reasonable. Google would still have been given a great deal on existing infrastructure, and the city of Provo would have some money to pay down the bonds faster.

In the negotiations for this I’m sure Google held all the cards. The city of Provo was likely happy to bend over backwards and into a pretzel to make sure Google didn’t walk away from the deal.

Google Fiber in Provo

The big announcement in Utah yesterday was that Google Fiber is coming to Provo. Instead of building out completely new infrastructure, Google will be purchasing the existing fiber network in Provo. From there they will be upgrading it to be in line with other Google Fiber installs.

I live about a 30 minute drive north of Provo, so this won’t make it to my home. Though Comcast recently upped my connection to 50Mbps down, so my current connection isn’t horrible. I wonder if Comcast knew this announcement from Google was coming and wanted to preempt some of the complaints from users.

The other thing that I wonder about is the NSA datacenter a short hop north of Provo. Was this a motivating factor on the either side? No idea. Would be nice to know if Google Fiber in Provo ends up peering with the NSA data center.

Speaking of peering, there are a few others in the area that would probably love to have a network peering arrangement with Google Fiber in Provo. C7 has a data center in Bluffdale ( north of Provo and not far from the NSA data center ) that apparently has a hefty number Twitter servers. Bluehost has a data center in Provo. Those are the two I could think of off the top of my head, there are data centers in the area who would be interested as well.

This is just the beginning of Google Fiber in Provo, and even though I won’t have access to it, I’ll be watching closely to see how it develops.

Older posts

© 2014 Joseph Scott

Theme by Anders NorenUp ↑