Granted, I have not tried today, but my bookmarks still take me to the site.
Still, contacting him with that free offer is a fine step for someone to take.
toggle quoted message
Show quoted text
On Wed, 20 Sep 2023, Z C wrote:
Has anyone messaged Tim Joy (Jeconais) about switching the site(s) to Let’s
Encrypt? The HTTPS certificates they give you are free (rather than $25 or
more for a basic site certificate), but they only last six months and need
some server-side setup to handle the automatic renewals. For basic HTTPS
service, once it’s set up, it’s free and you don’t have to worry about
renewals every year or two.
I would, but I lost his contact info.
On Wed, Sep 20, 2023 at 4:37 PM SlickRCBD <slickrcbdalerts@...> wrote:
On 9/20/2023 5:17 AM, DeliaDee via groups.io wrote:
I use Safari which will connect if I force it to (it argues with me but
I am adamant). The only problem - that I can see - is that the
certificate is expired. I'm pretty ignorant about these things. Is it
really that much of a risk if its a website that has been visited many
many many times before the certificate expired?
_._,_._,_
This is why I strongly disagree with the "https for everything" switch.
It is a risk for entering in your password, or doing any type of
e-commerce.
For just reading a fanfic, or anything where you wouldn't care if the
information was sent in clear text and intercepted/observed by a 3rd
party, there is no risk at all.
Up until around 5 years ago with the switch to HTTPS everywhere,
Fanficauthors.net used HTTP and sent the fanfics in clear text, where no
certificate was needed.
Now when you log in, it should be in HTTPS, and with an expired
certificate there is a risk that somebody has hacked the site and is
monitoring what you are doing so they can intercept your password in the
hopes that you use the same username and password on other sites with
more valuable stuff, such as being able to log into Amazon.com or Ebay
and purchase whatever they want on your credit or debit card.
However, if there is no logon required, and you aren't entering or
accessing any non-public information, there is no risk with
certificates, and this illustrates why they should not have abolished HTTP.
