dot_files VS Hacker News API

I tend to use jq a lot. As others have said, sometimes jq can be hard to grasp. Often it requires multiple attempts to get the correct answer. To make it a little easier for me, I've written a helper function[0] that combines it with fzf[1] to run jq as a REPL on any json. It allows to incrementally alter your DSL without having to continually call jq. This is similar to jid/jiq but a little more powerful. It includes functions to change the preview to output raw, compact (or not), and some other things.

I didn't use jid/jiq because jid uses go-simplejson, which is nowhere near as powerful as jq, and jiq seemed very buggy when I used it and it felt like it was hacked together. Plus there was no where to change jq's arguments while running it.

I'm sure this function can be improved on, but this has been good enough for me so far.

Also, I run gojq[2] instead of jq. It is a drop-in replacement for jq but is written in Go, and has some improvements over jq such as bug fixes, support for yaml input, and it also provides more helpful error messages.

[0] https://github.com/hoshsadiq/dot_files/blob/master/zshrc.d/m...

I built a plugin that allows Coze bots to make requests to the Hacker News API.

I recognise the huge amounts of effort involved in this and I applaud the moderators for keeping HN an interesting place to be.

That said, I think it's reasonable for us to have visibility on their manual interventions, and this could be easily surfaced via the Hacker News API (https://github.com/HackerNews/API), if the Story JSON included the values of "contro," "bury," and "gag" fields, which are currently opaque to users of the API

See https://medium.com/hacking-and-gonzo/how-hacker-news-ranking... for more discussion on terminology

Google probably stopped updating BigQuery when they started hosting live Hacker News data in Firebase: https://github.com/HackerNews/API

The live nature of the Firebase data is awesome, but the lack of ability to query is a loss.

Nice work! I did something similar with a personal project a few months ago using an open source llm. Also, not sure if you know, there is an api you can use. https://github.com/HackerNews/API

Hi HN, I made a live feed for viewing all of the new items on Hacker News in almost-realtime. It is a single, modern HTML file that doesn't use polling.

It works by establishing a websocket connection to the Hacker News Firebase database, to receive updates every time the HN server updates Firebase, which is about once every 30 seconds. This is very efficient, putting no load on HN's server and using minimal bandwidth.

To make the feed continuous despite the delay, it waits to display each item until exactly 30 seconds before displaying it. I think this is a fair tradeoff, it gives you a sense of how active HN is. For comparision, there are something like 6-7 thousand tweets every second.

Official HN Firebase API: https://github.com/HackerNews/API

Source code: https://github.com/jerbear2008/hn-live/blob/main/index.html

You could use the API: https://github.com/HackerNews/API

You can now get Hacker News data in real time from the Hacker News API powered by Firebase: https://github.com/HackerNews/API

This is great (real time!), but also kind of a pain (38+ millions individual http requests to get the whole thing).

Thankfully there's no authentication or apparent rate limiting. I fumbled my way through downloading the whole thing with curl. I screwed up a few times so made over 70 million requests in total.

Toy analysis of the data I downloaded here: https://public.tableau.com/app/profile/isna/viz/HackerNewsDa...

Get your submissions from this API

https://hacker-news.firebaseio.com/v0/user/ohjeez.json?print...

and then scan the "submitted" articles as described here

https://github.com/HackerNews/API

I have a crawler that sucks down all the posts from HN and then I read it into Pandas and write all sorts of queries. The boggle I have now is that I want to use the same system to (1) make sure YOShInOn never submits duplicate articles, and (2) have accurate vote and comment scores. (1) requires picking up articles as soon as possible, (2) requires waiting two weeks or so until the scores have settled down to what they are going to be. I guess I gotta come back and rescan things in 2 weeks so I have the right scores.