eric/gitlab-instance-0a899031_douyindmappi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

'ss'

Browse Source
This commit is contained in:
eric
2025-08-01 08:29:21 +08:00
parent 5d3cc0aeed
commit e1fe2caacc
16 changed files with 16403 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

183
README.md
View File

@@ -1,92 +1,109 @@
# douyindmappi
# 抖音网页版弹幕数据抓取
## 声明0：本代码库所有代码均只用于学习研究交流，严禁用于包括但不限于商业谋利、破坏系统、盗取个人信息等不良不法行为，违反此声明使用所产生的一切后果均由违反声明使用者承担。
## 侵权或涉及相关利益请联系作者：[微博](https://weibo.com/u/7751075499)、[B站](https://space.bilibili.com/4690313)、[邮箱](mailto:kukushka@126.com)
> 2024年1月2日
## 声明1：最近发现有人利用这个库的代码到CSDN还有其他博客去引流出售。。如果涉及到一些侵权或者其他利益相关的纠纷，此repo将会停止更新并归档，且行且珍惜。。。再次重申，如果涉及侵权请联系作者删除本库代码，此repo仅仅用于学习交流，交流可提issue明细
> 2024年7月17日
### 环境：
- windows 10
- python 3.7+
- `protoc`版本：`libprotoc 25.1`
- NodeJs v18.2.0
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
## 有效测试：
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
- [x] 2024/11/07 09:04 成功 测试成功,根据[PPG888](https://github.com/PPG888) 提出的[issue#74](https://github.com/saermart/DouyinLiveWebFetcher/issues/74)更新signature获取方式
- [x] 2024/12/01 15:08 成功 测试成功
- [x] 2024/12/11 15:08 成功 测试成功,添加赞赏渠道(thx :)
- [x] 2024/12/17 10:41 成功 测试成功
- [x] 2024/12/22 11:12 成功 测试成功
- [x] 2025/01/03 14:52 成功 测试成功
- [x] 2025/01/27 18:43 成功 测试成功
- [x] 2025/01/28 09:15 成功 测试成功，新年快乐！！
- [x] 2025/02/08 10:45 成功 测试成功
- [x] 2025/03/05 21:22 成功 测试成功
- [x] 2025/03/11 13:14 成功 测试成功
- [x] 2025/03/14 20:52 成功 测试成功
- [x] 2025/03/17 18:38 成功 测试成功
- [x] 2025/04/10 18:20 成功 测试成功
- [x] 2025/04/16 19:41 成功 测试成功
- [x] 2025/04/29 09:15 成功 测试成功
- [x] 2025/05/18 05:29 成功 测试成功
- [x] 2025/06/08 08:40 成功 测试成功
- [x] 2025/06/22 21:09 成功 更新wss，测试成功
- [x] 2025/07/01 19:24 成功 测试成功
- [x] 2025/07/05 21:10 成功 测试成功
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin http://gitlab.yidooplanet.com/gitlab-instance-0a899031/douyindmappi.git
git branch -M main
git push -uf origin main
## 抓取样例：
```text
【进场msg】[79026102598][男]🌈尘埃🌈🌈 进入了直播间
【进场msg】[3548874980203464][男]姚先生 进入了直播间
【进场msg】[2594451873598365][女]王大锤锤锤 进入了直播间
【进场msg】[106602887532][男]嗨！ 进入了直播间
【进场msg】[1082384846973134][男]青泥湖茶食会所 进入了直播间
【进场msg】[94817345810][男]每天都要看妞，只为心情愉悦 进入了直播间
【进场msg】[83021093936][男]和财汽贸 进入了直播间
【进场msg】[106001704984][男]静能生慧 进入了直播间
【进场msg】[70493659812][男]格 局๑҉ 进入了直播间
【进场msg】[76589441190][女]大龙 进入了直播间
【进场msg】[70881184745][男]李浩哲 进入了直播间
【进场msg】[100754703019][男]RussB 进入了直播间
【进场msg】[102074576531][男]瞳可道 进入了直播间
【礼物msg】X L 送出了 为你点亮x1
【进场msg】[6782769126][男]舒克先生 进入了直播间
【进场msg】[59189841620][女]冷瞳 进入了直播间
【进场msg】[72741706046][男]I＇m glad to be part of you 进入了直播间
【点赞msg】小程๑ 点了9个赞
【进场msg】[1543342918217780][男]上班很烦丶 进入了直播间
【点赞msg】山东秋实微耗节能灶 点了12个赞
【进场msg】[70657797444][男]🌈itsDav 进入了直播间
【进场msg】[98472911773][男]真的小狮子 进入了直播间
【进场msg】[69456861335][男]何苦 进入了直播间
【进场msg】[81597830598][男]毣 进入了直播间
【统计msg】当前观看人数: 22164, 累计观看人数: 43.6万
【进场msg】[97729506904][男]流年 进入了直播间
【聊天msg】[67197561586]说谎: 去拿 去拿去哪
【进场msg】[1772006534547923][男]111 进入了直播间
【进场msg】[1437751228776316][女]🌈星辰 进入了直播间
【进场msg】[84994892671][男]浅蓝色的期许 进入了直播间
【聊天msg】[58977458943]🌈烹世酌生: 厕所里有6倍
【礼物msg】X L 送出了 为你点亮x1
【点赞msg】小程๑ 点了11个赞
【点赞msg】山东秋实微耗节能灶 点了1个赞
【进场msg】[2286579209737694][男]🐭🐮🐍🐔 进入了直播间
【进场msg】[60451809684][男]Nine九妹纸 进入了直播间
【进场msg】[84538127235][男]🆑No smoking 进入了直播间
【进场msg】[3984224739660126][男]か大龍貓か 进入了直播间
【进场msg】[77098767219][男]魑魅魍魉 进入了直播间
【进场msg】[25526482899][女]乘风 进入了直播间
【进场msg】[1939189844950083][男]一个疯批帅哥 进入了直播间
【点赞msg】小程๑ 点了9个赞
【进场msg】[71283358628][男]🌈纯黑 进入了直播间
【点赞msg】山东秋实微耗节能灶 点了8个赞
【进场msg】[1559550207732659][女]用户5865026012091 进入了直播间
【礼物msg】🐷囔囔滴男盆友 送出了 粉丝团灯牌x1
【进场msg】[71297253367][男]ꪏꪶꪭꪆꪮ 皮 进入了直播间
【进场msg】[108182840023][男]Time 进入了直播间
【进场msg】[3918302612818491][女]用户4168810991567 进入了直播间
【进场msg】[108698785871][男]万一啊 进入了直播间
【进场msg】[24033588453][男]Intro 进入了直播间
【点赞msg】小程๑ 点了3个赞
【点赞msg】山东秋实微耗节能灶 点了1个赞
【礼物msg】安好． 送出了 入团卡x1
【进场msg】[87369427576][男]失格 进入了直播间
【粉丝团msg】 恭喜 安好． 成为粉丝团第289687名成员
【进场msg】[96183051026][男]王胖子 进入了直播间
【进场msg】[3931489880510067][男]leee 进入了直播间
【统计msg】当前观看人数: 22140, 累计观看人数: 43.6万
【进场msg】[73874992083][男]😦 进入了直播间
```
## Integrate with your tools
- [ ] [Set up project integrations](http://gitlab.yidooplanet.com/gitlab-instance-0a899031/douyindmappi/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
## buy me a coffee
<img src="alipay.jpg" width="400" height="400">