- Twitter Open Sources Their Emoji Library — Emoji are the sparklines of sentiment.
- Interactive 360-degree Films. From Google (Medium) — you move the camera through a movie shot in 360 degrees, and can choose what you’re looking at through the scene. I can’t wait to try this, it sounds brilliant.
- Bitcoin Crackdown — everyone who started exchanges and mutual funds thinking Bitcoin wouldn’t be regulated like a currency is getting an SEC headache.
- Connected Choices: How the Internet is Challenging Sovereign Decisions (PDF) — Ultimately, the Internet remains both a global commons and part of each nation’s sovereign infrastructure, and thus activities in cyberspace must continue to navigate two sets of demands: national interests and global interests. […] Political leaders are responsible for articulating a vision and establishing general principles and policies to achieve their goals and, accordingly, are constantly trying to advance their agendas using policy, law, market mechanisms, regulation, standards, and other initiatives. The evidence is clear; you just have to look for it.
Google has asked the U.S. Supreme Court to review the CAFC’s ruling that Oracle's Java APIs are copyrightable.
Editor’s note: this is a forthcoming article for the March 2015 issue of Communications of the ACM (CACM); it is published here with permission.
For more than 20 years, the prevailing view has been that application program interfaces (APIs) are unprotectable elements of copyrighted computer programs. Under this view, programmers are free to reimplement other firms’ APIs in independently written code. Competition and innovation in the software industry has thrived amazingly well in part because of rulings upholding this understanding.
Challenging this view is the Court of Appeals of the Federal Circuit (CAFC) May 2014 decision in Oracle v. Google. The CAFC held that the “structure, sequence, and organization” (SSO) of Oracle’s Java APIs that Google reimplemented in its Android software are protectable expression under copyright law. It reversed a lower court ruling that the Java APIs were not copyrightable.
Google has asked the U.S. Supreme Court to review the CAFC’s ruling. Several amicus curiae (friend of the court) briefs have been filed in support of this effort. Hewlett-Packard, Red Hat, and Yahoo! (PDF) are among these amici (as am I and 77 computer scientists).
The Supreme Court may take the case because the CAFC’s decision is in conflict with other appellate court rulings that exclude APIs from copyright protection.
This article will explain the Oracle and Google theories about the copyrightability of Java APIs and the precedents on which each relies. The stakes in this case could not be higher. Read more…
Google requires quid for its quo, but it offers something many don’t: user data access.
Despite some misgivings about the company’s product course and service permanence (I was an early and fanatical user of Google Wave), my relationship with Google is one of mutual symbiosis. Its “better mousetrap” approach to products and services, the width and breadth of online, mobile, and behind-the-scenes offerings saves me countless hours every week in exchange for a slice of my private life, laid bare before its algorithms and analyzed for marketing purposes.
I am writing this on a Chromebook by a lake, using Google Docs and images in Google Drive. I found my way here, through the thick underbrush along a long since forgotten former fishmonger’s trail, on Google Maps after Google Now offered me a glimpse of the place as one of the recommended local attractions.
Admittedly, having my documents, my photos, my to-do lists, contacts, and much more on Google, depending on it as a research tool and mail client, map provider and domain host, is scary. And as much as I understand my dependence on Google to carry the potential for problems, the fact remains that none of those dependencies, not one shred of data, and certainly not one iota of my private life, is known to the company without my explicit, active, consent. Read more…