> Because if the click-jacking incident yesterday it seems you've added
>
> something like:
>
> //<![CDATA[
> twttr.form_authenticity_token =
> '966f6780e3bb206fe5f451d9ea40407f6532277f';
> if (window.top !== window.self) { setTimeout(function()
> {document.body.innerHTML='';},1);window.self.onload=function(evt)
> {document.body.innerHTML='';};}
> //]]>
>
> Which I guess fixes the click-jack problem but now our app at
> http://topichawk.com/ is broken because we use an iFrame in a harmless
> way to display tweets. Is there a process to keep our site from being
> treated like a spammer?
Twitter doesn't support using <iframe>s and anything you had working before
was almost certainly by accident. You're going to have to code something up
that queries the API.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected]
-- The faster we go, the rounder we get. -- The Grateful Dead, on relativity --
