Whatever happened to "Error 404 - File Not Found" ?
$ curl -Is https://slack.com/404 | grep HTTP/1.1 HTTP/1.1 404 Not Found It's still there.
Not in the page body
Slack's 404 page
41–50 of 53 posts
Re: Slack's 404 page
#42[deleted]
Re: Slack's 404 page
#43I can't help but be reminded of this post: https://news.ycombinator.com/item?id=14460013 (tl;dr, the flying butterflies are dead butterflies)
Re: Slack's 404 page
#44For those not in the know, once upon a time a guy named Stewart Butterfield and some friends tried to make a game, called Game Neverending. Somehow they ended up making Flickr instead! Later, he tried again, this time to make a game called Glitch. Again, he failed, and somehow ended up with Slack. That's why Slack's 404 page is like this ("you found a Glitch!"). To further confuse things they sold the name Glitch off…
I think they were just nice enough to let Fog Creek use the name.
Re: Slack's 404 page
#45Am I the only one who's like -- you've raised $80M (another $250M on the way?), this 404 page exists, and yet your app still uses over a Gig of RAM for my rather pedestrian work uses? What gives?
Because this 404 page was probably made on a Friday afternoon while fundamental issues inherent with their core framework choices takes longer to fix. Just a guess.
Re: Slack's 404 page
#46This is amazing. Slack was developed by accident - it was an internal tool for the company. Maybe this 404 should now become their mainline.
Also the story of Yammer.
Re: Slack's 404 page
#47Earlier quoted context omitted.
$ curl -Is https://slack.com/404 | grep HTTP/1.1 HTTP/1.1 404 Not Found It's still there.
Not in the page body
404 doesn't need to say 'File not found' -- it's not a file, but a resource. But yeah, I don't know why it would need to say so in the page?
Re: Slack's 404 page
#48Glitch was my favorite MMORPG ever - I'm really sad they ran out of money to fund it (though I guess I'm glad they made Slack).
Re: Slack's 404 page
#49Earlier quoted context omitted.
You must work at Slack... The point is, I'm using one org, dozen channels, etc -- some are seeing several times this amount of resource usage and with seemingly endless supplies of capital and users complaining, it seems to get less attention than it deserves.
I gave up on the web UI and started using the IRC gateway. Doesn't really miss anything for my usage, but there's always things like wee-slack[1] that offer threads, reactions, etc in an IRC client. [1]: https://github.com/wee-slack/wee-slack
Ah, word, I didn't know this even existed -- I might look into it.
Re: Slack's 404 page
#50Am I the only one who's like -- you've raised $80M (another $250M on the way?), this 404 page exists, and yet your app still uses over a Gig of RAM for my rather pedestrian work uses? What gives?
But don't most computers have many gigs of RAM? If it's not really hurting performance, who cares?
Because when you have several similar programs, which all use a GB of RAM due to poor optimisation, then you run out of RAM.