frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Pirating the Pirates

https://mubi.com/en/notebook/posts/pirating-the-pirates
106•piotrgrabowski•1h ago•22 comments

Hijacking the PS5's RTMP Stream

https://yashgarg.dev/posts/hijacking-ps5-rtmp-stream/
51•ibobev•2h ago•7 comments

Show HN: HN.watch – Videos of all Hacker News posts

https://hn.watch/
24•mrborgen•2h ago•8 comments

Parley: Federated, decentralised chat that speaks plain IRC

https://git.mills.io/prologic/parley
240•davidcollantes•7h ago•115 comments

What Heraldry and Mon Can Teach Us About Building Visual-Identity Generators

https://benovermyer.com/blog/2026/09/japanese-vs-western-heraldry/
36•bovermyer•3h ago•12 comments

Launch HN: Vespper (YC F24) – SOTA Docx MCP

https://www.vespper.com/blog/launching-vespper-docx-mcp
5•topaztee•15m ago•2 comments

MongoDB CEO resigns to join Meta

https://www.reuters.com/technology/mongodb-ceo-desai-steps-down-lead-metas-enterprise-platform-20...
138•diek•2h ago•138 comments

Driver Ticketed for No Insurance Just Because Flock (YC 2017) Said She Didn't

https://www.techdirt.com/2026/09/28/driver-ticketed-for-no-insurance-despite-having-insurance-jus...
39•HotGarbage•52m ago•6 comments

The problem is not AI code, but not knowing about system architecture or intent

https://www.ssp.sh/brain/the-problem-is-not-the-ai-code-but-nobody-knows-anything-anymore/
248•zazuke•1h ago•166 comments

Cf: The Agentic CLI for the Cloudflare API

https://blog.cloudflare.com/cloudflare-cf-cli-launch/
22•macleos•2h ago•4 comments

OpenAI still doesn't seem to have a handle on all of its rogue AI activity

https://techcrunch.com/2026/09/28/openai-still-doesnt-seem-to-have-a-handle-on-all-of-its-rogue-a...
10•mikelgan•16m ago•4 comments

Coding Is Not Solved

https://blog.alexewerlof.com/p/coding-is-not-solved
306•firstSpeaker•3h ago•315 comments

37,500 border drawings: a map of the world as people remember it

https://www.habibicode.org/thedrawnworld
138•nicocarsui•9h ago•31 comments

Show HN: PaperMono, e-ink fridge magnet shopping list with mobile web page

https://github.com/seamusc/papermono-shopping-list
85•seamus_c•7h ago•37 comments

What Would a Serious AI Product Look Like?

https://blog.glyph.im/2026/09/serious-ai-product.html
52•lumpa•6h ago•20 comments

13 Months Sober (2025)

https://www.bobbytables.io/p/13-months-sober
57•btables•1h ago•44 comments

Kids turned low-traffic NPR Spotify comments into a secret group chat

https://www.thisamericanlife.org/897/transcript
108•simonpure•2h ago•79 comments

Solving a corn puzzle with CP-SAT

https://thill.me/2026/07/16/corn-puzzle-sat-solver.html
7•luu•20h ago•3 comments

Owed a billion dollars in Nvidia stock

https://colo.to/nvidia-stock-narrative.html
995•Eric_Gullichsen•15h ago•422 comments

Footguns with Postgres "at time zone 'UTC'"

https://bookofrevenue.com/blog/6ab81e9a97a13f0001f7e4e1/postgres-at-time-zone-u-does-not-do-what-...
134•birdculture•1d ago•75 comments

Ember-1

https://fireworks.ai/blog/ember-1
561•gmays•1d ago•241 comments

Show HN: Free alternative to graphics design giants

https://scissor.studio/
57•sia_xi•8h ago•22 comments

When did Google get so weird?

https://sancho.bearblog.dev/google-weird/
1655•sancho-panza•21h ago•908 comments

Show HN: Hntui – A TUI for Hacker News

https://github.com/ahmd-sh/hntui
96•ahmd-sh•5h ago•51 comments

Nissan's third generation e-POWER powertrain

https://www.nissan-global.com/EN/INNOVATION/TECHNOLOGY/ARCHIVE/E_POWER_GEN3/
137•mroche•15h ago•314 comments

Thinking fast and slow in AI: The role of metacognition (2021)

https://arxiv.org/abs/2110.01834
163•teleforce•14h ago•65 comments

Self-Hosting on the Dark Web

https://david.alvarezrosa.com/posts/self-hosting-on-the-dark-web/
318•mooreds•21h ago•106 comments

How Pew Research Center is – and is not – using AI in our work

https://www.pewresearch.org/decoded/2026/09/28/how-pew-research-center-is-and-is-not-using-ai-in-...
11•hn_acker•42m ago•3 comments

Malleable software: Restoring user agency in a world of locked-down apps (2025)

https://www.inkandswitch.com/essay/malleable-software/
144•evakhoury•22h ago•69 comments

Guitar amp and effects pedal built on the Waveshare ESP32-S3-Touch-AMOLED-2.06

https://github.com/dashersw/coyopedal
150•arbayi•2d ago•75 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?