frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

GPTZero finds 100 new hallucinations in NeurIPS 2025 accepted papers

https://gptzero.me/news/neurips/
481•segmenta•4h ago•258 comments

Why does SSH send 100 packets per keystroke?

https://eieio.games/blog/ssh-sends-100-packets-per-keystroke/
48•eieio•39m ago•26 comments

Show HN: isometric.nyc – giant isometric pixel art map of NYC

https://cannoneyed.com/isometric-nyc/
245•cannoneyed•3h ago•77 comments

It looks like the status/need-triage label was removed

https://github.com/google-gemini/gemini-cli/issues/16728
191•nickswalker•3h ago•53 comments

Qwen3-TTS Family Is Now Open Sourced: Voice Design, Clone, and Generation

https://qwen.ai/blog?id=qwen3tts-0115
295•Palmik•6h ago•87 comments

CSS Optical Illusions

https://alvaromontoro.com/blog/68091/css-optical-illusions
65•ulrischa•2h ago•7 comments

I was banned from Claude for scaffolding a Claude.md file?

https://hugodaniel.com/posts/claude-code-banned-me/
132•hugodan•1h ago•95 comments

Tree-sitter vs. Language Servers

https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/
161•ashton314•5h ago•43 comments

Recent discoveries on the acquisition of the highest levels of human performance

https://www.science.org/doi/abs/10.1126/science.adt7790
31•colincooke•2h ago•4 comments

Mote: An Interactive Ecosystem Simulation [video]

https://www.youtube.com/watch?v=Hju0H3NHxVI
37•evakhoury•21h ago•2 comments

Launch HN: Constellation Space (YC W26) – AI for satellite mission assurance

https://constellation-io.com/
20•kmajid•3h ago•3 comments

AnswerThis (YC F25) Is Hiring

https://www.ycombinator.com/companies/answerthis/jobs/r5VHmSC-ai-agent-orchestration
1•ayush4921•3h ago

Design Thinking Books (2024)

https://www.designorate.com/design-thinking-books/
240•rrm1977•8h ago•111 comments

In Europe, Wind and Solar Overtake Fossil Fuels

https://e360.yale.edu/digest/europe-wind-solar-fossil-fuels
388•speckx•5h ago•410 comments

Show HN: BrowserOS – "Claude Cowork" in the browser

https://github.com/browseros-ai/BrowserOS
17•felarof•3h ago•9 comments

ISO PDF spec is getting Brotli – ~20 % smaller documents with no quality loss

https://pdfa.org/want-to-make-your-pdfs-20-smaller-for-free/
123•whizzx•9h ago•71 comments

Keeping 20k GPUs Healthy

https://modal.com/blog/gpu-health
21•jxmorris12•4d ago•5 comments

30 Years of ReactOS

https://reactos.org/blogs/30yrs-of-ros/
215•Mark_Jansen•12h ago•113 comments

How LLM agents solve the table merging problem

https://futuresearch.ai/deep-merge-tutorial/
10•ddp26•45m ago•2 comments

TTY and Buffering

https://mattrighetti.com/2026/01/12/tty-and-buffering
22•mattrighetti•5d ago•3 comments

Your brain on ChatGPT: Accumulation of cognitive debt when using an AI assistant

https://www.media.mit.edu/publications/your-brain-on-chatgpt/
578•misswaterfairy•21h ago•420 comments

Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

https://huggingface.co/sweepai/sweep-next-edit-1.5B
495•williamzeng0•20h ago•107 comments

Doctors in Brazil using tilapia fish skin to treat burn victims

https://www.pbs.org/newshour/health/brazilian-city-uses-tilapia-fish-skin-treat-burn-victims
250•kaycebasques•14h ago•80 comments

Show HN: Synesthesia, make noise music with a colorpicker

https://visualnoise.ca
7•tevans3•14h ago•2 comments

Show HN: Interactive physics simulations I built while teaching my daughter

https://www.projectlumen.app/
59•anticlickwise•3d ago•14 comments

Joe Armstrong and Jeremy Ruston – Intertwingling the Tiddlywiki with Erlang [video]

https://www.youtube.com/watch?v=Uv1UfLPK7_Q
36•kerim-ca•2d ago•3 comments

The mushroom making people hallucinate tiny humans

https://www.bbc.com/future/article/20260121-the-mysterious-mushroom-that-makes-you-see-tiny-people
79•1659447091•9h ago•38 comments

eBay explicitly bans AI "buy for me" agents in user agreement update

https://www.valueaddedresource.net/ebay-bans-ai-agents-updates-arbitration-user-agreement-feb-2026/
295•bdcravens•22h ago•315 comments

In Praise of APL (1977)

https://www.jsoftware.com/papers/perlis77.htm
85•tosh•11h ago•52 comments

Threat actors expand abuse of Microsoft Visual Studio Code

https://www.jamf.com/blog/threat-actors-expand-abuse-of-visual-studio-code/
268•vinnyglennon•19h ago•266 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•8mo ago

Comments

balloob•8mo ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•8mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•8mo ago
Comments moved thither. Thanks!
pabs3•8mo ago
They are two different articles, I don't think that was correct.
tomhow•8mo ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•8mo ago
Thanks for the response, guess that makes sense.
pabs3•8mo ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?