frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Copyright does not protect AI-generated content in EU

https://mathstodon.xyz/@maxpool/117128107757895678
70•u1hcw9nx•1h ago•65 comments

The August 17 outage, and the work ahead

https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/
313•0xedb•6h ago•355 comments

Consumer Rights Wiki

https://consumerrights.wiki/w/Main_Page
213•gregsadetsky•7h ago•31 comments

I like 'em thick: an apology to my English teachers

https://www.experimental-history.com/p/i-like-em-thick
558•Ariarule•2d ago•258 comments

AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint

https://blog.laserphile.com/2026/08/aliexpress-webpage-keeping-multipoint.html
880•emctech•15h ago•287 comments

Aaron Swartz was prosecuted for scraping, while Meta does it without consequence

https://blog.curiousquail.com/im-upset-again-about-a-co-creator-of-rss-being-prosecuted-for-somet...
954•speckx•5h ago•220 comments

There's no such thing as a small software team anymore

https://jacob.gold/posts/theres-no-such-thing-as-a-small-software-team/
16•mooreslaw•1h ago•11 comments

I should have loved biology (2020)

https://jsomers.net/i-should-have-loved-biology/
199•tyre•7h ago•74 comments

HTML Can Do That

https://chrisburnell.com/html-can-do-that/
573•encyclopedism•1d ago•163 comments

Stealth Model

https://openrouter.ai/stealth/ox-alpha
23•mtokmak06•1h ago•5 comments

Malicious Rust crate Arrayref runs a build-time payload

https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/
394•abhisek•12h ago•364 comments

Show HN: Huzzah – a novel approach to coding with AI

https://www.danielvaughn.dev/posts/huzzah/
220•danielvaughn•6h ago•121 comments

It is a sign of the times that Amazon gets to call this fair use

http://observationalepidemiology.blogspot.com/2026/08/it-is-sign-of-times-that-amazon-gets-to.html
9•sonicrocketman•1h ago•2 comments

Show HN: I trained a 125M model to autocomplete piano on-device

https://simedw.com/2026/08/20/midi-autocomplete/
501•simedw•13h ago•106 comments

CIA funding helped keep NeXT afloat in the 80s

https://www.wsj.com/tech/steve-jobs-apple-next-cia-161b65f9?st=NWWds1&reflink=desktopwebshare_per...
331•EwanG•1d ago•207 comments

My Microscope Is a Dashcam

https://xecaz.com/reverse.engineering/tomlovdm9/
8•xecaz•3d ago•1 comments

Why aren't smart people happier? (2022)

https://www.experimental-history.com/p/why-arent-smart-people-happier
85•rafaelc•6h ago•137 comments

Linux 7.2

https://www.igalia.com/2026/08/19/Linux-72-Released.html
192•mariuz•9h ago•67 comments

Detecting scraper bots through scroll behaviour

https://niki.cat/detecting-scraper-bots-through-scroll-behaviour
24•theanonymousone•2h ago•9 comments

Vomit: Clean up Claude 5's token output with a separate LLM

https://github.com/zachahn/vomit
191•Bluestein•10h ago•202 comments

SpacetimeDB: A Short Technical Review

https://strn.cat/posts/spacetime/
58•hurrrr•6h ago•12 comments

Tidal Cycles – Live coding music with Algorithmic patterns

https://tidalcycles.org/
55•gjvc•6h ago•9 comments

Sixtyfour (YC P25) Is Hiring

https://www.ycombinator.com/companies/sixtyfour/jobs/39SkSrA-software-engineering-intern
1•HPMOR•8h ago

How to compromise your system with a job interview

https://www.codedge.de/posts/how-to-compromise-your-system-with-a-job-interview
118•codedge•9h ago•100 comments

Anti-AI fonts are useless and harmful

https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/
114•speckx•10h ago•79 comments

Speeding Up the Plush Garbage Collector

https://pointersgonewild.com/2026-08-17-speeding-up-the-plush-garbage-collector/
13•maxime_cb•3d ago•1 comments

Mojo is now open source

https://www.modular.com/blog/mojo-open-source
344•visheshdembla•2d ago•76 comments

Git at any scale

https://cursor.com/blog/git-at-any-scale
275•meetpateltech•2d ago•92 comments

Speeding Up (Small) Ruby Hashes

https://byroot.github.io/ruby/performance/2026/08/13/speeding-up-ruby-hashes.html
19•arto•6d ago•0 comments

Every Model Cheats

https://dreadnode.io/research/every-model-cheats-prompt-level-mitigation-of-cheating-on-offensive...
81•vga805•11h ago•62 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?