Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable UOS by default and enable by WECHATY_PUPPET_WECHAT_UOS=true #193

Closed
hxianseng opened this issue Jan 2, 2022 · 4 comments
Closed

Comments

@hxianseng
Copy link

Now the UOS protocol cannot log in

@huan
Copy link
Member

huan commented Jan 3, 2022

If we can confirm the UOS has problems and the original web protocol will be better, then we can use a options & environment variable to enable UOS, and disable UOS by default.

For example, the following names will be preferred:

  1. WECHATY_PUPPET_WECHAT_UOS=true for the shell environment variable
  2. options.uos = true for the puppet option.

I'd like to accept a PR based on that.

@huan huan added question Further information is requested pull request is welcome labels Jan 3, 2022
@henrycoding
Copy link

现在大多数web都封了

@hxianseng
Copy link
Author

@ @

如果我们能确认UOS有问题,原来的web协议会更好,那么我们可以使用options&环境变量来开启UOS,默认关闭UOS。

例如,以下名称将是首选:

  1. WECHATY_PUPPET_WECHAT_UOS=true 对于 shell 环境变量
  2. options.uos = true 对于人偶选项。

我想接受基于此的 PR。

This technology is used for the first time. How to turn off the UOS protocol

@huan
Copy link
Member

huan commented Jan 14, 2022

This feature has been implemented by @pacoyang, thank you very much!

@huan huan closed this as completed Jan 14, 2022
@huan huan removed the question Further information is requested label Jan 14, 2022
@huan huan changed the title Can we get rid of UOS and use the original web protocol Disable UOS by default and enable by WECHATY_PUPPET_WECHAT_UOS=true Jan 16, 2022
huan added a commit to wechaty/getting-started that referenced this issue Jan 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants