Skip to content

Instantly share code, notes, and snippets.

@javaarchive
Last active January 26, 2022 06:25
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save javaarchive/742759e5f506dd9bf503ed7a707d7928 to your computer and use it in GitHub Desktop.
Save javaarchive/742759e5f506dd9bf503ed7a707d7928 to your computer and use it in GitHub Desktop.

Hello there, I regret to inform you that back in June, the glitch team noticed that pinging services affected the stability of glitch by a significant amount so they took action by banning all traffic that appeared to originate from a pinging service. Pinging services may or may not have also been the causes of the frequent outages as outages now happen a lot less frequently after the ban. Another reason was that a lot of money was being wasted, because most projects spend a lot of idle time waiting for requests or in the case of discord bots responding to gateway ping events. The glitch project wakeup system is designed so that a project with no requests in 5 minutes will sleep allowing more apps to run on the platform concurrently and ensuring better stability. You might argue that discord bots don't do that, and you might be right if your discord bot is in a large amount of servers(>=1000). In that case you should be getting glitch boosted OR moving to a paid server. However most of the lesser used discord bots will spend a lot of time receiving messages that the bot should ignore, and also processing typing intents(this can be filtered out with an option though). If you still want to try to host bots on glitch, checkout this experimental bot relay created by community member wh0.

@aboutdavid
Copy link

This is a very good response on why pinging services are dead on Glitch.

@trentwiles
Copy link

Pretty solid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment