frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Pebble Production: February Update

https://repebble.com/blog/february-pebble-production-and-software-updates
75•smig0•2h ago•22 comments

C++26: Std:Is_within_lifetime

https://www.sandordargo.com/blog/2026/02/18/cpp26-std_is_within_lifetime
23•ibobev•57m ago•7 comments

Don't Trust the Salt: AI Summarization, Multilingual Safety, and LLM Guardrails

https://royapakzad.substack.com/p/multilingual-llm-evaluation-to-guardrails
108•benbreen•2d ago•30 comments

Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app

https://github.com/fjrevoredo/mini-diarium
62•holyknight•2h ago•38 comments

Paged Out Issue #8 [pdf]

https://pagedout.institute/download/PagedOut_008.pdf
63•SteveHawk27•2h ago•9 comments

Bridging Elixir and Python with Oban

https://oban.pro/articles/bridging-with-oban
49•sorentwo•3h ago•7 comments

Coding Tricks Used in the C64 Game Seawolves

https://kodiak64.co.uk/blog/seawolves-technical-tricks
26•atan2•2h ago•3 comments

The Mongol Khans of Medieval France

https://www.historytoday.com/archive/feature/mongol-khans-medieval-france
53•Thevet•2d ago•14 comments

-fbounds-safety: Enforcing bounds safety for C

https://clang.llvm.org/docs/BoundsSafety.html
21•thefilmore•3d ago•11 comments

Show HN: A physically-based GPU ray tracer written in Julia

https://makie.org/website/blogposts/raytracing/
56•simondanisch•3h ago•24 comments

Sizing chaos

https://pudding.cool/2026/02/womens-sizing/
690•zdw•17h ago•374 comments

Famous Signatures Through History

https://signatory.app/#famous-signatures
10•elliotbnvl•55m ago•7 comments

27-year-old Apple iBooks can connect to Wi-Fi and download official updates

https://old.reddit.com/r/MacOS/comments/1r8900z/macos_which_officially_supports_27_year_old/
390•surprisetalk•17h ago•222 comments

Voith Schneider Propeller

https://en.wikipedia.org/wiki/Voith_Schneider_Propeller
39•Luc•3d ago•10 comments

Old School Visual Effects: The Cloud Tank (2010)

http://singlemindedmovieblog.blogspot.com/2010/04/old-school-effects-cloud-tank.html
55•exvi•8h ago•7 comments

15 years of FP64 segmentation, and why the Blackwell Ultra breaks the pattern

https://nicolasdickenmann.com/blog/the-great-fp64-divide.html
152•fp64enjoyer•12h ago•53 comments

Ask HN: How do you employ LLMs for UI development?

19•jensmtg•40m ago•10 comments

Cosmologically Unique IDs

https://jasonfantl.com/posts/Universal-Unique-IDs/
432•jfantl•20h ago•129 comments

Step 3.5 Flash – Open-source foundation model, supports deep reasoning at speed

https://static.stepfun.com/blog/step-3.5-flash/
146•kristianp•12h ago•56 comments

DOGE Track

https://dogetrack.info/
125•donohoe•2h ago•43 comments

Tailscale Peer Relays is now generally available

https://tailscale.com/blog/peer-relays-ga
437•sz4kerto•21h ago•214 comments

Anthropic officially bans using subscription auth for third party use

https://code.claude.com/docs/en/legal-and-compliance
495•theahura•11h ago•591 comments

Lilush – LuaJIT static runtime and shell

https://lilush.link/
33•ksymph•2d ago•6 comments

Zero-day CSS: CVE-2026-2441 exists in the wild

https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_13.html
355•idoxer•22h ago•201 comments

Virgins, Unicorns and Medieval Literature (2017)

https://www.bowdoin.edu/news/2017/11/virgins-unicorns-and-medieval-literature.html
6•mooreds•2d ago•4 comments

How to choose between Hindley-Milner and bidirectional typing

https://thunderseethe.dev/posts/how-to-choose-between-hm-and-bidir/
120•thunderseethe•3d ago•39 comments

UK to force social media to remove abusive pics in 48 hours

https://www.theregister.com/2026/02/19/uk_intimate_images_online/
34•beardyw•2h ago•39 comments

Visualizing the ARM64 Instruction Set (2024)

https://zyedidia.github.io/blog/posts/6-arm64/
57•userbinator•3d ago•11 comments

ShannonMax: A Library to Optimize Emacs Keybindings with Information Theory

https://github.com/sstraust/shannonmax
21•sammy0910•3h ago•3 comments

A word processor from 1990s for Atari ST/TOS is still supported by enthusiasts

https://tempus-word.de/en/index
73•muzzy19•2d ago•37 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

balloob•9mo 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•9mo ago
Discussion for the other article in the series:

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

tomhow•9mo ago
Comments moved thither. Thanks!
pabs3•9mo ago
They are two different articles, I don't think that was correct.
tomhow•9mo 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•9mo ago
Thanks for the response, guess that makes sense.
pabs3•9mo 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?