Fortunately, the discovery of the publicly available tumblr API allowed me to solve this problem. Still, requesting post info from there requires having the post ID and currently it has to be collected from the page anyway, involving searching for the post container regardless of different and often faulty designs (just how many times have I seen id attributes being used as classes?). Sometimes the post contents and post meta are in two different containers with separate parent nodes, which further complicates the search. Perhaps I should come up with something even more independent from local designs; something that would figure out which series of post the user is currently viewing and request info from API with the appropriate offset and post amount. I don't really know how to do that now, the address bar contains current page number relative to start, but every tumblr might have individual amount of posts per page, and in case of dashboard it's not applicable at all.
0 commit comments