Funny, that twitter post is actually from 1 year ago today. "12:23 PM - 18 Apr 2013". That is a bizarre coincidence.
Regardless, I may have jumped the gun given that I seem to be the only one with an issue.
It stopped working for me despite the usual fixes. Their homepage is returning a HTTP 421 as of this post. Google still had the cache of the site which makes me think that their site not working was a recent change.
That's hilarious - I didn't notice the year at all. Good catch. Twitter's presentation method leaves a lot to be desired - they call out the year on the other posts, but not the one in question:
Comments
Funny, that twitter post is actually from 1 year ago today. "12:23 PM - 18 Apr 2013". That is a bizarre coincidence.
Regardless, I may have jumped the gun given that I seem to be the only one with an issue.
It stopped working for me despite the usual fixes. Their homepage is returning a HTTP 421 as of this post. Google still had the cache of the site which makes me think that their site not working was a recent change.
Still not working for me unfortunately.
That's hilarious - I didn't notice the year at all. Good catch. Twitter's presentation method leaves a lot to be desired - they call out the year on the other posts, but not the one in question:
http://i.imgur.com/QADYYbX.png
I have no idea what the health of Rapportive is as a company, but both the plugin and their site are working fine for me even as of now.