frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Civic Hygiene – avoid building technologies that could be used by a police state (2013)

https://shkspr.mobi/blog/2013/11/civic-hygiene/
124•felineflock•39m ago•60 comments

Geolocating a random island using geometry and CUDA programming

https://yassa9.github.io/osint/gralhix-004/
235•yassa9•4h ago•47 comments

A joke domain purchase turned in geopolitical warfare

https://sprocketfox.io/xssfox/2026/08/19/sondehub-and-war/
315•kareiva•5h ago•41 comments

OpenLogi

https://openlogi.org/en
1302•amatheus•14h ago•358 comments

Microgpt in pure C hits 10M tps on Apple m5

https://github.com/vixhal-baraiya/microgpt-c
48•dhorthy•1d ago•10 comments

PostgreSQL for Everything

https://www.raphaelbauer.com:443/posts/postgresql-everything/
158•karlmush•3h ago•107 comments

Launch HN: OneCLI (YC S26) – OSS sandboxed agent harness for teams

https://github.com/onecli/onecli
5•guyb3•17m ago•0 comments

Moderna reports first positive Phase 3 for mRNA neoantigen therapy in melanoma

https://twitter.com/NoubarAfeyan/status/2090050162441752787
275•heydenberk•3h ago•111 comments

Devices with GrapheneOS support should be available in 2027

https://grapheneos.social/@GrapheneOS/117078064184215730
448•exceptione•5h ago•266 comments

Remote workers report the highest well-being in study of 7,700 employees

https://www.colorado.edu/today/2026/08/12/remote-workers-report-highest-well-being-study-7700-emp...
81•downbad_•1h ago•34 comments

Chain-of-Thought Reasoning in the Wild Is Not Always Faithful

https://arxiv.org/abs/2503.08679
7•florianherrengt•28m ago•2 comments

Ornith-1.5: From Self-Scaffolding to Self-Improvement

https://ornith.ai/ornith_1_5.html
24•CommonGuy•1h ago•2 comments

Air Theremin – a browser theremin you play by waving at your webcam

https://theremin.bizibah.com/
165•gurov•6h ago•65 comments

Taffy: A flexible, high-performance, cross-platform UI layout library

https://github.com/DioxusLabs/taffy
59•robin_reala•6d ago•23 comments

Extensible Software in the Age of LLMs

https://jeremymorrell.dev/blog/extensible-software-in-the-age-of-llms/
3•coloneltcb•20m ago•0 comments

A decades-old bug in Knuth's long division (TAOCP Vol II, Algorithm 4.3.1D)

https://kolja.rs/algorithm-d/
104•nk_kolja•6d ago•21 comments

Cerebras CS-4

https://www.cerebras.ai/cs4
407•sunils34•16h ago•247 comments

Rings forged from meteorites may have been fashionable among ancient Greek elite

https://phys.org/news/2026-08-forged-meteorites-fashionable-ancient-greek.html
86•pseudolus•5d ago•35 comments

Being ambitious and being a dad

https://nicholascharriere.com/blog/being-ambitious-and-being-a-dad/
789•nichochar•3d ago•599 comments

Supersonic Trebuchet [video]

https://www.youtube.com/watch?v=Co57SfcT-h0
209•CharlesW•4d ago•92 comments

Mathematics in the Age of AI

https://arxiv.org/abs/2608.16753
7•jonbaer•1h ago•3 comments

Activation Energy is a good model for a lot of things

https://homosabiens.substack.com/p/activation-energy-is-a-good-model
117•surprisetalk•5d ago•32 comments

Show HN: Nikon F100 Film Camera Repair Notes

https://github.com/enthdegree/f100
25•enthdegree•4d ago•12 comments

Palomar: A registry of Lean verified mathematics

https://terrytao.wordpress.com/2026/08/18/palomar-a-registry-of-lean-verified-mathematics/
155•matt_d•14h ago•37 comments

A 3D fruit fly on macOS desktop powered by the real FlyWire connectome

https://github.com/DenisSergeevitch/desktop-fly
355•phoenix120•18h ago•163 comments

New Casio F-B100W – Upgrade to the iconic F-91W after 40 years

https://www.casio.com/uk/watches/casio/product.F-B100W-1A/
75•__fst__•1h ago•62 comments

How does IKEA come up with names for its products?

https://www.ikea.com/se/en/customer-service/knowledge/articles/6f564c4d-2ccc-46de-b643-545a3948dc...
427•NaOH•22h ago•304 comments

λλ: A Programming Language for Silicon Photonics

https://dl.acm.org/doi/10.1145/3789240.3829151
74•matt_d•10h ago•16 comments

Finger: the 1971 social network that never died

https://en.andros.dev/blog/54572bc7/finger-the-1971-social-network-that-never-died/
296•andros•1d ago•99 comments

A 25-year-old video patent just expired, ending a legal headache for Linux

https://www.xda-developers.com/25-year-old-brazilian-video-patent-expired-legal-headache-linux/
288•theanonymousone•4d ago•143 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?