<div dir="ltr"><div>At least the way I would (minimally) consider implementing it, the default Jabber server simply would be a blank string..<br><br>So either you would have to (1) choose "Register" from the home screen XO character's right-click menu, (2) enter in an alternative Jabber/school server's name in the Network Control Panel, or (3) programmatically insert the alternative name into your XOs.<br><br></div>At one point I had an extension for OLPC OS builder to do the latter, as well as replace the name "schoolserver" hardcoded in many OLPC utilities. But said extension (if still around) probably is a bit out of date.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 18, 2016 at 6:35 PM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Currently, ejabberd is used on the school server (with gabble). Does
this change mean that something must be done on the XO or
schoolserver to enable collaboration (it is now automatic)? So far
as I know, the XO uses salut for ad hoc links and gabble with
ejabberd. Generally, if it isn't broken, don't fix it.<span class="HOEnZb"><font color="#888888"><br>
<br>
Tony</font></span><div><div class="h5"><br>
<br>
<div>On 01/19/2016 01:27 AM, Samuel
Greenfeld wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>I don't see this as a change disabling gabble so much as a
change where no default jabber server is specified. This
forces salut (ad-hoc) to be used until a jabber server is
specified.<br>
<br>
</div>
Given pretty much everyone who uses gabble outside of testing
uses their own local jabber server and not Sugar Labs', there
should be no user impact {apart from apps currently being broken
with gabble staying broken until fixed}.<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 18, 2016 at 6:17 PM, Tony
Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div 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?<span><font color="#888888"><br>
<br>
<br>
Tony</font></span>
<div>
<div><br>
<br>
<div>On 01/18/2016 12:14 PM, Sam P. wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Hi All,
<div><br>
</div>
<div>Currently Sugar defaults to using "<a href="http://jabber.sugarlabs.org" target="_blank">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 href="http://jabber.sugarlabs.org" target="_blank">jabber.sugarlabs.org</a>
neighbourhood.</div>
<div><br>
</div>
<div>* More features. File transfers work via
salut, but not via <a href="http://jabber.sugarlabs.org" target="_blank">jabber.sugarlabs.org</a></div>
<div><br>
</div>
<div>* More speed and less lag. <a href="http://Jabber.sugarlabs.org" target="_blank">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 href="http://jabber.sugarlabs.org" target="_blank">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></fieldset>
<br>
</div>
</div>
<span>
<pre>_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</span></blockquote>
<br>
</div>
<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>