Eg.: "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/..." would then go to: "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/..."
A shout out to Tomomi Imura, because HTTP Status Cats was her idea and I just made the images available through an API.
It's crazy to think that since 2010 this still pops up on the HN front page from time to time. Thank you for that!
http.cat is a testament of how simple, fun and silly the internet was back then. I'll try to keep it online for as long as I can.
I love reading the stories you all share online about it, they fuel my motivation to keep it up and I'm always open to feedback and new ideas. So feel free to share them here or on the github repo.
Cheers!
> Administered by the non-profit Fundació puntCAT under the oversight of ICANN, registrations are available only to individuals and organizations demonstrating use or promotion of the Catalan language and culture.
ETA: This category lists 314 ccTLDs.
https://icannwiki.org/Category:CcTLD
There are 316 ccTLDs. So; it's either missing 2, or they are documented but not in the right category.
If you're looking for an authoritative source I think you should check out the PSL, but it doesn't have the right metadata to answer your question. You'd need to supplement it somehow.
nyan.cat has a language picker that includes Catalan, even though it just changes the page title.
One could say by having the websites become popular and viral, and offering versions of the their websites in Catalan, they are spreading Catalan culture to more parts of the internet. We're having a discussiong about it right now, others are reading, pretty big impact from just the TLD choice :)
I ended up getting a call to explain why the website is showing middle finger to our VIP customer.
https://news.ycombinator.com/item?id=37735614 (2023)
https://news.ycombinator.com/item?id=31438989 (2022)
It does not, however, use a cartoon dog in a room on fire.
The cats make it much more fun than a regular docs page, whilst still being a useful quick reference. I wonder if other bits of reference information could be made more interesting in this way.
I maintain a list of domains, so it was quite easy to find them
(Every web site I've built in the last ten years has a series of conditions that combined will trigger a 418.)
https://github.com/tantalor/emend/blob/master/app/static/ima...
Still gives me a chuckle
At that time we had a couple of DB problems, it would get overwhelmed, shit itself and our page would show an error. I found some time and, instead of fixing the error (duh ;P), I downloaded around 20-30 funny cat gifs, assigned each a funny caption and modified the error page so that each would show randomly.
Next time the DB shit itself, the error page showed up and the cats wrought refresh chaos upon Apache but it took it in stride since the error page was mostly static.
Everyone was delighted but after around 15 minutes I got a call from sales asking my to take the cats down. „It’s not very businessy, take it down!”. „The site is down either way, would you rather our clients stare at a dry message or something funny?”. „Dry message! Take it down”. „No” and I hung up. So proud of myself that I stood up to them. I think the cats are still up to this day ;)
The point of this story is that http.cat made me think of those cat pages, thanks!
https://github.com/tanelpoder/catbench
Also, a simple browser-only page for visually demonstrating what embeddings/vectors physically are, for explaining this to database & storage folks:
https://tanelpoder.com/catvector/
(Initial load of the vector heatmaps may take a few seconds when you click on a pet type)
In the acknowledgments section,
> Thanks also to Ray Bradbury.
A soft, indestructible automaton provided by nature to be kicked when things go wrong in the domestic circle.Only feedback I have is when I click into an image then hit back, it brings me to the top of the page which is kind of annoying. I wish it held my place.
Issue created: https://github.com/httpcats/http.cat/issues/258
Anything in the 4XX range is going to be treated as just a regular ol' response, just like 404. (You could serve an entire site with all responses set to status=404, and be fine... other than probably never getting any cache hits) If you don't include a body in the response, the browser might sub in it's own error page, but it will just communicate that the user agent made a bad request.
I successfully wrote a bot that would bypass it all, but it was weird, and became a slight challenge since I couldn't rely on response codes to determine if I succeeded. When I solved the challenge, it would return a 400 Bad Request while serving me the content I was looking for.
URL to test: https://httpbin.org/status/204
That said, at least they have a broad cipher set support and their HTTPS-only implemetation does work in older browsers and systems. That's nice. But HTTP+HTTPS would be better.