[RSS Feed/News] Babblet: Real Time Chat Lite

Not open for further replies.

XenForo Rocks

Team Member
+Lifetime VIP+
True Member
Laptop fund sale. My laptop is getting quite old and needs replacing soon. Since i use the profits from my apps as a "do whatever with" money, I've decided to use it to buy a new laptop. the sale will run till i have enough to buy a decent laptop/macbook. So everything 50% off till whenever!

NOTICE: If you are upgrading Babblet, you will need to restart your babblet.js application. if you have moved it from the default directory you will need to take the updated one, verify the information it contains, and replace the one you removed and then restart the babblet.js app for node.

Babblet is the little brother to Babble. It is a real time chat using node.js and sockets. It uses less resources and doesn't rely on long polling or interval scripts to check for new messages, like many other chat systems available. Babblet doesn't have as many features as its big brother Babble, but it is still feature rich.


A modern browser that supports web sockets. (Firefox/IE11/Edge/Chrome/Safari supports websockets. For mobile browsers, I will only be supporting Safari and Chrome).

Node.js installed on a local or a remote server that can run a node.js script. I have only tested the last 4 versions of node.js, but the latest version of node.js you can install, the better. I will attempt to compile a node.js versions that are compatible with Babble.

The php side of babble should work on php 5.5-7 (IPS 4 doesn’t official support php 7 due to incompatibilities with htmlpurifier has with php 7).

Notes: babblet requires node.js. This is an unconditional requirement. So many of the features of babblet are nodejs dependent, that there isn’t any fallback to another web technology (like ajax/long polling). With that in mind, Babblet is very javascript dependent, it will not degrade gracefully if javascript has been disabled in the browser,if you have any tin foil hat wearing members, they will not be able to use babblet.


*If you have SSL(HTTPS) on your server, you must be able to create a "reverse proxy" in nginx/apache to be able to use babble.
**if you are running a server that doesn't use a LAMP ( Linux, Apache, MySQL, PHP) or LEMP (Linux, NGINX, MySQL, PHP) server, I will not be able to give support for. AFAIK nodejs/socket.io will run on windows and mac os x, but configuration might prove difficult. As for *BSD servers, they should operate similar to a Linux server.

Each purchase only entitles a installation on 1 live site and 1 dev site. If you wish to run babblet on multiple sites, you will need to purchase babble for each site. If you are found in violation of this agreement, I can choose to revoke your access to future updates and support until the matter is rectified.

If you purchase a copyright removal, Babblet will occasional make a call home to http://codingjungle.com to validate the copyright removal key. Copyright Removal keys will need to be purchased for each purchase of babblet if you wish to run it on multiple sites without branding.


  • Uploads: If the upload is an image, the image will be “lazy loaded” and resized to fit the dimensions of the message area better. If it is a non-image upload, it will display a link to download. NOTE: Groups who can see Babblet , can also download and view images.
  • Sounds: Babble comes with a collection of sounds for send, receive, entering, leaving and whispers. Users can enable or disable each sound as they see fit. The sound files can be replaced at any time in the ACP by pointing to the corresponding sound setting to the new location (this is to avoid future updates from overwriting your sound files). NOTE: due to some limitations in mobile OS’s (iOS and android) even if the sounds are enabled by the user, there is one additional step they must take to hear sounds on the effected OS’s. On mobile devices a Speaker Icon will appear, that will need to be activated to be able to hear sounds, this action must be done each page refresh.
  • Whispers: Whispers are private messages that are sent in between users. They will open in a “tab” in the room and will flash when a new message is received if you aren’t currently active on the tab that is. Whispers only work inside the room, you currently can not “whisper” to some one who is not logged into the room you are in (at a later date this might change).
  • Browser Notifications: A user can set how many new messages they receive in a room before a browser notification is triggered (or they can disable them all together). Currently these do not work on mobile OS’s, in the future I plan on adding notifications for iOS and Android.
  • New Message Order: By default babble will order messages newest to oldest, for some users this might not be ideal, so they can reverse the order to oldest to newest. Any new message after this will honor the setting.
  • Archive - if enabled, a user can select to load messages previous made in the room. this is a group permission.


Commands can perform special functions when issued. The commands can be issued thru the chat area (similar to how IRC does it). Some commands have group restrictions. If you need more advanced functionality you can create a “command” file.

Command list:

  • Announce – adds or removes an announcement to the room
  • Ban – bans a user for a room.
  • Unban – unbans a user for a room.
  • BanList – Show’s who has been banned from a room.
  • Ignore – Ignore a user in a room.
  • Unignore – Stop ignored a user in a room.
  • Kick – kick a user from a room.
  • Me – an action command for a room.
  • Mute – Mutes a member for everyone in a room.
  • Unmute – unmutes the member in a room.
  • Mutelist – shows a list of users who have been muted.
  • Rules - Show the rules for a room if they have them.
  • Purge - deletes all the existing messages in a room
  • and many more!

Continue reading...
Not open for further replies.