Hi Simon,<br>I agree with your request to 'see' more information in the short term because it is nearly impossible to debug. I believe we needed this bug to be fixed because sharing just didn't work in some cases; but you are correct that without knowing if you are connected to a school server or not; and without being able to choose to connect to a specific jabber server or none, there will be confusion.
<br><br>We are working on the requirements for a Control Panel that can let you choose your jabber server. Maybe it should also let you choose NOT to connect to a jabber server so you can only talk to other XOs that not connected to any server (and they can choose not to be connected).
<br><br>I want to see if we can get the most basic aspects of a control panel in by FRS (even if it doesn't get a real UI) so that we can have a little more insight and a little more control that we have right now.<br>
<br>Kim<br><br><br><div><span class="gmail_quote">On 9/20/07, <b class="gmail_sendername">Zarro Boogs per Child</b> <<a href="mailto:bugtracker@laptop.org">bugtracker@laptop.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
#3506: XOs connected to jabber server AND can link local don't share well<br>-------------------------------+--------------------------------------------<br> Reporter: kimquirk | Owner: J5<br> Type: defect | Status: new
<br> Priority: blocker | Milestone: Trial-3<br> Component: presence-service | Version:<br>Resolution: | Keywords: review+<br> Verified: 0 |<br>-------------------------------+--------------------------------------------
<br><br>Comment(by smcv):<br><br> (I should note that turning off Salut like this when we have a server<br> connection doesn't do anything to address any concerns you may have about<br> network traffic caused by Salut - as I explained in an email thread a
<br> month or so ago, most of Salut's network traffic will already have<br> happened by the time you connect to the server and turn Salut off.)<br><br> The fundamental UI problem here is that we don't give the child any
<br> indication or control of whether the activity will be shared locally, or<br> on the server, we don't give them that information about activities they<br> can see, and we don't show them whether they and their buddies can see the
<br> server or not; but the observable behaviour is inexplicably different,<br> depending on these things.<br><br> I realise hiding irrelevant technical details from the children is a goal,<br> but perhaps for 1.1 it would make things clearer if the sharing UI could
<br> distinguish between local and server sharing (People Near Me vs My School<br> perhaps?), and add a badge or other scope indication to<br> activities/buddies, or something?<br><br>--<br>Ticket URL: <<a href="https://dev.laptop.org/ticket/3506#comment:11">
https://dev.laptop.org/ticket/3506#comment:11</a>><br>One Laptop Per Child <<a href="https://dev.laptop.org">https://dev.laptop.org</a>><br>OLPC bug tracking system<br></blockquote></div><br>