Allow bot users to access connected user accounts of guild members

Комментарии

Комментариев: 7

  • Thunder33345
    while it could open up to abuses(forcing sub to use this chat) and scraping data i think it should be a thing, maybe with permission of users?
    1
    Действия с комментариями Постоянная ссылка
  • tt2468

    That could work. The main factor is that since bots are added through the manage server permission, it would restrict server members from collecting the data. There could also be a permission that allows/disallows said bot to be able to access the deeper regions of the api. Or even a good option would be to add a switch to the privacy options that would allow the user to be able to change whether their account connections could be seen by bots in a specific server. It would be opt-in of course, but there could also be a setting in the privacy section to enable connections access by default (change to opt-out).

    Telling users to change a setting within Discord is a lot easier to do than to direct them to some page where they have to sign in through discord and another account.

    1
    Действия с комментариями Постоянная ссылка
  • MagSynchro (Convertible Turtle)

    I feel that this function is already exposed somewhere.

    My reasoning is Nightbot.tv is able to sync YouTube accounts on a YouTube channel with Discord roles.

    Example:

    I have a YouTube channel. I have multiple users that are moderators.
    I have a Discord with multiple users that are Moderators.l

    I add Nightbot.tv to both my Discord and YouTube. I set my moderator role on Discord.

    Nightbot magically finds those users who have YouTube accounts that are flagged as moderators on my channel that are on my Discord with linked accounts.

    At no point in this process have the users made any additional actions on their part.

    0
    Действия с комментариями Постоянная ссылка
  • NoNameNamer

    @MagSynchro because nightbot is definitely using the bot scope for all automation. Kappa

    1
    Действия с комментариями Постоянная ссылка
  • Lachee

    There is a reason why you need a separate oAuth2 scope to get connections. Bots shouldn't be given this information, its unnecessary and can lead to privacy concerns. Its one thing for users to be able to see your connected accounts but being able to automate that can lead to bots that data-scrape connections and automated doxxing.

    -2
    Действия с комментариями Постоянная ссылка
  • kgns

    Majority of discord servers are communities formed around third party connections (like Steam or Twitch or Youtube etc.). Without these connections, integrations, Discord would be a dull communication client not much different than TeamSpeak or even Ventrilo. Every community would benefit from being able to use bots of their own accessing these user connection data, and automate a lot of new processes. Disallowing bots from accessing these connections is just outright funny in the age of informatics.

    For privacy issues, Discord can just add a new option that must be activated per server by the user to allow bots in that server to access its selected connections data. By default this can be disabled, which would emulate as is right now. Where as you can enable bots in X server to access your Twitch connection data.

    At its current state, Discord is denying the choice of sharing your connection data with bots even if you wanted to.

    2
    Действия с комментариями Постоянная ссылка
  • DingleFlop

    I completely agree... You can already automate this to abuse it using selfbots... It's only the people that are writing legit bots that are harmed by this restriction.

    0
    Действия с комментариями Постоянная ссылка

Войдите в службу, чтобы оставить комментарий.