Exactly,<div><br></div><div> As I've said before people do a dis service to values of openess by these point comparisons</div><div> between iPhone and everything else. But if that comparison must be made then</div>
<div> let the first bullet point be this: Open versus Closed. That said if the goal is to create</div><div> an iPhone clone with Linux on board then I see these paths:</div><div><br></div><div> 1. Convince Apple that Copyleft is the way to go for hardware and software. Good chance</div>
<div> there. NANNY APPLE won't even let you put adult content on your phone. I spent the day</div><div> two days ago with a really cool company that signed all apple agreements, developed some</div><div> VERY COOL hardware to attach to the phone and Apple shut them down COLD.. after</div>
<div> they originally told the company that they could develop the hardware. Why? the hardware</div><div> would fuck with apple's roadmap. thank you Nanny Apple.</div><div><br></div><div> 2. Build a Copyleft version of the Iphone from scratch. pass me 400Million and I'll get right</div>
<div> on it! But you can't just build the iPhone, you have to build what apple will ship 18 months</div><div> from now to be competitive. </div><div><br></div><div> 3. Do an Anti vendor port. I support mickey 100% in his anti vendor ports. This is one way</div>
<div> to get open software on closed platforms. HOWEVER, by the time the port is done</div><div> the hardware is obsolete ( by iPhone standards) and more importantly, the hardware</div><div> hackers are left out. That said I think Mickey's approach is one that people should support</div>
<div> with their time and effort. It will bear fruit over time.</div><div><br></div><div> 4. Take an existing design ( like NanoNote) and over time add capability to it. Start small</div><div> and simple. Open the design from the start. Allow the hardware community to mod</div>
<div> the hardware ( and copy back design improvements) and give the software community</div><div> a stable but evolving platform to develop on. </div><div><br></div><div>So. #1. I didn't want to waste my time trying to talk apple into destroying their business.</div>
<div> #2. I didnt have 400 Million dollars.</div><div> #3. Mickey is going down his path. That's one front in the war. Put your efforts behind him.</div><div> #4. I can start down the long long path of planting a seed and helping it grow.</div>
<div><br></div><div>The beginning of that Journey ( #4) happens to be a cool little linux in my pocket. We've been</div><div>contacted by people who want to turn it into a "twitter client" or jabber client. Will we do that?</div>
<div>I'm not sure. But since the hardware will be copyleft, if SOMEBODY wants to take the design</div><div>and optimize it for SMS or email, then 1.) the community will have another device with Linux</div><div>on it. 2) they won't be able to charge outrageous prices. 3 They'll have to copy back the design</div>
<div>improvements. When they copy back designs then one can hope for network effects and the</div><div>long journey gets some momentum. </div><div><br></div><div>Many are missing the importance and the critical difference that Copyleft hardware brings.</div>
<div>If you don't like the fact that nanonote doesnt have a touch screen then, take the design files</div><div>add a touch screen, copy back the design. If you have money, then get that design built and </div><div>sell it. Qi-hardware won't complain. Why? because the community will have more choice about</div>
<div>what to buy. If somebody, for example, really really thinks that clamshell sucks, then there is</div><div>a ready solution. take our design, modify and improve it, copy back the improvements, build</div><div>the thing and let the market decide. </div>
<div><br></div><div>In short, I think the only effective way I have of competing on the hardware side is by</div><div>applying the principles of Copyleft. </div><div><br><div class="gmail_quote">On Fri, Jul 24, 2009 at 2:27 AM, john <span dir="ltr"><<a href="mailto:jptmoore@gmail.com">jptmoore@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Actually one of the things I would like to do with a NanoNote is turn<br>
it into a dedicated Twitter client! I think opinion will always be<br>
divided on form factor. I have owned many devices from the Psion<br>
Series II through to the iPhone but I still like Zaurus clamshell<br>
designs. I also like the idea of a tiny Linux computer in my pocket or<br>
even on a key chain. I don't see the progression as trying to compete<br>
with the iPhone but to look at new areas such as hackable wearable<br>
computing. Thus I am interested in seeing things get smaller and<br>
cheaper and more hackable and not getting more shiny!<br>
<br>
John.<br>
<br>
2009/7/24 Christoph Pulster <<a href="mailto:openmoko@pulster.de">openmoko@pulster.de</a>>:<br>
[snip]<br>
<div><div></div><div class="h5">><br>
> Psion Plc. invent the clamshell and set the top-level of usable keyboard<br>
> verses form-factor with Series 3 twenty years ago.<br>
> We are in the SMS/twitter age now. Some vitual keyboard with multi-touch<br>
> usability is sufficient. People who want to write full sentences buy a<br>
> pencil with white paper.<br>
><br>
><br>
> In general, what advantage does the NanoNote have to an Iphone with<br>
> Linux installed ?<br>
><br>
><br>
> Christoph<br>
><br>
> _______________________________________________<br>
> Openmoko community mailing list<br>
> <a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
> <a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
><br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br></div>