I'm curious as to how it displays the images without first downloading the full size first (and thus not saving bandwidth), is anyone able to explain this?
There's no magic, Browsh is just designed to be run on a remote server where internet is fast and cheap and then accessed over SSH or the browser client from a local network that is likely slow and/or expensive.
It runs a ‘real’ browser on the server and renders pages there.
The use case here is one where one has slow access to a machine with fast internet access, or where the local machine doesn’t have enough resources (e.g. screen resolution, battery live) to render web pages.
While I think Browsh is very interesting, you can immediately see a couple issues with this. When I tried it last week, it worked pretty well for a bit, and then I got an error that all the servers were busy.
That sounds like you were trying the SSH demo. I've currently got that limited to 20 instances. Each one has 2Gb of RAM and a CPU, so it's not cheap. And I'm currently funding it off a modicum of donations.
Yeah, I was using the web demo, and it was fine, but more limited, so I tried the ssh version to check YouTube (my coworker said that was working) and got the error.
Obviously, I don't expect a free service like this to let me stream unlimited video. At first glance, I saw the demo server as the actual service, rather than seeing this as a tool to set up on your vpn. That eliminates the scaling issue and the privacy issues.
It's a free demo with unlimited access to the web. I'm just covering my back for any possible misuse. If there's demand you can pay to turn off logging.
