Complexity vs. Government Control?
Will attempts by governments to control information on the Internet be thwarted by complexity? http://eicker.at/CR
Tagged: Complexity Toggle Comment Threads | Keyboard Shortcuts
-
Gerrit Eicker
-
Gerrit Eicker
Complex Technical Systems
It’s a complicated world and complex technical systems are rapidly evolving; http://eicker.at/CR
-
Gerrit Eicker
Media: More Simplistic
The world is becoming more complex, old and new media are becoming increasingly simplistic; http://eicker.at/Hyperconnectivity
-
Gerrit Eicker
Google Plus API
The Google Plus API starts with public data only: This is the start. Experiment with it; http://eicker.at/GooglePlusAPI
-
Gerrit Eicker
Google: “Google+ APIs: Now With Search and More! – Last month we launched search in Google+, and now it’s available in the API. … Our first API release let you retrieve public posts. We’ve now added ways for you to see how people are publicly engaging with those posts – you can find out who reshared a post or who +1‘d a post, and you can read the comments on a post.”
Gerrit Eicker
Gamification
Meaningful Play, getting gamification right with: meaning, mastery, autonomy; http://eicker.at/Gamification @dingstweets
Gerrit Eicker
The Internet, Our Thinking
Naughton: Is the internet changing the way we think? Affecting the way we think for the worse? http://j.mp/apBvu3
Gerrit Eicker
The Internet
Naughton: 9 key steps to understanding the most powerful tool of our age, the Internet; http://j.mp/b7puKP
-
Gerrit Eicker
Naughton: “The strange thing about living through a revolution is that it’s very difficult to see what’s going on. … We’re living through a radical transformation of our communications environment. … Often, these interpretations are compressed into vivid slogans, memes or aphorisms: information ‘wants to be free’; the ‘long tail’ is the future of retailing; ‘Facebook just seized control of the internet’, and so on. … Here’s a radical idea: why not see if there’s anything to be learned from history? … So let’s conduct what the Germans call a Gedankenexperiment – a thought experiment. Imagine that the net represents a similar kind of transformation in our communications environment to that wrought by printing. What would we learn from such an experiment? … The most common – and still surprisingly widespread – misconception is that the internet and the web are the same thing. They’re not. … Disruption is a feature, not a bug. … The internet’s disruptiveness is a consequence of its technical DNA. … Think ecology, not economics. … Complexity is the new reality. … [Common] strategies are unlikely to work in our emerging environment, where intelligence, agility, responsiveness and a willingness to experiment (and fail) provide better strategies for dealing with what the networked environment will throw at you. … The network is now the computer. … The Web is changing. … Huxley and Orwell are the bookends of our future. … Our intellectual property regime is no longer fit for purpose. … The sad fact is that if there is a ‘truth’ about the internet, it’s rather prosaic: to almost every big question about the network’s long-term implications the only rational answer is the one famously given by Mao Zedong’s foreign minister, Zhou Enlai, when asked about the significance of the French Revolution: ‘It’s too early to say.’ It is.“
Google: “[W]e want every one of you who builds applications to be able to include rich sharing, identity, and conversations in your app. Today, we’re taking the next step on that journey by launching the first of the Google+ APIs. … This initial API release is focused on public data only – it lets you read information that people have shared publicly on Google+. … We love the way the programmable web has evolved, so we’re using existing standards and best practices wherever we can: Our API methods are RESTful HTTP requests which return JSON responses. Our payload formats use standard syntax (e.g. PoCo for people info, ActivityStrea.ms for activities). We use OAuth 2 for secure trusted access to user data. – In addition, since most of us no longer write raw HTTP requests these days, we provide libraries for your favorite language: Java, GWT, Python, Ruby, PHP, and .NET. These libraries are all open source, so we’d love to have your feedback and help with them. … For all of you developers who have been asking for a Google+ API, this is the start. Experiment with it. Build apps on it. Give us your feedback and ideas. This is just the beginning; the Google+ platform will grow and we value your input as we move Google+ forward.”
Google Developers: “The Google+ API is the programming interface to Google+. You can use the API to integrate your app or website with Google+. This enables users to connect with each other for maximum engagement using Google+ features from within your application. … Applications are limited to a courtesy usage quota. This should provide enough access for you to preview the API and to start thinking about how you want to build your application. … Many API calls require that the user of your application grant permission to access their data. Google uses the OAuth 2.0 protocol to allow authorized applications to access user data.”
RWW: “Since the social network launched in June and put out a call for developers, this API has been hotly anticipated. Our ReadWriteHack poll found that a commanding majority of our developer readers were interested in playing with it. This summer, we laid out some ground rules about what Google would have to do to win developers’ hearts with this API, and it looks good so far, though devs only have access to public data at this point.”
TC: “A week ago, we noted the talk amongst developers that a Google+ API could be months away. The next day, we learned that Google was reaching out to ‘trusted’ developers – among them, Google Ventures-backed startups – to try out their early stab at the API. Google was not happy we found this out (and went on a witch hunt to find the leaker) – so it shouldn’t be too surprising that today they’re announcing some initial APIs for everyone to use. … [T]he main focus of Google+ is clearly on the Circles sharing concept. The API for that is probably one that everyone is really waiting for. And that one could be a ways off since it involves complex connections and tricky privacy implications. Even more important will be the write API. But again, with the Circles element, it’s complicated.”
Winer: “Google doesn’t get it – I usually don’t say this about people or companies, aware that I am that it’s often the other way around. The one saying they don’t get it is the one that don’t. In this case I am absolutely sure that Google is the one. … They should just support RSS, and forget APIs to read publicly available content. All that’s going to happen now is people are going to write apps that produce feeds from their API so they can hook into the reading tools that were written a hundred years ago, like the one Google itself has.”