frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

MAI-Code-1-Flash

https://microsoft.ai/news/introducingmai-code-1-flash/
213•EvanZhouDev•2h ago•98 comments

Gmail thinks I'm stupid, so I left

https://moddedbear.com/gmail-thinks-im-stupid-so-i-left
251•speckx•1h ago•125 comments

MAI-Thinking-1

https://microsoft.ai/news/introducing-mai-thinking-1/
80•LER0ever•2h ago•25 comments

Open Repair Data Standard – Open Repair Alliance

https://openrepair.org/open-data/open-standard/
30•cassepipe•1h ago•1 comments

A walking tour of surveillance infrastructure in Seattle (2020)

https://coveillance.org/a-walking-tour-of-surveillance-infrastructure-in-seattle/
333•eustoria•7h ago•190 comments

GitHub Copilot App

https://github.com/features/preview/github-app
68•theanonymousone•2h ago•41 comments

Launch HN: Rudus (YC P26) – AI for concrete contractors

26•rishipankhaniya•2h ago•1 comments

The advertising cartel coming to your web browser

https://blog.zgp.org/the-advertising-cartel-coming-to-your-web-browser/
49•speckx•1h ago•11 comments

Trump signs downsized AI order after weeks of reversals

https://www.politico.com/news/2026/06/02/trump-signs-downsized-ai-order-00946389
110•_alternator_•4h ago•78 comments

HP re-releases classic computer science calculator: The HP-16C

https://hpcalcs.com/product/hp-16c-collectors-edition/
36•dm319•1h ago•14 comments

Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai

https://blog.adafruit.com/
538•semanser•10h ago•226 comments

Uber caps employee AI spending after blowing through budget in four months

https://techcrunch.com/2026/06/02/uber-caps-employee-ai-spending-after-blowing-through-budget-in-...
19•notfried•42m ago•2 comments

QBE – Compiler Backend – 1.3

https://c9x.me/compile/release/qbe-1.3.html
48•birdculture•3h ago•7 comments

Bringing Up DeepSeek-V4-Flash on AMD MI300X

https://fergusfinn.com/blog/deepseek-v4-flash-mi300x/
49•kkm•2h ago•4 comments

How we index images for RAG

https://www.kapa.ai/blog/how-we-index-images-for-rag
30•mooreds•4h ago•5 comments

CT scans of BYD car parts

https://www.lumafield.com/scan-of-the-month/byd
8•viasfo•21m ago•1 comments

Why Janet? (2023)

https://ianthehenry.com/posts/why-janet/
402•yacin•11h ago•212 comments

Expanding Project Glasswing

https://www.anthropic.com/news/expanding-project-glasswing
134•surprisetalk•7h ago•178 comments

Fidonet: Technology, Use, Tools, and History (1993)

https://www.fidonet.org/inet92_Randy_Bush.txt
126•BruceEel•6h ago•43 comments

Preparing for KDE Plasma's Last X11-Supported Release

https://blog.davidedmundson.co.uk/blog/596/
107•jandeboevrie•6h ago•129 comments

Made a Tool to Streams Changes from Microsoft SQL Server to Apache Kafka

https://github.com/Niyko/Athena
6•hyvr_official•2d ago•1 comments

BQN: What Is a Primitive?

https://mlochbaum.github.io/BQN/commentary/primitive.html
21•tosh•3d ago•1 comments

Love systemd timers

https://blog.tjll.net/you-dont-love-systemd-timers-enough/
295•yacin•11h ago•189 comments

Great Question (YC W21) Is Hiring Applied AI Interns

https://www.ycombinator.com/companies/great-question/jobs/J5TNvQH-ai-engineer-intern
1•nedwin•8h ago

Microsoft announces Scout, an autonomous AI agent built on OpenClaw

https://www.computerworld.com/article/4180103/microsoft-unveils-scout-an-autonomous-ai-agent-buil...
45•EvanZhouDev•2h ago•40 comments

Rethinking search as code generation

https://research.perplexity.ai/articles/rethinking-search-as-code-generation
56•1zael•4h ago•16 comments

Three Ways to Get Paid (2018)

https://jasonzweig.com/three-ways-to-get-paid/
182•nate•3h ago•113 comments

Age verification for social media, the beginning of the end for a free internet?

https://mullvad.net/en/blog/age-verification-for-social-media-the-beginning-of-the-end-for-a-free...
375•StrLght•21h ago•271 comments

Multicore suppport for DOS is real – partly

https://www.vogons.org/viewtopic.php?t=111336
15•beebix•2d ago•3 comments

Show HN: RePlaya – self-hosted browser session replay with live tailing

https://github.com/s2-streamstore/replaya
22•shikhar•3h ago•3 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?