Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Michael last won the day on October 17

Michael had the most liked content!

Community Reputation

192 Excellent


About Michael

  • Rank
    Head Developer

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

8,362 profile views
  1. Babble Chat Service

    in its current form, an ajax request wouldn't be enough (as the namespace the socket.io is the room), in version 3 this will be easier to do, so that will be something in 3. right now the easiest thing to do, would be when it is a widget, to have it open in a new tab. yeah, not a bad idea, i'll take it into consideration for version 3.
  2. Babble Chat Service

    so you'd want it to open up another tab if it is the widget switching rooms? not a bad idea, only question would be how to handle it if they are in multiple clubs, I'll see about it for version 3.
  3. Number of users

    2.6.2 will have some tweaks to this, the count number comes from the online list and the online list is directly tied to the socket connections. i've been unable to reproduce this so far, and working on this in version 2 is delaying work on version 3. hopefully the tweaks in 2.6.2 fixes this issue, but i any issues with the online list and/or counts from this moment, will no longer be addressed until version 3.
  4. Number of users

    Changed Status from Duplicate to Closed Changed Fixed In to Next Version
  5. Babble 2.6.1 Self Hosted

    There will not be a 2.6.1 version of the babble self hosted, as a vast majority of the changes were for the chat service. There will be a 2.6.2 released in a few days to address a few other issues for self hosted (that were in the self hosted specific bits of the code).
  6. Service not working

    where you located in the world?
  7. Service not working

    okay try it now.
  8. Service not working

    yeah i thought it was the forcing websockets only, but now i am not sure. I've isolated it to it emitting the online list. hopefully i can get it solved soon.
  9. Service not working

    are you using menu counts by chance? i thought i had this tracked down, but it appears to be linked to counts atm.
  10. Connecting time

    Tomorrow at the earliest, there are a few things i need to test out a bit more before rolling out. instead of using /ban, you can use /mute, it will "silence" them for 24 hours
  11. Connecting time

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  12. Connecting time

    i believe this might be related to an issue in 2.6.0 where i am forcing only websockets. i misunderstood something in the socket.io documentation and thought that would be a good thing, but i also have noticed that sometimes i need to refresh once or twice to get it to connect, cause depending on browser/device/internet connection/server load/ping/etc, websockets can take awhile to fully establish. so i've gone back to the default method in 2.6.1, hopefully this will resolve this issue. there are 2 servers currently for babble chat service, one is in North America (NYC) and the other one is in Europe (Amsterdam), European and Asian sites are reporting much better connections with the European server ( i am not sure where your site or a majority of its users are coming from, so if the NA server suits you best, stick with it ).
  13. Cannot ban username if there is a space

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  14. Cannot ban username if there is a space

    fixed in next version.
  15. the /purge command

    Changed Status from Pending to Closed