frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The MacBook Pro's OLED PWM Problem: When a 'Better' Display Becomes Worse to Use

https://macanorak.com/the-macbook-pros-oled-pwm-problem-when-a-better-display-becomes-worse-to-use/
80•MacAnorak•1h ago•40 comments

SpaceX catches the Starship to end Flight 15

https://www.spacex.com/launches/starship-flight-15
1412•ls612•17h ago•937 comments

Understanding Positional Embeddings in Modern LLMs

https://magazine.sebastianraschka.com/p/understanding-positional-embeddings
45•vismit2000•2h ago•0 comments

Things That Turbo Pascal Is Smaller Than (2011)

https://prog21.dadgum.com/116.html
27•ksec•1h ago•3 comments

Why did some Apollo missions carry a grenade launcher?

https://space.stackexchange.com/questions/37775
113•Skyfall106•5h ago•69 comments

Lovable apps expose passport details and more than 200K private messages

https://www.crissyfield.de/research/lovable-en/
913•armcat•21h ago•345 comments

Court denies motion to dismiss DRAM price fixing case

https://litnews.ai/articles/garciaguirre-samsung-sk-hynix-micron-dram-conspiracy-suit-survives-di...
322•ybathaee•13h ago•130 comments

What thousands of conversations look like inside a language model

https://operator0x.com/field-notes/qwen-conversation-state-space/
42•josip208•2d ago•10 comments

The Hypertext Transfer Protocol Status Code 483 (I'm Not a Freezer)

https://datatracker.ietf.org/doc/draft-banffy-httpbis-not-a-freezer/
6•rbanffy•20m ago•7 comments

A NES emulator written in Odin

https://lucypero.com/lucynes.html
15•frostbyte7•2h ago•0 comments

The Telephone Changed the World

https://lithub.com/how-the-telephone-changed-the-world/
7•NaOH•15h ago•0 comments

Chasing an audio artifact on power loss

https://subalpinecircuits.com/chasing-an-audio-artifact-on-power-loss/
16•ireflect•2d ago•1 comments

Lutnick Pushed to Weaken Chip Rules That Overlap with His Family Business

https://www.nytimes.com/2026/11/15/us/politics/lutnick-pushed-to-weaken-chip-rules-that-overlap-w...
93•JumpCrisscross•3h ago•24 comments

Handwritten 200-year-old dismissal notice found on roof tile

https://www.bbc.co.uk/news/articles/c6jdmdzv25r9o
42•nephihaha•2d ago•24 comments

How did Woz write the Apple 1 BASIC before building the computer?

https://retrocomputing.stackexchange.com/questions/17957
256•Skyfall106•16h ago•134 comments

My favourite modern NES games

https://jordi.inversethought.com/blog/25-of-my-favourite-modern-nes-games/
146•jordigh•12h ago•20 comments

Disk encryption on NetBSD – achieving secrecy

https://netbsd.org/~nia/disk-encrypt/
66•jaypatelani•9h ago•14 comments

Strictly monotonic timestamps and gapless sequences in Rust

https://tsoracle.rs/
21•znano•2d ago•8 comments

KDE: The documentary [video]

https://tube.kockatoo.org/w/fFinNHfanLT7aBEb2B8y4c
529•mrkn1•1d ago•121 comments

A family tree of software job titles

https://zwischenzugs.com/2026/11/03/a-family-tree-of-software-job-titles/
369•umerf•21h ago•184 comments

How to read codes from (many) IR remote controls with as little code as possible

https://bitbanksoftware.blogspot.com/2026/11/how-to-read-codes-from-many-ir-remote.html
4•speckx•3d ago•1 comments

Show HN: Carton Clock – A working pendulum clock made from empty drink cartons

https://www.niklasroy.com/carton-clock/
23•r0r0•2d ago•1 comments

Open-Source HF Communications for Remote Communities and Experimenters

https://www.ardc.net/rhizomaticas-hermes-and-mercury-expand-open-source-hf-communications-for-rem...
41•tejtm•4d ago•5 comments

Semicircle Packing

https://rorz.io/writing/semicircle-packing
58•sarreph•2d ago•5 comments

Why get an expensive Pi when I have an old phone?

https://so.long.thanks.fish/why-pi-when-i-have-an-old-phone/
591•casi•5d ago•313 comments

The Evolving Story of How Chemistry Became Biology

https://www.quantamagazine.org/the-evolving-story-of-how-chemistry-became-biology-20261112/
69•pseudolus•2d ago•16 comments

PyPI's redesigned project pages with clearer security signals are now live

https://blog.pypi.org/posts/2026-11-06-ui-updates-complete/
259•rbanffy•23h ago•114 comments

500 Lines or Less A 3D Modeller

https://aosabook.org/en/500L/a-3d-modeller.html
81•myth_drannon•2d ago•11 comments

Book list for streetfighting computer scientists

https://nick-black.com/dankwiki/index.php?title=Book_list_for_streetfighting_computer_scientists
70•num42•7h ago•27 comments

Project Zero will disclose vulnerabilities 90 days after reporting

https://projectzero.google/2026/11/disclosure-policy.html
292•hacb•1d ago•165 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?