rdrview VS w3m

See also the C port here: https://github.com/eafer/rdrview/

It works well with text-mode browsers like w3m.

i also use rdrview sometimes.

They both parse untrusted content content without sandboxing.

I typically send content through rdrview[0] before piping through w3m-sandbox[1], which should be pretty safe.

[0]: https://github.com/eafer/rdrview

[1]: https://git.sr.ht/~seirdy/bwrap-scripts/tree/trunk/item/w3m-...

Could have been nice to have this integrated to w3m. Somthing along the lines of rdrview.

I do a lot of this work[3] (web to documents) and it's interesting to see other approaches. The medium image problem is something I've faced as well, but never got around to fixing. I'm planning to get a Remarkable soon, so will definitely be trying this out.

My personal solution has been https://github.com/captn3m0/url-to-epub/ (Node/readability), which I've tested against the entirety of Tor's original fiction collection[0] where it performs well enough (I'm biased). Another tool that does this beautifully well is percollate[1], but it doesn't give enough control of the metadata to the user - something I really care about.

I've also started to use rdrview[2], which is a C-port of the current Firefox implementation of "reader view". It is very unix-y, so it is easy to pipe content to it (I usually run it through tidy first). Quite helpful in building web-archiving or web-to-pdf or web-to-kindle pipelines easily.

[0]: https://www.tor.com/category/all-fiction/original-fiction/

[1]: https://github.com/danburzo/percollate

[2]: https://github.com/eafer/rdrview

[3]: https://captnemo.in/ebooks/

Two projects that do this with nearly identical output:

- https://github.com/eafer/rdrview

- https://github.com/go-shiori/go-readability

Pipe the filtered HTML output into your favorite textual web browser for an ideal reading experience.

This may help if you can do some piping around it.. https://github.com/eafer/rdrview

SEEKING WORK | Argentina | Remote

Email: [email protected]

I'm a programmer, most familiar with C on Linux and Win32. I'll be happy to start a project from scratch, or to help support any old codebase. For a sample of my work please see rdrview [1], a small command line tool that found some success here on Hacker News; or [2], a naive filesystem implementation I've been working on.

My current rate is 20 USD/hour. For what it's worth, I have a background in math.

[1] https://github.com/eafer/rdrview

[2] https://github.com/linux-apfs

Get the w3m sources: git clone https://github.com/tats/w3m

nvi2 [0]: I got to like the simplicity of nvi when installing Void Linux on my laptop, but it had some annoying bugs that made me switch to nvi2. In general, it feels like `good' software; powerful enough by virtue of being a 1:1 vi clone with a few crucial improvements (multibyte, multi-undo, etc.), but simple enough to hack on if I miss some feature. Though no autocomplete means it's not suitable for more verbose languages, like Java.

QuickJS [1]: qjscalc is my go-to scientific calculator, and qjs my go-to JavaScript implementation for simple programs. The C interface is very nice to use, too. All in all, it feels very much like a "complete" engine, even if not quite as fast as one with JIT.

w3m [2]: Somewhat lacking as a web browser, but a very good pager. Would take it over less any day. Also has the best table display of any text-mode browser, supports inline images, and is rather extensible.

Wine [3]: It's gotten so good that I no longer have to dual boot Windows. Still not perfect, but definitely on my list of "good software".

[0]: https://github.com/lichray/nvi2

[1]: https://bellard.org/quickjs/

[2]: https://github.com/tats/w3m

[3]: https://www.winehq.org/

newer https://github.com/tats/w3m

I liked w3m a lot back when I had a job were rando browsing was discouraged. https://github.com/tats/w3m

> I've been noodling about the implementation of adding functionality to w3m and lynx so there is a separate fetch-page func but report a different User-Agent header (eg, "Mozilla"). I've encountered many pages that don't allow access until I change the "lynx-*" header (bastards).

Wouldn't this feature suffice? https://github.com/tats/w3m/blob/master/doc/README.siteconf

The first result, ffs: https://github.com/tats/w3m

But the problem is that a lot of the code isn't commented to explain what they're doing and there isn't a lot of documentation online to use the software effectively. (In order to not make my question vague, I'm trying to build a front end Gtk GUI to w3m. But I don't need explanation to the code or steps to do this. even though I didn't understand it and I don't know the steps I need. What I'm looking for is a method to effectively study the code of an open source project that didn't take into consideration that you'll study it, therefor they didn't document well the structure of their codebase and how the project was build and the different parts of making it).