Re: [Sugar-devel] Default Collaboration Server
Presumably the jabber server is set to point to the server on the school
server in your use case. This change would not impact that.
-walter
On Mon, Jan 18, 2016 at 6:35 PM, Tony Anderson
wrote:
> 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.
>
> Tony
>
>
> On 01/19/2016 01:27 AM, Samuel Greenfeld wrote:
>
> 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.
>
> 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}.
>
> On Mon, Jan 18, 2016 at 6:17 PM, Tony Anderson
> wrote:
>
>> 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).
>>
>> 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?
>>
>>
>> Tony
>>
>>
>> On 01/18/2016 12:14 PM, Sam P. wrote:
>>
>> Hi All,
>>
>> Currently Sugar defaults to using "jabber.sugarlabs.org" 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.
>>
>> Why?
>>
>> * 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)
>>
>> * 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 jabber.sugarlabs.org neighbourhood.
>>
>> * More features. File transfers work via salut, but not via
>> jabber.sugarlabs.org
>>
>> * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully)
>>
>> * Privacy. Users (specifically kids) aren't by default sharing their
>> names and colours online and inviting others to send them things.
>>
>> Is this ok? Will defaulting to use salut (local network) cause any
>> issues for anyone? Is this ok for the 108 cycle?
>>
>> Thanks,
>> Sam
>>
>>
>> ___
>> Sugar-devel mailing
>> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> ___
> Sugar-devel mailing
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Default Collaboration Server
At least the way I would (minimally) consider implementing it, the default
Jabber server simply would be a blank string..
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.
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.
On Mon, Jan 18, 2016 at 6:35 PM, Tony Anderson
wrote:
> 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.
>
> Tony
>
>
> On 01/19/2016 01:27 AM, Samuel Greenfeld wrote:
>
> 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.
>
> 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}.
>
> On Mon, Jan 18, 2016 at 6:17 PM, Tony Anderson
> wrote:
>
>> 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).
>>
>> 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?
>>
>>
>> Tony
>>
>>
>> On 01/18/2016 12:14 PM, Sam P. wrote:
>>
>> Hi All,
>>
>> Currently Sugar defaults to using "jabber.sugarlabs.org" 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.
>>
>> Why?
>>
>> * 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)
>>
>> * 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 jabber.sugarlabs.org neighbourhood.
>>
>> * More features. File transfers work via salut, but not via
>> jabber.sugarlabs.org
>>
>> * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully)
>>
>> * Privacy. Users (specifically kids) aren't by default sharing their
>> names and colours online and inviting others to send them things.
>>
>> Is this ok? Will defaulting to use salut (local network) cause any
>> issues for anyone? Is this ok for the 108 cycle?
>>
>> Thanks,
>> Sam
>>
>>
>> ___
>> Sugar-devel mailing
>> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> ___
> Sugar-devel mailing
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Default Collaboration Server
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.
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}.
On Mon, Jan 18, 2016 at 6:17 PM, Tony Anderson
wrote:
> 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).
>
> 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?
>
>
> Tony
>
>
> On 01/18/2016 12:14 PM, Sam P. wrote:
>
> Hi All,
>
> Currently Sugar defaults to using "jabber.sugarlabs.org" 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.
>
> Why?
>
> * 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)
>
> * 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 jabber.sugarlabs.org neighbourhood.
>
> * More features. File transfers work via salut, but not via
> jabber.sugarlabs.org
>
> * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully)
>
> * Privacy. Users (specifically kids) aren't by default sharing their
> names and colours online and inviting others to send them things.
>
> Is this ok? Will defaulting to use salut (local network) cause any issues
> for anyone? Is this ok for the 108 cycle?
>
> Thanks,
> Sam
>
>
> ___
> Sugar-devel mailing
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Default Collaboration Server
It should be fine for 0.108, also, I think OLPC images had been doing the same think for ages now. On Mon, Jan 18, 2016 at 12:46 PM, Walter Bender wrote: > +1 The privacy argument is a strong one. > > -walter > > On Mon, Jan 18, 2016 at 5:14 AM, Sam P. wrote: > >> Hi All, >> >> Currently Sugar defaults to using "jabber.sugarlabs.org" 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. >> >> Why? >> >> * 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) >> >> * 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 jabber.sugarlabs.org neighbourhood. >> >> * More features. File transfers work via salut, but not via >> jabber.sugarlabs.org >> >> * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully) >> >> * Privacy. Users (specifically kids) aren't by default sharing their >> names and colours online and inviting others to send them things. >> >> Is this ok? Will defaulting to use salut (local network) cause any >> issues for anyone? Is this ok for the 108 cycle? >> >> Thanks, >> Sam >> >> ___ >> IAEP -- It's An Education Project (not a laptop project!) >> i...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/iaep >> > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting a few errors when following tutorials given in the Write your Own Activity page
Hi Sam, To be honest, I'm not familiar with volo. May be you could start with Sugarizer development environment: just copy/paste the Sugarizer source code then follow instructionq in the Sugarizer part of the https://developer.sugarlabs.org/activity.md.html file. Best regards from France. Lionel. 2016-01-18 11:23 GMT+01:00 Sam P. : > Hi Mukund! > > On Mon, Jan 18, 2016 at 5:24 PM, mukund code > wrote: > >> Hi guys, >> >> I am new to Sugar. I am currently going through the tutorial posted here: >> https://developer.sugarlabs.org/activity.md.html >> >> I created a sample activity(using exactly the same instructions given in >> the tutorial). In the console, I noticed the following error: >> >> Error: Load timeout for modules: webL10n >> http://require.js.org/docs/errros.html#timeout >> onError >> onError >> checkLoaded >> (anonymous function) >> >> I tried: >> volo add webL10n >> >> It gave me a 301 error. >> > > That's funny. 301 shouldn't be an error, 3xx codes are redirect codes [1]. > > I don't involve my self with too many crazy nodejs things, but presenting > a 3xx code as an error sounds well within the relm of possibility > for some of these funny libraries. > > >> >> I then tried: >> volo add https://github.com/fabi1cazenave/webL10n >> >> which successfully installed webL10n. But the error still appears in the >> console. >> > > Did the info at [2] help? > > If not, maybe post your activity on github and try to find > somebody who knows about this js stuff to have a look > (CC Lionel). > > >> >> Also, I am not able to load any dynamic content using mustache(despite >> having a successful volo add) or console log out a statement when >> "my-button" ( >> https://developer.sugarlabs.org/activity.md.html#first%20steps) is >> clicked. I guess all of this is possible once js/activity.js. That loading >> happens via lib/require.js. But that script is giving me this error. I >> don't see any failed fetches in the Network tab of the console window also. >> > > Where did you put the console.log statements in the code? > Were they within the require.js callback? > If so, maybe your problems are all interconnected. > > Thanks, > Sam > > [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 > [2] http://requirejs.org/docs/errors.html#timeout > > >> >> Would be glad if someone helped out. >> Thanks! >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: Re: Getting a few errors when following tutorials given in the Write your Own Activity page
-- Forwarded message -- From: "mukund code" Date: 18 Jan 2016 20:02 Subject: Re: [Sugar-devel] Getting a few errors when following tutorials given in the Write your Own Activity page To: "Sam P." Cc: Hi Sam, That's funny. 301 shouldn't be an error, 3xx codes are redirect codes [1]. I don't involve my self with too many crazy nodejs things, but presenting a 3xx code as an error sounds well within the relm of possibility for some of these funny libraries. Apologies for the statement about the 301. I should have rather said,trying the command volo add webL10n gave me a 301 status: Using github repo "fabi1cazenave/webL10n" for "webL10n"... Downloading: https://codeload.github.com/fabi1cazenave/webL10n/legacy.zip/master raw.github.com/volojs/repos/master/fabi1cazenave/webL10n/amd.json returned status: 301. Which pretty much resulted in a failure to install webL10n via the command, which led me into trying the second command. Did the info at [2] help? The link suggests, that the error could be due to errors in setting up the path configuration. I hadn't tried to modify any of the path config files, so I really don't think the error could be because of that. Where did you put the console.log statements in the code? Were they within the require.js callback? If so, maybe your problems are all interconnected. Just to simplify things a bit, I decided to create a new project with no code additions from my side at all, except for the change in activity/ activity.info where I change the Activity name and bundle_id. The error came up again. So, it seems like the error exists when you install the app out of the box. I did manage to fix the issue though: I manually installed webL10n again, this time with a different URL volo add github:sugarlabs/webL10n/master which gave a successful install and removed the LoadError for webL10n that I was getting. But there was a new LoadError that popped up now, which looks very similar to the last one: Load timeout for modules: domReady!_unnormalized2, domReady http://require.js.org/docs/errros.html#timeout onError onError checkLoaded (anonymous function) So, I just did a volo add domReady and the app works fine now. I happen to look into the sugar-web-template folder that was used to create the app in the first place using the volo create my-activity ./sugar-web-template and in its lib/ , it doesn't have domReady.js or webL10n.js In retrospect, would it be a good idea to add the two files (domReady.js or webL10n.js) into the folder on the sugar repository so that people won't have this problem when creating their apps from the template? Cheers, Mukund On Mon, Jan 18, 2016 at 3:53 PM, Sam P. wrote: > > Hi Mukund! > > On Mon, Jan 18, 2016 at 5:24 PM, mukund code wrote: >> >> Hi guys, >> >> I am new to Sugar. I am currently going through the tutorial posted here: >> https://developer.sugarlabs.org/activity.md.html >> >> I created a sample activity(using exactly the same instructions given in the tutorial). In the console, I noticed the following error: >> >> Error: Load timeout for modules: webL10n >> http://require.js.org/docs/errros.html#timeout >> onError >> onError >> checkLoaded >> (anonymous function) >> >> I tried: >> volo add webL10n >> >> It gave me a 301 error. > > > That's funny. 301 shouldn't be an error, 3xx codes are redirect codes [1]. > > I don't involve my self with too many crazy nodejs things, but presenting > a 3xx code as an error sounds well within the relm of possibility > for some of these funny libraries. > >> >> >> I then tried: >> volo add https://github.com/fabi1cazenave/webL10n >> >> which successfully installed webL10n. But the error still appears in the >> console. > > > Did the info at [2] help? > > If not, maybe post your activity on github and try to find > somebody who knows about this js stuff to have a look > (CC Lionel). > >> >> >> Also, I am not able to load any dynamic content using mustache(despite having a successful volo add) or console log out a statement when "my-button" ( https://developer.sugarlabs.org/activity.md.html#first%20steps) is clicked. I guess all of this is possible once js/activity.js. That loading happens via lib/require.js. But that script is giving me this error. I don't see any failed fetches in the Network tab of the console window also. > > > Where did you put the console.log statements in the code? > Were they within the require.js callback? > If so, maybe your problems are all interconnected. > > Thanks, > Sam > > [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 > [2] http://requirejs.org/docs/errors.html#timeout > >> >> >> Would be glad if someone helped out. >> Thanks! >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org ht
Re: [Sugar-devel] [IAEP] Default Collaboration Server
+1 The privacy argument is a strong one. -walter On Mon, Jan 18, 2016 at 5:14 AM, Sam P. wrote: > Hi All, > > Currently Sugar defaults to using "jabber.sugarlabs.org" 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. > > Why? > > * 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) > > * 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 jabber.sugarlabs.org neighbourhood. > > * More features. File transfers work via salut, but not via > jabber.sugarlabs.org > > * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully) > > * Privacy. Users (specifically kids) aren't by default sharing their > names and colours online and inviting others to send them things. > > Is this ok? Will defaulting to use salut (local network) cause any issues > for anyone? Is this ok for the 108 cycle? > > Thanks, > Sam > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting a few errors when following tutorials given in the Write your Own Activity page
Hi Mukund! On Mon, Jan 18, 2016 at 5:24 PM, mukund code wrote: > Hi guys, > > I am new to Sugar. I am currently going through the tutorial posted here: > https://developer.sugarlabs.org/activity.md.html > > I created a sample activity(using exactly the same instructions given in > the tutorial). In the console, I noticed the following error: > > Error: Load timeout for modules: webL10n > http://require.js.org/docs/errros.html#timeout > onError > onError > checkLoaded > (anonymous function) > > I tried: > volo add webL10n > > It gave me a 301 error. > That's funny. 301 shouldn't be an error, 3xx codes are redirect codes [1]. I don't involve my self with too many crazy nodejs things, but presenting a 3xx code as an error sounds well within the relm of possibility for some of these funny libraries. > > I then tried: > volo add https://github.com/fabi1cazenave/webL10n > > which successfully installed webL10n. But the error still appears in the > console. > Did the info at [2] help? If not, maybe post your activity on github and try to find somebody who knows about this js stuff to have a look (CC Lionel). > > Also, I am not able to load any dynamic content using mustache(despite > having a successful volo add) or console log out a statement when > "my-button" ( > https://developer.sugarlabs.org/activity.md.html#first%20steps) is > clicked. I guess all of this is possible once js/activity.js. That loading > happens via lib/require.js. But that script is giving me this error. I > don't see any failed fetches in the Network tab of the console window also. > Where did you put the console.log statements in the code? Were they within the require.js callback? If so, maybe your problems are all interconnected. Thanks, Sam [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 [2] http://requirejs.org/docs/errors.html#timeout > > Would be glad if someone helped out. > Thanks! > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Default Collaboration Server
Hi All, Currently Sugar defaults to using "jabber.sugarlabs.org" 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. Why? * 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) * 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 jabber.sugarlabs.org neighbourhood. * More features. File transfers work via salut, but not via jabber.sugarlabs.org * More speed and less lag. Jabber.sugarlabs.org 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 jabber.sugarlabs.org (hopefully) * Privacy. Users (specifically kids) aren't by default sharing their names and colours online and inviting others to send them things. Is this ok? Will defaulting to use salut (local network) cause any issues for anyone? Is this ok for the 108 cycle? Thanks, Sam ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
