frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Frontier AI agents violate ethical constraints 30–50% of time, pressured by KPIs

https://arxiv.org/abs/2512.20798
249•tiny-automates•5h ago•157 comments

Rust implementation of Mistral's Voxtral Mini 4B Realtime runs in your browser

https://github.com/TrevorS/voxtral-mini-realtime-rs
204•Curiositry•7h ago•21 comments

Discord will require a face scan or ID for full access next month

https://www.theverge.com/tech/875309/discord-age-verification-global-roll-out
1626•x01•18h ago•1548 comments

Brutalist Southbank Centre Listed

https://www.architectsjournal.co.uk/news/brutalist-southbank-centre-finally-listed-after-35-years...
18•daverol•2h ago•19 comments

Pure C, CPU-only inference with Mistral Voxtral Realtime 4B speech to text model

https://github.com/antirez/voxtral.c
129•Curiositry•7h ago•9 comments

Why is the sky blue?

https://explainers.blog/posts/why-is-the-sky-blue/
572•udit99•17h ago•189 comments

Converting a $3.88 analog clock from Walmart into a ESP8266-based Wi-Fi clock

https://github.com/jim11662418/ESP8266_WiFi_Analog_Clock
494•tokyobreakfast•16h ago•161 comments

Discord Alternatives, Ranked

https://taggart-tech.com/discord-alternatives/
201•pseudalopex•14h ago•86 comments

Hard-braking events as indicators of road segment crash risk

https://research.google/blog/hard-braking-events-as-indicators-of-road-segment-crash-risk/
277•aleyan•16h ago•405 comments

Is particle physics dead, dying, or just hard?

https://www.quantamagazine.org/is-particle-physics-dead-dying-or-just-hard-20260126/
114•mellosouls•9h ago•171 comments

Luce: First Electric Ferrari

https://www.ferrari.com/en-US/auto/ferrari-luce
174•kaizenb•13h ago•176 comments

LiftKit – UI where "everything derives from the golden ratio"

https://www.chainlift.io/liftkit
165•peter_d_sherman•11h ago•96 comments

The original vi is a product of its time (and its time has passed)

https://utcc.utoronto.ca/~cks/space/blog/unix/ViIsAProductOfItsTime
14•ingve•2d ago•17 comments

Sandboxels

https://neal.fun/sandboxels/
280•2sf5•17h ago•35 comments

Eight more months of agents

https://crawshaw.io/blog/eight-more-months-of-agents
126•arrowsmith•1d ago•134 comments

America has a tungsten problem

https://www.noleary.com/blog/posts/1
168•noleary•12h ago•159 comments

Upcoming changes to Let's Encrypt and how they affect XMPP server operators

https://blog.prosody.im/2026-letsencrypt-changes/
114•zaik•12h ago•112 comments

LLMs as Language Compilers: Lessons from Fortran for the Future of Coding

https://cyber-omelette.com/posts/the-abstraction-rises.html
50•birdculture•2d ago•13 comments

Game Theory Patterns at Work (2016)

https://daeus.blog/2026/01/18/game-theory-patterns-at-work/
82•kurinikku•12h ago•6 comments

UEFI Bindings for JavaScript

https://codeberg.org/smnx/promethee
220•ananas-dev•19h ago•108 comments

MIT Technology Review has confirmed that posts on Moltbook were fake

https://www.technologyreview.com/2026/02/06/1132448/moltbook-was-peak-ai-theater/
72•helloplanets•1d ago•25 comments

Zulip.com Values

https://zulip.com/values/
40•nothrowaways•8h ago•6 comments

Stop using icons in data tables

https://medium.com/@codythistleward/stop-using-icons-in-data-tables-7537af18ea0d
108•ctward•4d ago•48 comments

Thoughts on Generating C

https://wingolog.org/archives/2026/02/09/six-thoughts-on-generating-c
223•ingve•19h ago•75 comments

Generative Pen-Trained Transformer

https://theodore.net/projects/Polargraph/
40•Twarner•4d ago•0 comments

Ask HN: What are you working on? (February 2026)

280•david927•1d ago•942 comments

Another GitHub outage in the same day

https://www.githubstatus.com/incidents/lcw3tg2f6zsd
329•Nezteb•14h ago•246 comments

Game Boy Advance Audio Interpolation

https://jsgroth.dev/blog/posts/gba-audio-interpolation/
92•ibobev•15h ago•38 comments

Everyone’s building “async agents,” but almost no one can define them

https://www.omnara.com/blog/what-is-an-async-agent-really
50•kmansm27•15h ago•39 comments

Expansion Microscopy Has Transformed How We See the Cellular World

https://www.quantamagazine.org/expansion-microscopy-has-transformed-how-we-see-the-cellular-world...
83•sohkamyung•4d ago•4 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?