Hi everyone, this is my second "Show HN" submission posted in Hacker News. The first one was https://github.com/aome510/hackernews-TUI. I received a lot of good feedbacks and suggestions from the community back then. For the second one, I also look forward to hearing the community's opinions.
A bit background on the project: I started `hackernews-tui` and after that `spotify-player` (both are terminal application) because I want to learn Rust and build applications with Rust which I'm able to use daily.
`spotify-player` is a terminal application that can be used as either a remote player to control another Spotify client or a local player with an integrated Spotify client. So if you already know spotify-tui[1] or ncspot[2], `spotify-player` is kinda a simplified combination of both =).
> something that cuts out all layout, formatting and images and shows me the raw article text in a fixed with font.
FYI, I have implemented a reader view for `hackernews_tui v0.6.0` [0] which seems to satisfy most of the conditions above. Judging from my experience, this reader view works quite well and can cover many use cases.
Really hope to see Emacs get more attention after `native-comp` branch merged to master.
Recently, I have switched to Emacs full-time (first spacemacs[0], now doom[1]). So far, it has been a great experience. Spacemacs is a bit slow but with doom and `native-comp`, I rarely encounter any performance issues.
I just played around with newspaper3k today, and it works really well out of the box.
I plan to add support for article view reader mode with newspaper3k integration. My current approach is to create a child process with `std::Process:Command` then run a python script. Doesn't seem to be the best approach, but I guess it's the easiest one.
> It's actually more than that: when there are lots of sub-comments, it helps to see the immediate "mother" of the comment node you're reading. Imagine a comment that has two replies, and the first reply has dozens and dozens of sub-replies and sub-sub-replies, which typically veer into all sorts of adjacent issues. By the time I'm done with the 1st reply and its dozens and dozens of sub-replies, it is often unclear what the initial comment (or even topic) was. It is then very helpful to be able to glance back up to the initial comment across the now-collapsed first reply and its dozens and dozens of sub-replies, before reading reply #2. Simply navigating to reply #2 doesn't give you that.
I think I get what you mean. Instead of adding 3 different collapse commands, WDYT about adding one command to collapse the current comment and one command to move up to the parent comment?
> I mean this page of the HN site: https://news.ycombinator.com/active . It has the currently actively discussed stories, and is a great way to catch up after not reading HN for a day or two. A kind of intermediate step between best ( https://news.ycombinator.com/best ) and the homepage.
Interesting, I don't know `/best` and `/active` exist. `/best` seems to be a list of stories (up to past 4 days) sorted by `points`.
`/active`, on the other hand, and `/news` as well are quite weird. I don't really know the algorithm behind the order of sorting submissions in those.
In the meantime, I guess open the `Story View - All stories` with `sort_by=popularity` and `time_range=past 24 hours` might do the job.
> 1. collapsable threads, ideally with three different shortcuts: (i) collapse daughters of current comment, (ii) collapse mother of current comment - this is very useful when on the Nth comment far away below the mother comment, so no need to scroll up, but can continue reading the sister of mother's comment, (iii) collapse entire thread.
Please correct me if I misunderstand your request. I guess what you want is navigating between sibling comments right? It seems that most of the use cases you mention above can be done with a combination of `l` (move to the next sibling) and `h` (move the previous sibling) commands.
> 2. A story view for the /active section. I think there is no official API for it, but I find it to be the most useful entrypoint into HN at the beginning of the day, to catch up.
I don't really get this feature. Can you elaborate more?
> 3. Semi-offtopic dreamland: a version adapted to (a terminal in) the remarkable and related tablets :)
Yeah, I also would love to achieve this, but supporting tablets seems to be quite painful experience :<.
If I understand correctly, Algolia front-page API[0] only allows you to get at most 34 stories (either with `sort_by` points or submitted date).
Hacker News official APIs[1], on the other hands, use a specific algorithm to determine the ranking of submissions and allow you to get at most 500 stories.
update: add `?` as a hotkey to open the help dialog in the new version `v0.5.1`. It seems that many feel more comfortable using `?` than `<ctrl-h>/<alt-h>` as the default hotkey.
I just realize that you are the author of https://github.com/ggerganov/hnterm. I just came across with it recently while finding some HackerNews apps on GitHub. If I understand correctly, `hnterm` seems to use the official Hacker news API for rendering. I found it quite hard to use compared to the HN Algolia APIs. Do you have any suggestions on how to utilize the official APIs better?
Yeah, I was thinking the same thing. The main reason I didn't add `?` in the first place because I want users to be able to open the help menu while typing in the Search View.
Edit: it seems to work now.