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