frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Meta blocks human rights accounts from reaching audiences in Arabia and the UAE

https://www.alqst.org/ar/posts/1190
613•giuliomagnifico•3h ago•244 comments

Goodbye Visa and Mastercard: 130M Europeans switching to sovereign payment

https://www.lesnumeriques.com/banque-en-ligne/adieu-visa-et-mastercard-130-millions-d-europeens-b...
604•healsdata•3h ago•491 comments

Qwen3.7-Max: The Agent Frontier

https://qwen.ai/blog?id=qwen3.7
350•kevinsimper•6h ago•124 comments

Saying Goodbye to Asm.js

https://spidermonkey.dev/blog/2026/05/20/saying-goodbye-to-asmjs.html
161•eqrion•4h ago•71 comments

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/
21•yacin•56m ago•0 comments

Map of Metal

https://mapofmetal.com/
252•robin_reala•5h ago•81 comments

Victory: Tennessee man jailed 37 days for Trump meme wins $835,000 settlement

https://www.fire.org/news/victory-tennessee-man-jailed-37-days-trump-meme-wins-835000-settlement-...
265•ceejayoz•2h ago•131 comments

Stable Audio 3

https://arxiv.org/abs/2605.17991
19•guardienaveugle•1h ago•1 comments

Google's AI is being manipulated. The search giant is quietly fighting back

https://www.bbc.com/future/article/20260519-google-tackles-attempts-to-hack-its-ai-results
114•tigerlily•5h ago•63 comments

Testing distributed systems with AI agents

https://github.com/shenli/distributed-system-testing
29•shenli3514•1h ago•2 comments

Everything in C is undefined behavior

https://blog.habets.se/2026/05/Everything-in-C-is-undefined-behavior.html
385•lycopodiopsida•10h ago•529 comments

Formal Verification Gates for AI Coding Loops

https://reubenbrooks.dev/blog/structural-backpressure-beats-smarter-agents/
12•pyrex41•1h ago•1 comments

When Fast Fourier Transform Meets Transformer for Image Restoration (2024)

https://github.com/deng-ai-lab/SFHformer
47•teleforce•2d ago•4 comments

Autoregressive next token prediction and KV Cache in transformers

https://medium.com/advanced-deep-learning/autoregressive-next-token-prediction-kv-cache-in-transf...
23•coarchitect•2d ago•0 comments

Smartmedia Card Spec Opened, available free (2000)

https://www.edn.com/smartmedia-card-interface-spec-opened-available-for-free/#google_vignette
15•brudgers•2d ago•4 comments

Gemini 3.5 Flash

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-5/
908•spectraldrift•22h ago•620 comments

FiveThirtyEight articles on the Internet Archive

https://fivethirtyeightindex.com/
322•ChocMontePy•15h ago•75 comments

I’ve built a virtual museum with nearly every operating system you can think of

https://virtualosmuseum.org/
908•andreww591•1d ago•201 comments

Japan is gripped by mass allergies. A 1950s project is to blame

https://www.bbc.com/future/article/20260515-the-1950s-blunder-which-causes-mass-hay-fever-in-japan
267•ranit•14h ago•126 comments

Handling the great code forge fragmentation

https://www.alexselimov.com/posts/forge_fragmentation/
4•mooreds•3d ago•1 comments

Show HN: Forge – Guardrails take an 8B model from 53% to 99% on agentic tasks

https://github.com/antoinezambelli/forge
605•zambelli•1d ago•218 comments

Infomaniak transitions to a foundation model to protect user data privacy

https://news.infomaniak.com/en/infomaniak-foundation-sovereign-cloud/
140•darktoto•10h ago•36 comments

No way to parse integers in C (2022)

https://blog.habets.se/2022/10/No-way-to-parse-integers-in-C.html
46•konmok•6h ago•56 comments

Google changes its search box

https://blog.google/products-and-platforms/products/search/search-io-2026/
642•berkeleyjunk•22h ago•876 comments

Apparently Google hates us now

https://twitter.com/pokemoncentral/status/2057123807404638250
8•zeitg3ist•9m ago•0 comments

America's Greatest Strategic Blunder: The Imprisonment of Qian Xuesen

https://danieltan.weblog.lol/2026/05/americas-greatest-strategic-blunder-the-imprisonment-of-qian...
75•danieltanfh95•3h ago•33 comments

Remove-AI-Watermarks – CLI and library for removing AI watermarks from images

https://github.com/wiltodelta/remove-ai-watermarks
355•janalsncm•18h ago•222 comments

College students drown out AI-praising commencement speeches with boos

https://www.tomshardware.com/tech-industry/artificial-intelligence/college-students-drown-out-ai-...
286•iancmceachern•4h ago•266 comments

Gemini CLI will stop working from June 18, 2026

https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/
351•primaprashant•22h ago•182 comments

Mistral AI acquires Emmi AI

https://www.emmi.ai/news/mistral-ai-acquires-emmi-ai
315•doener•21h ago•92 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?