# Discord 的 Discourse 信任等级

**URL:** <https://meta.discourse.org/t/discourse-trust-levels-for-discord/108232>\
**Category:** Development\
**Created:** [2019 年2 月 3 日 06:05 UTC](https://meta.discourse.org/t/discourse-trust-levels-for-discord/108232 "2019-02-03T06:05:26Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

作者： ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
发布日期： [2019 年6 月 25 日 21:24 UTC](https://meta.discourse.org/t/discourse-trust-levels-for-discord/108232/54 "2019-06-25T21:24:11Z")

</div>

> [@Falco](#):
>
> Use our [Discord Oauth2 Plugin](https://meta.discourse.org/t/discord-oauth2-plugin/67174) for login.
> 
> It receives the correct, authenticated Discord user ID.
> 
> Check if it stores it, if not creat a PR to store it.
> 
> Then you have the Discord Data for every user to use during sync.

Perfect advice 👍

Heads up (and @featheredtoast) I’m working on a PR for this plugin to

- change the class inheritance up a level to `Auth::ManagedAuthenticator` to
  - leverage the richer functionality to simplify the plugin
  - bring the implementation in line with Facebook and Google OAuth (storing additional info in `user_associated_accounts`)

- store the user ID to facilitate my next step … 😉

UPDATE: [Submitted](https://meta.discourse.org/t/discord-oauth2-plugin/67174/55)

---

_[View the full topic](https://meta.discourse.org/t/discourse-trust-levels-for-discord/108232)._
