Better than "can't do HTTP" which seems to get more common every year. I prefer this kind of info site being HTTP-only to being HTTPS-only. HTTPS causes occasional problems with certificates and some people can't use HTTPS.
One example would be running a client on hardware not capable of performing encryption fast enough. I think would be particularly relevant to web browsers on Amiga.
There are extremists out there who submit the URL they would like to view, then receive it on e-mail later on in a document like format they are comfortable using and that does not track you.
There's enough change in the ecosystem that outdated OSes (that people still use) often can't handle the current recommendations for which TLS versions to allow, don't have root certificates for newer certificates, ..., so how to set that up is an interesting balance if you need to reach as many people as possible (which for government info sites is probably the case)
* in China TLS 1.3 is blocked by the state firewall
* based on past reading of discussions here, in some states using encryption may be illegal, not sure if this is really the case, this may eventually come to the West as well, see Australia and U.S. officials attacks on encryption
* old computers/OS/browser that the user can't update