4 ms·

Well, it was the last i486 online. All it took was posting it on HN.

by jaywalk 5y ago

Daunk 5y ago
Came looking for this comment, heh.
projektfu 5y ago
If they put cloudflare in front, would it still be right?
- willcipriano 5y ago
  You could put one of those tiny embedded microcontrollers behind cloudflare and it would be alright, provided the site is static. You might need a pro plan, but with the right cache headers each cloudflare origin would hit you once then serve many requests with that response.
  - moltke 5y ago
    Heh yeah, you don't even need to do TLS.
- mike_d 5y ago
  If they put any CDN in front of it. Or another web server hosted in a datacenter. Cloudflare isn't anything unique or special aside from getting a bunch of VC funding so they could make the entry level plan free. Historically CDNs didn't do this because most sites don't need it, and abuse was common. However it clearly worked out for them in community name recognition.
  - grishka 5y ago
    Cloudflare is special because it regularly pisses me off with its captchas that feel like actual work to prove my humanity or, even worse, outright non-bypassable "this website uses Cloudflare to protect itself from online attacks". I don't know how good of a CDN it is, but its reputation in my eyes is "something that meddles with my web browsing for no good reason when I least expect it".
    - freitasm 5y ago
      Cloudflare will only block inbound traffic in two situations: - if the request contains an exploit (the Cloudflare WAF) - if the website owner created a rule to block a request Most of the "this website uses Cloudflare to protect..." is a consequence of the second one. To make things easier Cloudflare has a switch to automate the second one - basically it just looks at IP threat levels based on honeypot services all around. Visitors receive a "level" based on IP, region, browser version, etc and if the level is above the switch (Low, High, Medium) then it's blocked. People go for this option - set the switch to High and block almosty everything. Other people will set it to Low or Off and then create their own firewall rules - for example a website owner can create a complex set of rules (in addition to the Cloudflare WAF exploit, or replacing it). See https://community.cloudflare.com/t/the-firewall-rules-we-follow/308849 https://community.cloudflare.com/t/the-firewall-rules-we-fol... for an example. People will see the page sayng "Cloudflare blocked you" when in fact was most likely the website owner.
- freitasm 5y ago
  Any CDN. They just need to set the cache header right - or set to cache everything.
ibic 5y ago
Found this hilarious XD..
Sohcahtoa82 5y ago
Right? A 486 running a webserver behind CloudFlare returning a 502 Bad Gateway was the perfect "I don't know what I expected" moment.
major505 5y ago
It was the same when someone posted a web server running on a Sinclair zx81

Well, it was the last i486 online. All it took was posting it on HN.

Daunk 5y ago

Came looking for this comment, heh.

projektfu 5y ago

If they put cloudflare in front, would it still be right?

willcipriano 5y ago
You could put one of those tiny embedded microcontrollers behind cloudflare and it would be alright, provided the site is static. You might need a pro plan, but with the right cache headers each cloudflare origin would hit you once then serve many requests with that response.
- moltke 5y ago
  Heh yeah, you don't even need to do TLS.
mike_d 5y ago
If they put any CDN in front of it. Or another web server hosted in a datacenter. Cloudflare isn't anything unique or special aside from getting a bunch of VC funding so they could make the entry level plan free. Historically CDNs didn't do this because most sites don't need it, and abuse was common. However it clearly worked out for them in community name recognition.
- grishka 5y ago
  Cloudflare is special because it regularly pisses me off with its captchas that feel like actual work to prove my humanity or, even worse, outright non-bypassable "this website uses Cloudflare to protect itself from online attacks". I don't know how good of a CDN it is, but its reputation in my eyes is "something that meddles with my web browsing for no good reason when I least expect it".
  - freitasm 5y ago
    Cloudflare will only block inbound traffic in two situations: - if the request contains an exploit (the Cloudflare WAF) - if the website owner created a rule to block a request Most of the "this website uses Cloudflare to protect..." is a consequence of the second one. To make things easier Cloudflare has a switch to automate the second one - basically it just looks at IP threat levels based on honeypot services all around. Visitors receive a "level" based on IP, region, browser version, etc and if the level is above the switch (Low, High, Medium) then it's blocked. People go for this option - set the switch to High and block almosty everything. Other people will set it to Low or Off and then create their own firewall rules - for example a website owner can create a complex set of rules (in addition to the Cloudflare WAF exploit, or replacing it). See https://community.cloudflare.com/t/the-firewall-rules-we-follow/308849 https://community.cloudflare.com/t/the-firewall-rules-we-fol... for an example. People will see the page sayng "Cloudflare blocked you" when in fact was most likely the website owner.
freitasm 5y ago
Any CDN. They just need to set the cache header right - or set to cache everything.

ibic 5y ago

Found this hilarious XD..

Sohcahtoa82 5y ago

Right? A 486 running a webserver behind CloudFlare returning a 502 Bad Gateway was the perfect "I don't know what I expected" moment.

major505 5y ago

It was the same when someone posted a web server running on a Sinclair zx81