1. There is no such thing as a "pending" ban or Steam admin. Anyone threatening your account is a scammer trying to scare you. Read more.

Declined DiscordRep

Discussion in 'Archived Applications' started by leny32, Feb 17, 2020.

  1. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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.
  2. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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.
  3. Enstage

    Enstage SteamRep Admin Partner Community Donator - Tier V

    Messages:
    4,657
    Steam:
    STEAM_0:1:52569926
    This is not possible. Anyone who has the extension can see its code, and therefore replicate any sort of process or technique you use to validate where the request came from.

    Refreshing the browser does not guarantee that the data on the page is what was sent by the server. This can be changed at so many points throughout the process. Besides, anyone could just write their own request to your API with whatever data they want, replicating any sort of validation or verification used in the extension.

    None of this is particularly hard to do, it could be accomplished by most people who know how to open their browser's developer tools.
  4. Manatee

    Manatee SteamRep Moderator Friend Community

    Messages:
    24
    Steam:
    STEAM_0:1:39625442
    Hi leny32, I glossed through the application and replies and had a few inquiries of my own:

    • You mentioned in an above reply that you do not permit payment for reputation, however; in your own FAQ on your website, it mentions that users can donate to the community for reputation. Perhaps you can clarify for me as to what specifics or contexts payment is or is not permitted in regard to rep.
    • [​IMG]
    • My second question would be that of the auto identification system you mention within discord that can identify fabricated reputation.
      I was curious if you would be able to elaborate what parameters this system evaluates on (how do you or the bot know they're fake or bought), how the flags go through human eval and then how it would then be administrated.
    Best regards--
  5. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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/.
  6. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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:
    upload_2020-3-5_10-57-17.png
    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.
  7. Enstage

    Enstage SteamRep Admin Partner Community Donator - Tier V

    Messages:
    4,657
    Steam:
    STEAM_0:1:52569926
    I'm telling you now, there is no way to verify the legitimacy of the data you receive from this extension. Anyone can just forge a request and include this "extension ID" in the request.
  8. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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.
  9. Sniper Pro

    Sniper Pro FirePowered Head Admin Partner Community

    Messages:
    176
    Steam:
    STEAM_0:1:49525162
    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.
  10. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    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.
  11. leny32

    leny32 New User

    Messages:
    18
    Steam:
    STEAM_0:0:109744853
    Another Staff member @_Blizzard_ will inform you of upcoming updates and will be following up on further questions.
  12. _Blizzard_

    _Blizzard_ Donator - Tier V

    Messages:
    29
    Steam:
    STEAM_0:0:102035596
    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.
    alkon likes this.
  13. _Blizzard_

    _Blizzard_ Donator - Tier V

    Messages:
    29
    Steam:
    STEAM_0:0:102035596
    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.

    =[o.W.n]= FD GoD likes this.
  14. Lava

    Lava Public Relations SteamRep Admin

    Messages:
    5,684
    SteamRep Admin:
    STEAM_0:1:46187366
    Sorry for the excessive delay in getting back to you. As I said earlier in this thread, I want to commend what you're trying to accomplish, even if it's not compatible with how things are done at SteamRep (which is not an automatic disqualifier). As such, I think you deserve a better written reason for our response.

    While we do think you have your heart in the right place, we are unable to consider your application. The main reason for this is that you did not meet the membership requirements. Unique visitors to your web page do not qualify as "members", and neither do tallies of members in servers your bot happens to reside in. It's a real stretch to call them "active members". Although you tried to present yourself as active and established with over 1000 active members, your community is still just starting up, and we think you should try to become a little more established before applying as a SteamRep Friend Community.

    I realize that's a little harsh, and may come off as elitist, but learning from historical mistakes in our own growth we're still suffering from from today, we talk about why here.
    This is not to suggest that you at DiscordRep are in fact using SteamRep as a stepping stone, but if you depend on us to establish yourselves, then your community was not going to thrive either way, and our endorsement won't help. Onboarding and training new communities who seek to become partners (which I'm sure was in your long-term plans) takes time and resources from our staff. We are still cleaning up messes from other communities who disappeared overnight without telling us (often taking evidence with them) back when we were more lenient on this, so to protect our limited resources moving forward, we had to set a minimum bar to entry.
    Sniper Pro likes this.