Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Site support request: yaplog.jp & blog.livedoor.jp #190

Closed
schleifen opened this issue Mar 14, 2019 · 0 comments
Closed

Site support request: yaplog.jp & blog.livedoor.jp #190

schleifen opened this issue Mar 14, 2019 · 0 comments
Labels
site:support

Comments

@schleifen
Copy link

Hello,
It would be great to be able to download images from these blog websites too.

Here are the related links:
https://yaplog.jp/
https://yaplog.jp/*blogname*
https://yaplog.jp/*blogname*/archive/
https://yaplog.jp/*blogname*/image/

http://blog.livedoor.jp/*blogname*
http://livedoor.blogimg.jp/*blogname*/imgs
mikf added a commit that referenced this issue Apr 4, 2019
@mikf
[yaplog] add user- and post-extractors (#190)
2ff043e
mikf added a commit that referenced this issue Apr 6, 2019
@mikf
[yaplog] fix archive_id and posts with more than 24 images
13526f3 
- 'post_id' and 'image_id' are only unique per user
- /image/ pages only show a maximum of 24 images, but there can be more
  images than that in a blog post
- let extraction run in its own thread and maybe improve speed
- #190
mikf added a commit that referenced this issue Apr 6, 2019
@mikf
[livedoor] add blog- and post-extractors (#190)
35919a9
mikf added a commit that referenced this issue Apr 6, 2019
@mikf
[yaplog] update metadata structure (#190)
2c32dc7 
Put all blog post related fields in its own dict.

'image_id' -> 'id'
'post_id'  -> 'post[id]'
'title'    -> 'post[title]'
etc ...
@mikf mikf closed this as completed Apr 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
site:support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikf @schleifen