Twitter Changed Yesterday

It means a whole lotta nothing

The change that Twitter made was when accessing their site directly. That's different than how JFBConnect uses Twitter to access through their API. Their API has required using the https protocol for a long time (as long as I've used it, at least). It's a basic security move and one we've respected, even with social networks that don't require it.

Please note that the requirement for using https is only to communicate with their server. Your site does not have to have an SSL certificate installed. Your server simply needs to be able to establish secure sessions to Twitter (and other providers) for JFBConnect to function properly.

I hope that helps, and should you have any other questions, just let us know!

Thanks,
Alex

Glad to help explain. Should you need anything else, just let me know.

Thanks,
Alex