Alternatives
Products that do what An analysis of the complete HN history with command line tools only does
- 1AG
2019 · github.com
- 2BE
2019 · github.com
- 3HL
2015 · 2ton.com.au
- 4HT
2016 · hnlive.tk
- 5EH
2024 · blog.wilsonl.in
- 6MA
2018 · github.com
- 7QAQ&A for HN users▲142
2012 · askolo.com
- 8WA
2015 · github.com
- 9HA
2018 · github.com
- 10UA
2019 · github.com
- 11HA
2019 · github.com
- 12UH
2014 · github.com
- 13SA
2014 · github.com
- 14HA
This project is a tool for engineers who live in the terminal and are tired of losing their command history to ephemeral servers or fragmented `.bash_history` files. If you’re jumping between dozens of boxes, many of which might be destroyed an hour later, your "local memory" (the history file) is essentially useless. This tool builds a centralized, permanent brain for your shell activity, ensuring that a complex one-liner you crafted months ago remains accessible even if the server it ran on is long gone. The core mechanism wants to be a "zero-touch" capture that happens at the connection…
Jan 2026 · github.com
- 15SS
2013 · github.com
- 16AA
2018 · github.com
- 17HT
2013 · 41j.com
- 18WA
2017 · github.com
- 19TA
2017 · flaque.github.io
- 20AI
2021 · github.com
- 21HD
2016 · udocz.com
- 22HA
2020 · github.com
- 23AB
2015 · j-vdh.blogspot.com
- 24HN
2015 · hackernews.im
Ranked by how close each launch is in meaning, then by votes. Refine with a description →