HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wting
hackernews
Arc2013–2026
wting / hackernews

hackernews

Hacker News web site source code mirror.

90Distinct people
99Mentions
0Explicit recommenders
656GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Hacker News web site source code mirror.

GitHub

Where it is used

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

What people are saying

No recommendation phrase was found in the indexed comments.

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, 1:57:11 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 year99 dated mentions

Observed mentions: 2013-01-04 06:10:04 UTC to 2026-03-02 19:38:40 UTC.

0510152013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 16 mentions; 0 submissions, 16 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC16016
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC14014
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC12111
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC808
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC909
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
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 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC918
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC707
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC514
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Note Instructions copied from the original download site. The files from the tarball in step 2 have been copied into this repository. Original Instructions Install version 372 of MzScheme. (Don't use the latest version. Versions after 372 made lists immutable.) Get http://ycombinator.com/arc/arc3.tar and untar it. Type mzscheme -m -f as.scm and you should get an Arc prompt. If you ^C an Arc program, you'll get the Scheme REPL. Use (tl) to get back to the Arc REPL. If you have questions or suggestions, post them on the forum.
Read the full README on GitHub

What Hacker News says

8 sources
...the "destroying" part seems like a pretty good thing imho. Setting some forests on fire to make room for some new sprouts seems pretty appealing :) "Community destruction" in the online landscape is pretty much a synonym for "pushing people towards better communities where they are better off anyway"... So a good thing. (And I don't see the place of Wikipedia and donations in this. Wikipedia is obviously not selling any in-app purchases and the software they run on is "open source". HN is also "true free". Even their platform is open-source: https://github.com/wting/hackernews not that this should count that much. And donations are obvious not profit, they are not even taxed as such. No ambiguity here.)
In The web's original sin
> but right on the policy: not only did you not make it up, it's in the FAQ! Linked at bottom of every page. Haha, my bad! I actually did try to search around for it, but it didn't occur to me to check the FAQ. I even checked the github mirror of the code [0] (no idea how up-to-date it is), but I can't read Arc very well. It just goes to show you could probably plaster rules like that as a header over the entire website and people like myself would still look in the wrong place :P I have read the FAQ before, so that's probably where I "heard it", but I didn't think to check it this time. [0] https://github.com/wting/hackernews
In Dragula: Drag and drop so simple it hurts
The voting code in the copy of Arc HN runs is not public (the rest of it is - https://github.com/wting/hackernews/blob/master/news.arc) because apparently business decisions are made off of it and it would be trivial to game it. That said, I'm fairly certain it involves some kind of "keep the ball afloat" algorithm, where more upvotes in a smaller time period gives it a higher internal score than a slower sequence of upvotes would. This post has been upvoted very slowly, and I theorise this is why it's on page >2.
In Tell HN: I’d like to sponsor your passion project

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.