search

discord-net / Discord.Net

An unofficial .Net wrapper for the Discord API (https://discord.com/)
https://discordnet.dev
MIT License
3.29k stars 743 forks source link

Deprecation Warning: User Accounts (2.x) #827

Closed foxbot closed 5 years ago

foxbot commented 6 years ago

This is an early warning that user tokens will no longer be supported under the primary library distribution starting in Discord.Net 2.0.

As we approach the development cycle for the next major version, 3.0, an alternative for users that wish to continue using user tokens may be provided - but this will not be a first-class feature of Discord.Net moving forward.

Starting in Discord.Net 2.0, user tokens will be marked as deprecated, and we will formally stop providing support for user logins. As a side-effect of this, we would like to warn users against using user tokens, including selfbots.

Discord's official stance against selfbots is vague, but there are certain methods that we would advise against using from your selfbot, if you must use a selfbot:

As of November 2017, selfbots are not allowed, at all. See Discord Support for the official stance. As such, you should not use selfbots or userbots. The following methods are known to trigger red-flags on your account if you use them from a userbot or selfbot:

Using these methods may result in your account being unverified, flagged as spam, or deleted for violating Discord's Terms of Service.

Blizzardo1 commented 6 years ago

If I may be honest, this option was a really great idea, as it allowed me to do extra things with discord. I guess they don't want us modding for our own benefit...

foxbot commented 6 years ago

After further consideration, we have decided to remove support for user tokens starting in the next major version, 2.0.

This change may be tracked on #958.

GreemDev commented 6 years ago

@Blizzardo1 agreed. I wanted to setup a Server Count program for my user account, but I can't now.

Still34 commented 6 years ago

This is not up to the developers of the API wrapper to decide. Discord has made it clear that it violates the API Terms of Service. Deprecating the TokenType is the right move.

GreemDev commented 6 years ago

@Still34 yeah, I know that. I'm just stating it

HurricanKai commented 5 years ago

Selfbotting, to quite a big extend coud be done using the RPC api. it contains all the commonly needed features, and is explicitly connected to the Discord Client itself.

GreemDev commented 5 years ago

@HurricanKai yeah, it can. i've seen it done before.

L4BORG commented 5 years ago

Quick question are there any alternatives? In C#?

We're only running a few selfbots as dummy accounts to catch spammers (as they would usually PM everyone on channel starting top down) and autoban them, it still works with old Discord.net but I'm kinda worried things will break in near future. Any ideas?

Thanks!

Still34 commented 5 years ago

It is already deprecated, and as mentioned previously, selfbot is strictly prohibited according to the developer terms of service regardless of the goal.

HurricanKai commented 5 years ago

An alternative, as I mentioned above, is to run an application that would get tokens from those users which you control using selfbotting right now. Using those tokens the Direct Messages can also be read, and your system could work without breaking the ToS. @L4BORG

REVENGE977 commented 4 years ago

any method to bypass this error ?!

GreemDev commented 4 years ago

any method to bypass this error ?!

Why do people insist on breaking Terms of Service? You can't drink and drive for a reason

CamK06 commented 4 years ago

any method to bypass this error ?!

Why do people insist on breaking Terms of Service? You can't drink and drive for a reason

Because people don't give a shit about their bullshit terms of service. I get that they don't want selfbots because they can be used maliciously but adding that to TOS doesn't and hasn't changed anything as it is still very easy to make one by using older versions of libraries and if someone is looking to do something maliciously, of course they're not gonna follow the TOS. By disallowing selfbots as a whole instead of maybe just stating that they are to be used non-maliciously (though that's as redundant as banning them altogether) they are really blocking a lot of opportunities for people to make useful things for themselves that are not malicious but actually serve a purpose. One example of this would be getting various statistics for whatever reason. As you cannot add bot users to any other server it is very nice to be able to use your own account to just grab some numbers

AntiTcb commented 4 years ago

any method to bypass this error ?!

Why do people insist on breaking Terms of Service? You can't drink and drive for a reason

Because people don't give a shit about their bullshit terms of service. I get that they don't want selfbots because they can be used maliciously but adding that to TOS doesn't and hasn't changed anything as it is still very easy to make one by using older versions of libraries and if someone is looking to do something maliciously, of course they're not gonna follow the TOS. By disallowing selfbots as a whole instead of maybe just stating that they are to be used non-maliciously (though that's as redundant as banning them altogether) they are really blocking a lot of opportunities for people to make useful things for themselves that are not malicious but actually serve a purpose. One example of this would be getting various statistics for whatever reason. As you cannot add bot users to any other server it is very nice to be able to use your own account to just grab some numbers

Cool story.

This library's going to go ahead and comply with the ToS though.