I thought I'd mention this since I just saw it. The HTML source for the Forum home page (and other pages on the forum) includes a number of links to resources (scripts etc) which are http: (ie not secure) vs https: (secure).
When the site loads these scripts for the first time, the browser will show a 'not secure' warning in the address bar since not all resources are being loaded via secure connections and thus (in theory) are potentially dangerous. Once you've got the page loaded and cached, this goes away, because the browser doesn't have to fetch those resources again until the cache expires. So you won't see it all the time.
As a general principle, all links to all resources loaded by a secure page and its scripts should be https. From what I can see, all of the insecure resources could be called via https (schema.org and forum.sexlikereal.com both support TLS, for example). Should be an easy fix.
One for the techies in the back room, I guess.
