Hacker News new | ask | show | jobs
by TeMPOraL 920 days ago
Then again, it's hacker news. If the audience of this site won't individually hack the UX to match their preferences, who will?
2 comments

With that logic, why not just provide an API. Everybody just hack together their own client. Being a hacker doesn't mean you never get to benefit from prior work, or never work together on something, or never share your work.

I get the appeal of providing a minimal service like HN, but unless I'm missing something, my proposed change is an absolute no-brainer considering it's effort-reward ratio.

<https://github.com/HackerNews/API>

Linked under "API" at the bottom of the page you're reading now.

Emphasis was on "just", as in: no web client.
That seems an unreasonable expectation.

There are and were message- and discussion-oriented protocols, most notably Usenet, of which you may be aware there were some persistent issues:

<https://news.ycombinator.com/item?id=36194941>

<https://web.archive.org/web/20220321105208/https://old.reddi...>

The thought's occurred to me that among the conspicuous omissions from the HTML spec is of a threaded discussion (or more specifically, messages within a threaded context) as a first-order object, permitting arbitrary structuring of that content at the volition of the reader.

Though on reflection: if you're really interested in a technical discussion site, the speedbump of needing to code (or at least install) your own client might make for an interesting form of gating.

To that extent, your suggestion's somewhat growing on me.

Or search:

<https://duckduckgo.com/?t=ftsa&q=alternative+hacker+news+fro...>

"Alternative hacker news front ends".