We need to fix the discord ban mega-thread

The issue with the Discord ban mega-thread

If you have been around on the glitch forum for a while, you may have seen the discord ban mega-thread. It’s the spot to report banned IPs. But unfortunately, it is an endless loop. The scammers who get their bots banned are also likely posting them. When they get sent to a new host, that host will get banned, and so on. If we want this problem to end, I have a few ideas.

Idea 1: The pricey but more user-friendly idea.

To stop this, Glitch would have to give each user a unique IP. If they got a bot banned, all of their bots would be banned and Glitch could look into the problem to see if they need to take action. This, in an ideal world, would be the solution. The issue is that getting everyone an IP would cost a very, very large amount of money.

Idea 2: The cheap but not so user-friendly idea.

When a new Glitch account is created, the user would have to enter a credit card. Discord spammers probably don’t have lots of cards, so this would, in theory, work, but it causes another issue. Most people using Glitch will not want to put in a credit card because of the fear they could get charged or scammed.

Thank you for reading,
Riverside Rocks

It would make the free version of Glitch more paid and many users use Glitch because it doesn’t require a credit card (among other great things).


I remember reading a post where cori said that each container had a different IP or something (correct me if I’m wrong) and how they change dynamically over time.


We could at least reduce this problem for boosted projects by locating them in another server. That way, paid users will no longer find this as a headache. @glitch_support, are there any updates regarding the Discord IP ban.

The only issue is that boosted users could also spam discord. Its would not be as common as free users, but still possible.

Yes, but we can also narrow the search on who is spamming Discord. Unless it happens randomly and unknowingly by bots.

1 Like

Well glitch can just configure there network to monitor connection times to the discord api. THey could always rate limit bots themselves.

1 Like

Or Glitch could monitor the outgoing requests as well, like a 429 for outgoing requests as well, although that would suck.

1 Like

Yeah… that also raises the question about paid users and unlimited requests.

The limit could be for free users only…then free users are really gonna go mad with technical restrictions.

2 Likes

I don’t see why a free user would need a glitch project to connect to a url multiple times very fast. Unless they are trying to build a supercluster of computers.

cough, cough, @Jonyk56

I mean if you want all that power you could just get google colab notebook they have like 100gb of storage, 12gb of ram, and fast gpus for all your parellel processing needs.

1 Like

:insert_grunt_emote: @javaarchive discord bots do that already =P

If I am right, Glitch has an API. If the team could expand that API than possibly they could make a form where people put in their project name and then the form will automatically refresh the container it’s on. That would decrease the huge efforts that the Glitch team have to put in to manually refresh the containers and the huge forum thread!


For now, could we add a Google Form instead of the long forum post, just to clean things up?

2 Likes

Glitch automatically restarts your container when you run process.exit().

I meant that it will refresh the full container (all the projects on it) not just yours to refresh the IP

That could be abused, and glitch would become the holy grail of web scrapers.

1 Like

Unfortunetly you have a bit of a point.

collecting cards from all users would most likely result in a data breach

1 Like

Digital Ocean does it.


1 Like

still there’s always a chance.

1 Like

Delete the card numbers like 1 day after… Also charge and return twice in case they use a temp card

Still would pose massive security issues even sending the card numbers somewhere

Accepting credit cards online is a common practice, and if glitch used a trusted db, (like aws), I’m sure there would be very few issues.

potentially but I could imagine many people leaving the platform

How about we initially block the discord api through a firewall and you have to add a credit card to unlock it for a container.

personally I wouldn’t have a problem as I don’t host bots here but I can see many small bot devs disliking that

2 Likes

That could work but I also agree with what @anon43649539 said.

offtopic but its 1:23am so I gtg

Lol ok seeya.


Don’t think requiring a credit card is the way to do it.
Reason being the point behind glitch was to help young coders who want to learn how to code. Requiring a credit card will turn away a huge portion of these coders, defeating glitch’s point.

Better Solution
Monitor/log each request to Discord, when an IP gets banned, find the ones that might have caused it, then take appropriate actions.

There really is no “good” way to do this, at the end of the day, Glitch is still a free service. So free users should be ok with waiting a few days for service restoration. (Paid users are a different story, they should get a separate host)

4 Likes

The issue is, how do you log the activity? Maybe thousands of bots on the same host look the same to discord.

2 Likes

On the glitch side, you have a basic logging system.

3 Likes

Ok here’s a possible solution, if the glitch team could setup container servers just for discord bots and let people move their code to the discord bot servers. Here’s the catch the glitch team has a system where it monitors the rate of requests it sends to the discord api if it’s too fast it automatically suspends the app. Or, you could go through a background check and a person would look at your code to ensure it isn’t being malcious.
Personally I think the automated solution might work better since according to the megathread, we have a lot of discord bots

3 Likes

Something needs to be done.
The current thread shows just how bad the situation is.

4 Likes

Sorry, I know we hate bumps, but this is only relevant here: if you don’t want the megathread to clog up the forum when you are viewing it, just change it from Normal/Tracking/Watching to Muted at the bottom of the thread so it doesn’t appear.

5 Likes

assuming most nodejs packages respect proxies we can set the default system proxy to a proxy that rate limits your requests so they never hit the discord servers

socket.io long polling will make tons of requests in a short interval so it is definitely reasonable.

How about identifying users via IPv6? Many people don’t change it. Many VPN’s don’t change it.

That might work but not everyone has a v6 address plus it’s easy to change for both v6 and v4