A Few Modest Repairs
Posted: Tue Oct 09, 2018 9:30 pm
A funny thing happened on the way to the '59 Forum.
In an effort to expand membership, I opened up the Forum to logins from Social Media - Facebook, in particular. However, Facebook only supports integration if the site you log into from Facebook, uses "secure certificates" - that is, an Authorizing Body certifies that a particular site is not malicious, and that they are who they say they are. Furthermore, when registering a secure certificate for a site, all activity between that site and the user's desktop browser is encrypted.
It was a lot of back and forth (and, cost) for me to implement, and I have seen a Facebook user or two show up. But the downside of encryption - it places a significant load on the server for sites like ours, that are top heavy with media (images, videos, pdfs, etc.). You've all seen the broken links, and sluggish performance. You don't get broken links, if your site doesn't use certificates - and, doesn't encrypt traffic.
So, Mea Maxima Culpa. I plan to back out these changes in the next week or so. If Facebook users want an account, they can register through the front door just like everybody else. Instead of going to https://59plymouth... you will be directed to https://59plymouth... - just like before. (The difference is the "s" in "https", which stands for "secure".) One thing you may notice: The "cookie" the browser deposits on your computer when you check "remember my password" will probably go stale, and you will have to log in again, and check that box again.
Sorry for the inconvenience. Mostly, sorry about the bad behavior of the site. I'll make it right.
Dan
In an effort to expand membership, I opened up the Forum to logins from Social Media - Facebook, in particular. However, Facebook only supports integration if the site you log into from Facebook, uses "secure certificates" - that is, an Authorizing Body certifies that a particular site is not malicious, and that they are who they say they are. Furthermore, when registering a secure certificate for a site, all activity between that site and the user's desktop browser is encrypted.
It was a lot of back and forth (and, cost) for me to implement, and I have seen a Facebook user or two show up. But the downside of encryption - it places a significant load on the server for sites like ours, that are top heavy with media (images, videos, pdfs, etc.). You've all seen the broken links, and sluggish performance. You don't get broken links, if your site doesn't use certificates - and, doesn't encrypt traffic.
So, Mea Maxima Culpa. I plan to back out these changes in the next week or so. If Facebook users want an account, they can register through the front door just like everybody else. Instead of going to https://59plymouth... you will be directed to https://59plymouth... - just like before. (The difference is the "s" in "https", which stands for "secure".) One thing you may notice: The "cookie" the browser deposits on your computer when you check "remember my password" will probably go stale, and you will have to log in again, and check that box again.
Sorry for the inconvenience. Mostly, sorry about the bad behavior of the site. I'll make it right.
Dan