https://github.com/knightchaser/keyzardbuster
For who dislike registering every post one by one. (Inspired from megabuster that bursts mega.nz.)
https://github.com/knightchaser/keyzardbuster
Last synced: about 2 months ago
JSON representation
For who dislike registering every post one by one. (Inspired from megabuster that bursts mega.nz.)
- Host: GitHub
- URL: https://github.com/knightchaser/keyzardbuster
- Owner: KnightChaser
- Created: 2023-07-24T11:03:38.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-07-28T08:33:08.000Z (almost 3 years ago)
- Last Synced: 2025-06-24T08:03:30.279Z (12 months ago)
- Language: Python
- Homepage:
- Size: 9.77 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# KeyzardBuster (For `blog.naver.com` users)
1. Execute `get_blog_post_urls.py` to extract every URL of posts in your blog.
2. After step `1`, execute `auto_register.py` to automatically register your blog post to kzd's Google registering service.
This code may be unstable because it hasn't been tested enough. However, it seems to be operating normally in usual usage. Please feel free to leave any issues whenever you find something to be fixed or improved.
#### Future improvements (probably)
`auto_register.py`: My method is based on the assumption that every registering process would be okay(not blocked by the security system) unless this script works so fast that the administrator would consider this spam. However, it'd be better to handle the alert message indirectly - by checking the result response after registering. Officially, the `Selenium` package in Python3 doesn't support getting and utilizing responses from websites like `requests`. Based on my simple research, I checked every process can be conducted statically. So I'd like to switch my method to use `requests` in the future.