feature request: move images to atom enclosures #3
Comments
sure! worth considering. looks like we also investigated this somewhat thoroughly a bit ago in snarfed/granary#113. |
interesting, just found another alternative, at least for single photo/video posts: they could be the top-level content, e.g. no idea how reader support for this is. probably even worse than for image enclosures...which is already the main reason i'm reluctant here. :/ |
fixes #120...but by dropping the <img> *outside* content, not the one inside as requested. that may still be the right long term answer, but right now it's reused as atom content, and we're still debating whether we want to move that to an enclosure in #113 and snarfed/instagram-atom#3. reader support seems unclear at best.
Hi, the instagram-atom is great. FYI, I added the instagram-atom feed to Feed Burner. I've also use an IFTTT applet to post my instagram feed toa private twitter account - so I can have my Instagram in my Twitter :). Has there been a recent change to the instagram-atom tool? |
thanks for reporting, @Nick-Shannon! looks like there was a minor Atom validation error. i've fixed it and pushed the update. let me know if your feed is happy now! or if not, please post the specific error you're seeing and any other details. |
Thanks @snarfed. Feed is back to normal! Thanks for the rapid fix. |
done in snarfed/granary@92341ea. feel free to try @aaronpk! |
I'd love to see the instagram photos added as atom enclosures rather than being embedded in the HTML. When I run an instagram-atom feed through XRay to convert it to the jf2 format used by my new reader, right now the images just appear in the embedded HTML. Ideally they'd show up in XRay's
photo
property, but I can only do that if they're marked as atom enclosures. Maybe this could be a query string parameter to change the behavior since I know some feed readers won't support that attachment very well.The text was updated successfully, but these errors were encountered: