HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
reddit-archive
reddit
Python2010–2024
reddit-archive / reddit · Archived

reddit

historical code from reddit.com

Web Development
Explore on GitHubRead Hacker News discussions
148Distinct people
170Mentions
3Explicit recommenders
16.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

historical code from reddit.com

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

If you use Python for anything remotely performance sensitive, I highly recommend giving Cython a shot. The trick is to find your computation-intensive inner loop stuff, move…

ketralnis used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:02:26 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year170 dated mentions

Observed mentions: 2010-07-01 14:04:07 UTC to 2024-01-01 19:05:34 UTC.

05101520252010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 21 mentions; 2 submissions, 19 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 18 mentions; 3 submissions, 15 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 25 mentions; 6 submissions, 19 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 19 mentions; 0 submissions, 19 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 24 mentions; 1 submissions, 23 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC202
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC808
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC21219
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC18315
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC25619
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC13112
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC13112
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC19019
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1019
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC808
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC24123
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

18 sources
shadowmint·Dec 10, 2013
So, a massively, massively popular site that makes it business by ranking the user generated content on it by importance... is wrong. > Maybe there is no moral. Reddit screwed up. ...or maybe, they know what they're doing. Maybe not. ...but when you supply a bugfix, the onus is on the submitter to demonstrate that 1) the fix fixes the problem and 2) that it doesn't break anything else. It would appear that no effort has been made at (2), to demonstrate that the proposed change would not have an adverse affect on other high-vote rankings. To be fair, it would have been nice to see the pull request response (https://github.com/reddit/reddit/pull/583) mention that an alternative algorithm choice would have to be demonstrably better in a large scale analysis before they would even dream of changing their core ranking algorithm, but it's not u
Read the rest
nfair for them to take that stance. It's like asking Google to change their page rank algorithm because you don't like it.
In Reddit’s empire is founded on a flawed algorithm
jedberg·Dec 2, 2013Submission

How reddit tried to solve the "new link" problem. Why HN doesn't need a new algo

This morning I saw two articles on the front page about how HN should change their algorithms. I would contend that an algo change is not the right solution. Here is what we did to try and solve the problem on reddit. First, there is the "organic" box at the top of the page. The first link in that box is always an ad, but after that, it shows pseudo random links from the new page (more on that in a second): https://github.com/reddit/reddit/blob/89f6f1ad9c1babbf520b83c49fa27f509bb5d0ef/r2/… What this does is give exposure to up and coming links to a lot of people all at once, which helps overcome the luck factor of who is looking at the new page at any given time. The second solution is the "rising" sort on the new page: https://github.com/reddit/reddit/blob/89f6f1ad9c1babbf520b83c49fa27f509bb5d0ef/r2/… The
Read the rest
rising sort accounts for how many times the link has been shown in its ranking algo, which helps better new links rise to the top. The organic box on the front page uses this rising ranking to choose what is in the box, and also contributes to the view counts. So I would humbly suggest that HN should do as it has done often in the past, and copy reddit's solution here by implementing the rising sort and the organic box.
198 points · Open discussion
xSwag·May 2, 2013
The HN "basic" source code is available online[1] or if you're looking for something modern, try Telescope which is built in Node and the Meteor framework[2]. There is also a demo available[3] Or you could try forking the Reddit source code[4] and setting it up, but im not sure if you'll need multiple subreddits functionality. [1]https://github.com/wting/hackernews [2]http://telesc.pe/ [3]http://demo.telesc.pe/ [4]https://github.com/reddit/reddit
In Ask HN: How to build a Hacker-News-like website using Wordpress?

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.