<br><br><div class="gmail_quote">On Mon, Dec 15, 2008 at 7:47 PM, David Leeming <span dir="ltr"><<a href="mailto:leeming@pipolfastaem.gov.sb">leeming@pipolfastaem.gov.sb</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am using USB active antenna (prototype). Has always worked well with 0.4.<br>
</blockquote><div><br>I've used both the AA and AP's and it doesn't seem to matter as far as this ejabberd issue goes.<br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I concur with Anna that if you leave them connected, after considerable time<br>
they do partially populate.<br></blockquote><div><br>My user group is fairly loyal and extremely patient. It helps that we have other methods of communication, such as a home page, email, wordpress (once I installed mysql and migrated the database), laconica (once I figured out that darn missing dependency), and a permanent jabber MUC room. Once we let each other know, one way or another, that ejabberd wasn't behaving as it did under 0.4, most folks understood.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I have run olpc-netstatus on all four laptops, making first certain that:<br>
- all are connected to School Server<br>
- all appear in eJabberd as online users<br>
- none appear in network neighbourhood (you can't see any on any laptop) 15<br>
mins+ after first connected<br>
<br>
Remember, they are all registered and running 8.2</blockquote><div><br>This doesn't seem like an XO issue. It looks like a server issue.<br><br>My user group is quite diverse. They're literally all over the continent. We didn't have any issues under 0.4, so 0.5 is kind of a hassle right now. We're currently using and testing XS 0.5 ejabberd with:<br>
<br>Traditional Sugar XOs with 656, 714, 767, and joyride builds, mostly using the chat activity, gajim, or finch as clients<br><br>XO's booting gentoo, ubuntu, and debian, usually using pidgin for the client<br><br>Regular desktops/laptops running Ubuntu, Mandriva, or Windows XP with assorted clients<br>
<br>My personal Ubuntu desktop where I log in as the "admin" user for ejabberd on pidgin<br><br>A Macbook Pro (that's you tinker!) using adium as a client<br><br>Webchat applications such as jwchat (one of my users wants to connect via her work and that's the only thing that will work with Internet Explorer and I can't get it to work on the XS) and jabberworld, which I installed locally.<br>
<br>So I think we've tested ejabberd on XS 0.5 with as much as any user group could possibly throw at it and it still isn't reliable as far as seeing everyone. Since we're extremely patient, we do eventually see most folks, but it's been a perplexing experience. We never had this issue under XS 0.4. And I can't comfortably install XS 0.5 in a school if ejabberd keeps acting like this.<br>
<br>Anna Schoolfield<br>Birmingham<br></div></div><br>