frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

IPv8 Proposal

https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
67•EvanZhouDev•47m ago•39 comments

Darkbloom – Private inference on idle Macs

https://darkbloom.dev
81•twapi•1h ago•49 comments

Why Sal Khan's AI revolution hasn't happened yet, according to Sal Khan

https://www.chalkbeat.org/2026/04/09/sal-khan-reflects-on-ai-in-schools-and-khanmigo/
17•the-mitr•48m ago•3 comments

FSF trying to contact Google about spammer sending 10k+ mails from Gmail account

https://daedal.io/@thomzane/116410863009847575
45•pabs3•2h ago•17 comments

The paper computer

https://jsomers.net/blog/the-paper-computer
96•jsomers•3d ago•15 comments

Cybersecurity looks like proof of work now

https://www.dbreunig.com/2026/04/14/cybersecurity-is-proof-of-work-now.html
337•dbreunig•1d ago•120 comments

RedSun: System user access on Win 11/10 and Server with the April 2026 Update

https://github.com/Nightmare-Eclipse/RedSun
28•airhangerf15•2h ago•1 comments

A Look into NaviDial, Japan's Legacy Phone Service

https://www.tokyodev.com/articles/a-look-into-navidial-japan-s-legacy-phone-service
15•pwim•1h ago•0 comments

Airbnb discloses a billion-series Prometheus metrics pipeline

https://medium.com/airbnb-engineering/building-a-high-volume-metrics-pipeline-with-opentelemetry-...
9•jmarbach•53m ago•0 comments

Introduction to spherical harmonics for graphics programmers

https://gpfault.net/posts/sph.html
66•luu•2d ago•7 comments

I made a terminal pager

https://theleo.zone/posts/pager/
109•speckx•7h ago•23 comments

ChatGPT for Excel

https://chatgpt.com/apps/spreadsheets/
161•armcat•8h ago•116 comments

Too much discussion of the XOR swap trick

https://heather.cafe/posts/too_much_xor_swap_trick/
10•CJefferson•2d ago•2 comments

Fast and Easy Levenshtein distance using a Trie

https://stevehanov.ca/blog/fast-and-easy-levenshtein-distance-using-a-trie
21•sebg•3d ago•0 comments

Cal.com is going closed source

https://cal.com/blog/cal-com-goes-closed-source-why
267•Benjamin_Dobell•14h ago•193 comments

Google broke its promise to me – now ICE has my data

https://www.eff.org/deeplinks/2026/04/google-broke-its-promise-me-now-ice-has-my-data
1307•Brajeshwar•12h ago•566 comments

Stealth signals are bypassing Iran’s internet blackout

https://spectrum.ieee.org/iran-internet-blackout-satellite-tv
79•WaitWaitWha•3h ago•23 comments

Show HN: Hiraeth – AWS Emulator

https://github.com/SethPyle376/hiraeth
18•ozarkerD•3h ago•5 comments

The buns in McDonald's Japan's burger photos are all slightly askew

https://www.mcdonalds.co.jp/en/menu/burger/
331•bckygldstn•8h ago•173 comments

Retrofitting JIT Compilers into C Interpreters

https://tratt.net/laurie/blog/2026/retrofitting_jit_compilers_into_c_interpreters.html
65•ltratt•17h ago•15 comments

PiCore - Raspberry Pi Port of Tiny Core Linux

http://tinycorelinux.net/5.x/armv6/releases/README
95•gregsadetsky•10h ago•12 comments

Show HN: SmallDocs - A CLI and webapp for private Markdown reading and sharing

7•FailMore•18h ago•2 comments

Live Nation illegally monopolized ticketing market, jury finds

https://www.bloomberg.com/news/articles/2026-04-15/live-nation-illegally-monopolized-ticketing-ma...
490•Alex_Bond•10h ago•142 comments

Anna's Archive loses $322M Spotify piracy case without a fight

https://torrentfreak.com/annas-archive-loses-322-million-spotify-piracy-case-without-a-fight/
391•askl•21h ago•395 comments

US v. Heppner (S.D.N.Y. 2026) no attorney-client privilege for AI chats [pdf]

https://fingfx.thomsonreuters.com/gfx/legaldocs/xmvjyjekkpr/Rakoff%20-%20order%20-%20AI.pdf
115•1vuio0pswjnm7•16h ago•91 comments

The Gemini app is now on Mac

https://blog.google/innovation-and-ai/products/gemini-app/gemini-app-now-on-mac-os/
123•thm•12h ago•58 comments

Agent - Native Mac OS X coding ide/harness

https://github.com/macOS26/Agent
27•jv22222•5h ago•6 comments

North American English Dialects

https://aschmann.net/AmEng/
4•skogstokig•2h ago•0 comments

CRISPR takes important step toward silencing Down syndrome’s extra chromosome

https://medicalxpress.com/news/2026-04-crispr-bold-silencing-syndrome-extra.html
110•amichail•13h ago•67 comments

Intel Xpress Resurrection: Reviving a Forgotten EISA Beast

https://x86.fr/intel-xpress-resurrection-reviving-a-forgotten-eisa-beast/
41•ankitg12•3d ago•3 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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