Bring back our selfbots!

未計画

コメント

45件のコメント

  • Hyper

    Saying "No" won't stop people from using selfbots, so I think it would be a great idea to introduce a new API, or a better version of the current ones, that make selfbots less of a nuisance and more of a tool, or a bit of fun. As it stands, discord isn't just a "chat app for gamers" anymore. It's a place to hang out and make new friends, or show off your skills. programming is an extremely rewarding passtime and selfbots are interesting to work on, and its easier to show people what you've done, or help other people if you can run a self bot. Sorry for rant but selfbots are really neat

    tl;dr Stop ignoring the community discord. you see how many upvotes this has

    50
    コメントアクション Permalink
  • ToS

    I disagree with SuperSajuuk Selfbots are just not controlled yes they basicly bypass it but Selfbots can be useful, you just have to controlle its usage!

    23
    コメントアクション Permalink
  • lieuwe_berg

    Agreed.

    1) Special, heavily ratelimited API
    2) Option in server settings
    3) Disallow fetchMessages, fetchUsers

    22
    コメントアクション Permalink
  • Ralf

    Just make sure that other people/bots can easily detect use of selfbots, okay?

    80% of selfbots are used to bypass some protection of other bots and services.

    17
    コメントアクション Permalink
  • ! lul

    Selfbots can be very useful in some cases please discord bring them back

    14
    コメントアクション Permalink
  • FRNathan13

    Upvote! We need selbots again... Just deny some API endpoints like guild ban, etc, or create different user agent for handling selfbot requests, or different scope, example: in bots we use request header `Authorization: Bot DISCORD-BOT-TOKEN` they can add `Authorization: Self-Bot DISCORD-USER-TOKEN`.

    11
    コメントアクション Permalink
  • Greem

    I kinda miss my selfbot. It was very risky, and I don't use it anymore. But I loved the ability to embed content, and even find out what guild an emote was from.

    If this comes back, that'd be cool. If not, whatever. I do see why Discord doesn't like them in the first place, because it's automating user accounts which is why they made bot accounts in the first place.

    10
    コメントアクション Permalink
  • PiggyPlex

    If people want to use selfbots maliciously, they are already able to. If users want to make malicious selfbots, the API is already there. There will always be malicious users, but they shouldn't stop others.

    Also, what about adding a Selfbot API, and a way of detecting selfbots through the API (would be useful for bots; they can ban selfbots in servers who don't want any selfbots at all).

    10
    コメントアクション Permalink
  • rico᠖᠖᠖

    It's mid-2019. I have made a self-bot and I intend to keep using it and here's why:

    • When creating it, I wasn't aware there being a "ban on self-bots". I started simply from 0/scratch, because in the programming language I use, there was no discord bot code available at all.
    • The bot is in development, as is my knowledge of the Discord-API. Right now I simply do not know yet how to achieve some features (DM talking, list of DM connections) with the "normal bot" API.
    • The bot lives only on my server and it will probably never live on any other server and most certainly not without the server masters knowledge / agreement.
    • The bot does none of the nefarious things I read about like scanning and storing history, spamming and similar. In fact, if you want something from the bot, you have to DM it.

    So, assuming at Discord work some people who kept flexible thinking and common sense, I will assume - for the time being - that my little evolving self-bot is safe from being slashed.

    • I may use the regular bot API some day, because real time, bi-directional websocket yadda yadda sounds really nice than the more primitive ASYNC pull/push I am doing right now, but I would like to develop at my own pace.

     

    Because this is my first writeup here, I need to take the opportunity and would like to thank the whole Discord Team for Discord.

    Thank you.

    9
    コメントアクション Permalink
  • FRNathan13

    And i don't agree with "nitro users only" stop making discord pay 2 win jesus.

    7
    コメントアクション Permalink
  • Soheab_

    Lol you saying it like it’s not possible anymore.. it is still possible the api supports it even.. but they just saying “don’t do it”

    7
    コメントアクション Permalink
  • lieuwe_berg

    Such rebel.

    Anyways, one of the biggest reasons I think most people want selfbots is because they want to expand the possibilities of their user account. It'd be so dang useful to be able to easily make calls to certain api's without having to have a bot hosted somewhere. Also polls, giveaways, quizzes, even -- everything small you have a bot for can easily be made into a selfbot to provide a clean and better approach at utilising all of Discord's features.

    As I said before, Discord can easily limit certain things (such as spamming). It could be made that only the account owner can use it (not only owner messages come through, but it can only respond (usually edit or add a reaction) to the owner's message. i.e. it can't manipulate others' messages), the selfbot cannot create its own messages, read history, etc.

    There could be a few options in the server settings:

    1. Allow self bots (general, would make the rest unusable if false)
    2. Receive other messages (only give the selfbot the owner's messages if set to false)
    3. ...

     

    Selfbots could be hosted much like normal bots, but due to them having a limited api you should be able to somehow maybe select a local folder where your selfbot is located. You also enter a command to start it and Discord runs the selfbot much like a normal bot, but in the background. I have no idea how it was done before, I wasn't there yet back then.

    7
    コメントアクション Permalink
  • ScriptKitty

    Would be nice if there were an alternative API which allowed registering commands in the discord client to do simple stuff on behalf of the user with its own set of permissions governed by whatever a guild has chosen.

    6
    コメントアクション Permalink
  • FRNathan13

    Regardless of whether or not the user has nitro subscription, if there is no restriction of the API itself, users with nitro will abuse.

     

    Example: Games that are paid and that have cheaters, they are banned and they buy the game again and this cycle stays.

     

    As I said in my post above, it should have a separate dedicated API for handling selfbot requests (if the discord would like to add again).

    6
    コメントアクション Permalink
  • Rovester

    FRNathan13, don't get me wrong. I'd love to have selfbots back.

    But one way to restrict abuse is to make it nitro users only.

    Nitro users do not want to lose their account (most of them).

    Some kid is not going to waste money for this kind of stuff.

     

    Or you allow us to buy a license to use a selfbot. in the dev section.

    5
    コメントアクション Permalink
  • scorbunny

    I would love to see self bots be brought back they are very useful in a way that normal bots are not

    5
    コメントアクション Permalink
  • IngwiePhoenix

    Hello!

    I would like to chime in here - and I come at this from a *very* different angle. This one: https://matrix.org/docs/projects/bridge/matrix-appservice-discord

     

    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. ^.^

    5
    コメントアクション Permalink
  • FRNathan13

    @PiggyPlex exactly! 

    @sOhEaB_ yes  but discord developers (or whatever) team don't see in this way.

    4
    コメントアクション Permalink
  • lieuwe_berg
    • Things such as capturing custom emotes, etc. etc. become more tedious and annoying, as i need to include other modules I've written into said bots for their own development- on the servers the bot is expected to be on, which sucks.

    Ugh, yes! This is pretty annoying. I keep having to eval stuff, making need for an eval command which is later removed anyways.

    4
    コメントアクション Permalink
  • Mazzy

    I would only want this added with restrictions. Self bots have only ever caused problems in my experience. This would have to be a permission to add, so that if you so choose, only mods, or the owner could do it.

    3
    コメントアクション Permalink
  • 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.

    2
    コメントアクション Permalink
  • 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 :)
    2
    コメントアクション Permalink
  • Noita

    What upsets me is that, as a bot developer- having a self bot with it's own methods kept me from needing to refresh/reload my own bots i'm writing on the servers i'm writing them on- in their own development environment(my development server). Things such as capturing custom emotes, etc. etc. become more tedious and annoying, as i need to include other modules I've written into said bots for their own development- on the servers the bot is expected to be on, which sucks. Where I understand why they are banned, and don't entirely disagree- A blanket ban really hurts those who were using them for positive reasons.

    Where all of this is stated above by people who miss it as a feature, just figured i'd toss in my chips and back how much I miss my self-bot.

     

    Edit- I'd imagine it'd be possible to enable a permission that grants access to "self-bots api channel" on specified servers.

    EG. Users with permission X on server Y may receive api information on the self-bot API channel on server Y. I'm not sure if there is a solution for "illegal" self bots, as i'm not sure how those are tracked I don't work for discord, unfortunately :(, but a permitted channel would be nice for those who would like to use it, i'd imagine? Especially when the permissions are governed in that aspect. Of course self-bot users already can't access information in channels/servers they are restricted from- so this extra flag in my mind follows that architecture, but prevents information on that channel for the bot- as stated above, and if that makes sense.

    Just an idea :) Din't want to just post without submitting one of those as well. I'm sure with enough ideas, features we want can come to the platform, right?

    1
    コメントアクション Permalink
  • HankyFace

    Hi there, 

    If you own a big community and you can't use a selfbot, then you're screwed. People are contacting me just because I'm the owner... 

    0
    コメントアクション Permalink
  • nedmac.exe

    The only reason i want self-bots back, because i want to be able to show online 24/7

    0
    コメントアクション Permalink
  • Anime forever

    Agree, but with limits. Can't DM with selfbot, no loud music, no raids, no exploits and etc.

     

    0
    コメントアクション Permalink
  • Dimensional

    As much as I'm not keen on the idea of having a bot connected to a user's account, it can help out a lot in areas where a normal bot account can't function properly. For instance if you restrict user accounts from changing their nicknames, due to them possibly trying to use profanity, a bot is useful to automate that, but what if you were to use a bot to automate it for a game? The biggest problem with automation of changing a nickname is the bot isn't allowed to change the nickname of the server owner at all. Even if it's given admin privileges, it still can't change the nickname of the owner, so they end up being singled out and left to do it manually for themselves when they might want to have it handled by the bot they trust on their server. So if they had a bot they trusted implicitly, even one they built and host on their own PC or personal server, connected directly to their account, then they'd have everything necessary. Even could have it connect with a standard bot account to ensure a higher level of separation and functionality.

    0
    コメントアクション Permalink
  • Code Disease Dev

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

    0
    コメントアクション Permalink
  • DM Discordian-7736

    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.

    0
    コメントアクション Permalink
  • 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.

    0
    コメントアクション Permalink

サインインしてコメントを残してください。