frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

YouTube to automatically label AI-generated videos

https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/
982•nopg•16h ago•594 comments

AMD pulls a bait-and-switch on Linux users with Vivado licensing changes

https://itsfoss.com/news/amd-vivado-bait-and-switch-on-linux-users/
88•teleforce•1h ago•28 comments

A Eureka machine that thinks like nature and explores what AI cannot

https://iisc.ac.in/a-eureka-machine-that-thinks-like-nature-and-explores-what-ai-cannot/
100•kunalsin9h•5h ago•30 comments

Hallucinate – Massively Multiplayer Online Rave

https://hallucinate.site
249•stagas•8h ago•100 comments

I analysed 20 years of my chats

https://drobinin.com/posts/am-i-a-bad-friend/
177•valzevul•12h ago•68 comments

AI sticker shock hits corporate America

https://www.axios.com/2026/05/28/ai-spending-roi-enterprise-costs
62•1vuio0pswjnm7•1h ago•31 comments

I think Anthropic and OpenAI have found product-market fit

https://simonwillison.net/2026/May/27/product-market-fit/
923•simonw•19h ago•1038 comments

Rapira (Рапира) – Soviet programming language interpreter

https://github.com/begoon/rapira
42•begoon•3d ago•20 comments

SimCity 3k in 4k (2025)

https://www.thran.uk/writ/hdid/2025/12/simcity-3k-in-4k.html
392•speckx•18h ago•158 comments

What Apple and Google are doing to push notifications

https://www.jacquescorbytuech.com/writing/what-apple-and-google-are-doing-your-push-notifications
311•iamacyborg•17h ago•315 comments

I'm Getting into Mesh Networks (Meshtastic, MeshCore, and Reticulum)

https://www.jonaharagon.com/posts/im-getting-into-mesh-networks-meshtastic-meshcore-and-reticulum/
228•Panda_•16h ago•91 comments

Ruby vs. Java vs. TypeScript: my experience on building a Cowork DOCX plugin

https://tanin.nanakorn.com/ruby-java-typescrip-claude-docx-plugin/
13•theanonymousone•2d ago•3 comments

Commission fines Temu €200M for breaching the Digital Services Act

https://ec.europa.eu/commission/presscorner/home/en
26•MrDresden•1h ago•11 comments

More Whimsical OEIS Sequences

https://www.jeremykun.com/shortform/2026-05-22-1528/
17•surprisetalk•1d ago•4 comments

The Ask

https://randsinrepose.com/archives/the-ask/
91•digitallogic•2d ago•55 comments

Rust (and Slint) on a Jailbroken Kindle

https://sverre.me/blog/rust-on-kindle/
179•homarp•16h ago•26 comments

DuckDuckGo search saw 28% more visits after Google said people love AI mode

https://www.pcgamer.com/hardware/duckduckgos-ai-free-search-saw-nearly-28-percent-more-visits-in-...
916•HelloUsername•19h ago•436 comments

Seeing Around Corners Using Smartphone-Grade Lidar

https://spectrum.ieee.org/smartphone-grade-lidar
19•marc__1•3d ago•3 comments

FBI Arrests CIA Official with $40M in Gold Bars in His Home

https://www.nytimes.com/2026/05/27/us/politics/fbi-arrest-cia-official-gold-bars.html
377•cwwc•13h ago•262 comments

Go: Support for Generic Methods

https://github.com/golang/go/issues/77273
261•f311a•1d ago•225 comments

RamAIn (YC W26) Is Hiring

https://www.ycombinator.com/companies/ramain/jobs/hqvmyKN-founding-gtm-engineer
1•svee•10h ago

Biff is a command line datetime Swiss army knife

https://github.com/BurntSushi/biff
46•burntsushi•9h ago•29 comments

Incident with Pull Requests, Issues, Git Operations and API Requests

https://www.githubstatus.com/incidents/xy1tt3hs572m
314•maxnoe•1d ago•202 comments

Warm up your MacBook (2019)

https://z3ugma.github.io/2019/11/18/warm-up-your-macbook/
91•kristianp•15h ago•94 comments

Investigating how prompt politeness affects LLM accuracy (2025)

https://arxiv.org/abs/2510.04950
84•KnuthIsGod•2d ago•77 comments

Zero Lines Maze: What the 8-Bit Guy's One-Liner Can Still Teach Us

https://retrogamecoders.com/zero-lines-maze/
57•ibobev•1d ago•19 comments

Google employee charged with $1M Polymarket insider trading bet on search term

https://www.cnbc.com/2026/05/27/google-employee-polymarket-insider-trading.html
218•pseudolus•11h ago•123 comments

Stress disrupts hippocampal integration of overlapping events, memory inference

https://www.science.org/doi/10.1126/sciadv.aea5496?user_id=66c4bf745d78644b3aa57b08
136•gmays•19h ago•21 comments

A New Typst Template for Pandoc (2025)

https://imaginarytext.ca/posts/2025/typst-templates-for-pandoc/
86•ankitg12•2d ago•15 comments

Mini Micro Fantasy Computer

https://miniscript.org/MiniMicro/index.html#about
262•nicoloren•1d ago•82 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?