Ello's IFTTT channel is now Then That-ing again.
A few weeks back our Firewall started seeing IFTTT crawler traffic as suspicious. We discovered this is likely because IFTTT traffic actually comes from an old version of Chrome as the user agent, making it look like an automated attack to our Firewall. On top of that, IFTTT doesn't give out IPs to whitelist. We were able to find a workaround in the end, but this is why it took a while.
We'd also made a change on our end as to how html pages render for folks in a common browser, vs search engine bots. As IFTTT crawling appears as a common browser, we were no longer serving up html in a way where they could find an image in the post to upload it to Twitter, Tumblr, or other connected services. We have removed this optimization for the moment.
Things appear groovy again. Sorry about the length of the issue, but we now understand a lot more about how things work on the IFTTT side, which should help us keep it running in the future.
cc/ @chelsea @mayah @davidseibold @lucian @todd @jayzes