<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
This is probably a correct analysis for those in the US with online
broadband connection. However, at deployments which depend on the
school server (those without internet access), gabble is needed to
enable all XOs to collaborate. One of the first tests at a
deployment is to ensure that XOs connected to the schoolserver are
visible to each other (i.e. that gabble is working and not salut).<br>
<br>
Such a change needs a more thorough study. Should we limit
collaboration to XOs with a common router (partition the LAN)? Does
collaboration with salut work for XOs connected to the school
server? Is it a reasonable restriction at a deployment that only
some XOs can chat?<br>
<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 01/18/2016 12:14 PM, Sam P. wrote:<br>
</div>
<blockquote
cite="mid:CACVKbrWGcn=m18OgDuR07fmD9-s1P8v7wkqj3R+HBVT8zmXmmQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi All,
<div><br>
</div>
<div>Currently Sugar defaults to using "<a
moz-do-not-send="true" href="http://jabber.sugarlabs.org">jabber.sugarlabs.org</a>"
as a collaboration server in Sugar on a Stick and other GNU
distros (fedora, debian, etc.). However, I propose that we
change the default (this release!) to use the local network
(telepathy salut). This is a feature is that is already in
sugar, and is used on XOs and normal computers.</div>
<div><br>
</div>
<div>Why?</div>
<div><br>
</div>
<div>* Better activity support. Tubes are supported by salut,
but not by gabble (server based collab.). This means that
activities that haven't been ported this cycle (most of them)
will still work under salut (proposed default), but will not
work under gabble (current default)</div>
<div><br>
</div>
<div>* More contextual neighbourhood view. You only see people
on your local WiFi (or wired) network. This is more helpful
for finding your friends than the trawling the crowded <a
moz-do-not-send="true" href="http://jabber.sugarlabs.org">jabber.sugarlabs.org</a>
neighbourhood.</div>
<div><br>
</div>
<div>* More features. File transfers work via salut, but not
via <a moz-do-not-send="true"
href="http://jabber.sugarlabs.org">jabber.sugarlabs.org</a></div>
<div><br>
</div>
<div>* More speed and less lag. <a moz-do-not-send="true"
href="http://Jabber.sugarlabs.org">Jabber.sugarlabs.org</a>
is hosted in the mit. While that is good if you are a student
at the mit, it is very laggy if you are in say Australia. I
prefer near instant collaberation provided by my local
network. Even if you are at the mit, your wifi router is
still closer than <a moz-do-not-send="true"
href="http://jabber.sugarlabs.org">jabber.sugarlabs.org</a>
(hopefully)</div>
<div><br>
</div>
<div>* Privacy. Users (specifically kids) aren't by default
sharing their names and colours online and inviting others to
send them things.</div>
<div><br>
</div>
<div>Is this ok? Will defaulting to use salut (local network)
cause any issues for anyone? Is this ok for the 108 cycle?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>