My latest post on Justia’s Legal Marketing & Technology Blog just went live and it is all about Structured Data and the Semantic Web. I talk and write quite a bit about the Semantic Web and decided it was high time I write a primer on just what it is and why it is important. Be sure to check it out over on Justia’s blog.
I did a wrap up of how the Google Assistant compares with its competitors at Apple, Microsoft and Amazon for Justia’s Legal Marketing & Technology Blog. My brief overview discusses what each of the Digital Personal Assistants brought to the table, and how Google has taken what they see as the best aspect of each and added their own flair.
Many people have long lamented that unlike Twitter, Facebook, LinkedIn, Tumblr, and many other services, Google+ does not let you use an API to post. There is an API for posting to Google+ Pages, but Google is restricting this feature to approved services. Apparently WordPress.com is one of those services, and in the latest 2.7 version of the Jetpack plugin for self-hosted WordPress blogs released yesterday, they are extending that service to your own self hosted WordPress blog.
It is interesting to note that the blog post on Jetpack’s blog indicates that this feature works both for Pages and individual profiles as well, which the Google+ Platform API documentation specifically says you cannot do.
This helps save time and energy when posting blog posts, and also helps if you schedule your blog posts for later. With this feature you can now schedule your blog posts to post at a specified time and rest easy knowing that it will be shared to Google+ at the same time. This is also a great feature for multi-author blogs. You can add multiple Google+ Profiles and Pages to the feature and have your posts post both to your individual profile as an author and to a shared page for the blog as a whole.
It is hard to believe that it was just 1 year and 1 week ago, Google uploaded to its YouTube channel, a teaser video for a project they had been working out of from their top-secret “moonshot” [x] Labs called Project Glass.
The project was ambitious, an augmented reality layer over your very life, answering questions before you even asked, and all around simplifying your life.
2 Months later at Google I/O 2012, Google staged a “demonstration” involving a blimp, skydivers, BMX Trick bikers and more to show off the device as what seemed like little more than a network connected GoPro camera. They then asked Developers who are interested in getting an early look at the technology if they would be willing to fork over $1,500 for the chance to be one of the first non-Google employees with this whole new class of Technology.
I and 2,000 other attendees happily stood in a long line to put down our commitment to try it out. Then, months of agonizing waiting began. Waiting for a future that was so close we could taste it.
Google I/O is almost here, and the Google Developers have created a nifty widget for enabling the live stream of the video on your blog, as well as embedding my own Google+ stream as a Live Blog of sorts, so head on after the break for my live blog where I will post about the stream while it happens.
In preparation for I/O, on the Google Developers Plus page, the Development team has now officially confirmed the name of the next version of Android will be “Jelly Beans.” The confirmation comes with a new statue on the Googleplex Lawn. Continue reading →
Since the very beginning, when met with an Atom or RSS feed, Google Chrome responds by rendering the XML as unformatted xml (unless your feed happens to have an XSL stylesheet like feedburner adds). One of the earliest bugs reported to Google is that this should not be, that it would instead be more friendly to invite the user to subscribe to the feed in a feed reader (like Firefox does) or render the feed yourself (like Safari does).
In the recently released stable Chrome 19, one of the new features is that instead of displaying the XML as unformatted xml, it fires off a view web intent instead. This may be a good first step towards making feeds friendlier to use. Instead of seeing a page the average reader doesn’t understand, they could be shown their own apps that they’ve installed. Continue reading →
Remember when GMail first came out? 1GB of email was unheard of, especially in a free service at the time. One of Google’s big selling points was “you’ll never need to delete another message.” It was right there on the home page. If you compare the home pages from 2004 and today for Gmail you’ll note they still refer to it as being “Lots of space” but they no longer say you’ll never need to delete another message. The message about never deleting email disappeared sometime between March, 2009 and December 2009.
Why did the message go away? Because the users proved that 1GB (then 2GB, then 4GB, then 7GB) simply wasn’t enough to store EVERY email. To combat this, back in 2007, Google released a means of purchasing more storage space at a rate of 6GB for $20/year, this storage would be shared amongst your Google Docs, GMail, and Picasa accounts. Over time these prices got even better. Yesterday you could buy 20GB of storage for $5 a year.
Today however, with the Google Drive release, the prices have changed from being yearly, to being monthly, while yesterday you could get 20GB for $5 a year, today the cheapest plan is 25GB for $2.49 a month (which comes out to $29.88/year). This is a very significant increase, but it’s not what I find the most annoying: GMail storage space is now completely separate than Google Drive (formerly Google Docs) and Picasa storage. The 25GB you are purchasing is only for Google Drive and Picasa, not for GMail.
This morning Google opened up a programming competition using the same system as Google Code Jam (they called it the Google Code Jam Sprint to I/O) to win the right to buy 1 of 100 tickets to Google I/O. Normal Registration for the conference closed 20 minutes after it opened back on March 27th due to the incredible demand, so naturally those developers who couldn’t get in before were excited and ready to battle for the chance to buy a ticket.
The competition consisted of 2 problems, programmers could write their code in any language (as long as the compiler is free to use). It would work like this, you would write a program according to their specifications of the problem, and then you would submit it. When you submit it, google would provide you with a file of sample input data and then give you 1 minute to run your code against that sample data and then submit the output to them. They would then run a validator across the output and tell you if you were correct or not. If you were correct, it would accept your answer, if not, it would reject it.
The first question went like this (paraphrasing)
Even though Google doubled the price (paid $450 last year, this year $900), Google I/O sold out even faster than last year. Last year it took about 45 minutes for Google’s Developer conference to sell out, this year it was all over in just over 20 minutes according to a post on Google+ by Google VP Vic Gundotra.
I’m glad to say I will be at I/O this year once again, but all but one of my colleagues who tried to buy tickets were unable to acquire them. Will I see you at Google I/O?