两个提议
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.3k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
1,group uid直接获取已经被wxc5s23sc.js用实时key加密了，用wxBot类从contact中暴力获取@@，已经取不到为空。不妨伪造群消息获取最新的group uid，这样按需获取容易避开微信风控，否则容易被CD。
2,个人给群发消息不妨归为msg_type_id===3，但是紧接着碰到这段疑问
sp = content.find('
')
uid = content[:sp]
content = content[sp:]
content = content.replace('
', '')
区别在于：
其他人给群发消息
u'Content': u'@d85a4205309f32ed50d562b80215cd98140a613ee59ccfd92cc2b14b947912a6:
oo',
自己给给群发消息
u'Content': u'Cv',
但为了甄别真正的消息源，可以再考虑复用这种情况下的
u'FromUserName': u'@069b65f4ceaba06ed3ff75663da82b7bb5e266c0d86053548cf03bc64b867f3c',
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the wxBot class and the referenced wxc5s23sc.js behavior, then trace how contact data, group UIDs, msg_type_id, content, and FromUserName are parsed. The issue proposes alternative group-UID retrieval and sender handling but does not define acceptance criteria; confirm the intended behavior and test coverage before estimating completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100