moving towards product development after sketching
"the one skill I think will be most important for the 21st century is the graceful negotiation of different protocols."
"resist looking for the uber-protocol"
Networked Objects, the class
why don't the embedded net projects jive with embedded net products
the problem is the Internet
- "comes with a lot of metaphorical baggage"
- we think of it is as a place, not a media
- in contrast, we think of our devices as ways to do things
- the network of objects is local, intimate, short, and many-to-many
open device design
- write open control APIs and publish them
- standard (or accessible) protocols
- hybrid open/closed
- do we need to rethink warranties?
- for example, CHDK does not void the warranty of the Canon, because it doesn't permanently change the firmware
- so how do we modify warranties?
- flexible warranties: that allow companies to make a BEST EFFORT to restore the firmware
expose the firmware programming port
do companies really need to do this? is it their problem if you're an idiot?
is it their responsibility to sell a device that cannot be wiped and returned to default?
limited access to programming -- like the Arduino -- you can program a lot of it, but you never touch the bootloader
peer to patent project
- community patent review
practical layers of openness (drawing on Phil Torrone)
- circuit design
- mechanical design
- component choice
- Firmware (binary or code)
- physical function API
- aesthetic standards
- interface standards
- encouraging warranty
- open patent
Tom's slides here