frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The URL shortener that makes your links look as suspicious as possible

https://creepylink.com/
529•dreadsword•11h ago•107 comments

Ideas are cheap, execution is cheaper

https://davekiss.com/blog/ideas-are-cheap-execution-is-cheaper/
23•grncdr•3d ago•7 comments

Claude Cowork exfiltrates files

https://www.promptarmor.com/resources/claude-cowork-exfiltrates-files
741•takira•18h ago•330 comments

Raspberry Pi's New AI Hat Adds 8GB of RAM for Local LLMs

https://www.jeffgeerling.com/blog/2026/raspberry-pi-ai-hat-2/
164•ingve•6h ago•119 comments

Programming, Evolved: Lessons and Observations

https://github.com/kulesh/dotfiles/blob/main/dev/dev/docs/programming-evolved.md
4•dnw•1h ago•0 comments

Test your square brackets

https://fluca1978.github.io/2025/12/10/testAndSquareBrackets.html
34•speckx•6d ago•21 comments

The 3D Software Rendering Technology of 1998's Thief: The Dark Project (2019)

https://nothings.org/gamedev/thief_rendering.html
33•suioir•3h ago•11 comments

Z80 Mem­ber­ship Card

https://sunrise-ev.com/z80.htm
52•exvi•3d ago•15 comments

Jiga (YC W21) Is Hiring Full Stack Engineers

https://jiga.io/about-us
1•grmmph•2h ago

The 500k-ton typo: Why data center copper math doesn't add up

https://investinglive.com/news/the-500000-ton-typo-why-data-center-copper-math-doesnt-add-up-2026...
41•thebeardisred•1h ago•59 comments

Ask HN: How are you doing RAG locally?

237•tmaly•23h ago•99 comments

Ask HN: Share your personal website

698•susam•21h ago•1926 comments

San Remo Pasta Measurer

https://www.toxel.com/tech/2025/09/17/san-remo-pasta-measurer/
28•surprisetalk•5d ago•15 comments

Impeccable Style

https://impeccable.style
27•noemit•3d ago•11 comments

Show HN: MailPilot – Freedom to go anywhere while your agents work

16•keepamovin•7h ago•16 comments

French Court Orders Popular VPNs to Block More Pirate Sites, Despite Opposition

https://torrentfreak.com/french-court-orders-popular-vpns-to-block-more-pirate-sites-despite-oppo...
25•iamnothere•1h ago•12 comments

Scaling long-running autonomous coding

https://cursor.com/blog/scaling-agents
231•samwillis•16h ago•141 comments

Ask HN: What did you find out or explore today?

139•blahaj•20h ago•223 comments

Python: Tprof, a Targeting Profiler

https://adamj.eu/tech/2026/01/14/python-introducing-tprof/
28•jonatron•5h ago•0 comments

Photos Capture the Breathtaking Scale of China's Wind and Solar Buildout

https://e360.yale.edu/digest/china-renewable-photo-essay
220•mrtksn•4h ago•155 comments

Bubblewrap: A nimble way to prevent agents from accessing your .env files

https://patrickmccanna.net/a-better-way-to-limit-claude-code-and-other-coding-agents-access-to-se...
129•0o_MrPatrick_o0•12h ago•98 comments

New Safari developer tools provide insight into CSS Grid Lanes

https://webkit.org/blog/17746/new-safari-developer-tools-provide-insight-into-css-grid-lanes/
91•feross•13h ago•50 comments

A letter to those who fired tech writers because of AI

https://passo.uno/letter-those-who-fired-tech-writers-ai/
243•theletterf•6h ago•157 comments

The State of OpenSSL for pyca/cryptography

https://cryptography.io/en/latest/statements/state-of-openssl/
167•SGran•16h ago•38 comments

Crafting Interpreters

https://craftinginterpreters.com/
160•tosh•16h ago•33 comments

Furiosa: 3.5x efficiency over H100s

https://furiosa.ai/blog/introducing-rngd-server-efficient-ai-inference-at-data-center-scale
190•written-beyond•13h ago•128 comments

Show HN: Sparrow-1 – Audio-native model for human-level turn-taking without ASR

https://www.tavus.io/post/sparrow-1-human-level-conversational-timing-in-real-time-voice
88•code_brian•20h ago•20 comments

Bare metal programming with RISC-V guide (2023)

https://popovicu.com/posts/bare-metal-programming-risc-v/
47•todsacerdoti•5d ago•8 comments

Handy – Free open source speech-to-text app

https://github.com/cjpais/Handy
145•tin7in•9h ago•83 comments

Find a pub that needs you

https://www.ismypubfucked.com/
337•thinkingemote•22h ago•311 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?