Four short links: 6 October 2009

Birdwatching Technology, Transportation Data, Multitouch in Python, and Face Detection on the iPhone

1. Bird-watching Turns To Technology (BBC) -- CCTV-esque automated bird watching. Sensor networks + computer vision for an ecological purpose. In a bid to track the guillemots behaviour, Dr Dickinson is refining established work that involves modelling the visual structure of an area around a nest. The computer system will be able to use this model to identify changing elements in the scene, and determine if they correspond to movement by a guillemot. "That is the typical way of doing surveillance," said Dr Dickinson, "work out what's moving, that gives you an idea about what is interesting in a scene."
2. The Case for Open MTA Data -- If you live in Portland, there are dozens of mobile applications that help fill gaps in transit information. You can check your phone to see when the next bus is supposed to come. You can plan a trip from one unfamiliar part of town to another. You can even have your mobile device buzz if you fall asleep before reaching your destination. For the basic stuff, there's no iPhone necessary (although that certainly helps for information luxuries). Anyone who has a plain old cell phone with text messaging can ride the train or the bus with greater ease thanks to these apps. (via Making Light)
3. PyMT -- a python module for developing multi-touch enabled media rich applications. Currently the aim is to allow for quick and easy interaction design and rapid prototype development. There is also a focus on logging tasks or sessions of user interaction to quantitative data and the analysis/visualization of such data.
4. Near Realtime Face Detection on the iPhone with OpenCV Port -- we're probably only one or two revisions of iPhone hardware away from being able to do some serious computer vision tasks on the handset. Proof of concept adds a tie to the face you're pointing the camera at.

Four short links: 5 October 2009

Bozo Cloud Talk, Annotation Fail(ish), Python MySQL Slash, and Infinite Books

1. Brown Cloud Marketing -- advertorial "interviewing" GM of a company offering "DNS in the cloud". This might be a worthwhile service, but the way he markets it (by saying open source is "freeware" and the market leader is "legacy") reveals a rich vein of bozo. Freeware legacy DNS is the internet's dirty little secret (actually, it's the reason we have a functioning DNS), Nominum software was written 100 percent from the ground up, and by having software with source code that is not open for everybody to look at, it is inherently more secure. (security through obscurity is equating clothing with being naked yet blind). The Internet kindly did the poor man's homework: screenshot of a cross-site scripting vulnerability in their customer portal, a Nominum security advisory from 2008, and the Nominum web server is running Linux, Apache, and PHP (all legacy freeware yet apparently not the Internet's dirty little secret). (via Bert Hubert and Securosis)
2. Public Annotations on Healthcare Bill -- using technology from SharedBook, Congressman Culberson hoped to get citizens marking up the healthcare bill. They're using the software but many are just commenting on page 1--turning the hosted annotation platform into a forum with an odd user interface. It's a UI challenge: designing a way to let focused people comment on specific things, while also permitting impatient unfocused people to comment on the general topic. It's like asking for a SmartCar that seats 80. See also OpenCongress and their annotation system which also has hundreds of comments on the first few lines of the bill (including 39 on the one line "111th Congress"--apparently more contentious than you'd think!).
3. MyConnPy -- pure-Python MySQL client library, useful because it requires no C compilation to install (and thus can work on systems without C compilers installed, e.g. mobile). (via Simon Willison)
4. The Infinite Book -- design concept for an ebook reader (not a product you can buy yet). Sexy. (via Gizmodo)

Four short links: 25 September 2009

On Wheel Reinvention, Research Visualization, New Comments, and Defective Congressional Data

1. Diesel: A Case Study In That Thing I Just Said -- a new asynchronous I/O library in Python, which earned this fabulous review from Glyph Lefkowitz who wrote the granddaddy of all asynch libraries in Python, Twisted. Again, I don't want to dump on Diesel here; for what it is, i.e. an experiment in how to idiomatically structure asynchronous applications, it's all right. For that matter Twisted has its fair share of bugs too, which would be pretty easy to lay out in a similar post; you wouldn't even need to do the research yourself, just go look at our bug tracker. But both Diesel and Tornado make the mistake of attempting to replace the years of trial-and-error, years of testing discipline, and years of portability and feature work that Twisted has accumulated with a few oversimplified, untested hacks.
2. Eigenfactor -- ranking and mapping scientific knowledge. Visualizations and analyses from when geeks attack scientific publishing.
3. Washington Post Develops Visual, Web-like Commenting System -- WebCom displays comments in a dynamic web instead of a traditional list. As new comments come in, the web gets bigger. The web, however, is not organized by chronology. King and his team believe that the most valuable comments are those that are rated highly by peers and those that spur responses. WebCom uses those criteria to organize the web. (via The Evolving Newsroom)
4. Congressional Data is Defective By Design -- You should have better access to this info! You should have — at your fingertips — immediate, unrestricted digital access to the full text of any piece of legislation the very moment it’s released publicly by Congress. This is punishingly ridiculous. Congress could immediately take steps to make all publicly-relevant legislative data comply with the community-derived Eight Principles of Open Government Data.[...] That is to say, bill info from Congress could and should be available today in real time, free of charge, open-source, and licensed openly, via such open-standards technologies as XML, API’s, and regular bulk data downloads. We're entering a time where the tools and methods that make good software can help make good laws. (via timoreilly on Twitter)

Four Short Links: 28 August 2009

The Future, Python Metrics, Distributed Version Control, and Stylish R

1. What The Future's All About (Webstock Words) -- Bruce Sterling on the future. We’re not going to get a future Cloud World as somehow opposed to a future Augmented Reality World. It can’t happen. The ideas can be clearly distinguished, but ideas about technology, labels for technology, predictions and suppositions about technology, they don’t map onto actual real-world technology. Human culture doesn’t work like a logical argument.
2. PyMetrics -- code analysis software that produces metrics for your code. (via the excellent 10 Ways To Let People Know You're a Bad Python Programmer by Noah Gift)
3. Prophet and SD 0.7 Are Now Available -- Prophet is a lightweight schemaless database designed for peer to peer replication and disconnected operation. Prophet keeps a full copy of your data and (history) on your laptop, desktop or server. Prophet syncs when you want it to, so you can use Prophet-backed applications whether or not you have network. SD (Simple Defects) is a peer-to-peer issue tracking system built on top of Prophet. In addition to being a full-fledged distributed bug tracker, SD can also bidirectionally sync with your RT, Hiveminder, Trac, GitHub or Google Code issue tracker.
4. Google's R Style Guide -- R is a high-level programming language used primarily for statistical computing and graphics. The goal of the R Programming Style Guide is to make our R code easier to read, share, and verify. The rules below were designed in collaboration with the entire R user community at Google. (via Bo Cowgill's blog)

Four short links: 12 August 2009

Health Data, Python Term Extraction, Network Neutrality, New Database

1. Improving Health Care -- Adam Bosworth's speech to the Aspen Health Forum. It starts strong and just gets better: There is a lot of talk about improving health care. And there is a lot to improve. Inadequate Evidence: We don’t know enough about what works. We should require sharing of population statistics across practices and hospitals in order to better determine what works for whom. We should reward practices and hospitals that are delivering the best most cost-effective long-term outcomes and penalize those that deliver the worst.
2. topia.termextract -- Python library for term extraction, so you can get a list of the nouns and noun phrases used in a piece of text. (via Simon Willison)
3. Key to Understanding Network Neutrality -- David Pennock neatly identifies the crucial issue, that service quality and price levels be uniformly applied and not arbitrary based on how much the service provider thinks they can gouge from the customer. The key to understanding this debate is recognizing the difference between anonymity and egalitarianism. A mechanism is anonymous if the outcome does not depend on the identity of the players: two players who bid the same are treated equally. It doesn’t matter what their name, age, or wealth is, what company they represent, or how they plan to use the item — all that matters is what they bid. This is a good property for almost any public marketplace that ensures fair treatment, and one worth fighting for on the Internet.
4. (the item I linked to releases in a week's time, I will link again when it's live--sorry for the inconvenience. In the meantime, please enjoy this video of a monkey washing a cat)

Four short links: 11 August 2009

1. The Slowing Growth of Wikipedia and More Details of Changing Editor Resistance -- researchers at PARC analysed Wikipedia and found the number of new articles and number of new editors have flattened off, and more edits from first-time contributors are being reverted. This is a writeup in their blog, with the numbers and charts. It's interesting that coverage in New Scientist talked about "quality", but none of the metrics PARC studied are actually quality. Wikipedia launched a strategic review which aims to tackle this and many other issues. (via ACM TechNews)
2. The Information Architecture of Social Experience Design: Five Principles, Five Anti-Patterns and 96 Patterns (in Three Buckets) -- teaser for upcoming O'Reilly book with some really good stuff. Balzac once wrote, “The secret of great wealth with no obvious source is some forgotten crime, forgotten because it was done neatly,” and many successful social sites today founded themselves on an original sin, perhaps a spammy viral invitation model or unapproved abuse of new users' address books. Some companies never lived down the taint and other seems to have passed some unspoken statute of limitations. (via BoingBoing)
3. Skulpt -- entirely in-browser implementation of Python. (via Andy Baio)
4. Why Can't Local Government and Open Source Be Friends? -- the Birmingham example is one of many. Government procurement and tendering processes are often fishing expeditions, which biases responses in favour of commercial software companies making mad margins such that they can respond to RFPs that are really RFIs, etc. It's an issue everywhere in the world because it happens at local, not just central, level.

Four short links: 28 July 2009

UI Library, 3rd Party Wave Server, Mobile Phones + Parasites, Single API to Cloud Providers

1. CNMAT Resource Library -- The CNMAT Resource Library is our fast growing collection of materials, sensors, gestural controllers, interface devices, tools, demos, prototypes and products - all organized and annotated to support the design of physical interaction systems, "new lutherie" and art installations. (via egoodman on Delicious)
2. PyGoWave Server -- first third-party Google Wave server, based on Django.
3. Mobile Phones Identify Parasites and Bacteria -- UCB Researchers developed a cell phone microscope, or CellScope, that not only takes color images of malaria parasites, but of tuberculosis bacteria labeled with fluorescent markers.. The sensor network is built out, and the computers in our pockets surprise us with their uses. (via BoingBoing)
4. libcloud -- a unified interface to cloud providers, written in Python and open source. Covers EC2, EC2-EU, Slicehost, Rackspace, Linode, VPS.net, GoGrid, flexiscale, Eucalyptus. (via joshua on Delicious)

Four short links: 19 June 2009

Cute Math, Fast Slo-Mo, Open Source HVAC, xkcd Hack

1. Inside-Out Multiplication Table -- very cool way to view the patterns of factors. Math is beauty with subscripts.
2. High-Speed Camera -- capture 100 frames at up to 1M frames/second. The sample videos, of a bullet liquefying on impact and a shotgun string boiling past, are stunning. The Makezine high-speed photography kit is the cheap amateur version.
3. Open Source Energy Management for Commercial Buildings -- open source project to enable interoperable applications for integrated Building Automation Systems (BAS). From NovusEdge. I wonder how they're planning to spread their open source and use it to disrupt. (via earth2tech and timoreilly on Twitter)
4. xkcd Knapsack Solution -- for those of you who like literal Python geeking with your comics. Have a great weekend!

Four short links: 29 Apr 2009

4chan, urban redesign, 3d printing, python

1. Moot Wins, Time Inc. Loses -- summary of how the 4chan group Anonymous rigged the voting in Time's 100 Most Influential poll to not just put their man at the top, but also spell an in-joke with the initial letters of the first 21 people. Time tried weakly to prevent the vote-rigging, and ReCAPTCHA gave the Internet scalliwags their biggest setback, but check out how they automated as much as possible so that human effort was targeted most effectively. It's the same mindset that build Google's project management, ops, and dev systems. Notice how they tried to game ReCAPTCHA, a collective intelligence app whose users train the system to read OCRed words, by essentially outvoting genuine users so that every word was read as "penis". Collective intelligence should never be the only security/discovery/etc. feature because such apps are often vulnerable to coordinated action.
2. The old mint in downtown SF painted by 7 perfectly mapped HD projectors -- looks absolutely spectacular. I love the combination of permanent and fleeting, architecture and infotexture. (via BoingBoing)
3. 3-D Printing Hits Rock-bottom Prices With Homemade Ceramics Mix (Science Daily) -- University of Washington researchers invent, and give away, a new 3D printer supply mix that costs under a dollar a pound (versus current commercial mixes of $30-50/pound).
4. Haystack and Whoosh Notes (Richard Crowley) -- notes on installing the search framework Haystack and the search back-end Whoosh, both pure Python. It's a quick get-up-and-go so you can add quite sophisticated search to your Django apps. (via Simon Willison)

Four short links: 2 Apr 2009

Predictions, PDF, source code control, and recommendation engines:

1. Wrong Tomorrow -- track pundits predictions and see how accurate they really are. From the ever-awesome Maciej Ceglowski.
2. PDFMiner -- Unlike other PDF-related tools, it allows to obtain the exact location of texts in a page, as well as other layout information such as font size or font name, which could be useful for analyzing the document. It also infers text running within a page by using clustering technique. Entirely written in Python.
3. Migrating from svn to a Distributed VCS -- to decide which distributed VCS to use, Brett Cannon gathered Python use cases and then showed how they'd be done with different dvcses. The result is a very useful comparison document for svn, bzr, git, and hg.
4. Online Monoculture and the End of the Niche -- interesting post summarising and explaining research into recommendation engines, drawing the conclusion that although Internet World recommendation engines show everybody lots of new stuff, we're all seeing the same new stuff and the end result is less the "riches of niches" Long Tail fantasy and more a monoculture.

Four short links: 16 Feb 2009

A lot of Python and databases today, with some hardware and Twitter pranking/security worries to taste:

1. Free Telephony Project, Open Telephony Hardware -- professionally-designed mass-manufactured hardware for telephony projects. E.g., IP04 runs Asterisk and has four phone jacks and removable Flash storage. Software, schematics, and PCB files released under GPL v2 or later.
2. Don't Click Prank Explained -- inside the Javascript prank going around Twitter. Transparent overlays would appear to be dangerous.
3. Tokyo Cabinet: A Modern Implementation of DBM -- ok, so there's definitely something going on with these alternative databases. Here's the 1979 BTree library reinvented for the modern age, then extended with PyTyrant, a database server for Tokyo Cabinet that offers HTTP REST, memcached, and a simple binary protocol. Cabinet is staggeringly fast, as this article makes clear. And if that wasn't enough wow for one day, Tokyo Dystopia is the full-text search engine. The Tyrant tutorial shows you how to get the server up and running. And what would technology be without a Slideshare presentation? (via Stinky)
4. Whoosh -- a pure Python fulltext search library.

Four short links: 10 Jan 2009

Here are four fun links to set the tone for your weekend: high risk money, productive failure, consumer-grade BitTorrent, and architecture criticism for the rest of us.

1. How Porsche hacked the financial system and made a killing -- perhaps "hack" is a little excessive, but it's a readable short account of how Porsche made a lot of money playing "millionaire's poker" against hedge funds. (via Ivan Krstić, the author of Apache Security former Director of Security Architecture for the OLPC)
2. Missteps in Django -- a Python programmer documents the mistakes he makes programming in Django. This helps other people as they face similar problems, and shows the Django developers where their expectations differ from those of mortal programmers. I think it's a great idea because it makes visible the useful mistakes that are how we learn. It also reinforces the idea that it's okay to make mistakes, we all do it, and they're as worth of discussion as successes.
3. Netgear Unveils TV Torrent Player -- consumer device with BitTorrent built in. The easier it becomes for mortals to get files through BitTorrent, the harder it is to ignore unauthorised file sharing through BitTorrent, and the more pressing a solution to the business problem will be. (via Glynn Moody)
4. How Buildings Learn -- if you haven't seen this show, you should. On-the-money criticism of architecture and architects, talking about what's important when you design things for people. (via Kottke)

Four short links: 9 Jan 2009

Four questions, one per link: what next, can it solve a big problem, what's the final boss for Python programming, and why on earth would anyone want yogurt that glows in the dark?

1. End Times - gloomy piece on the future of journalism, to be added to the large pile of other gloomy pieces on the future of journalism (e.g., Bad News, Good News). The critical problem is still how to pay for journalism if the new media revenues are significant lower than old, and if the new media economics decree that journalism is dead then who fills the social good role that journalism's death will leave?
2. Ward Cunningham's Visible Workings - an intriguing glimpse, from March last year, into the way Ward lays out web interactions. Nice system for laying out these interactions, but it's also fascinating for how it makes transparent what will happen as a result of the data you submit. How scalable is this? Could it tackle privacy?
3. Project Euler - fun programming exercises that require more than math to finish. We learn by doing, not by reading, so interesting exercises are part and parcel of training. It's interesting to see educators are moving from being authors to being game designers, providing a series of staged challenges that make us stronger by defeating them. I'm presently dieing in as many ways as I can while learning iterators and generators in Python, as a way of ensuring I have Python's "game physics" sussed.
4. Rise of the Garage Genome Hackers - more on hobbyist molecular biology. It mentions DIYBio, the Cambridge biohacker collective that I first heard about at BioBarCamp. (via Glynn Moody)

code_swarm - visualizing the life of open source

code_swarm was created by Michael Ogawa with Processing.

This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.

(thanks to Todd Ogasawara for pointing this out!)