Four short links: 24 July 2009

Copytweet, MacMarket iShare, Open Source Under Fire, and OLPC War Stories

  1. Are Tweets Copyright-Protected (WIPO) — According to an Internet posting on blogherald.com by Jonathan Bailey, every time a new communication technology emerges, it shifts the copyright landscape, and new copyright issues that do not fit existing intellectual property (IP) standards arise. With Twitter, for example, while its terms of service clearly state that tweeters own anything they post on the service, the 140-character limit to a Twitter post makes it almost impossible for the work to reach the level of creativity required for copyright protection. In the same vein, titles or short phrases usually cannot be protected since their length contributes to their lack of originality, as defined by copyright law. A roundup of the copyright issues raised by Twitter, which is a little like a roundup of the climate issues raised by ants.
  2. Apple Has 90% Revenue Share Of >$1000 Computers (Ars Technica) — wow. (via publicaddress on Twitter)
  3. Open Source on the BattlefieldFortunately, SFC Stadtler knew how to use open source software. Using found hardware, like a laptop pulled from the trash, and wires pulled from collapsed buildings, he was able to establish a wireless network between the towers and the home base. He was able to install freely available voice-over-ip software on this recycled hardware, which turned the computer into a wireless telephone. The soldiers were now able to communicate with each other and the home base. At no cost. (via Jim Stogdill)
  4. Sweet Nonsense Omelet (Ivan Krstić) — Horror stories from the inside about the shoddy suppliers of OLPC hardware. Thinking back, there’s a hardware incident I remember particularly fondly: one of our vendors sent us a kernel driver patch which enhanced support for their component in our machine. They chose to implement the enhancement by setting up a hole which allowed any unprivileged user to take over the kernel, prompting our kernel guy to send a private e-mail to the OLPC tech team demanding that, in the future, we avoid buying hardware from companies whose programmers are, direct quote, “crack-smoking hobos”.
tags: , , , , , , ,