frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How to Write an Effective Software Design Document

https://refactoringenglish.com/excerpts/write-an-effective-design-doc/
188•fagnerbrack•2h ago•57 comments

Notes on gotchas while migrating 35kb preprompts from Opus to self-hosted Ollama

https://patrickmccanna.net/notes-on-migrating-large-prompts-away-from-anthropic-openai-to-self-ho...
41•0o_MrPatrick_o0•1h ago•12 comments

Jabber/XMPP: How Do We Gain Traction?

https://gultsch.de/posts/how-do-we-gain-traction/
50•inputmice•1h ago•27 comments

RubyGems Open Source Supply Chain Security and OpenAI

https://rietta.com/blog/rubygems-supply-chain-openai/
28•rietta•1h ago•4 comments

EuroBirdPortal – Live bird movements across Europe

https://www.eurobirdportal.org/ebp/en/
186•NKosmatos•7h ago•52 comments

An atlas of periodic solutions to the three-body problem

https://www.threebodyorbits.com/
203•danielmorozoff•2d ago•43 comments

A 386 PC for Your RP2350

https://github.com/rh1tech/frank-386
159•SamuraiLion•7h ago•44 comments

Devil's Arrows: Ancient builders hauled 55k-lb stones 11 miles for UK stone row

https://www.sciencedaily.com/releases/2026/09/260909005152.htm
32•bookofjoe•3d ago•22 comments

Show HN: Pelican-bicycle alternatives (updated for 2026)

https://gally.net/temp/20260914pelican-alternatives/index.html
34•tkgally•2h ago•8 comments

Principles for Fast Tokio Applications

https://dial9-rs.github.io/blog/principles-for-fast-tokio-applications/
5•carllerche•25m ago•0 comments

Trying to Make a Loop Auto-Vectorize

https://jsgroth.dev/blog/posts/trying-to-make-a-loop-auto-vectorize/
12•zdw•4d ago•3 comments

Where has Construction Automation been successful?

https://www.construction-physics.com/p/where-has-construction-automation
23•ltononro•1h ago•21 comments

Apple's Siri AI Can Be Swapped Out for Claude, ChatGPT, Code Shows

https://www.macrumors.com/2026/09/14/siri-can-be-swapped-out-for-chatgpt-claude/
173•tosh•3h ago•97 comments

1,000+ shoes reviewed and cut in half

https://runrepeat.com
7•bushwart•1h ago•0 comments

Adversarial Fashion Makes a Statement on AI Panopticon

https://spectrum.ieee.org/adversarial-fashion
18•rbanffy•1h ago•5 comments

Texas judge rules TikTok misled users on child safety feature

https://www.reuters.com/legal/litigation/texas-judge-rules-tiktok-misled-users-child-safety-featu...
102•1vuio0pswjnm7•3h ago•42 comments

Graphic Rants: Nanite Tessellation

http://graphicrants.blogspot.com/2026/02/nanite-tessellation.html
18•ibobev•1h ago•3 comments

Show HN: Kinesis – Control your Mac with the Meta Neural Band

https://github.com/callbacked/kinesis
87•callbacked•3h ago•26 comments

Apple's Dimensional Drawings

https://developer.apple.com/accessories/dimensional-drawings/
329•herbertl•15h ago•109 comments

OpenArch – PyTorch implementations of modern LLM architectures

https://github.com/anuj0456/OpenArch
111•anuj0456•7h ago•26 comments

Spaceships (Reverse Asteroid)

https://spaceships.treybastian.com/
326•zdw•4d ago•66 comments

Fable 5.1 Solves the Cyphral Distich, a 370-year-old cipher

https://www.vals.ai/blogs/fable-solves-cyphral-distich
1137•u1hcw9nx•18h ago•525 comments

The case against JPEG XL

https://giannirosato.com/blog/post/case-against-jxl/
238•contact9879•14h ago•305 comments

SDR–; open source SDR with a patchable signal graph, Rust DSP, web UI

https://github.com/Newspicel/sdrminusminus
30•newspicel•3h ago•2 comments

Optimizing Anamorphic Sculptures

https://tncardoso.com/blog/2026/09/optimizing-anamorphic-sculptures/
13•zbsc•3d ago•0 comments

Yoneda Lemma in Double Categories

https://bartoszmilewski.com/2026/09/13/yoneda-lemma-in-double-categories/
3•ibobev•1h ago•0 comments

A list of 1,325 AI assisted repositories, mined from GitHub

https://github.com/ActuallyTaylor/strata/blob/main/paper/data/large/datasets/ai-assisted-reposito...
8•ActuallyTaylor•1h ago•8 comments

Mullenweg has returned as CEO after attempted board ouster

https://techcrunch.com/2026/09/12/automattic-confirms-mullenweg-has-returned-as-ceo-after-attempt...
242•ilamont•19h ago•323 comments

Largest known Roman mosaic, beneath Baths of Trajan, opens to the public

https://www.theartnewspaper.com/2026/09/14/largest-roman-mosaic-opens-to-the-public
21•bookofjoe•2h ago•4 comments

Ask HN: What are you working on? (September 2026)

243•david927•22h ago•733 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?