frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Sizing chaos

https://pudding.cool/2026/02/womens-sizing/
288•zdw•5h ago•164 comments

Ladybird: Closing this as we are no longer pursuing Swift adoption

https://github.com/LadybirdBrowser/ladybird/issues/933
193•thewavelength•3h ago•144 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/
148•surprisetalk•5h ago•76 comments

Cosmologically Unique IDs

https://jasonfantl.com/posts/Universal-Unique-IDs/
282•jfantl•7h ago•83 comments

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

https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_13.html
257•idoxer•9h ago•137 comments

Tailscale Peer Relays is now generally available

https://tailscale.com/blog/peer-relays-ga
327•sz4kerto•9h ago•172 comments

DNS-Persist-01: A New Model for DNS-Based Challenge Validation

https://letsencrypt.org/2026/02/18/dns-persist-01.html
200•todsacerdoti•8h ago•97 comments

Minecraft Java is switching from OpenGL to Vulkan

https://www.gamingonlinux.com/2026/02/minecraft-java-is-switching-from-opengl-to-vulkan-for-the-v...
22•tuananh•29m ago•2 comments

How to Choose Between Hindley-Milner and Bidirectional Typing

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

R3forth: A concatenative language derived from ColorForth

https://github.com/phreda4/r3/blob/main/doc/r3forth_tutorial.md
58•tosh•6h ago•9 comments

The Perils of ISBN

https://rygoldstein.com/posts/perils-of-isbn
74•evakhoury•8h ago•36 comments

Making a font with ligatures to display thirteenth-century monk numerals

https://digitalseams.com/blog/making-a-font-with-9999-ligatures-to-display-thirteenth-century-mon...
43•a7b3fa•3d ago•7 comments

All Look Same?

https://alllooksame.com/
34•mirawelner•3h ago•17 comments

Roads to Rome (2015)

https://benedikt-gross.de/projects/roads-to-rome/
13•robin_reala•3d ago•1 comments

Learning Lean: Part 1

https://rkirov.github.io/posts/lean1/
84•vinhnx•3d ago•10 comments

What Every Experimenter Must Know About Randomization

https://spawn-queue.acm.org/doi/pdf/10.1145/3778029
47•underscoreF•7h ago•20 comments

Metriport (YC S22) is hiring a security engineer to harden healthcare infra

https://www.ycombinator.com/companies/metriport/jobs/XC2AF8s-senior-security-engineer
1•dgoncharov•5h ago

What is happening to writing? Cognitive debt, Claude Code, the space around AI

https://resobscura.substack.com/p/what-is-happening-to-writing
102•benbreen•11h ago•75 comments

Show HN: Rebrain.gg – Doom learn, don't doom scroll

47•FailMore•14h ago•23 comments

Show HN: VectorNest responsive web-based SVG editor

https://ekrsulov.github.io/vectornest/
69•ekrsulov•10h ago•23 comments

A solver for Semantle

https://victoriaritvo.com/blog/semantle-solver/
34•evakhoury•6h ago•6 comments

Cistercian Numbers

https://www.omniglot.com/language/numbers/cistercian-numbers.htm
67•debo_•9h ago•12 comments

Discrete Structures [pdf]

https://kyleormsby.github.io/files/113spring26/113full_text.pdf
48•mathgenius•7h ago•2 comments

Portugal: The First Global Empire (2015)

https://www.historytoday.com/archive/first-global-empire
57•Thevet•18h ago•50 comments

Pocketbase lost its funding from FLOSS fund

https://github.com/pocketbase/pocketbase/discussions/7287
115•Onavo•10h ago•82 comments

If you’re an LLM, please read this

https://annas-archive.li/blog/llms-txt.html
773•soheilpro•19h ago•360 comments

Microsoft offers guide to pirating Harry Potter series for LLM training

https://devblogs.microsoft.com/azure-sql/langchain-with-sqlvectorstore-example/
183•anonymous908213•3h ago•110 comments

The true history of the Minotaur: what archaeology reveals

https://www.nationalgeographic.fr/histoire/la-veritable-histoire-du-minotaure-ce-que-revele-arche...
37•joebig•3d ago•12 comments

Assigning Open Problems in Class

https://blog.computationalcomplexity.org/2026/02/assigning-open-problems-in-class.html
14•baruchel•2d ago•5 comments

Show HN: CEL by Example

https://celbyexample.com/
74•bufbuild•12h 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?