←back to thread

Ask HN: Is it time to fork HN into AI/LLM and "Everything else/other?"

469 points bookofjoe | 2 comments | 15 Jul 25 14:51 UTC | HN request time: 0.412s | source

I would very much like to enjoy HN the way I did years ago, as a place where I'd discover things that I never otherwise would have come across.

The increasing AI/LLM domination of the site has made it much less appealing to me.

Show context
simonw ◴[15 Jul 25 15:11 UTC] No.44571983[source]▶
I built you this: https://tools.simonwillison.net/hacker-news-filtered

It shows you the Hacker News page with ai and llm stories filtered out.

You can change the exclusion terms and save your changes in localStorage.

o3 knocked it out for me in a couple of minutes: https://chatgpt.com/share/68766f42-1ec8-8006-8187-406ef452e0...

Initial prompt was:

  Build a web tool that displays the Hacker
  News homepage (fetched from the Algolia API)
  but filters out specific search terms,
  default to "llm, ai" in a box at the top but
  the user can change that list, it is stored
  in localstorage. Don't use React.
Then four follow-ups:

  Rename to "Hacker News, filtered" and add a
  clear label that shows that the terms will
  be excluded

  Turn the username into a link to
  https://news.ycombinator.com/user?id=xxx -
  include the comment count, which is in the
  num_comments key

  The text "392 comments" should be the link,
  do not have a separate thread link

  Add a tooltip to "1 day ago" that shows the
  full value from created_at
replies(21): >>44572045 #>>44572051 #>>44572058 #>>44572072 #>>44572117 #>>44572167 #>>44572402 #>>44572709 #>>44573004 #>>44573505 #>>44573595 #>>44574229 #>>44574695 #>>44574746 #>>44574897 #>>44575009 #>>44575796 #>>44575863 #>>44576014 #>>44576896 #>>44578374 #
1. heavyset_go ◴[16 Jul 25 03:21 UTC] No.44578374[source]▶
Almost certain you can use the HN Algolia to do the same thing by excluding terms
replies(1): >>44578927 #
2. simonw ◴[16 Jul 25 05:19 UTC] No.44578927[source]▶
I had to switch away from Algolia - the problem is they only model "show items on the homepage" using a tag that's automatically applied to exactly 30 items, which means any filtering knocks that down to eg 15.

I switched to using the older firebase API which can return up to 500 item IDs from the current (paginated) homepage - then I fetch and filter details of the first 200.

https://github.com/simonw/tools/commit/ccde4586a1d95ce9f5615...