-
Notifications
You must be signed in to change notification settings - Fork 0
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
User-oriented FAQ for WeChat in uProxy #8
Comments
Want to check on this - last I heard, this module is essentially blocked by server-side changes in wechat. If that is the case, then maybe this issue should be revised to "note that this module is blocked in the main landing README." Thoughts? |
as i understand it, it's not 'blocked', it's just a slightly worse user On Wed, May 11, 2016 at 2:29 PM, soycode [email protected] wrote:
|
Ah yeah, I think I recall the conversation more clearly now, but I also think that uProxy basically considers that a pretty unusable state (since with wechat those messages alert your phone). Do we have any plausible path for fixing that? |
Left this in an issue raised in the uproxy issue, but I'll just copy here for completeness. @soycode, From when I was last looking, Will is right in that it is a usability issue -- the messages can no longer be sent hidden. However, Within the wechat api (last I checked), users don't have to be alerted of messages; i.e. a message can get to a phone, and a user can see the message if they look, but the phone will not vibrate or make any sounds to alert a user that a new/unread message is available in a thread. The current path is to create a separate thread for uproxy's use with your friend, meaning that all uproxy related information will be isolated into a new "contact" where you won't be alerted of any messages passed through there, while keeping a thread between your original contact uncluttered. Some work has been made in order to accomplish this, but hasn't been taken to completion. |
No description provided.
The text was updated successfully, but these errors were encountered: