You seem to imply that there is a technical infeasibility that cannot be overcome. If the public point database were segregated by a UNIX-style permissions system and connected to via SSH, wouldn't it be just about as safe as any public file server or database? Files that are "shared" can be accessed, files that are private stay private. A server-side daemon could negotiate friends lists, proximity, and other details without ever exposing private position data publicly.
<br><br>Am I missing something on the privacy front? Perhaps I just didn't grok your example.<br><br><div><span class="gmail_quote">On 7/3/07, <b class="gmail_sendername">Ian Stirling</b> <<a href="mailto:OpenMoko@mauve.plus.com">
OpenMoko@mauve.plus.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Dylan McCall wrote:<br><snip><br><br>There is another aspect.
<br>Privacy.<br>For example, I might be happy to be visible to other phone users in<br>50-100m, and my friends.<br>I certainly do not want to be locatable by a random person over the<br>internet.<br><br>This does imply some sort of server, to which I upload my position, and
<br>will push to me information about any nearby phones.<br><br>Also that publishes public key encrypted position, which anyone can<br>download.<br><br>A static database simply can't really do this.<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">http://lists.openmoko.org/mailman/listinfo/community
</a><br></blockquote></div><br>