- Wide Open Future of the Art Museum (TED) — text of an interview with curator at the Walters Art Museum about CC-licensing content: reasons for it, value to society, value to the institution. What I say in a very abbreviated form in my talk is that people go to the Louvre because they’ve seen the Mona Lisa; the reason people might not be going to an institution is because they don’t know what’s in your institution. (via Carl Malamud)
- Twitter Resiles From API-Driven Site (Twitter) — performance was the reason to return to server-assembled pages, vs their previous “client makes API calls and assembles the page itself”.
- Stripe Einhorn — language-independent shared socket manager. Einhorn makes it easy to have multiple instances of an application server listen on the same port. You can also seamlessly restart your workers without dropping any requests. Einhorn requires minimal application-level support, making it easy to use with an existing project.
- Petition the Whitehouse For Access to Taxpayer-Funded Research (Whitehouse) — We believe in the power of the Internet to foster innovation, research, and education. Requiring the published results of taxpayer-funded research to be posted on the Internet in human and machine readable form would provide access to patients and caregivers, students and their teachers, researchers, entrepreneurs, and other taxpayers who paid for the research. Expanding access would speed the research process and increase the return on our investment in scientific research. Sign this and spread the word: it’s time to end the insanity of hiding away research to protect a handful of publishers’ eighteenth century business models.
ENTRIES TAGGED "APIs"
CC-Licensed Museum, Bye Bye API, Socket Server, and Free Taxpayer-Funded Research NOW!
REST Interfaces, Browser History, Crappy Textbooks, and Wireless Babies
- Designing RESTful Interfaces (Slideshare) — extremely good presentation on how to build HTTP APIs.
- Manipulating History for Fun and Profit — if you want to make websites that are AJAX-responsive but without breaking the back button or preventing links, read this.
- Why Textbooks Are So Broken (Salon) — Let’s say a publisher hires a developer for a certain low-bid fee to produce seven supplemental math books for grades 3-8. The product specs call for each student book and teacher guide to have page counts of roughly 100 pages and 80 pages, respectively. The publisher wants these seven books ready for press in five weeks—over 1,400 pages. To put this in perspective, in the not too recent past at least six months would be allotted for a project of this size. But publishers customarily shrink their deadlines to get a jump on the competition, especially in today’s math market. Unreasonable turnaround times are part of the new normal, something that almost guarantees a lack of quality right out of the gate.
- exmobaby — wireless biosensor baby pyjamas send ECG, skin temperature, and movement data via Zigbee. (via Jo Komisarczuk)
Alyona Medelyan and Anna Divoli on the opportunities in chaotic data.
Alyona Medelyan and Anna Divoli are inventing tools to help companies contend with vast quantities of fuzzy data. They discuss their work and what lies ahead for big data in this interview.
GreenGoose looks to unlock the data in everyday activities.
Put a GreenGoose sticker on an object, and just like that, you'll have an Internet-connected sensor. In this interview, GreenGoose founder Brian Krejcarek discusses stickers as sensors and the data that can be gathered from everyday activities.
Fluidinfo's Terry Jones on the role of APIs in the future of publishing.
APIs enable developers to work with your content like a box of Legos, building solutions you may never have dreamed of. In this TOC podcast, Fluidinfo CEO Terry Jones says the real world is "writable" and describes how APIs can offer powerful publishing solutions.
What happens when everyone has access to your Starbucks card? Jonathan Stark found out.
Jonathan Stark raised eyebrows last summer when he made his Starbucks card available for anyone to use. Here, Stark looks back on the "Jonathan's Card" experiment and examines its lessons.
Medical devices are remotely hacked, Google Maps get a price tag, and Linus Torvalds really doesn't like a certain language.
If you own an insulin pump, someone out there might have a hack with your name on it. Google decides to make high-volume Maps API users pony up some cash, and the creator of Linux goes after C++.
Google Platforms, Securing Software, Interactive Design, and Building Proverbs
- Steve Yegge’s Google Platforms Rant — epic. Read it. (updated with new link)
- Guidelines for Securing Open Source Software (EFF) — advice from the team that audited some commonly-used open source libraries. Avoid giving the user options that could compromise security, in the form of modes, dialogs, preferences, or tweaks of any sort. As security expert Ian Grigg puts it, there is “only one Mode, and it is Secure.” Ask yourself if that checkbox to toggle secure connections is really necessary? When would a user really want to weaken security? To the extent you must allow such user preferences, make sure that the default is always secure. (via BoingBoing)
- Ladder of Abstraction — a visual and interactive exploration of design that will delight as well as inform. (via Sacha Judd)
- On “Build It And They Will Come” — I wasn’t saying “build it and they will come”—I was saying “don’t build it and they can’t come”. Wonderfully captures the idea that success can’t be guaranteed, but failure is easy to ensure. (via Ed Yong)
- Twilio Client SDK — 1/4 cent/minute API-to-API calls, embeddable in browser apps.
- Postel’s Principle Reconsidered (ACM) — The Robustness Principle was formulated in an Internet of cooperators. The world has changed a lot since then. Everything, even services that you may think you control, is suspect. Excellent explanation of how interoperability and security are harder than they should be because of Postel’s Law (“Be conservative in what you do, be liberal in what you accept from others.”, RFC 793). (via Mike Olson)
- HTTP Pipelining on Mobiles — HTTP pipelining has a much higher adoption amongst mobile browsers. Opera Mini, Opera Mobile and the Android browser all use HTTP pipelining by default. Together they account for about 40% of mobile browsing. If you’re developing a mobile site, your site is experiencing HTTP pipelining daily, and you should understand how it works. (via John Clegg)