frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU

https://github.com/synchopate/llama-modchip
189•joshcsimmons•6h ago•61 comments

The Reconstruction of Torn Documents

https://www.bundesarchiv.de/en/stasi-records-archive/the-reconstruction-of-torn-documents/
34•jacquesm•2d ago•6 comments

OpenAI raises $11B at a $1.25T valuation

https://247wallst.com/investing/2026/11/07/openai-just-raised-11-billion-at-a-1-25-trillion-valua...
121•armcat•2h ago•103 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
105•jruohonen•6h ago•22 comments

Porting Android 16 to my blind mother's keypad phone

https://z1x.us/blog/four-hundred-bucks-of-e-waste
84•z1xus•4d ago•30 comments

I'm not a fan of Deno's security model (2024)

https://goldstein.lol/posts/deno-security/
27•maxloh•2h ago•8 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
551•karagenit•14h ago•348 comments

Show HN: Vegetable Gardening for Engineers

https://jrcpl.us/contrib/2020/gardening-for-engineers/
22•jrcplus•4d ago•3 comments

JIT bitmap text rendering for microcontrollers

https://linebender.org/blog/jit-bitmap-text/
64•dmit•6h ago•11 comments

What I run on my $10 USD OpenStick homelab

https://blog.bosscher.ch/posts/openstick/
696•LaurensBER•23h ago•125 comments

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
502•shmulc•20h ago•364 comments

Clj.rs – a Clojure dialect implemented in Rust

https://clj.rs/
119•simonpure•4d ago•47 comments

Agent memory needs its OpenTelemetry moment

https://www.lorekit.io/blog/open-agent-memory-format
123•mthines•8h ago•90 comments

Person of Interest

https://krthr.co/person-of-interest/
232•krthr•5h ago•155 comments

Petered

https://aworkinglibrary.com/writing/petered
118•adrianhoward•6h ago•74 comments

How to prove equations using diagrams, part 1

https://www.epatters.org/post/e-graphs-1/
12•frostbyte7•4h ago•2 comments

Earliest evidence of cannabis use found in ancient Siberian tomb

https://www.cnn.com/2026/11/05/science/ancient-cannabis-siberia-scli-intl
47•mooreds•2d ago•37 comments

Top Astrophysicist Leaves U.S.

https://www.nytimes.com/2026/11/07/science/space/holley-bockelmann-astrophysicist-space-trump.html
22•xqcgrek2•1h ago•5 comments

Tesla Hasn't Had a Successful New Product Launch Since JB Straubel Stepped Down

https://cleantechnica.com/2026/11/07/tesla-hasnt-had-a-successful-new-product-launch-since-jb-str...
162•gumby•1h ago•136 comments

The Gordon Gekko effect: The role of culture in the financial industry (2016) [pdf]

https://www.newyorkfed.org/medialibrary/media/research/epr/2016/epr_2016_gordon-gekko-effect_lo.pdf
67•tylerdane•1d ago•46 comments

Drones built to look like birds evaded detection at Air Force tech exercise

https://taskandpurpose.com/news/drone-mimicking-bird-test/
27•bushwart•2h ago•13 comments

Quadrillion-parameter transformers and how to train them

https://qlabs.sh/research/parameters
54•frozenseven•5d ago•44 comments

Finding Xanadu: Inside a JRPG classic translation 15 years in the making

https://readonlymemo.com/legend-of-xanadu-pc-engine-fan-translation-interview-making-of/
56•speckx•3d ago•12 comments

Tasfer: a text editor drawn on a 2D canvas

https://www.hamza.se/blog/tasfer
65•hamza512b•4d ago•46 comments

New typeface using intricate designs from Shakespeare's First Folio (2023)

https://www.itsnicethat.com/news/typeland-shakespeares-globe-amifer-folio-graphic-design-090323
39•bryanrasmussen•3d ago•11 comments

Uranium cubes reveal why the German nuclear project failed

https://arstechnica.com/science/2026/11/uranium-cubes-reveal-why-the-german-nuclear-project-failed/
194•rbanffy•3d ago•125 comments

Every Mac comes with an (undocumented) family member classifier

https://8rank.ai/game/apple-intelligence-personal-knowledge-graph
804•infwhispers•1d ago•428 comments

Making any integer with four 2s (2025)

https://eli.thegreenplace.net/2025/making-any-integer-with-four-2s/
182•germanrabbit•18h ago•47 comments

Every Windows 11 app should kill Electron, and Discord just showed why

https://www.windowslatest.com/2026/11/06/every-windows-11-app-should-kill-electron-and-discord-ju...
408•thunderbong•1d ago•409 comments

ISponsorBlockTV: SponsorBlock client for all YouTube TV clients

https://github.com/dmunozv04/isponsorblocktv
97•xnx•13h ago•42 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?