#5141 BLOC Ship.2: Set jabber server address to null

[Zarro Boogs per Child]

#5141: Set jabber server address to null
----------------------+-----------------------------------------------------
  Reporter:  jg       |       Owner:  jg    
      Type:  defect   |      Status:  new   
  Priority:  blocker  |   Milestone:  Ship.2
 Component:  distro   |     Version:        
Resolution:           |    Keywords:        
  Verified:  0        |  
----------------------+-----------------------------------------------------

Comment(by robot101):

 I don't consider this necessary if we include a fix for #4965 in the
 build. Even if our Jabber sever catches fire and we turn it off for hours
 or days at a time, or replace it with completely different software, the
 XOs in the field will fall back gracefully to Salut. The benefit of
 leaving this enabled is that provided #4965 is fixed, we have the option
 of deploy server-side solutions (as described
 [http://lists.jabber.ru/pipermail/ejabberd/2007-November/003230.html
 here]) as they are devised, allowing us to maintain the current user
 experience (allowing people to find other users across the world, but also
 to interact with their friends) on Ship.2 machines. And, if I'm completely
 wrong, we can just shut the server off anyway, but disabling it on the
 builds means we don't even have a chance to make it work.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5141#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system