SBF's Lawyer Scrambles to Explain Signal Messages to Potential Witnesses [pdf]

It's kind of like "urlview" or "fzf" but smaller, less sophisticated and less complicated. It extracts URLs from an HTTP proxy log and puts a selection into the clipboard buffer. There's a list of URLs and one makes a selection from the list by indicating a line number.

I have recently begin using another script that periodically extracts all URLs I want to save from the log, i.e., excludes ones I do not want to save, and adds them to a simple HTML file (it also extracts other stuff I want to save to other files such as POST payloads), then it clears the log. This way I have a browseable URL history stored outside the browser.

The old way I did things was to use the log directly for getting URLs but I am trying to now get used to using these other files as a source for URLs.

I do not use X11 or other similar graphics layer. Consequently, I do not use a so-called "modern" browser. Everything is done in textmode. I use a 1.3M text-only browser static binary to read simple HTML files. I have utilities to convert back and forth from list of URLs to simple HTML. I use the simple HTML format for saving continued web search results as well, i.e., up to several hundred results per query from an array of search engines combined into a single simple HTML file named according to the query string. All these results files are stored in a searchable directory.

Whether any of this is "fun" depends on personal opinion but using an enormous, insanely overcomplicated "tech" company browser that's an ever-growing hassle to modify and re-compile is "not fun" IMO and so, for me, this is better.