Bring back our selfbots!

Non pianificato


57 commenti

  • Wyatt

    Doubt they'll be bringing back selfbots after situations like and h0nda.

    I'd also rather not let people have full access to all my private channels and everything.

    Why can't just you use regular bots?
    If there's something they can't do you either find another way around or just deal with it.

  • lieuwe_berg

    Access to your private channels?

    The idea we're proposing is that we're able to automate the items the Discord client currently offers. The selfbots would see exactly the same as their respective user.

  • IngwiePhoenix


    I would like to chime in here - and I come at this from a *very* different angle. This one:


    I use Matrix as a means to communicate with all my friends on different networks. So far, I have been using this module in order to bridge together a telegram group and a discord server channel. However, I always need to have Discord open if I want to talk just to a few individual people. I don't need voice calling or stuff like that - but what I do need is a way to reduce the amount of programs I have to keep running in order to talk to my friends.


    Basically, I am using three main systems: A desktop PC (R9 3900X, 2080 TI, 32GB DDR4), a laptop (MacBook A1342, mid 2010, 16GB DDR3 and a GPU that deserves no mention) and a phone (iPhone XR). I plan on switching most of my workloads to vanilla Linux with GNOME 3 as a desktop environment, and using Riot as a means of communicating with all my networks is very, very handy. But not just that - it also just makes more sense.


    Self-bots (aka. puppeted accounts, aka. automated personal accounts, etc...) are one way to make sure that each message sent in Matrix is correctly represented in Discord - and not just in servers, but also in private chats, once selfbots are allowed again. Yes, the Matrix bridge mentioned above _does_ have that feature, but it is against the ToS and thus I do not use it and do not plan to do so. However, I really want to.


    On platforms with way more restrictions, writing a custom client (which is obviously not the official client and thus considered a selfbot) would be a much more sufficient solution and even fix a few other issues. One of them is accessibility. Discord is based on Electron, which is based on Chromium, which exports a rather mixed result of accessibility layers that screen readers and other such devices and software can take advantage of. So, using a third-party application would allow someone to develop an application that is more oriented towards this very feature - and boy you dont know how happy my friends would be =). I myself only need screen magnification, so I am fine. But my blind friends? NVDA can only do so much...let alone Orca.


    Selfbots can be regulated, there can be restrictions, but as long as it is possible to control an actual user account to tap into private messages and all available servers, there is a lot of potential to be used - or rather, wasted, as long as selfbots stay disabled.


    Here is another feature. Secure, private messages. Yes, if you and your pal want to message securely, then just use Matrix or something else instead of Discord. But sometimes, this is not so much an option for a variety of reasons. If two clients send encrypted messages and can thus decrypt them, Discord only gets to log the encrypted bulk, but it is not readable to anyone but the reader and sender - or those holding the keys. This is not something I would suggest, but something that would be made possible with custom clients that are able to take advantage of selfbots: Features that Discord does not provide. At all. And this is just one example - there could be many more things that could be done, but it is the first that came to my mind.


    Electron might be an easy way to write application - but it sucks from a performance standpoint. Literally, it sucks away your memory. Look at how much Discord consumes on memory, and then compare it to a native Telegram client for instance. This is not Discord's fault, but something they have to deal with and accomodate for. All they can do is make the best of it...but there could be better, which I think would be possible through selfbots + custom clients. For accessibility, for less-powerful systems and for adding features that may be easily implemented on the client side. There is a reason stuff like BetterDiscord exists, after all.


    I know, this went kinda long but I just *had* to chime in here. This is important to me as I am one of those people that want to centralize communication as much as possible, even if it is across multiple networks - something Matrix does. There are possibly more things that could be done than I could come up with and neither of them would deprecate the official client. Because, it **is** the official client. If a 3rdparty one does not work? Well you can always use the official one, after all.


    Hopefuly something happens in this regard, seeing as the last message was 17 days ago. I am hoping for the best and wish you a great day. ^.^

  • Code Disease Dev

    if this ever does get allowed maybe put a self bot badge next to the self bots username!

  • Discordian

    Hello, I'm also a Matrix user. If Discord would allow self-bots, I could very easily allow my Discord friends to get ahold of me, without having to now add/message another account. I'm not sure how many friends I have, but it looks like it's over 1000, and I don't know how I'd even tell them all about the new bot, without self-botting.

    For anyone unfamiliar with puppet accounts, they're very nice. On Matrix every single Discord user just looks like they're in Matrix as a regular Matrix user, and on Discord a bot makes itself look like the Matrix user it's puppeting, so the chat /history makes it look it it's just a bunch of Discord users talking to eachother (icons and all).

    I don't see why I can't just flag myself as a bot. Restrict me from interacting with other bots, like current bots seem to be, problem solved.


    I'd also like to note that I wouldn't have left Discord if they hadn't dropped Linux support. It's annoying.

  • JackTEK

    Rather than allowing any old Nitro user to create self-bots, how about Verified Bot Developers instead? Let's be honest, no bad actor is going to go through the lengthy process of verification (and adding it into 100 placeholder servers doesn't work either), so this is a better alternative in my opinion. It gives Discord peace of mind at least.

    I doubt I'd ever have any need for a self-bot, but other users seem to have some pretty valid reasons for wanting self-bots to come back. Just an idea.

  • Bricklou

    Personnaly I would like that selfbot come back with a dedicated API because currently I am playing with an arduino with wifi support to do an IoT lamp. It would be awesome if I can show on this lamp a notification about if someone ping me or DM me.

    I know that was some problems before with selfbot but if you want more control and less problem you will need to have an API just for that.


    A lot of peoples would like to be able to get data from their account programmaticly to do projects like mine.

  • SuperGDPro3

    I say make it that self-bots can only send messages once every 5 seconds.

    Also, if a self-bot says a certain message over and over again, terminate the account.

    However allow it for:

    • Embeds
    • Custom Rich Presence
    • Commands
    • Other positive stuff :)
  • Lemon

    Well, I was abused by someone (self-bot spam), but I agree with this, self-bots have a lot of potential :), take the right measures!

  • TheCloaker

    I think that discord should add back self bots they are a lot of fun to use and very handy in some ways now to address the "Huge" security issue their can me very easy ways to patch the issue, also I might add that for everytime their is a force stopping something their we be something to fight back their are still people self-boting even though it is against the rules and it is undetected! so I think just building a self-bot api beside the existing bot api will be amazing for the geeky community and the guy that created this thread has ALOT of very good points like the way for server owners to disable the feature :D I do hope that you guys that discord reopen this fun rabbit hole.

  • Bobby(buizel)#3313

    I see no reason bringing back Discord selfbot they are used for malicious intent

  • alistair

    My two cents...

    Allow for things like selfbotted messages and embeds (presences can already be done programatically) with an exclusive selfbot API with marginally higher rate limits. Additionally, allow for servers and users dms to disable the API if they don't want selfbots there. Finally, on every message sent programatically, place a minute border to the left or something visually indicating that the message was not sent my a human – making it easier for others and yourself to distinguish between the different messages.

  • cmppc

    the only reason why i need self bot is for being able to include discord in my app. i use my rpi for controlling my led and i already include the facebook api so i can acess my msg when gaming. dx12 dont like shift tab or some game like league of legend, metal gear survive, conan exile you need to disable all overlay. so discord become useless if i cannot access with overlay and shift tab 


  • Willow

    Option 2. I think selfbots were a great way for younger users to learn how to use the API. We should be able to use them without paying, and we should see about hiring a team of people to moderate. I think a selfbot mode in the server would be excellent.

  • bruhmoment

    You can keep bumping this all you want they prob wont bring it back lmao. im not agaist self bots but yk thats there choice

  • keyChan_

    We really need 'em back. they were so helpful. 

  • Nan0Scho1ar

    I doubt this decision will ever be reversed. Handing over your credentials to random 3rd party tools puts the average user at risk. It's also very difficult to moderate misuse. Advanced users are not the target demographic of this platform. It's designed to be a simple foolproof way for people to communicate. Some more advanced features can be implemented through bots, but if you want full control over your experience you should probably just use a different platform which is specifically designed to cater to that type of user. If you have the technical capability to set up a self bot, you should also be able to simulate your presence in a different service in using a discord bot and/or webhooks. If it's not enough of an issue for you to go to those lengths, then you are probably closer to understanding why trying to find some middle ground for self bots which can't be abused is probably low on the list of priorities.

  • YodaLightsabr

    Discord’s ban on Self Bots doesn’t stop people from using it maliciously. I mean, it prevents us good people from using them, but bad people will still use them regardless. As other people have mentioned, I think Discord should do 1 of 3 things:

    1) Allow self bots for nitro users
    This way people will have to pay for it, and you can’t do it if you don’t pay

    2) Allow self bots for users that created a verified bot
    I can’t say verified bot developer anymore because the badge is done for new users (I disagree with that descision, but that’s another story ), but you should allow people with verified bots to do it. This way people who know what they are doing and have good intents can use it

    3) Make a different form of authorization
    Many people have suggested a new Discord API for self bots, but that’s not going to happen. Instead, maybe if users add the “selfbof” keyword before their authorization when using the API, it can be the same structure and same system, but with stricter rate limits and whatever other backend changes Discord wants.

  • YodaLightsabr


    Who would be stupid enough to do that? Before they were banned, I would only use it for my personal things, not handing it over.

  • lieuwe_berg


    2) Allow self bots for users that created a verified bot

    Requirements for verified bots are way too low so this would not be a good option. Personally I think option 3 would be best, but I could see that that'd incur a lot of people using the regular user api instead. The issue remains that it's hard to moderate.

  • zelda

    only for nitro is the part I disagree with the most. Making discord more and more a paid thing isn't good for free users. is a good example of this.

    Also sounds like over-complication in settings, more features that are simply not really needed

  • jean_ravenclaw

    I want to make a selfbot - not for making my user into a 'bot', but to be able to use my discord from a third-party app, like VScode or some other thing. Sometimes I like being able to access discord from other platforms and being able to chat from other apps. Would be really nice.

  • wumpus

    sounds cool but i dont think it will happen, maybe users could set their account to "selfbot account" so that then they get ratelimit and cant join servers who disallow self bots, but then again self bots are just a huge risk and its better just to keep them against the tos

  • Chris.

    I agree that self bots should be allowed. Removing the ban on self bots will not allow people to raid any more than they already are. Raiding is already against Terms of Service, and you can still self bot, even though you're not allowed to. The only people they are preventing from using self bots are the people who abide by Terms of Service and who would do it responsibly.

    Self bots could be used for things like setting up auto-responses in Direct Messages, custom commands, where you're sending one thing through the Desktop client and have the self bot automatically edit it for you to say what you actually want it to say (e.g. !w will automatically be edited to "Welcome!" or another message of the programmers choice), or setting a custom status based on their calendar to reflect whether they are busy or not. There are endless of creative use cases for self bots. I would personally use it with a pressure sensor to set my status to "Idle" when I'm not by my computer.

    Self bots are not inherently a technological security risk, neither for the developer nor Discord.

  • Dolfies

    That sums up my argument perfectly. People using selfbots maliciously are already breaking ToS. They don't care about breaking it more.

    They'll just make new accounts.

    The only people this affects is regular people that abide by the ToS.

  • /Nexus_Prime>

    My self-bot is secured, for automations not for raid. But, the peoples hate me when know that i use self-bot in my account..

    But self-bots are so cool.....

  • Rixy

    I agree to bring back selfbots, but with restricted special API.

    But sadly Discord is a company, and when a company decides something, we can't change it back, even if we are millions to say that...

    Discord banned selfbots, and that's it.

    If you want to make one/use one, do it (at you own risk; you can get banned), but if you don't want to get your account banned, don't do that.

    It might be fun to use one, but with the present risks, I, personally, don't think it's worth it to use a selfbot.

    Bots literally replaced selfbots; you can do basically everything a member can do, with restricted things, maybe, but it's still worth it (if you know programming).
    Selfbots are just dead, just move on and, i know this is sad, forget about selfbots.

    Discord will never add them back.


Accedi per aggiungere un commento.