Hacker News API VS hackernews

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.

From looking at the Hacker News API, you might be able to use that instead of scraping from the DOM: https://github.com/HackerNews/API#users

You just need to make 38 million requests to the Firebase API document here https://github.com/HackerNews/API. :-)

I actually made many more than that because I screwed up a few times. Might clean up the compiled data and put it on Kaggle (GitHub? Torrent?), or anywhere else if people have suggestions.

this might help a little: https://github.com/wting/hackernews

I think it's a ratio of votes to time. I think as little as 4 votes can get something on the homepage if they come in fairly quickly.

The source code for hn is available if you want to go and look up the specifics. I'm not sure if this is the most up-to-date mirror, but the site doesn't change that often: https://github.com/wting/hackernews

Might not count as modern, but the original Reddit and HackerNews codebases:

- https://github.com/reddit-archive/reddit1.0

- https://github.com/wting/hackernews (actually news.arc, based on old hn)

There's also this https://github.com/wting/hackernews -- which is a version of the source code to the site from sometime in the past.

"Otherwise" was the operative word in my (slightly sarcastic) example. :)

Avoiding all caps words means you sometimes have to go back and change "FAA" back from "Faa".

HN's software is no longer open source, but at one time, this is how it processed titles on initial submission: https://github.com/wting/hackernews/blob/master/news.arc#L15...

And at any rate, #1 on HN is not the product of any simple rule like "most upvotes per unit time with some decay function applied." There is significant judgment in expressed in the way that stories are ranked. The sourcecode as of 2012 was enough to demonstrate this, but in my understanding yet more judgment has been applied since then.

https://github.com/wting/hackernews/blob/master/news.arc

"ad-hoc filesystem based solution" is the closest of your definitions, I think. Last time I saw/heard, HN was built in Arc, a Lisp dialect, and use(s/d) a variant of this (mirrored) code: https://github.com/wting/hackernews

Check out around this area of the code to see how simple it is. All just plain files. A database, of sorts, but not in the way you might be expecting: https://github.com/wting/hackernews/blob/master/news.arc#L16...

There is a modern maintained variant at https://github.com/arclanguage/anarki/tree/master/apps/news as well.

File syncing between machines is pretty much an easily solved problem. I don't know how they do it, but it could be something like https://syncthing.net/ or even some scripting with `rsync`. Heck, a cronned `tar | gzip | scp` might even be enough for an app whose data isn't exactly mission critical.

The old version in arc, mirrored at https://github.com/wting/hackernews/blob/5a3296417d23d1ecc90..., uses the file system as a database.

https://github.com/wting/hackernews/blob/5a3296417d23d1ecc90... shows the monotonically increasing number:

  (def new-item-id ()