Part of the problem I'd been having is when using certain browsers that use web browser is unable to verify the brickboard.com identity as an OCSP error.

Online certificate validation = OCSP.

Opera says the response from the online certificate validation (OCSP) server (brickboard.com) was too old. OCSP is better and more secure than the CRL authentication between domain+protocol and the web client. TLS encrypt methods helps OCSP during the public key exchange, tho.

An older authentication method that occasionally works with Opera 12.17 (newest version sans heartbleed) Opera 12.17 is the final Presto browser before crappy and insecure Chromium browser nonsense.

Yet OCSP is not immune to those that may seek the private key brickboard.com uses to encrypt your data session.

Yet the public / private key security methodology that is at the root of the web server and web client is primitive, insecure, and is a bunch of malarkey.

You can still use brickboard.com free of the annoying and insecure JavaScript runtime. Yet through the Chromium and Mozilla (FireFox) about:config, you can disable crappy JavaScript. (Don't need no asynchronous client, Ajax, Web 2.0, and the host of JavaScript frameworks for the ads and multimedia content I despise, and is insecure).

And so, brickboard does not collect much ad revenue from me, I guess. I dunno the how this site tallies visits, hits, and clicks.

Probably like a newspaper site.

I also turn off the media run-time extensions and plug-ins, all of them, in the browser, until I need them.

The more you tun on and add to a browser, the more likely your browser gets hijacked or worse deeper into your OS.

cheers,

dud.