😒 Explained : Deletion of Old Bot

To our existing users, moderation teams and owners, we sincerely apologize for the major inconvenience of our service entirely being wiped out from Discord.

This situation was (somewhat) avoidable, but it involved a painful process of over 30 days with our predicament getting dire by the day till the global shutdown of our service.

We currently have a renewed bot that is fully operational and verified by Discord.

You can add the new bot here.

For servers that were previously using our bot before deletion, just type the following command to renew the verification message.

/latest-verification

Start of Issue

On July 14th 2022 (PDT), our CEO and sole developer received an account suspension notice from Discord due to "fraudulent charges" after attempting to purchase a Nitro subscription with his personal debit cards.

This Nitro purchase was unsuccessful multiple times prior to the suspension, even after switching to different debit cards with sufficient funds for the purchase.

After roughly half a dozen attempts, the account was aforementioned disabled and the CEO was locked out. The only unfortunate route that this can lead to is to either lay the account dead, or to file an appeal. Initially, we (the team at AuthenticateMe) knew that we have 14 days to get this issue sorted before an uncalled action by Discord's automated system gets permanently applied.

The CEO has filed an appeal on the same day in hopes of getting the account re-enabled and to continue operations on our Discord bot. This is crucial as the bot is tied directly to our CEO's Developer account. If the account goes down, the bot goes down with it.

Attempted Resolution

Our CEO received a reply from a Discord T&S Staff stating that the account will not be reinstated due to the aforementioned violation in the previous section. However, our CEO had substantial evidence to provide, proving that :

1. All debit cards attempted to purchase Nitro belongs to the CEO

2. No debited amount was made to the cards on monthly statement

3. Personal ID Card to go along with the previously mentioned items

Through some persuasion, the CEO followed up with the information to Discord's T&S team to review even if they did not request for it, in hopes of a resolution of a possible glitch issue that lead to the account suspension.

However, there was no further response from the staff that handled the ticket.

The CEO also followed up 3-5 days after providing the information to keep the ticket open for resolution.

14 days after the initial suspension, with multiple tickets open and no response from Discord's Support Team, the account was still disabled but not deleted. We started to get more concerned that the account would eventually be deleted by Discord's system if no human intervention in the ticket was done.

We also reached out to our sponsor for assistance, with aid using his publicity to gain some form of attention on public media to reach someone at Discord to remedy our issue.

RIP Bot, still NOTHING from Discord

On August 14 2022, the CEO's account was permanently deleted from Discord's database along with the bot. We received no warnings, no replies and no outreach from Discord regarding this situation that could have been easily resolved.

Our staff have sent in personal tickets to Discord's T&S team to reply, also to receive no replies and resulting the tickets to close automatically after a few days of inactivity.

Moving Forward : Future Plans & Personal Comments

We are currently working on a new bot that would take over the old bot's duties. It is currently active but limited to the standard 100 server cap due to Discord's slow process of verifying the bot.

As of September 2nd, we have received the follow-up phase of our initial application to verify our bot for more servers to re-add this bot into their server.

Stupidly enough, I have followed up a ticket on August 28 which has been closed by the ticketing system and received a reply from a competent staff in literal minutes after opening a follow-up enquiry. We are actively in touch as much as we can with the current staff handling this follow-up enquiry to pass on to the relevant department to handle this issue that could have been easily handled 49 days ago.

We are looking into more ways to prevent such issues from creating disruption to our users, which we will not reveal (security through obscurity), and we have attempted to contact Discord^ if they could offer any resolution to this issue.

Regards,

Shai the Haku

COO of AuthenticateMe

Last Revision : 13/08/2023

R1. New bot has been approved for use by Discord.

R2. New invite link with new domain.

R3. Discord's response to our issue : basically idgaf.

^ Discord has closed all tickets regarding this issues without offering any assistance / responses. This is not due to our incompetency, as we have sent multiple followups in the same ticket request for a response.