Declined DiscordRep

Firstly, the request is only being accepted through the extensions, which means we can't receive packets from anything but the extensions. In the extension, we use a technique where you click "Scan". It will then refresh your browser, and when the messages are loaded it will be saved and automatically uploaded to another URL. This URL can be shared in the Scam Report. We're expecting it to have good accuracy of gathering chat-logs. Currently, our extension is uploaded on Google Store Listings and can be added to the browser.

We have other procedures such as, but not limited to, screen share (through Discord), where you don't need to run the extension. Yes, of course, we allow them to appeal even if not using the extension even though in the report the extension were used by the reporter.

Well, if you didn't know, each chrome extension has its own ID. We only allow requests through that ID. The ID can be found in chrome://extensions/.

I'm sorry for the trouble with our FAQ, and it's obviously not updated to current standards. The current FAQ was made by a previous Staff Member and is outdated. As shown here:

Allow me to explain this. We previously had the idea of using reputation as a trust factor. The higher the trust factor of the user you traded with the more money you could get back if the user was found guilty in a Scam Report. However we've changed up a lot since then, and we'll be doing an update to the FAQ to ensure that this will not be misunderstood. Thanks for letting me know.

To your second question. We can take a look at the bot. The bot can scan messages and through arguments/values, it matches and finds things like rep4rep, or other values. If we detect anyone against our reputation rules, we'll give punishments. We can detect bots by checking when their account was created, and usually, we do manual checks on users that are flagged. Users created under 1 month ago will not be permitted to use DiscordRep's voting feature.

I mean you are not wrong, but we manually ask both sides. We don't blindly believe in the scans, but it's better than a normal screenshot. It's not 100% accurate.

Even if the information coming in was 100% accurate, the fact that you require users to download and trust this extension in the first place is, in my opinion, a nonstarter.

Users are not required to use the extension, we are open for other options, and there is no need to use the extensions. Trust is something that must be built up, and we’ve built trust into our userbase and been interacting with them closely.

Another Staff member @_Blizzard_ will inform you of upcoming updates and will be following up on further questions.

Hey everyone. I'd like to first start by apologizing for the delayed update/response on my end. I had initially planned to post a full comprehensive update to this application a month ago, but lately, I have been entirely swamped with work-related issues and problems that needed my attention. I'd also like to thank all the SteamRep staff members that have personally reached out to me, sharing their input.

Overall quite a bit regarding DiscordRep has changed since we first submitted this application. One of the most significant and visible changes that many of you may have noticed was through our DiscordRep v3 release, which completely overhauled the layout and design of our website on the 1st of May. This significant change helped lay the foundation and groundwork towards what we wanted to build off of and create. Around this same time, both CsGoat and I joined the staff team as moderators/report resolvers. This decision by upper staff was made in efforts to shift their target audience directly towards the trading community as a majority of the staff team was made up of developers who had little experience with the trading community. Drawing from our experiences with the trading community, CsGoat and I have been moving forward with pitching the idea of DiscordRep to several CS:GO trading communities for them to test out and even adopt. Through this, we have been able to receive an influx of great ideas that we plan to implement soon. We also now have a staff handbook for our team to reference that outlines our process, standards, procedures, and punishments in regards to reports and appeals. On top of that, we have implemented a new opt-out feature on our site to address certain concerns presented by Top.gg that permanently deletes all data on the user who is opting out. We also have rebranded to a new logo that we believe better represents our community. I know that originally we didn’t have a Steam group listed on our application, but we have one now: link

Also, due to the feedback and concerns that we received from your staff regarding our extension idea, we have decided as a staff team to abandon the idea entirely as it does present several privacy issues.

That being said we have not been without some setbacks. The first setback that we encountered was that we had to migrate over to a new bot for our Discord bot, this led to a decrease in the number of servers that our bot was in. On top of that Top.gg, a well-known Discord bot list site has refused to approve our new bot on the basis of thinking the bot goes against Discord TOS, despite us having confirmation from a Discord staff member stating that our service in no way at all violates Discord TOS. To make matters even more difficult Discord implemented a new verification system that caps off the number of servers a bot can be in at 100 until the bot is verified by Discord. To pass our verification we had no choice but to rebrand the bot from “DiscordRep” to just “Reputation.” The silver lining in this is we believe the new name for the bot will increase its searchability among users. Recently we lost one of our head-developers, Janel, who was responsible for a majority of our site's development due to his decision to quit Discord in order to focus on life.

In regards to our current stats:

• 1155 Bans.
• 70 Warns.
• 35 Opt-outs.
• 47 API keys.
• 808 users with comments on their profiles.
• 3830 users with upvotes/downvotes.
• Our bot is in 239 servers.
• The 239 servers consist of a total of 115854 users.
• We have 1827 total users who have logged into our site so far.
• 689 members in our support Discord server.
• A total of 112454 searches through both our bot and website.
• A total of 7202 unique searches through our bot and website.

We have quite a few planned changes and updates that we have been working on that we plan to release soon. One of the most significant changes that we are looking to make is completely overhauling our report system and abandoning our forums

These changes can be broken down into two different sections:

Website:

• Add a report section to the top navigation bar of the website.
• Add a short instruction video on how to enable Discord Developer ID to the main page.
• Add RepBlock option back to profiles. This feature is used heavily as a way for Discord servers to quickly copy and paste the info on a specified account in their server.
• Add an Investigative Policy page that goes into greater detail of how we conduct our investigations and what evidence we require.
• Add Discord related scam prevention guides that outline all of the well-know scams through Discord as a way to educate users on the subject and help them identify scams.
• Add a ban evidence link to banned user's profiles. We have started doing this manually on more recent bans, but we want to add a submission button that uploads the evidence to the banned user’s profile.

Bot:

• Add an opt-in command for owners of Discord servers that auto bans, banned DiscordRep users.
• Add an opt-in command that instead sends an embed for each new banned user with evidence for staff to decide whether they want to ban the user from their server or not.
• Incorporate a mod mail system with extensive prompts into the bot for reports.
• Add ban date to user's who are banned on =rep embed.

Of course, these are the first of many changes and improvements that we would like to make.

As a quick update, we just added a new developer to our staff team named <bryce> to fill the gap that Janel left. Since I noticed that our staff team list at the beginning of this application was pretty outdated, I wrote up an updated version below.