81–90 of 330 posts
Earlier quoted context omitted.
This sounds like your ticket to making money then. Have a hosted option.
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.
Do you think such a service would be significantly different to an email service in terms of privacy concerns?
Earlier quoted context omitted.
Lynx uses whatever SSL is on your system, so if your OpenSSL doesn't support modern SSL, then it's time for you to upgrade ;)
I'm not sure that's true, for example elinks doesn't support SNI: https://bugzilla.redhat.com/show_bug.cgi?id=1527856
Lynx can render HTML5 web pages. Not sure what WebGL has to do with a web browser that is meant for terminal emulators. CSS is not supported in text browsers in general (not all of them are full-screen terminal applications) because it makes no sense - for decent text rendering, the browser needs to ignore style sheets and render in a way appropriate for text output.
This is cool. Had you not considered using a pixellated Sean Connery as the logo?
Still, I think for all the major benefits of text-based browsing, Lynx, Links, and eLinks are still far preferable as lightweight solutions.
What's with the Virus warning with the windows binary? Comes up with BrowserModifier Win32/Unwaders.B!ml detected.
Do you still get the warning with the latest v1.2.3? https://www.brow.sh/downloads/
Does "100 individual HTTP requests" mean 100 TCP connections?
As far as I know, according to RFC 2616, connection keep-alive was intended to promote making numerous HTTP requests. In fact, IME, most web servers default to setting max-requests at 100. Some are higher.
Following the guidance of the RFCs, for decades I have been using this HTTP feature to make 100 requests to a site in a single connection. That is 100 pages of HTML in one quick TCP connection. If I retrieve 3MB, it is 3MB of HTML from the website and zero from third parties. (Further, I have written filters to remove junk from the HTML and print only the content I want, e.g. for reading or to import into database. If I need to split into separate files, which is rare, csplit works nicely.)
In order to achieve this efficiency I could not and do not use a popular browser authored by ad-supported entities. I am an avid text-based web user who has no need for ads, graphics, and other external resources, e.g. Javascript. As such, I can use clients that can support http pipelining according to the RFCs. It works very well; no complaints.
Best of luck with this project.
Requiring a full version of WebExtensions Firefox is a real deal-breaker in terms of memory hogging (that and only having an x64 Windows binary). Why not do what Pale Moon, SRWare Iron, Chrome-Opera, Vivaldi (i.e. Opera-Chrome 2), and others have done, and create a full browser based on the FF code instead of requiring a separate install? Still, I think for all the major benefits of text-based browsing, Lynx, Links,…
Linking to FF/Chrome's libs is certainly an option and I agree a better approach, it's just a learning curve I wasn't willing to invest in.
Can it be made not to show WebGL, embedded video, and so forth? I enjoy a very serene internet using w3m set to monochrome, with mouse and images turned off. Every now and then it's necessary to use a graphical browser, and it's the sensory equivalent of being woken up by a toddler at 5:30 on Christmas morning.
"As of writing in 2018, the average website requires downloading around 3MB and making over 100 individual HTTP requests. Browsh will turn this into around 15kb and 2 HTTP requests - 1 for the HTML/text and the other for the favicon." Does "100 individual HTTP requests" mean 100 TCP connections ? As far as I know, according to RFC 2616, connection keep-alive was intended to promote making numerous HTTP requests . In…
> Browsh consists of a minimal Golang CLI client and a browser webextension. Most of the work is done by the webextension. When the CLI starts, it looks for a compatible browser (currently only Firefox) and starts it in headless mode. Once the browser has started it opens a remote debugging connection and installs the extension. So a browser wrapper .
In implementation, sure. But from the user's perspective, it's just a browser.