The first issue has been published, I invite you to watch and read it, constructive criticism is important to me, I have started working on the next one )) I hope it will be no worse.
5 Likes
Why do you think Donald Knuth is dead?
1 Like
no ssl?
the site does not collect cookies, encryption is not needed, only http
1 Like
corrected. thanks. ;-)
i guess that is fair i personally have ssl on any website i have but maybe its just me.
what are you using for your translations? real people or some machine translations? if i choose serbian from the menu is perfectly coherent, which i didnāt expect.
also ur website reminds of something my dad would browse back in 2007 via dialup, so the vibe of that era is perfect !
1 Like
I have SSL on my website, too, but I still allow HTTP as well as HTTPS connections.
i have HSTS preload on mine. even submited to preload list, so my domain is hardcoded as https into chromium
Thatās fine, but I donāt want to limit access to my site to browsers that implement HTTPS, because I still get visitors with really old, low-end computers that canāt do SSL, TLS, HTTPS. So I still allow HTTP on an āat your own riskā basis. It seems like the right thing to do.
3 Likes
my whole css would break on an old(er) browsers so thereās no point in trying to support them. most of my āvisitorsā are just me anyways if i can trust umami
thatās how it was planned)) so that the spirit of that era when the Internet was non-corporate could be felt. the translator is a neural network, I also checked Ukrainian (Iām Ukrainian), it translated very well
Iām still thinking about how to do it better, maybe ban HTTPS on the server? I donāt want to use third-party services, Iām irritated by sites that have a cloud spinning for a minute, then you prove that you are a person, this is inhumane, the site should just open, without unnecessary bells and whistles, I think so. Especially if no data is collected
1 Like
solved the problem with the certificate on the site
1 Like
I BLOODY HATE CLOUDFLARE TRUST i have whole blogpost lowkey shitting on them.
yeah i no longer get a warning !
2 Likes
I want to add it to Resources List
I am listed as a contributor but for some reason I canāt add or change anything
the prototype and design of the next issue are already ready, I hope that the previous one did not disappoint, the next one should be no worse than the first one ))
I am accepting materials for another week, if anyone wants to publish.
the issue will be released at the beginning of next month
7 Likes
I can definitely see the wisdom in this approach!
I would love for somebody to correct me if Iām wrong, but I think it should be technically feasible to run an HTTPS to HTTP proxy right on the average consumer WiFi router. I wonder if OpenWRT or anything like it offer something like that?
(Iām not arguing that webmasters shouldnāt still offer HTTP versions of their sites if they want to. Iām just thinking about how to better extend the useful life of older machines in general. I feel like youād want to push a lot of security measures into your gateway when taking an such a device onto the internet.)
the hosting on which the site is located is static, but has a built-in CMS, widgets, and additional modules that are built in using a script-construction, there is nothing to take specifically from the sites themselves, they do not collect cookies, so I do not understand what kind of data or what kind of protection is needed? this is an HTML site, all the data that is on the site is on the surface, nothing is encrypted or hidden, the siteās database cannot be hacked because it simply does not exist, text files. The design opens even with DOS browsers. and the server is maintained by a large hosting company, forget about DDoS.
if you host such a site at home and want to have HTTP - make sure that the site is as simple as possible
