frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codeberg Bans Cryptocurrency Projects

https://codeberg.org/Codeberg/org/pulls/1254
94•intunderflow•1h ago•79 comments

Run large language models at home, BitTorrent‑style

https://petals.dev/
24•snorbleck•1h ago•10 comments

Terrence Tao's ChatGPT Conversation about the Jacobian Conjecture Counterexample

https://chatgpt.com/share/6a5fdc7a-d6f8-83e8-bbea-8deb42cfed56
639•gmays•9h ago•393 comments

Quality non-fiction books are the antithesis of AI slop

https://resobscura.substack.com/p/quality-non-fiction-books-are-the
179•benbreen•12h ago•78 comments

GigaToken: ~1000x faster Language model tokenization

https://github.com/marcelroed/gigatoken/
384•syrusakbary•9h ago•76 comments

Show HN: Bento - An entire PowerPoint in one HTML file (edit+view+data+collab)

https://bento.page/slides/
675•starfallg•11h ago•152 comments

Medici family mystery may be solved after more than 400 years

https://www.cnn.com/2026/07/15/science/medici-family-mystery-dna-malaria
81•effects•4h ago•20 comments

Are AI Labs Pelicanmaxxing?

https://dylancastillo.co/posts/pelicanmaxxing.html
407•dcastm•9h ago•158 comments

Everyone Should Know SIMD

https://mitchellh.com/writing/everyone-should-know-simd
271•WadeGrimridge•8h ago•76 comments

Show HN: Cactus Hybrid: We taught Gemma 4 to know when it's wrong

https://github.com/cactus-compute/cactus-hybrid
78•HenryNdubuaku•8h ago•13 comments

John C. Dvorak has died

https://twitter.com/na_announce/status/2079952538040672302
589•coleca•7h ago•186 comments

Malleable Computing, Emacs, and You

http://yummymelon.com/devnull/malleable-computing-emacs-and-you.html
72•kickingvegas•5h ago•19 comments

Nobody knows what a used GPU cluster is worth

https://ciphertalk.substack.com/p/nobody-knows-what-a-used-gpu-cluster
177•rbanffy•1w ago•162 comments

Safari Technology Preview 248 Released

https://webkit.org/blog/18162/release-notes-for-safari-technology-preview-248/
80•Erenay09•5h ago•47 comments

Making

https://beej.us/blog/data/ai-making/
285•erikschoster•11h ago•112 comments

Fairphone 6 wide camera experimental Linux support

https://nondescriptpointer.com/articles/fairphone-6-wide-camera-linux/
74•helonaut•6h ago•6 comments

The startup's Postgres survival guide

https://hatchet.run/blog/postgres-survival-guide
325•abelanger•14h ago•175 comments

So Reddit has decided that plain HTML is unsafe

https://www.cole-k.com/2026/07/21/reddit/
295•montroser•14h ago•305 comments

Clarity didn't work, trying mysterianism (2012)

https://gwern.net/doc/fiction/science-fiction/2012-10-03-yvain-thewhisperingearring.html
43•dboon•7h ago•9 comments

What Rose Petals Teach Us about Induction

https://www.oranlooney.com/post/rose-petals/
15•olooney•4d ago•1 comments

Any text-to-SQL benchmark should address difficulties of real-world data stores

https://cacm.acm.org/blogcacm/if-you-think-you-can-do-real-world-text-to-sql/
35•shenli3514•4h ago•9 comments

NixOS is more complicated than you think but OpenCode fixed it

https://grigio.org/nixos-is-more-complicated-than-you-think-but-opencode-fixed-it/
9•grigio•2d ago•1 comments

OpenAI's accidental cyberattack against Hugging Face is science fiction

https://simonwillison.net/2026/Jul/22/openai-cyberattack/
7•abhisek•1h ago•0 comments

Launch HN: Unlayer (YC W22) – Add email and document builders to your app

https://unlayer.com
46•adeelraza•10h ago•32 comments

Businesses with ugly AI menu redesigns

https://blog.fiddery.com/businesses-with-ugly-ai-menu-redesigns/
192•speckx•13h ago•151 comments

Ghost Cut – or why Cut and Paste is broken everywhere

https://ishmael.textualize.io/blog/ghost-cut/
136•willm•11h ago•90 comments

Back to Kagi

https://blog.melashri.net/micro/back-to-kagi/
206•speckx•13h ago•162 comments

MemoryPack: Zero encoding extreme performance binary serializer for C#

https://github.com/Cysharp/MemoryPack
20•breve•3d ago•3 comments

I Inspected My Take-Home Interview Project. It Was a Whole Operation

https://citizendot.github.io/articles/fake-job-interview-git-hook-malware/
282•CITIZENDOT•6h ago•75 comments

All 253 Patterns from Christopher Alexander's a Pattern Language Summarized

https://claytondorge.com/patterns-list
29•toomuchtodo•4h ago•2 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?