Not sure if you’re aware if this issue, or if it’s relivent with the memory leak, but I’m currently running into an issue that freezes the page.
I can’t even open the console to figure out what’s happening.
Not sure if you’re aware if this issue, or if it’s relivent with the memory leak, but I’m currently running into an issue that freezes the page.
I can’t even open the console to figure out what’s happening.
Yeah that’s the memory leak. Still working it out.
I’m not sure if you’re taking suggestions, but if you are I have a couple:
A limited amount of serial codes, example:
code: test_123
serials: 1000
In this instance there would only be 1000 stock, so _ unique people could redeem this code and get the item.
A setting that when enabled limits your ability to redeem the code past a certain date (maybe even time?).
code: Halloween_31
expiration: (31, 10, 22) "Day, Month, Year"
Sounds SUPER suspicious to me, why does one need to be 16+ just to use a basic Twitter codes system? What kind of heavy data collection are you even doing?
Totally understand your concerns. We set the limit at 16 due to GDPR concerns, but we are actively working to fix this. It will still be locked at 13+, as we use Discord for authentication, and will not implement a custom solution, as I do not want to deal with COPPA regulations.
As for your concern about data collection, our privacy policy details what data we collect and store, and how we use it. To make it easier, I’ll put it here:
This is just the information that is given to us by Discord, we only store your ID, username, discriminator, and avatar, as well as the access and refresh tokens given to us by Discord.
To put it simply, we are trying to collect as little data as possible.
I will add this to the To-Do list! Thank you for your suggestion!
…why do you need all OF THAT for a TWITTER CODES SYSTEM?
All of it is completely unrelated and unneeded except for the discord username & avatar. You’re acting very suspicious.
It’s literally for authentication. Plus, if you read the rest of my message, you would know that we only store some of that information, as the data you’re concerned about is given to us by Discord.
Fine for username & avatar, but why do you need to know what my language is, what type of nitro I have, whenever I have two auth enabled and whatever “private & public flags” I have enabled? Why are you collecting such unneeded stuff?
Per our Privacy Policy:
Registration is done via Discord, which allows us access to the following data:
This doesn’t mean we STORE it, it just means we are given it by Discord. We have no control over this.
Why do we need to add a bot our server, though I thought the website was for codes for your Roblox game?
It’s the best way to make sure the user has permissions (MANAGE_SERVER) to modify the codes. I tried but there was really no other way to do it server-side.
Can’t you just change the codes from the website or just create new codes and remove old ones? I don’t see why you would need a bot to modify codes anyways?
Again, it’s to make sure the user has the permissions to modify the codes. This is the best way without using Roblox Verification. (connect Discord to Roblox, I am planning to add this soon)
TL;DR without this, anyone would be able to modify the codes.
How would that work, I thought the person who created the codes (On your website) is the only one who has access?
As I stated earlier, anyone who has the MANAGE_SERVER permission on the linked Discord server is able to modify the codes. Without this, anyone could technically modify any guild’s codes, as the permission checking is done on the server-side, and without any, anyone could change the guild settings.
Just pushed this update! If the user has access to Discord links, then they are able to use the service.
Also just wondering why the bot needs the ability to have the administrator permission. And who exactly manages this bot or what manages this bot?
The bot has the administrator permission only because I don’t exactly know what permissions it would need for whenever I add more features to it (i.e. moderation, group management, etc).
Basically so the user doesn’t have to re-add the bot when I add those features.
I manage the bot, and its only there to know when it’s added and removed from a guild, as when those actions happen it executes database actions. (i.e. bot added, add to database; bot removed, remove from database). There are so far no commands or listeners other than what I have listed.
Very bs reason to give a bot ALL permissions (including ban, manage server etc), if you need to add more stuff to the bot that requires a special permission, give it thru the oauth, if a user tries to use a feature that requires the permission; tell them so. Don’t continue your suspicious saga.