Consider this your official reply :
http://twitter.com/episod/status/21093220762

As far as I know, Twitter implements proper cache control. I haven't
seen the issue anymore, so I guess it's fine :-)

Tom


On 8/13/10 10:40 PM, Jerry Thompson wrote:
> Would be great if there was an official response from Twitter on
> this.  If the problem is fixed and its a user cache problem persisting
> the error, could a simple fix be to add a random number to the JS URL?
> 
> On Aug 13, 3:32 pm, Clint Ecker <clintec...@gmail.com> wrote:
>> I had some people reporting it on Ars Technica, but it appears to have
>> been fixed now.  If it's still happening its likely users have the
>> JavaScript cached and they need to clear their browser's cache.
>>
>> That being said, we have a lot of very unhappy readers right now ;(
>>
>> Clint
>>
>> On Fri, Aug 13, 2010 at 2:26 PM, Tom van der Woerdt <i...@tvdw.eu> wrote:
>>
>>> On 8/13/10 9:24 PM, Peter Denton wrote:
>>>> Hello,
>>>> seeing tons of reports about alerts happening because of the share
>>>> button. i.e. it alerts every variable.
>>
>>>> Anyone else seeing this?
>>
>>> Yes - I just noticed it at well. You are not the only one.
>>
>>> Tom
>>
>> --
>> Clint Ecker --http://blog.clintecker.com
>> c: 312.863.9323
>> ---
>> twitter: clint
>> skype: clintology
>> AIM: clintecker
>> Gtalk: clintec...@gmail.com

Reply via email to