frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Emacs 31 Is Around the Corner: The Changes I'm Daily Driving

https://www.rahuljuliato.com/posts/emacs-31-around-the-corner
122•frou_dh•1h ago•35 comments

Has W Social switched to closed source?

https://blog.elenarossini.com/w-social-public-institutions-and-the-theater-of-european-digital-so...
61•nemoniac•1h ago•27 comments

Hospitals and universities repurposing drugs at 90% lower cost

https://www.kcl.ac.uk/news/hospitals-and-universities-repurposing-drugs-at-90-lower-cost
110•giuliomagnifico•3h ago•42 comments

I found 10k GitHub repositories distributing Trojan malware

https://orchidfiles.com/github-repositories-distributing-malware/
70•theorchid•2h ago•18 comments

Midjourney Medical

https://www.midjourney.com/medical/blogpost
1020•ricochet11•12h ago•708 comments

Advanced Compilers: The Self-Guided Online Course

https://www.cs.cornell.edu/courses/cs6120/2025fa/self-guided/
50•ibobev•3h ago•0 comments

DeepSeek Introduces Vision

https://chat.deepseek.com/
276•RIshabh235•7h ago•113 comments

Microsoft new Outlook takes 10 seconds to do what Outlook Classic does instantly

https://www.windowslatest.com/2026/06/15/microsofts-new-outlook-takes-10-seconds-to-do-what-outlo...
124•Adam-Hincu•1h ago•72 comments

Local Qwen isn't a worse Opus, it's a different tool

https://blog.alexellis.io/local-ai-is-not-opus/
326•alphabettsy•11h ago•170 comments

We built a persistent agent memory layer on Elasticsearch with 0.89 recall

https://www.elastic.co/search-labs/blog/agent-memory-elasticsearch
42•showmypost•2h ago•9 comments

Lore – Open source version control system designed for scalability

https://lore.org/
1189•regnerba•23h ago•631 comments

.gitignore Isn't the Only Way to Ignore Files in Git

https://nelson.cloud/.gitignore-isnt-the-only-way-to-ignore-files-in-git/
45•FergusArgyll•3h ago•3 comments

Modos Color Monitor Pushes E-Paper Displays Further

https://spectrum.ieee.org/modos-e-paper-monitor
21•Vinnl•2h ago•7 comments

Vinyl Cache and Varnish Cache

https://vinyl-cache.org/organization/on_vinyl_cache_and_varnish_cache.html#org-vinyl-varnish
37•embedding-shape•3d ago•12 comments

Seven Perfect Shuffles Randomize a Deck of Cards. But How Many Sloppy Ones?

https://www.quantamagazine.org/seven-perfect-shuffles-randomize-a-deck-of-cards-but-how-many-slop...
29•layer8•5h ago•20 comments

Unity vs. Floating Point

https://aras-p.info/blog/2026/06/11/Unity-vs-floating-point/
9•ibobev•3d ago•0 comments

AMD silently removes memory encryption from consumer Ryzen CPUs

https://www.tomshardware.com/pc-components/cpus/amd-silently-removes-memory-encryption-from-consu...
263•lompad•6h ago•129 comments

US holds off blacklisting DeepSeek, more than 100 firms deemed security risks

https://www.reuters.com/world/china/us-holds-off-blacklisting-chinas-deepseek-more-than-100-firms...
491•giuliomagnifico•1d ago•539 comments

I need your clothes, your boots, and your motorcycle

https://rbelmont.mameworld.info/?p=1725
91•ingve•5h ago•80 comments

I hate compilers

https://xeiaso.net/notes/2026/anubis-wasm-vendor-binary/
117•xena•8h ago•96 comments

Wages in America Are Too Low for the 30% Rule to Work for Renters Anymore

https://www.realtor.com/advice/rent/wages-in-america-are-too-low-for-the-30-rule-to-work-for-rent...
99•littlexsparkee•46m ago•168 comments

Sogen – High-performance Windows and Linux userspace emulator

https://sogen.dev/
54•fratellobigio•3d ago•16 comments

Clojure Hosted on Go

https://github.com/glojurelang/glojure
177•dnlo•14h ago•22 comments

How we run Firecracker VMs inside EC2 and start browsers in less than 1s

https://browser-use.com/posts/firecracker-browser-infra
300•gregpr07•1d ago•209 comments

Storied Colors – A catalogue of named colors

https://storiedcolors.com/
199•susiecambria•16h ago•47 comments

The Alaska Server

https://serialport.org/blog/the-alaska-server/
36•speckx•2d ago•10 comments

Taxonomy of the Occlupanida (parasitoids on bread bag tags)

https://www.horg.com/horg/?page_id=921
169•beatthatflight•14h ago•41 comments

Smashed Toilet Phone Web Server

https://www.offthebricks.com/articles/smashed-toilet-phone-web-server
35•mircerlancerous•3d ago•15 comments

How Madrid built its metro cheaply (2024)

https://worksinprogress.co/issue/how-madrid-built-its-metro-cheaply/
183•trymas•18h ago•131 comments

RFC 10008: The new HTTP Query Method

https://www.rfc-editor.org/info/rfc10008/
392•schappim•1d ago•162 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?