Not sure this has a better solution

So I’ve trying to step up my reccing game. It shouldn’t be hard since I’m almost starting from scratch; I didn’t manage to consistently update the blog I made for it, but it’s kind of more complex than I’d like.

The whole idea behind using for this was to automate as much as possible, as well as to get into using Markdown more.

First I used IFTTT to scrape a specific tag on my Pinboard account. but I ran then into the same issue I’m running into now: IFTTT can only append a .txt file on Dropbox. And wants .md files.

What I used to do was to try and once a week go and manually grab all the automatically scraped / formatted markdown from the .txt file that IFTTT had updated and Copy-paste this in an .md file that would recognize as a post. But it grew tedious; I forgot; it wasn’t the solution I wanted.

Right now I’m leaning towards using the ready-made HTML markup that AO3 generates with its Share button, and I was looking into finally learning how to use Quicksilver to append text to a file (say, a file to feed, but again I ran into that problem: an .md file IS a plain text file but Quicksilver only reads files with the extensions txt, .rtf, .rtfd, .doc and .TEXT

Siiiiigh. I’m now contemplating using Hazel to watch over a given .txt file and make a copy of it with the .md extension every time I update it; I think it would work, but how clumsy is that? Ugh.

Meanwhile, prodding at this issue also made me realize that another problem arising from the AO3 not having media-type differentiation (yet) and metadata-specificity is that the Share button for a podfic post doesn’t give any indication as to the author of the fic, which means I have to add it in myself even when trying to automate – it might not seem like a big deal but it can easily become a barrier to casual/rapid reccing, imo.

Comments are closed.