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
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 :)
![[N6] avatar](/site_screenshots/22/24/blankbarrel/index.html.50x50.webp)
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 :)