Several parts for your replies refer to issues we have discussed before.<br>The tickets 4463,4405,4404,4403 include the new requirements and enhancements for the presence service, in benefit of user+developer<br><br>To summarize
<br><br>1. User+devel should be able to switch between gabble to salut manually using the options: auto,salut,gabble (4403)<br><br>2. User+devel should be able to connect/disconnect to one (or many, in the future) jabber server (4463)
<br><br>3. User+devel should have access to public+private IP (4405)<br><br>There are several reasons for each one of these. Now, if you observe them combined, the importance of IP information is:<br><br>user's prespective: assume for example 60 XOs are connected to a public jabber server(
e.g. <a href="http://jabber.laptop.org">jabber.laptop.org</a>). Five of these belong to the same school. They should be able to filter themselves.<br><br>devel's perspective:<br>1. From 1 XO we can test intantly which XO's are connected in a specific configuration
<br>2. IPs give irreplaceable information regarding whether the XO is connected to MPP, AP, schoolserver, NAT etc<br>3.(very important). when an XO is connected is connected to an MPP, we need to now the name of it. The buddy list links IP with name
<br>and many more<br><br>regarding the privacy issue of giving away the IP, regarding that all p2p or IM offer this capability , it shouldnt be an issue,<br><br>yani<br><br><div><span class="gmail_quote">On 10/26/07, <b class="gmail_sendername">
Sjoerd Simons</b> <<a href="mailto:sjoerd@luon.net">sjoerd@luon.net</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;">
On Fri, Oct 26, 2007 at 12:20:01AM -0400, Giannis Galanis wrote:<br>> The feature, although not usable by the activities, it has other benefits.<br>><br>> By observing the buddy list, you acquire instant information of the network
<br>> connection go the users:<br>> when connected to channel 1 for example:<br>> 169.254.x.x address are in link-local<br>> 172.18.x.x are connected to schoolserver<br><br>> when connected to a jabber server:
<br>> 169.254.x.x are connected through an MPP<br>> 18x.x.x are media lab<br>> 172.18.x.x are connected to schoolserver in olpc<br>> etc<br><br>> It is information continuously used in network testing,<br>For the link-local case you can just ask avahi for this information directly.
<br><br>For the jabber/server case, i'm unsure why your interested in how other nodes are<br>connected to the jabber server in the first place.<br><br>> also useful from the users prespective:<br><br>> 1. in the case of connecting to multiple jabber servers, the user should be
<br>> able to tell which XO in the neighbout view belongs to the same school<br><br>Maybe this has changed. But afaik there will be one jabber server per school<br>(on the school's server) and you can thus look at the users jid.
<br><br>> 2. get the geopraphical location of another user<br>A much better way for doing this would be to integrate some geoclue[0] information into<br>telepathy. Instead of having each XO's trying to work out where others are by
<br>the small amount of information an ip reveals.<br><br>> In future versions of the neighbor view, or through other activities, the<br>> user should be able to filter for specific XOs according to location, or<br>
> school(in the case he's connected to many servers). Two children in the same<br>> school should be able to recognize each other even if they are connected<br>> through a jabber server, other then the one in the school.
<br><br>An xo should always connect to the same jabber server afaik..<br><br>> It can also be useful for locating an XO in case of theft.<br><br>In the case of theft the jabber server the XO is connecting to always has the
<br>information of where a connection came from (or at least of the last nat hop<br>and you can work from there). I don't see the point of pushing that info to all<br>xo's.<br><br>> I have also added a ticket(4405) for adding the public id in the buddy list
<br>> properties.<br>><br>> It is a small part of data(both IPs, private and public), which can be<br>> harmfully incorporated in the telepathy services.<br><br>I definately agree that having some information of where in the world your
<br>buddy's are is something very nice. I disagree that exposing ip addresses is<br>the way to do it though.<br><br> Sjoerd<br>0: <a href="http://www.freedesktop.org/wiki/Software/GeoClue">http://www.freedesktop.org/wiki/Software/GeoClue
</a><br>--<br>Mediocrity finds safety in standardization.<br> -- Frederick Crane<br></blockquote></div><br>