frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Twenty Years of RISC OS Open

https://www.riscosopen.org/news/articles/2026/06/20/twenty-years-of-risc-os-open
15•AlexeyBrin•43m ago•1 comments

Meshdiff – visually compare two STL versions in the browser, client-side

https://meshdiff.com/
63•projscope•1h ago•8 comments

Show HN: Bor – Open-source policy management for Linux desktops

https://getbor.dev/blog/2026-08-02-bor-v080-release/
68•eniac111•4h ago•13 comments

The Vanishing Page: AI Firms Scan Then Destroy Rare Book Editions

https://dallasexpress.com/national/the-vanishing-page-ai-firms-scan-then-destroy-rare-book-editions/
42•throw0101a•4d ago•37 comments

Only 8.9% of sites block AI crawlers, but 94.8% are never cited in AI answers

https://website-auditor.io/ai-visibility-index
34•SpikeyCoder•1h ago•42 comments

Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

https://github.com/syncular/syncular
34•quambo•3h ago•17 comments

Artificial Intelligence: Ars Notoria and the Promise of Instant Knowledge

https://publicdomainreview.org/essay/ars-notoria/
44•jruohonen•3h ago•6 comments

Wikimedia Foundation refuses union recognition, hires union-busting law firm

https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2026-08-02/News_and_notes
138•akolbe•1h ago•90 comments

Great Question (YC W21) Is Hiring Senior Demand Gen Manager

https://www.ycombinator.com/companies/great-question/jobs/YutDxyf-senior-demand-generation-manager
1•nedwin•1h ago

Go 1.27 Interactive Tour

https://victoriametrics.com/blog/go-1-27/index.html
258•Hixon10•11h ago•106 comments

Show HN: Fuse – statically typed functional programming language

https://fuselang.org
17•the_unproven•1h ago•1 comments

Show HN: I'm a 15 Year Old Wannabe Engineer, This Is a Cycloidal Gearbox I Built

https://github.com/tom-ilan/cycloidal_gearbox
197•tomilan•11h ago•68 comments

Seedance 2.5

https://seed.bytedance.com/en/blog/one-take-creation-flexible-referencing-introducing-seedance-2-5
384•njaremko•16h ago•201 comments

Cyberscript

https://cyberscript.dev
27•dtj1123•5h ago•26 comments

Diátaxis

https://diataxis.fr/
397•ryanseys•16h ago•49 comments

MkLinux and the pimped-out Apple Workgroup Server 9150

http://oldvcr.blogspot.com/2026/08/mklinux-and-pimped-out-apple-workgroup.html
69•goldenskye•10h ago•4 comments

An internal OpenAI Astra model solved 10 major open math and CS problems

https://twitter.com/polynoamial/status/2083467194663571701
34•wa5ina•1h ago•18 comments

IBM i (OS/400) the Database Operating System

https://osadmins.com/en/ibm-i-os-400-the-database-operating-system/
30•naves•6h ago•16 comments

Running Kimi K3 on MI355X at Better Performance per Dollar Than B300

https://www.wafer.ai/blog/kimi-k3-mi355x
156•ilreb•8h ago•74 comments

Holocloth

https://holocloth.vercel.app
34•ingve•2d ago•7 comments

Show HN: Katharos Functional programming and CSP-style concurrency for Python

https://github.com/kamalfarahani/katharos
6•kamalf•2h ago•1 comments

Deep-sea vehicles spot 'alien' sharks deep beneath the waves in the Pacific

https://www.science.org/content/article/deep-sea-vehicles-spot-alien-sharks-deep-beneath-waves-pa...
68•pkaeding•10h ago•33 comments

A big win for Android interoperability

https://www.openhomefoundation.org/blog/a-big-win-for-android-interoperability/
158•soheilpro•1d ago•115 comments

When random.bytes() runs but doesn't work

https://insider.btcpp.dev/p/when-randombytes-runs-but-doesnt
66•Funes-•11h ago•31 comments

Atom is better than RSS, in ways that matter

https://chrismorgan.info/atom%3Erss
103•frizlab•15h ago•56 comments

ASRock BC-250: Building the Budget Steam Machine

https://plug-world.com/posts/2026/asrock-bc250-the-budget-steam-machine/
75•plug_world•11h ago•34 comments

Elena, a library for building Progressive Web Components

https://elenajs.com/
41•brianzelip•2d ago•3 comments

Has the New Cocaine Arrived?

https://playboy.substack.com/p/has-the-new-cocaine-finally-arrived
4•bookofjoe•14m ago•0 comments

US Treasury undertakes historic intervention in yen market

https://www.ft.com/content/0f9b2fe7-bde4-4f5f-b49e-93ccb5da9ea8
28•23pointsNorth•2h ago•19 comments

Postmortem for Kernel Soundness Bug #14576

https://leodemoura.github.io/blog/2026-8-1-postmortem-for-kernel-soundness-bug-14576/
155•juhopitk•18h ago•59 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?