Headless_Death
u/QuartetGhent
With the encouragement over the last few years by large players like Google, Mozilla, Cisco, and such to have more websites convert to HTTPS, has a conversion at any point been considered?
For example, the W3C encourages more sites to convert. Info Here
One setback I can see is the incompatibility with out of date platforms like Windows XP prior to SP3. But a vast majority of people are going to be using compatible browsers so I don't think this is that much of an issue.
Another Could be cost, with many sites asking to $50-150 for certificates. But a solution to this could be Let's Encrypt, which offers Domain Verification certificates for free by being sponsored by a large list of the big internet players.
And I suppose the largest hurdle to them all would be time to look into how to implement on your site, and which URLs may need to be updated to have that added 's'. The most I can find related to the SMF platform is from this thread on their board. Another consideration is the DV certificates provided by Let's Encrypt expire every 90 days, so they suggest renewing the certificate automatically every 60 days.
I can easily see this something that may take time to implement, and may not be done with how life typically gets in the way of side projects like this. I mostly bring this up because I'm hoping to no longer see the not secured warning when looking at SK.net.
For example, the W3C encourages more sites to convert. Info Here
One setback I can see is the incompatibility with out of date platforms like Windows XP prior to SP3. But a vast majority of people are going to be using compatible browsers so I don't think this is that much of an issue.
Another Could be cost, with many sites asking to $50-150 for certificates. But a solution to this could be Let's Encrypt, which offers Domain Verification certificates for free by being sponsored by a large list of the big internet players.
And I suppose the largest hurdle to them all would be time to look into how to implement on your site, and which URLs may need to be updated to have that added 's'. The most I can find related to the SMF platform is from this thread on their board. Another consideration is the DV certificates provided by Let's Encrypt expire every 90 days, so they suggest renewing the certificate automatically every 60 days.
I can easily see this something that may take time to implement, and may not be done with how life typically gets in the way of side projects like this. I mostly bring this up because I'm hoping to no longer see the not secured warning when looking at SK.net.