mirror of
https://github.com/only-cli/oc.git
synced 2026-09-15 10:40:56 +02:00
only-cli
0435b386ae
The budget was being spent on whatever came first in the document, which on most pages is menus. On the Reddit thread the benchmark uses, all 500 tokens went to nav, sidebar, and moderator boxes, so an agent that opened the page to read the discussion had to escalate to oc raw to see a single comment. distill now finds the content (main, role=main, a single article, else the densest run of prose) and emits it first, with the rest of the page after it under a divider. Nothing is dropped, so do <n> still reaches every link. Link labels that repeat down a page go with it: a thread stamps permalink, save, and report onto every comment, which cost more than the comments. The count and three examples are printed in place, and oc raw still has them. Same thread, before and after: 660 blocks to 254, whole compact page 4,184 tokens to 2,712, and the first view now holds comments instead of a sidebar. Pages small enough to print whole keep document order.
109 lines
5.4 KiB
HTML
109 lines
5.4 KiB
HTML
<!doctype html>
|
|
<html>
|
|
<head>
|
|
<title>Best terminal web browser : fixtureforum</title>
|
|
</head>
|
|
<body>
|
|
<nav>
|
|
<a href="/section/0">section 0</a>
|
|
<a href="/section/1">section 1</a>
|
|
<a href="/section/2">section 2</a>
|
|
<a href="/section/3">section 3</a>
|
|
<a href="/section/4">section 4</a>
|
|
<a href="/section/5">section 5</a>
|
|
<a href="/section/6">section 6</a>
|
|
<a href="/section/7">section 7</a>
|
|
<a href="/section/8">section 8</a>
|
|
<a href="/section/9">section 9</a>
|
|
<a href="/section/10">section 10</a>
|
|
<a href="/section/11">section 11</a>
|
|
<a href="/section/12">section 12</a>
|
|
<a href="/section/13">section 13</a>
|
|
</nav>
|
|
<header><a href="/login">log in</a> <a href="/signup">sign up</a></header>
|
|
<div id="sidebar">
|
|
<h2>About this forum</h2>
|
|
<p>This sidebar exists on every page of the forum. It explains the rules, links to the moderators, and repeats the same three hundred characters of boilerplate on every single thread, which is exactly the kind of text that should never be the first thing an agent pays to read when it opened a discussion to find out what the discussion says.</p>
|
|
<a href="/rules">rules</a>
|
|
<a href="/moderators">moderators</a>
|
|
</div>
|
|
<div id="content" role="main">
|
|
<h1>Best terminal web browser</h1>
|
|
<p>Which terminal web browser do people here actually use day to day, and why that one over the others?</p>
|
|
<div class="comment">
|
|
<a href="/user/commenter1">commenter1</a>
|
|
<span>37 points, 3 years ago</span>
|
|
<p>Lynx is the one I keep coming back to. It is fast, it never surprises me, and it renders documentation pages better than anything else I have tried in a terminal. The keybindings take an afternoon to learn and then they are yours forever, which is the opposite of how most software works.</p>
|
|
<a href="/c/1">permalink</a>
|
|
<a href="/c/1/reply">reply</a>
|
|
<a href="/c/1/save">save</a>
|
|
<a href="/c/1/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter2">commenter2</a>
|
|
<span>34 points, 3 years ago</span>
|
|
<p>I switched to w3m two years ago and never went back. Inline images in the terminal sound like a gimmick until you read a bug report with a screenshot in it and the screenshot is simply there, in the same window, without a browser tab in sight.</p>
|
|
<a href="/c/2">permalink</a>
|
|
<a href="/c/2/reply">reply</a>
|
|
<a href="/c/2/save">save</a>
|
|
<a href="/c/2/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter3">commenter3</a>
|
|
<span>31 points, 3 years ago</span>
|
|
<p>Nobody has mentioned links yet, which surprises me. It handles tables far better than lynx does, and the mouse support in the framebuffer version is genuinely useful when a page insists on being a grid.</p>
|
|
<a href="/c/3">permalink</a>
|
|
<a href="/c/3/reply">reply</a>
|
|
<a href="/c/3/save">save</a>
|
|
<a href="/c/3/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter4">commenter4</a>
|
|
<span>28 points, 3 years ago</span>
|
|
<p>For reading news I use w3m with a readability filter in front of it. The filter strips the navigation and the cookie banners before w3m ever sees them, so a news article arrives as an article instead of as a menu with an article somewhere inside it.</p>
|
|
<a href="/c/4">permalink</a>
|
|
<a href="/c/4/reply">reply</a>
|
|
<a href="/c/4/save">save</a>
|
|
<a href="/c/4/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter5">commenter5</a>
|
|
<span>25 points, 3 years ago</span>
|
|
<p>elinks deserves a mention for its tabs and its bookmark handling. It is the closest thing to a graphical browser that still runs over ssh, and the configuration file is plain and documented rather than a maze of hidden preferences.</p>
|
|
<a href="/c/5">permalink</a>
|
|
<a href="/c/5/reply">reply</a>
|
|
<a href="/c/5/save">save</a>
|
|
<a href="/c/5/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter6">commenter6</a>
|
|
<span>22 points, 3 years ago</span>
|
|
<p>The honest answer is that it depends on the page. You will use links for sites with tables, w3m for anything with images, and lynx when you want the fastest possible path from a url to the text on it. Keeping all three costs a few megabytes.</p>
|
|
<a href="/c/6">permalink</a>
|
|
<a href="/c/6/reply">reply</a>
|
|
<a href="/c/6/save">save</a>
|
|
<a href="/c/6/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter7">commenter7</a>
|
|
<span>19 points, 3 years ago</span>
|
|
<p>I run lynx inside tmux on a small server and read my mail queue reports with it. No javascript means no surprises, and a page that needs javascript to show me a number was never going to be a page I wanted to read anyway.</p>
|
|
<a href="/c/7">permalink</a>
|
|
<a href="/c/7/reply">reply</a>
|
|
<a href="/c/7/save">save</a>
|
|
<a href="/c/7/report">report</a>
|
|
</div>
|
|
<div class="comment">
|
|
<a href="/user/commenter8">commenter8</a>
|
|
<span>16 points, 3 years ago</span>
|
|
<p>w3m with the readable extension is my default. The extension is what makes the difference: without it you get the whole page, navigation and all, and with it you get the part a person would actually want to read.</p>
|
|
<a href="/c/8">permalink</a>
|
|
<a href="/c/8/reply">reply</a>
|
|
<a href="/c/8/save">save</a>
|
|
<a href="/c/8/report">report</a>
|
|
</div>
|
|
</div>
|
|
<footer><a href="/tos">terms</a> <a href="/privacy">privacy</a></footer>
|
|
</body>
|
|
</html>
|