Latest Activity > embeddable

You will be able to set & remove passwords on the dashboard, in order for the chat to load you'll also need to pass your password when you initialize your chats e.g. chattable.initialize({stylesheet:"chattable.css",password:prompt("Enter the password")});})

Let's gooooooooo

Thank you for your sustained support dude, we really appreciate it

Yay! Thanks a lot!!!

I work a full time blue collar job, and these issues surfaced in the middle of a work week meaning almost no time to troubleshoot. That's why the maintenance window is so wide. The goal is to have everything fixed and chat histories restored BEFORE May 10th

Again, thanks for the patience and support. And to my new followers, do not be discouraged. Things like this do not happen often, but is the exact reason why I keep things free, lol

Short story long, Old messages on Chattable will remain jumbled/unordered unless you clear the chat or me via email to manually rewrite your room's JSON and chronologically re-order your chat history. As I transitioned to a custom script to generate time-based IDs for messages, I created a timestamps-related bug which chronologically jumbled messages unexpectedly when generating message ID's aka "push ID's".

While this has now been corrected (I think?) I would recommend clearing any chats that don't matter, new messages going forward should sort themselves correctly but old messages may (definitely will) remain chronologically jumbled. If you absolutely need to recover chat history (in chronological order) just email me the chat ID and I can personally fix your room's JSON/rewrite it.

also ty everyone for being so patient :') i am literally one guy just trying to maintain a fun project lol

If your chat is acting funny, clearing your chat or contacting support may also fix the issue.

Ok, thanks!!!

Is this the cause for all chats being unusable currently? None are loading. I assume so, but would appreciate confirmation of my suspicions if they are true. No rush to get it fixed.

Yes, I've turned off Chattable's backend to prevent further issues and confusion

potatoes

I NEED TO BOOKMARK THIS, hehe!!!!

ended up going back to the non-beta links for now, which work a lot better :3

Woah... mega cool!

holy wow....

sick as hell!!!

woah I can't believe I haven't seen this post yet xDD thanks for the shoutout

Off Topic, but try out the new four chan demo/theme on Beta now :O

Some messages sent today may go missing while I am working on how chats are stored/saved

:D

What happen bro where ma messages

i like apples

is this possible with VLC Media Player? I've been meaning to print out each and every single frame of a video so that I could turn it into a series of flipbooks, with an MP3 player for the sound

Ooh, noted! (pun unintended yet welcome :) ) Thanks!

HUGE! Really glad I don't have to switch over

i dont use this nor care i just liek da idea of this but i want to say good luck to you, this does not look easy.

this is great news!!! Thank you so much for all the work you do for Chattable, it's a huge part of making the indie web more connected and with fun chat features :D

oh my goddd this is awesome! I really appreciate your perseverance on this project, chattable reigns supreme once more as the premier chatbox ^_^

I just identified an issue where Chattable beta & production versions were racing to overwrite chat messages, the loser would lose their messages. I've since cloned the database and use a separate db for beta now, chat history & ownership now varies between the two versions.

Now is a good time to change all your beta.iframe.chat links BACK to iframe.chat links, using BOTH can get confusing for you and me when troubleshooting

Ahh thats why some messages went missing. Anyways, congrats in the migration!!!

if you had messages go missing you may be able to recover them by switching from beta.iframe.chat links to iframe.chat links in your iframes

Yay! Hooray! Congrats!

YAAAAAAAAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! CONGRATS!!!!

hallu chattable! i have managed to create an account via the beta mirror site but i am unable to create a chat with my chat id :(

I believe I have fixed this, try visiting the chattable dashboard again and creating your chat if it doesn't exist yet. A few things to note though: 1. Chat IDs are like usernames, if one is taken already, you won't be able to use it to create your own. 2. The dashboard doesn't work in real time, most changes will require you to reload the page to see your changes, this will remain true while the project is in beta

I've started rewriting Chattable 3 days ago. Changes will only affect beta.iframe.chat links until the full rerelease of Chattable

As of April 8, 2026 on Beta, messages and chat room settings are officially stored locally on Chattable's servers. Removing the biggest Firebase dependency in this project. You can read the entire chat history of these chats (up to the last 200 messages) and send & receive new messages. You can also delete & edit existing messages per your permissions in each room.

Most of the dashboard and other chat functions do not work yet, including the emoji table, promoting users, demoting users, kicking users, banning users, creating chats, deleting chats, creating accounts, deleting accounts, adding emojis, removing emojis, adding profanity filters, removing profanity filters, clearing chats, executing commands, and many other features not listed.

I will prioritize certain features as I go through and rewrite each existing feature, but we're at a point that beta allows you to consistently read & send messages at no cost to me, 100% reliably.

The current features have also just been fixed on Beta, hide/show messages, kick, ban, and reply

Fixed the emoji table and auto scrolling to new messages

Let's gooooo!!! I'm ready for Chattable 2

Yay!!

the good ending. glad youre moving away from firebase, good luck on your journey! :-3

nice!

promoting & demoting moderators has been fixed

Most chat features are operational again, working on the dashboard now.

create chat, delete chat, add emojis, delete emojis, lock chat, unlock chat, and clear chat are now working again

Still using Firebase for Auth at the moment, sometimes chats won't load due to login rate limits. Will be fixed once Firebase is fully removed.

replies are working again, whispers are working but don't render in real time (yet) meaning whispered messages sent after page load won't render until the next page load.

omg yes please! i wanted to add chattable on my website so bad but i just recently found out that you we're down due to attacks, i hope those bad people get karma :(

Sign up page has been resurrected on beta.iframe.chat so new users can sign up & start creating chats again

by toy i mean rewrite and i'm maybe 15% finished, haven't even gotten to the rendering part yet so nothing loads

currently about 50% finished, might one shot this project over night, idk

it's not one shotted, BUT beta is now 90% self hosted, you can send & receive messages now. No double messages or broken renders, and no disappearing messages (messages getting eaten)

You can't interact with messages yet (delete, edit, promote, kick, ban, etc) or access the emoji tray or settings tab YET but I'll work on that soon. ALL of these changes are for beta.iframe.chat links only (not iframe.chat links)

If you are still using Chattable at this time, expect chats to not render on some page loads (because of connection queues) and double rendering of all messages (known issue on my end, happens during high traffic)

Was the limit for february reached or for march already? I thought it was already at the limit when the chat was down for a few days this month. The traffic has been really high for sure

Bread

Kuroi, brother, I don't even know. The limit for March hasn't been reached because the limit is supposed to be a full-stop when met. Like, when I reach this monthly limit it's supposed to full stop until it resets... but it didn't. Next month my limits will reset, they'll be the same limits but with a new balance at 0 bytes of data downloaded. Firebase rules seem to just be ignored for my project, however,

The concurrent active user limit seems to be harshly enforced. 100 users at any given time. If 100 users are online (including anons across all chats), other users will see a chat that is blank (no messages) when loading the page. It seems to be the only limit being enforced and there is absolutely 0 people online who have reported similar behavior.

According to Firebase: I'm allowed 360mb of download per day. I'm at 100+ GB of download for this month. It's been 25 days. Do the math, and you'll notice something is wrong. I have no idea how or why Chattable is able to send or receive messages still, this month has a recorded 224,000 monthly active user which is an all time high.

I can't begin to imagine what it's like to host so many users, but have you thought about moving to a dedicated server (i use railway). A simple Node.js server with socket.io might suffice, for little money. You could also optimize your queries and think about implementing throttling, if you are still have griefers? Apologies if this all sounds obvious or unreasonable, just wanting to help :)