sir yes sir. I am going to implement this today.
are there any examples of these?
yeah, this is risky. I dont think i can trust some random dude to send be a list of exploiters to ban, esspecially since it could be compromised and ban a ton of innocent people.
1 Like
can i see the devforum post?
Also im the only one managing this, so the chance of the token getting leaked is only slighly less that if i worked in an group
alright, I have switched to an sqlite3 database. The endpoint is now /users
Maybe make a game in Roblox where you can enter a banned username and you see the reason and stuff.
And a right to be forgotten Button.
yeah, prob gonna make that all a discord bot. (and button prob gonna be tiny so exploiters don’t notice it)
You have to inform the “hackers” that they are in your database and why. Then they should have the option to contest that. Or to be forgotten.
sort of defeats the whole purpose of a ban list lol
Banlist has 1 person, maybe at least build a database of exploiters before releasing. 1 person feels more like witch-hunting/a personal vendetta over anything else
1 Like
I know, that’s why I say it 24/7.Thats useless if you dont want to own a hacker thousands of dollars.
History repeats itself again, doesn’t it?
2 Likes
which one would you recommend?
yeah we are just sticking this up so people can report evidence
I like Vercel for Node.JS sites like this one. It’s easy to use, and unlike Render, it doesn’t have a storage limit.
I’m not here to try and discourage you but this resource is not very great. Many people have attempted to do this before and failed. Also, you should avoid using JSON files for tables like these which “should” at some point have tens of thousands of records. You should be using an actual database instead.
1 Like