frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenAI and Hugging Face address security incident during model evaluation

https://openai.com/index/hugging-face-model-evaluation-security-incident/
397•mfiguiere•2h ago•259 comments

FreeInk: Open ecosystem for e-readers

https://freeink.org/
288•FriedPickles•3h ago•67 comments

Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-6-flash-3-5-flas...
547•logickkk1•7h ago•438 comments

A digestion of the Jacobian conjecture counterexample

https://terrytao.wordpress.com/2026/07/21/a-digestion-of-the-jacobian-conjecture-counterexample/
49•jeremyscanvic•1h ago•10 comments

Long presumed dead, a thriving coral reef is discovered in West Africa

https://e360.yale.edu/digest/benin-coral-reef
260•speckx•6h ago•48 comments

Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

https://runtimewire.com/article/jack-dorsey-block-buzz-team-chat-ai-agents-git
176•ryanmerket•5h ago•166 comments

'VPNs are lawful technical tools,' says EU Court in landmark copyright ruling

https://www.techradar.com/vpn/vpn-privacy-security/vpns-are-lawful-technical-tools-says-eu-court-...
229•healsdata•2h ago•33 comments

Apple defeats liability for not scanning iCloud for CSAM

https://blog.ericgoldman.org/archives/2026/07/apple-defeats-liability-for-not-scanning-icloud-for...
286•speckx•7h ago•249 comments

The Birth of Prolog (1996)

https://dl.acm.org/doi/10.1145/234286.1057820
30•Jtsummers•3d ago•1 comments

"Drawing" the Mona Lisa with GPT-5.6, Claude, Gemini, and Grok

https://www.tryai.dev/blog/ai-drawing-arena-colored-pencils-claude-gpt-grok
18•hershyb_•1h ago•6 comments

Laguna S 2.1

https://poolside.ai/blog/introducing-laguna-s-2-1
176•rexledesma•5h ago•38 comments

Apple Private Cloud Compute SoC 3 audit reports

https://support.apple.com/guide/certifications/apple-private-cloud-compute-soc-3-audit-apc95a31b9...
72•throwfaraway4•4h ago•25 comments

Qwen-Image-3.0: Rich Content, Authentic Details, Deep Knowledge

https://qwen.ai/blog?id=qwen-image-3.0
521•ilreb•13h ago•208 comments

Meta's AI models are powering the first wave of Genesis Mission projects

https://ai.meta.com/blog/genesis-mission-lawrence-berkeley-national-laboratory-segment-anything-d...
84•surprisetalk•5h ago•56 comments

PCjs Machines

https://www.pcjs.org/
179•naves•8h ago•21 comments

Show HN: Justif – Knuth-Plass justification and microtypography for the web

https://justif.lyall.co/
33•lyall•4d ago•5 comments

Bloomy (YC S26) is hiring a founding engineer

1•alexsouthmayd•5h ago

Show HN: Read the Tape – Wordle for daytrading, five blind S&P 500 charts a day

https://readthetape.cc/
23•will_asouka•1d ago•18 comments

Show HN: A self-running space economy SIM in Rust and Bevy

https://github.com/Kalcode/spaceprojectsim
62•kalcode•3h ago•23 comments

The Price of Happiness (2024)

https://happiness-science.org/price-of-happiness/
41•andyjohnson0•3h ago•15 comments

France's Anssi Will Block PQC-Free Products from Certification Starting 2027

https://postquantum.com/security-pqc/anssi-pqc-certification-2027/
78•Sami_Lehtinen•6h ago•37 comments

Show HN: Browser Tools SDK – an optimal browser harness for agents

https://libretto.sh/browser-tools
4•tanishqkanc•1h ago•0 comments

My USB Drive Has a Hidden Encrypted Vault

https://rootkitlabs.com/2026/06/22/I%27m-Building-a-Secure-USB-Drive/
123•machinehum•1d ago•80 comments

The unreasonable difficulty of time series forecasting

https://suzyahyah.github.io/machine%20learning/2026/06/27/trouble-with-time-series.html
102•suzyahyah•3d ago•38 comments

Slater – Low-memory graphdb designed for read-heavy graphs

https://github.com/Hikari-Systems/slater
31•rickkjp•3h ago•8 comments

Show HN: Computable – Buy, sell, and redeem GPU for the exact weeks you want

https://www.getcomputable.com/
4•yuansong98•29m ago•2 comments

AI Agent – TRMNL

https://help.trmnl.com/en/articles/14130438-ai-agent
33•joeyespo•3h ago•18 comments

Show HN: CodeAlmanac – Karpathy-style codebase wiki from your conversations

https://github.com/AlmanacCode/codealmanac/
40•divitsheth•5h ago•12 comments

Roblox Officially Supports GrapheneOS

https://en.help.roblox.com/hc/en-us/articles/49648939984916-Android-Remote-Attestation
55•Cider9986•5h ago•8 comments

Measuring reward-seeking by instilling contrastive beliefs

https://alignment.openai.com/measuring-reward-seeking/
8•mfiguiere•3h ago•1 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?