-
Notifications
You must be signed in to change notification settings - Fork 6
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
feature: use custom avatar from wechat per msg #2
Comments
partially implement: #2 also add aiohttp as dep due to async slack client
TBD:
|
Disagree with introducing extra dependencies. I will try a serverless solution that generates the image URLs from the base64 data. Something like:
|
ok, this..., to put image in URL/base64 blew my mind 🤯!!!! It's totally next level🧎🏻... |
Indeed it has been worked out with CF worker(yeah, THANKS TO ChatGPT), try visiting this URL. I am currently stuck by not able to get the contact avatar.. P.S. the API spec is:
|
Aha, my regular expression was written by ChatGPT, too :P It worked like a charm! I am not familiar with the price model of CF worker, as it will require CF's edge computing resource to decode and respond with those small images, will this be scaling to anyone? (that is, we can place your single CF-worker-based endpoint by default to expect it will work for long? or do we need users to setup their own avatar base64 ping-pong service same as yours? |
Reported to wechaty: wechaty/python-wechaty#381 |
Oh, I encountered this, too, this is hard as python lib is just a wrapper and the gateway is the major part(hard for me to debug) :( anyway, I will look into it later, too, I have to prepare for the slides of tomorrow now 🤦🏻♀️. |
Indeed, but the error message |
@frostming If the |
I came up with an EVIL approach to fix the issue in a DIRTY way, let me check. |
Wow, this sounds neat...😏 |
A avatar cache should be built to custom msg sender's profile image.
support upload avatar to object storage with URL and pass to slack(seems to be the only way to specify avatar)The text was updated successfully, but these errors were encountered: