According to the 'Server' response header, Cowboy is the customer facing web server Https://github.com/ninenines/cowboy. Source: over 2 years ago

===> sh(git clone -n https://github.com/ninenines/cowboy .tmp_dir636214859401) Failed with return code 128 and the following output: Cloning into '.tmp_dir636214859401'... Fatal: unable to access 'https://github.com/ninenines/cowboy/': SSL certificate problem: unable to get local issuer certificate. Source: over 2 years ago

RE: HTTP/Web Sockets/TCP/UDP/etc. - check out NineNines libraries: Ranch (TCP Socket Acceptor), Cowboy (HTTP Server), Gun (HTTP client), and CowLib (General HTTP/SPDY library) are pretty good from what I hear. Source: over 2 years ago

Ranch is a pretty well optimized and battle hardened tcp acceptor. It powers the Cowboy/Phoenix server which scales to extreme level of concurrency and low latency. Cowboy uses ranch to pool and accept connections and I believe it uses {active,once}. https://github.com/ninenines/cowboy https://github.com/ninenines/ranch. - Source: Hacker News / over 2 years ago

I have a web application which uses cowboy and cachex every so often cachex errors, which means my server returns a 500. Source: over 2 years ago

Well I do also regularly make use of brow.sh expecially when I hit the slow hours of the internet. I just login to my old ssh sdf.org shell account and away I go. Source: over 1 year ago

15 years experience. You may have seen my text-based modern browser, https://brow.sh, here on the front page a few times. - Source: Hacker News / over 1 year ago

You might be interested in https://brow.sh. - Source: Hacker News / over 1 year ago

Some of you may know me from https://brow.sh `. - Source: Hacker News / about 2 years ago

That looks really useful! It would be even nicer to see something like this, but integrated with brow.sh for those who prefer to stay on the terminal. Source: about 2 years ago