frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Flipper One – we need your help

https://blog.flipper.net/flipper-one-we-need-your-help/
59•sandebert•52m ago•15 comments

Python 3.15: features that didn't make the headlines

https://blog.changs.co.uk/python-315-features-that-didnt-make-the-headlines.html
28•rbanffy•46m ago•3 comments

Show HN: Rmux – A programmable terminal multiplexer with a Playwright-style SDK

https://github.com/helvesec/rmux
73•shideneyu•2h ago•43 comments

An OpenAI model has disproved a central conjecture in discrete geometry

https://openai.com/index/model-disproves-discrete-geometry-conjecture/
1221•tedsanders•16h ago•891 comments

GitHub confirms breach of 3,800 repos via malicious VSCode extension

https://www.bleepingcomputer.com/news/security/github-confirms-breach-of-3-800-repos-via-maliciou...
892•Timofeibu•22h ago•373 comments

Google officially announces that ads will be included in AI Mode search results

https://blog.google/products/ads-commerce/google-marketing-live-search-ads/
143•sofumel•2h ago•154 comments

A Girl Who Couldn't Draw Home

https://www.gailweiner.com/post/the-girl-who-couldn-t-draw-home
6•signa11•34m ago•2 comments

Fender escalates legal campaign against S-style guitars

https://www.guitarworld.com/gear/electric-guitars/fender-cease-and-desist-lsl-instruments
13•rectang•2d ago•4 comments

Show HN: I reverse engineered Apple's video wallpapers

https://github.com/kageroumado/phosphene
320•kageroumado•12h ago•74 comments

Haskell Foundation 2026 Update

https://discourse.haskell.org/t/haskell-foundation-2026-update/14136
131•azhenley•9h ago•41 comments

The Letter S, by Donald Knuth (1980) [pdf]

https://gwern.net/doc/design/typography/1980-knuth.pdf
196•bambax•11h ago•27 comments

New features in GCC 16: Improved error messages and SARIF output

https://developers.redhat.com/articles/2026/04/28/gcc-16-improved-error-messages-sarif-output
101•siteshwar•2d ago•17 comments

Flipper One Tech Specs

https://docs.flipper.net/one/general/tech-specs
414•gregsadetsky•17h ago•141 comments

Typewise (YC S22) Is Hiring an AI Growth Engineer (Zurich or Remote)

https://www.ycombinator.com/companies/typewise/jobs/HmCzfBK-ai-growth-engineer
1•janisberneker•3h ago

DOS Zone

https://dos.zone/
271•rglover•13h ago•63 comments

No Slop Grenade

https://noslopgrenade.com/
53•napolux•2h ago•27 comments

Anthropic is expanding to Colossus2. Will use GB200

https://twitter.com/nottombrown/status/2057194829986300375
223•aurareturn•15h ago•230 comments

All the bugs they found

https://andreapivetta.com/posts/all-the-bugs-they-found.html
43•ziggy42•2d ago•14 comments

How fast is N tokens per second really?

https://mikeveerman.github.io/tokenspeed/
430•hexagr•3d ago•88 comments

Vivaldi 8.0

https://vivaldi.com/blog/vivaldi-on-desktop-8-0/
176•OuterVale•4h ago•97 comments

Simulating Infinity in Conway's Game of Life with Modern C++

https://ryanjk5.github.io/posts/GOLDE/
47•HeliumHydride•2d ago•10 comments

Earth is now heating up twice as fast as in previous decades

https://www.newscientist.com/article/2518362-earth-is-now-heating-up-twice-as-fast-as-in-previous...
14•Anon84•1h ago•0 comments

Show HN: I made a tactical map-based WWII submarine simulator (public beta)

https://silentshark.app/alpha/
66•epaga•2d ago•24 comments

OpenAI Is Preparing to File for an IPO Soon

https://www.wsj.com/tech/ai/openai-is-preparing-to-file-for-an-ipo-very-soon-0ec95af5
119•louiereederson•19h ago•259 comments

Archaeologists find Egyptian mummy buried with the 'Iliad'

https://www.openculture.com/2026/05/archaeologists-discover-ancient-egyptian-mummy-buried-with-pa...
152•diodorus•5d ago•113 comments

Show HN: The Hanging Sculptures of the Xiaoxitian

https://funes.world/apps/the-hanging-sculptures-of-the-xiaoxitian
12•hanyangwang•2d ago•3 comments

Saying goodbye to asm.js

https://spidermonkey.dev/blog/2026/05/20/saying-goodbye-to-asmjs.html
391•eqrion•23h ago•150 comments

Reviving old scanners with an in-browser Linux VM bridged to WebUSB over USB/IP

https://yes-we-scan.app/details
87•gmac•3d ago•29 comments

Your Most Improbable Life

https://kevinkelly.substack.com/p/your-most-improbable-life
122•jger15•2d ago•87 comments

What is a Demand Coop

https://cahootzcoops.com/blog/what-is-a-demand-coop
70•DeonRob•10h ago•74 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?