Very cool, thank you for sharing! I'm wondering which size of image it's able to get? In my experience, Tumblr's official archive is able to get the original images, which are hard to get otherwise (https://github.com/cebtenzzre/tumblr-utils/issues/24). Also, JSON would be very useful as an export format if possible! ^^
Thanks so much for the kind words! 😊
TumblBee is designed to always grab the original version of any media that’s passed to it. In newer posts, these original-size media are marked with has_original_dimensions: true, but this field is absent on posts made before the rollout of NPF and the new API (2018). To get around this, I’ve chosen to instead grab the first media file provided for any given block. Since media sizes are returned in descending order, in my testing, this always returns the original media file. If you should see anything different in your testing, though, please do report it as a bug so I can look into it.
JSON format is a great suggestion—thank you! I’ll see about getting that added sometime in the next few days!
Just to make sure I’m developing with the right use case in mind, can you tell me a little bit more about how you’d like to use a JSON export? Are you hoping for something that exports in Tumblr’s own JSON format, totally unmodified (so TumblBee just serves as a friendlier front end for the API), or would you like to see a modified JSON output with some content processing done, closer to what you’d get from the Markdown or HTML exports? Any details you can provide would be a big help! 💕
I'm so sorry for missing this! I didn't have email notifications for replies on. T_T I guess I'm thinking of something that could easily be processed later into HTML? As long as all the info is preserved in a useful way, I could hack something around it for my purposes!
Thanks again for making this, and for your reply above about the image sizes, I didn't know some of that!