frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Why is this fingerprinting script creating bioweapons?

https://nullpt.rs/fingerprinting-bioweapons
823•hazebooth•7h ago•184 comments

GitLab Security Incident: Attempted Exploitation of CVE-2026-97229

https://alpinelinux.org/posts/GitLab-security-incident-CVE-2026-97229.html
61•sashk•1h ago•11 comments

Qwenputer: A functioning, deterministic RISC-V CPU inside Qwen3.5

https://divagr.com/blog/qwenputer
14•csmantle•45m ago•0 comments

Get Ready for Touch on Mac

https://developer.apple.com/touch-on-mac/
24•nojs•1h ago•39 comments

New York Times adds more AI features to its Cooking app. Users aren't thrilled

https://www.niemanlab.org/2026/10/the-new-york-times-is-adding-more-ai-features-to-its-cooking-ap...
16•ilamont•54m ago•7 comments

A Health Update

https://furbo.org/2026/10/28/a-health-update/
85•frizlab•3h ago•7 comments

CNC Stone Carving

https://carmelitegothic.com/cnc-stone-carving/
398•bschne•10h ago•117 comments

Gemini 4 Carbon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-carbon/
792•acossta•8h ago•653 comments

The case of the 9 bit AES key

https://v12.sh/blog/the-case-of-the-9bit-aes-key
76•ledoge•4h ago•38 comments

MicroZig to Adopt Strict No LLM / No AI Policy

https://github.com/ZigEmbeddedGroup/microzig/blob/main/CODE_OF_CONDUCT.md
9•paaloeye•40m ago•2 comments

MacBook Pro with PROLED XDR Display and Touch

https://www.apple.com/macbook-pro/proled-xdr-display/
496•etothet•8h ago•843 comments

Formlabs Studio 1 $699 Resin Printer

https://formlabs.com/products/form-studio-1-basic-founders-edition/
107•mhb•3h ago•79 comments

The first wired XR glasses powered by Android XR

https://blog.google/products-and-platforms/platforms/android/xreal-aura/
11•yincrash•1h ago•10 comments

Nango (YC W23) Is Hiring Across Eng, FDE, Marketing, DevRel

https://nango.dev/careers
1•bastienbeurier•4h ago

The Grid, a factory-scale robot in Massachusetts that builds PCBs on demand

https://www.circuithub.com/post/unveiling-the-grid
410•seddona•2d ago•199 comments

Start Doing Graph Theory

https://vertex.degree/
576•ibobev•5d ago•126 comments

StackOverflow now gets fewer than 1000 questions a month

https://data.stackexchange.com/stackoverflow/query/1926661#graph?t=1
77•babelfish•1h ago•77 comments

How we made our MMDB files a 33% smaller

https://ipinfo.io/blog/how-made-mmdb-files-smaller
10•mmaia•3d ago•0 comments

Dayjob: Tax – evaluating AI agents on 50 professional tax assignments

https://surgehq.ai/blog/dayjob-tax
200•landonxi•9h ago•125 comments

Why Birds Can Fly over Mount Everest

https://lede-v2.nautil.us/why-birds-can-fly-over-mount-everest-237864
57•andsoitis•4d ago•10 comments

Image generation has come a long way since August 2022

https://www.hbrooks.com/writing/image-generation-has-come-a-long-way
34•hunterbrooks•2d ago•7 comments

AlpineBSD

https://wiki.alpinebsd.org
174•bradley_taunt•10h ago•161 comments

Spiders Spin 'Silk Dope' into Nature's Toughest Material

https://www.quantamagazine.org/how-spiders-spin-silk-dope-into-natures-toughest-material-20261028/
47•ibobev•7h ago•3 comments

Apple's git still trusts the compromised eMudhra certificates

https://emudhra.we-have-a-problem.com/apple.html
1036•galadran•14h ago•377 comments

Gaussian Splats part 3: There's always a bigger scene

https://www.magnopus.com/blog/gaussiansplats-part-3-theres-always-a-bigger-scene
101•ibobev•5d ago•21 comments

The Agent SDK

https://cursor.com/blog/agent-sdk
93•torutofu•11h ago•110 comments

Leak website releases data on DHS employees

https://www.reuters.com/legal/government/leak-website-releases-data-tens-thousands-dhs-employees-...
67•wondersky•4h ago•13 comments

Scaling Hierarchical Networks

https://www.cartesia.ai/blog/from-tokens-to-bytes-part-1
29•guybedo•7h ago•1 comments

Emacs Turns 50

https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/
411•internet_points•11h ago•174 comments

Show HN: SlideBySide – Present slides without sharing your screen

https://slidebyside.com/
54•denismenace•8h ago•23 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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