[bwag]

> Its main purpose is to significantly reduce bandwidth and thus both increase browsing speeds and decrease bandwidth costs.

How does it reduce bandwidth exactly? It still has to grab all the html/css/js for the site being rendered.

[robrtsql]

I think the use-case is that the user is running their headless browser on a remote server with a good internet connection. Then they open an SSH tunnel to that server from their local machine which has low bandwidth--and the only thing that needs to be received by the local machine is the browsh rendering of the webpage.

[tombh]

Exactly.

As well SSH/Mosh access there's a HTTP service, that currently only outputs static, noninteractive HTML and basic graphics. For example: https://html.brow.sh/https://news.ycombinator.com/item?id=17...

[_dark_matter_]

This sounds like your ticket to making money then. Have a hosted option.

[stockkid]

I'd be wary to use a hosted option because a browser in a remote server will then contain my credentials and browsing history.

So if OP goes down this road then I think he should allow users to access machines.

[tombh]

What do you mean by access to machines? Like SSH access?

Do you think such a service would be significantly different to an email service in terms of privacy concerns?

[peatmoss]

Yes, I do think it’s pretty different.

If you weren’t the fine upstanding person you are, you’d have all the web traffic of users at your disposal: banking, secure interactions with healthcare providers, credentials to Hacker News, the whole nine yards.

With access to my email, you could probably reset a handful of my passwords to various services that don’t support dual factor auth, and you could probably discover what services I subscribe to.

I mean, I wouldn’t want you to have access to my email, but I would much rather that than a permanent man-in-the-middle web client.

[bwag]

Ah, that makes sense. Cool project!

[mahesh_rm]

does it fetch images? if it does not, there you go..