The media in this post is not displayed to visitors. To view it, please go to the original post.
Out of curiosity, I requested my #data from #Pinterest. I think I’ve used it fewer than 10x in 10+ years and have restricted as much personal info as possible and/or lied to them (I look pretty good for being 116yo, no?), but I was curious anyway. Not a lot of identifiable info in there at first glance, honestly.
What is interesting though was the “Pins” folder. I’d started using #Mealie recently and adding #recipes, but quickly realized it was a slow-moving nightmare pulling urls out of Pinterest to add 1 at a time to Mealie. Turned out to be a blessing because I’d rather Mealie be a collection of recipes we’ve tried and liked rather than a massive hole of links like Pinterest, but I digress.
The point is, if you request your Pinterest data, you get a zip file, inside of which is a “Pins” folder that contains html files with all your pins in what looks to be an underlying .json - including the ‘canonical link’ to the original pin source. That’s exactly what you’d need to build your Mealie library. A savvy user could scrape these urls from the html files and queue them for upload and review in Mealie… or say, a #decentralized #fediverse Pinterest alternative (cough cough @dansup ) 🤔
