Groups | Search | Server Info | Login | Register
| From | D <nospam@example.net> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: terminal only for two weeks |
| Date | 2024-11-27 10:51 +0100 |
| Organization | i2pn2 (i2pn.org) |
| Message-ID | <d5614852-aa8a-639f-9b91-54744fff04cc@example.net> (permalink) |
| References | (1 earlier) <vi3ecs$35u53$1@dont-email.me> <6c4ae24b-7bb8-7d84-8f74-1f5fc14c0ec0@example.net> <87ed2yjkl8.fsf@tilde.institute> <55db8483-58f0-c3dc-de0b-7f44881fa180@example.net> <67464333@news.ausics.net> |
On Tue, 27 Nov 2024, Computer Nerd Kev wrote: > D <nospam@example.net> wrote: >> On Tue, 26 Nov 2024, yeti wrote: >>> D <nospam@example.net> wrote: >>>> I have been thinking about moving the reading part of web browsing >>>> into the terminal as well, but haven't found a browser I'm happy >>>> with. >>> >>> I use Elinks, Emacs/EWW and W3m, but none of them can replace the scary >>> fullfat browsers. They seem to just fit Smolweb stuff (FTP, Gemini, >>> Gopher and similar). >> >> True. > > I like seeing useful images, so prefer Dillo and Links (the latter > does support display via the framebuffer so you can run it > graphically without X). For some reason, I never managed to get the framebuffer to work. Have no idea why. =( I would like to get it to work though. Dillo was a good tip! I did play with it for a bit, but then forgot about it. Maybe the reason was a lack of tabs or buffers. I think links or maybe it was elinks, had a way for me to replicate tabs or vi buffers in the browser. It was super convenient! Basically my ideal would be to move all my "reading" to a text based browser, so that I would only have to keep work related stuff in the massive GUI browser. All the other 60+ tabs, would live in the text browser where I would reference them when needed. >>>> Maybe it would be possible to write a kind of "pre-processor" that >>>> formats web sites with a text based browser in mind? >>> >>> Despite me finding this solution really scary, something like that >>> indeed exists: >>> >>> <https://www.brow.sh/> >> >> Ah yes... I've seen this before! I did drop it due to its dependency on >> FF, but the concept is similar. My idea was to aggressively filter a web >> page before passing it on to elinks or similar. >> >> Perhaps rewriting it a bit in order to avoid the looooooong list of menu >> options or links that always come up at the top of the page, before the >> content of the page shows after a couple of page downs (this happens for >> instance if I go to wikipedia). > > Lucky if it's just a couple of page-downs, I can easily be > hammering the button on some insane pages where 10% is the actual > content and 90% is menu links. Often it's quicker to press End > and work up from the bottom, but many websites have a few pages of > junk at the bottom too now, so you have to hunt for the little > sliver of content in the middle. I know... as a perfectionist this does not go down well with me. ;) >> Instead parsing it, and adding those links at the bottom, removing >> javascript, and perhaps passing on only the text. > > A similar approach is taken by frogfind.com, except rather than > parsing the links and putting them at the end, it detetes them, > which makes it impossible to navigate many websites. It does the > other things you mention, but the link rewriting would probably be > the hardest part to get right with a universal parser. Did not know about frogfind! This could be a great start to improve the readability! In my home brew rss2email script, I automatically create archive.is links, so that when I want to read articles behind paywalls, archive.is is already built in. I imagine that I could whip up something similar, running page through http://frogfind.com/read.php?a=xyz... ! > Site-specific front-ends are a simpler goal. This is a list of ones > that work in Dillo, and therefore without Javascript: > https://alex.envs.net/dillectory/ > > Of course then you have the problem of them breaking as soon as the > target site/API changes or blocks them. This is the truth!
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar
terminal only for two weeks Retrograde <fungus@amongus.com.invalid> - 2024-11-25 13:34 +0000
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-25 22:18 +0100
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-25 21:52 +0000
Re: terminal only for two weeks Mike Spencer <mds@bogus.nodomain.nowhere> - 2024-11-26 03:18 -0400
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-26 21:28 +0000
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-11-26 09:22 +0042
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-26 21:24 +0000
Re: terminal only for two weeks candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-11-30 01:20 +0000
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-11-30 04:22 +0042
Re: terminal only for two weeks candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-12-01 20:40 +0000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-30 03:52 +0000
Re: terminal only for two weeks candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-12-01 20:40 +0000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-01 23:24 +0000
Re: terminal only for two weeks candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-12-02 02:00 +0000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-02 05:41 +0000
Re: terminal only for two weeks John McCue <jmccue@qball.jmcunx.com> - 2024-11-26 03:13 +0000
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-26 10:22 +0100
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-11-26 12:15 +0042
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-26 16:36 +0100
Re: terminal only for two weeks not@telling.you.invalid (Computer Nerd Kev) - 2024-11-27 07:52 +1000
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-27 10:51 +0100
Re: terminal only for two weeks not@telling.you.invalid (Computer Nerd Kev) - 2024-11-28 06:44 +1000
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-11-28 05:54 +0042
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-28 10:52 +0100
Re: terminal only for two weeks not@telling.you.invalid (Computer Nerd Kev) - 2024-11-29 06:17 +1000
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-28 22:05 +0100
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-11-29 02:19 +0042
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-29 10:38 +0100
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-29 22:39 +0100
Re: terminal only for two weeks Mike Spencer <mds@bogus.nodomain.nowhere> - 2024-11-26 17:57 -0400
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-27 10:54 +0100
Re: terminal only for two weeks Mike Spencer <mds@bogus.nodomain.nowhere> - 2024-11-28 01:41 -0400
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-28 06:42 +0000
Re: terminal only for two weeks D <nospam@example.net> - 2024-11-28 10:56 +0100
URIs within URIs: google.com/url?q= et al. Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2024-12-20 18:42 +0000
Re: URIs within URIs: google.com/url?q= et al. Andy Burns <usenet@andyburns.uk> - 2024-12-20 19:03 +0000
Re: URIs within URIs: google.com/url?q= et al. Mike Spencer <mds@bogus.nodomain.nowhere> - 2024-12-22 01:39 -0400
Re: terminal only for two weeks Oregonian Haruspex <no_email@invalid.invalid> - 2024-12-04 06:11 +0000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-04 06:42 +0000
Re: terminal only for two weeks candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-12-04 14:30 +0000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-05 01:46 +0000
Re: terminal only for two weeks not@telling.you.invalid (Computer Nerd Kev) - 2024-12-08 07:52 +1000
Re: terminal only for two weeks root <NoEMail@home.org> - 2024-12-08 14:11 +0000
Re: terminal only for two weeks Bozo User <anthk@disroot.org> - 2025-01-12 23:01 +0000
Re: terminal only for two weeks D <nospam@example.net> - 2025-01-13 10:46 +0100
Re: terminal only for two weeks not@telling.you.invalid (Computer Nerd Kev) - 2025-01-14 06:52 +1000
Re: terminal only for two weeks D <nospam@example.net> - 2025-01-14 18:54 +0100
web Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2025-01-16 07:55 +0000
Re: web not@telling.you.invalid (Computer Nerd Kev) - 2025-01-17 07:10 +1000
Re: web yeti <yeti@tilde.institute> - 2025-01-17 04:58 +0042
Re: web Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2025-01-18 14:05 +0000
Re: web not@telling.you.invalid (Computer Nerd Kev) - 2025-01-19 09:09 +1000
Re: web candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-01-29 20:10 +0000
Re: web Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-04 21:42 +0000
Re: web Ben Collver <bencollver@tilde.pink> - 2025-01-19 14:47 +0000
Re: web yeti <yeti@tilde.institute> - 2025-01-19 16:14 +0042
Re: web snipeco.2@gmail.com (Sn!pe) - 2025-01-19 16:05 +0000
Re: web Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2025-01-19 19:15 +0000
Re: web Ben Collver <bencollver@tilde.pink> - 2025-01-20 15:37 +0000
Re: web Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2025-01-24 18:45 +0000
Re: web news@zzo38computer.org.invalid - 2025-01-20 11:23 -0800
Re: web Dave Yeo <dave.r.yeo@gmail.com> - 2025-01-16 18:04 -0800
Re: terminal only for two weeks Bozo User <anthk@disroot.org> - 2025-01-12 23:01 +0000
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2024-12-05 06:34 +0042
Re: terminal only for two weeks yeti <yeti@tilde.institute> - 2025-01-16 11:42 +0042
Re: terminal only for two weeks Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2024-11-28 12:45 +0200
Re: terminal only for two weeks Bozo User <anthk@disroot.org> - 2025-01-12 23:01 +0000
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-01-12 22:03 -0300
Re: terminal only for two weeks D <nospam@example.net> - 2025-01-13 10:48 +0100
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-01-13 16:24 -0300
Re: terminal only for two weeks D <nospam@example.net> - 2025-01-14 18:50 +0100
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-01-15 22:10 -0300
Re: terminal only for two weeks Rich <rich@example.invalid> - 2025-01-16 04:15 +0000
Re: terminal only for two weeks Computer Nerd Kev <not@telling.you.invalid> - 2025-01-16 15:58 +1000
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-21 05:31 +0000
Re: terminal only for two weeks Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2025-01-23 19:33 +0000
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-02-12 13:12 -0300
Re: terminal only for two weeks Jerry Peters <jerry@example.invalid> - 2025-02-16 20:55 +0000
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-02-16 22:54 -0300
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-02-16 22:56 -0300
Re: terminal only for two weeks Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-17 03:41 +0000
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-02-19 13:02 -0300
Re: terminal only for two weeks kludge@panix.com (Scott Dorsey) - 2025-02-17 22:18 +0000
Re: terminal only for two weeks Salvador Mirzo <smirzo@example.com> - 2025-02-19 13:03 -0300
csiph-web