If you are in a live chat with another person, then your browser somehow needs to know when the other person has sent a new message. There are various ways to do that.
Websockets are the best way to do that, but websockets from PHP is difficult at best, and requires some special server setup that you won’t find with a web hosting service.
So the only alternative is polling. Which means: constantly refresh the page in the background to check if new messages have been posted. This means that every second or so, the browser needs to make a request to the server, which then needs to fire up a PHP script, which needs to open a database connection, and check the messages table for new messages. And it needs to do that again, and again, every second, for every active visitor.
This is extremely inefficient, and puts substantial stress on the servers. It generates so much load that even simply relying on the account limits was not enough.
Banning the “chat” word entirely in URLs is a very blunt instrument to combat live chat scripts, but it was necessary.
Live chat scripts are banned on premium plans too for the same reasons I described above. But the block on the “chat” keyword is not there.
We don’t do special requests. Our hosting is intended to work in a certain way, and it will work that same way for everyone.
I don’t think it’s banned for domains, but feel free to try.
That’s correct, on both counts. But that’s how it works.
If the chat messages pass through our servers (which they would probably need to), then yes. Again, for all the reasons I listed above, just replace “database” with “Discord API”.
I hope you’ll never encounter any other block, but there are a few more blocked keywords:
Just know that we don’t block “random” words. We block very specific words for very specific reasons. We are fully aware of the side effects they will have on legitimate websites, and we don’t make decision to block keywords like this lightly.