close
  • Ch chevron_right

    CoverseJS updated to version 7.0.4

    admin · pubsub.chatterboxtown.us / chatterboxtown-us-news-and-announcements · Friday, 11 December, 2020 - 21:10

Our ConverseJS web XMPP client hosted here at ChatterboxTown.US has been updated to version 7.0.4. It is a big jump from the previous version 6.0.1 that we were running for a while. So, far from our own testing, things seem to be working fine. Please feel free to report any problems encountered. Thanks.

  • Ch chevron_right

    More observations on the wacky bookmarks

    admin · pubsub.chatterboxtown.us / chatterboxtown-us-news-and-announcements · Monday, 30 November, 2020 - 04:18

It looks like JSXC does something really wacky with the bookmarks. I had added bookmarks via blabber.im and I was able to see the changes propagate to Gajim and ConverseJS. However when I logged into JSXC, all but two of my bookmarks disappeared. I don't know if JSXC has some browser cache that tries to "update" the bookmarks , but so far that is what I've observed.

  • Ch chevron_right

    Wacky bookmarks

    admin · pubsub.chatterboxtown.us / chatterboxtown-us-news-and-announcements · Saturday, 28 November, 2020 - 09:55 edit · 1 minute

Unfortunately the bookmarking feature breaks between XMPP clients. The symptoms between the different clients can be different. For example, if I make bookmarks in Conversations Android app and then make modifications in ConverseJS, like changing my nick, it doesn't seem to propagate to other clients and sometimes the chat room disappears altogether. Or one client takes control and any changes done in another client is undone. It's things like this that make XMPP so difficult to attract the general population and why centralized services thrive. Sometimes having too many choices and and too many different ways of implementing a concept causes incompatibility in ways that most people don't want to have to bother with. The moment you suggest a "workaround" to make something "just work" should be a big red flag to indicate that something needs to be fixed or improved. Workarounds signal to the end user that the product is not quite ready. It is just really surprising that with XMPP having been around for decades now, that this is still an issue. I really hope that developers would work together on this to create universal solutions rather than continuously imposing responsibility to other developers. Yeah, I get it. Nobody is breaking protocol with the way they have implemented a feature, but can we all figure out how to make things work with each other? In the meantime, the most common suggested workaround for this problem is to log out all other clients and modify your bookmarks in one client at a time. Well, not even that is perfect, but I generally do my bookmark management on the blabber.im android app or on Gajim. ConverseJS also has a good interface for managing bookmarks. But, again, be warned not to be logged in to more than one client as things can get messed up badly.

  • Ch chevron_right

    More pubsub problems squashed. ConverseJS and JSXC web clients OMEMO working

    admin · pubsub.chatterboxtown.us / chatterboxtown-us-news-and-announcements · Friday, 20 November, 2020 - 08:43

I was able to restore the 100% compliance test results after clearing one of the pubsub tables in PostgreSQL. However, this morning, I discovered that while my mobile and desktop clients appeared to be working perfectly the hosted web clients were having problems establishing OMEMO with my other clients. At least, this time I knew that it had something to do with pubsub databases. There's a few tables and I had only cleared one of them to pass the compliance test, but I guess there might have still been some entries in the other tables that were now missing associations causing more failures. I tried just clearing the pubsub related tables through phppgadmin, but it didn't seem to fix things. So, I decided to drop the pubsub tables completely and reload the database schema by importing the /opt/ejabberd-20.07/lib/ejabberd-20.07/priv/sql/pg.sql back into the database. Luckily, doing so will not overwrite any existing tables, but it did rebuild the missing pubsub tables. Anyway, that appears to have fixed that problem.

  • Ch chevron_right

    Migration to PostgreSQL, pubsub table errors

    admin · pubsub.chatterboxtown.us / chatterboxtown-us-news-and-announcements · Friday, 20 November, 2020 - 08:43

I migrated from Mnesia to PostgreSQL recently and while it appeared that the migration was successful (user accounts were preserved, etc.) the server was failing the OMEMO test on compliance.conversations.im. After speaking with Conversations and ejabberd support MUC, I was led to discovering the ejabberd server was reporting errors with the pubsub index. Unfortunately, I had to empty the pubsub tables to get things working again. That also means that any pubsub related entries (especially in Movim communities on this server) have been delete. I am hoping that there will not be any further errors related to the database migration.