Suggestion: Add an example video so we can see what this actually does.
It is very simple: When you run it it will create a web server (listening on port 5000) by default; when you visit that server with your browser you'll get a terminal to your system (the same terminal / user that was used to originally run the server).
Show HN: Cast.sh An adorable instance of your terminal in the browser
11–20 of 20 posts
Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#12Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#13Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#14Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#15How is this on the front page with basically no README and no screenshots or video?
Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#16Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#17How is this on the front page with basically no README and no screenshots or video?
Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#18Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#19I'm sure it is an interesting engineering exercise, but I struggle to think of a situation where I would fire a browser to use the terminal instead of just opening a terminal.
Re: Show HN: Cast.sh An adorable instance of your terminal in the browser
#20Come up with an interesting idea, spend n number of days working on idea, get to the front page of hackernews, have thousands of eyeballs on your thing...Spend 0 time on the readme and have everyone take a half second glance, not know what the thing is or does and move their attention else where. Let this be a lesson to everyone to spend some time on your readme's... https://github.com/matiassingers/awesome-readme