[rdin]

We had some issues integrating 3rd party systems, such as the Twitter button, which has had an invalid certificate for months now. If your site can live without these bells & whistles, then you should investigate and see if your site can take the performance hit.

[rubyskills]

Wow, I didn't think about twitter's button. :-/ We use the twitter widget.. Do you know if the twitter js is behind a valid cert?

[rdin]

Unfortunately, it's been invalid for awhile. You can check it out for yourself here:

http://platform.twitter.com/widgets.js vs https://platform.twitter.com/widgets.js

[rubyskills]

Drat! Someone over at twitter should fix this. :(

Luckily, we don't use that js, we use:

http://twitter.com/javascripts/blogger.js

and I just checked the certificate behind this and it's valid (I should hope twitter's main cert is valid!):

https://twitter.com/javascripts/blogger.js

and we use the json API:

http://api.twitter.com/statuses/user_timeline/healpay.json?c...

which also happens to have a valid cert:

https://api.twitter.com/statuses/user_timeline/healpay.json?...

So it looks like we're in the clear for this at least :)