On Tue, Apr 14, 2009 at 13:17, Caroline Meeks <carol...@solutiongrove.com> wrote: > > > On Tue, Apr 14, 2009 at 4:07 AM, Tomeu Vizoso <to...@sugarlabs.org> wrote: >> >> Caroline is right in her explanation. >> >> Sugar will first run both telepathy-salut and telepathy-gabble. The >> salut connection manager will use peer-to-peer connections for >> presence and collaboration, doesn't need a server but is limited to >> the local area network. >> >> The gabble connection manager will try to connect to the jabber server >> specified in the control panel and if it succeeds, Sugar will shutdown >> salut and only use gabble. If gabble fails, the salut one keeps >> running. >> >> For 99% of users, presence and collaboration should just work, but >> people setting up the environment like conferences, computer labs, >> etc. should take this behavior into account. > > And the UI should somehow make it clearer what is going on.
Yeah, could you please enter a ticket about this? If you have any suggestions about how to improve here, please add them to the ticket. Thanks, Tomeu >> >> >> Regards, >> >> Tomeu >> >> On Sun, Apr 12, 2009 at 03:01, Caroline Meeks <solutiongr...@gmail.com> >> wrote: >> > >> >> >> >> >> >> 4. Yesterday, Walter and Caroline noticed that a room full of people >> >> using Sugar's collaboration capabilities from a remote server on a >> >> conference centers network suboptimal. >> > >> > Actually you miss understood me. Collaboration worked fine I just >> > didn't >> > understand what was going on until the drive home. >> > >> > During the demo it was very odd, different people seemed to see >> > different >> > people and I was confused as to what was happening. >> > >> > The conference center/hotel was one of those places where to access the >> > internet you had to 1. Connect to the wireless hub. 2. Open a browser. >> > 3. >> > Enter username and password. >> > >> > This could be done on SoaS just fine. >> > >> > But some people did not complete all three steps. >> > >> > If you connected to a wireless hub in your neighborhood but didn't go >> > throug >> > the process with Browse to connect to the internet then you just saw the >> > other people who also just connected to that wireless hub and didn't >> > connect >> > to the internet. >> > >> > Given the internet was incredibly slow, this may well have been a better >> > user experience for Sugar collaboration. I don't have any data about >> > that. >> > >> > If I were to do a 50 person Sugar workshop in a random hotel with bad >> > internet connectivity I would bring in a hub or two. Name them different >> > names. And the workshop could collaborate without ever using the >> > hotel's >> > slow internet. WIN! >> > >> > If I wanted users to see things on the internet I could info slice them >> > before hand. >> > >> > And as an extra bonus no one could check their email during the >> > workshop. >> > >> > Note, Im not saying we did a serious test of the collaboration.I am just >> > saying that everything seemed to be fine at FOSSVT and that I am >> > intreged by >> > the possiblities of local collaboration. >> >> >> >> >> >> What would be the best way to set up a system like this? As I go back >> >> over the list, it like like I am asking for a School Server on >> >> Steroids:) >> > >> > No, I think you are asking for a school server the way it is envisioned >> > and >> > where it is getting to. Now that we can have groups of people on Sugar >> > comfortably we are starting to understand why we want and need the >> > school >> > server to work. >> > >> > My last couple of visits to schools, and talks to educators at FOSS VT >> > have >> > convinced me that having a local server and caching inside the school is >> > going provide a great deal of value to US Schools. >> > >> > Caroline >> >> >> >> >> >> david >> >> >> >> >> >> >> >> > - Jonas >> >> > >> >> > - -- >> >> > * Jonas Smedegaard - idealist og Internet-arkitekt >> >> > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ >> >> > >> >> > [x] quote me freely [ ] ask before reusing [ ] keep private >> >> > -----BEGIN PGP SIGNATURE----- >> >> > Version: GnuPG v1.4.9 (GNU/Linux) >> >> > >> >> > iEYEARECAAYFAknhEYYACgkQn7DbMsAkQLi6KQCeMOkIeojg2/4PYQnb7Qhy+8qO >> >> > AtUAn1qAdicnYUoFIF1pl4Slg/Ol8z5M >> >> > =7TlN >> >> > -----END PGP SIGNATURE----- >> >> > _______________________________________________ >> >> > IAEP -- It's An Education Project (not a laptop project!) >> >> > IAEP@lists.sugarlabs.org >> >> > http://lists.sugarlabs.org/listinfo/iaep >> >> > >> >> _______________________________________________ >> >> IAEP -- It's An Education Project (not a laptop project!) >> >> IAEP@lists.sugarlabs.org >> >> http://lists.sugarlabs.org/listinfo/iaep >> > >> > >> > -- >> > Caroline Meeks >> > Solution Grove >> > carol...@solutiongrove.com >> > >> > 617-500-3488 - Office >> > 505-213-3268 - Fax >> > >> > _______________________________________________ >> > IAEP -- It's An Education Project (not a laptop project!) >> > IAEP@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/iaep >> > > > > > -- > Caroline Meeks > Solution Grove > carol...@solutiongrove.com > > 617-500-3488 - Office > 505-213-3268 - Fax > _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep