frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenAI unveils its first custom chip, built by Broadcom

https://techcrunch.com/2026/06/24/openai-unveils-its-first-custom-chip-built-by-broadcom/
388•jamdesk•4h ago•266 comments

Qualcomm to Acquire Modular

https://www.reuters.com/business/qualcomm-buy-ai-startup-modular-2026-06-24/
71•timmyd•8h ago•23 comments

RubyLLM: A Ruby framework for all major AI providers

https://rubyllm.com/
312•doener•7h ago•47 comments

We’re making Bunny DNS free

https://bunny.net/blog/were-making-bunny-dns-free/
797•dabinat•13h ago•249 comments

PR spam today looks like email spam in the early 2000s

https://www.greptile.com/blog/prs-on-openclaw
141•dakshgupta•7h ago•87 comments

Computer use in Gemini 3.5 Flash

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-computer-use-...
122•swolpers•4h ago•69 comments

The Xteink X4 E-Ink Reader

https://blog.omgmog.net/post/xteink-x4-e-ink-reader/
119•felixdoerp•5h ago•95 comments

Crawling BitTorrent DHTs for Fun and Profit [pdf]

https://www.usenix.org/legacy/event/woot10/tech/full_papers/Wolchok.pdf
29•dgellow•3d ago•9 comments

There are a few things that I look back on as my mistakes in the early days

https://twitter.com/ID_AA_Carmack/status/2069799283369345247
447•shadowtree•6h ago•221 comments

Show HN: LookAway, a Mac break reminder that knows when not to interrupt

https://lookaway.com
37•_kush•8h ago•5 comments

45°C cooling design cuts data center water use to near zero

https://blogs.nvidia.com/blog/liquid-cooling-ai-factories/
91•nitin_flanker•8h ago•61 comments

Show HN: Nub – A Bun-like all-in-one toolkit for Node.js

https://github.com/nubjs/nub
171•colinmcd•8h ago•46 comments

Stealing Is a Skill

https://ben-mini.com/2026/stealing-is-a-skill
182•bewal416•9h ago•117 comments

Krea 2: SOTA open-weights 12B image model

https://www.krea.ai/blog/krea-2-technical-report
298•mattnewton•1d ago•34 comments

I can haz smoller NixOS ISOs?

https://natkr.com/2026-06-19-nixos-but-smol/
52•logickkk1•5d ago•17 comments

How the Fifth Lateran Council unlocked financial theory

https://sebastiangarren.com/2026/06/17/lending-is-meritorious-and-should-be-praised-how-the-fifth...
33•momentmaker•4d ago•3 comments

GLM-5.2 is a step change for open agents

https://www.interconnects.ai/p/glm-52-is-the-step-change-for-open
48•vantareed•1d ago•16 comments

GitHub shouldn't be a dependency for publishing Rust on crates.io

https://infosec.exchange/@mttaggart/116806641273303255
70•speckx•2h ago•27 comments

Pondering routing more of my traffic via nodes outside the UK

https://neilzone.co.uk/2026/06/pondering-routing-more-of-my-traffic-via-nodes-outside-the-uk-beca...
33•ColinWright•3d ago•24 comments

Thomann takes legal action against Fender

https://www.thomann.de/blog/en/inside/thomann-takes-legal-action-against-fender/
154•Audiophilip•3h ago•92 comments

A Practical Guide to SSH Tunnels: Local and Remote Port Forwarding

https://labs.iximiuz.com/tutorials/ssh-tunnels
232•signa11•4d ago•49 comments

Running Windows Games on a Hobby OS with Wine

https://astral-os.org/posts/2026/04/03/wine-on-astral.html
87•avaliosdev•7h ago•28 comments

Show HN: Monolisa v3 – a typeface for developers and creatives

https://www.monolisa.dev/
141•bebraw•2d ago•47 comments

Self-Harness: Harnesses That Improve Themselves

https://arxiv.org/abs/2606.09498
61•jonnonz•2d ago•2 comments

Exploiting vulnerabilities in Johnson and Johnson web apps

https://eaton-works.com/2026/06/24/jnj-webapp-hacks/
38•EatonZ•5h ago•1 comments

I taught a bucket to speak Git

https://www.tigrisdata.com/blog/objgit/
68•xena•6h ago•16 comments

NSA lost access to Mythos amid Anthropic dispute

https://www.nytimes.com/2026/06/23/us/politics/nsa-lost-access-anthropic-tool.html
181•thm•10h ago•163 comments

Big AI labs are hiring philosophers

https://www.economist.com/science-and-technology/2026/06/24/why-big-ai-labs-are-hiring-so-many-ph...
88•Brajeshwar•5h ago•73 comments

Genuinely, my all-time favourite image: Mamenchisaurus hochuanensis

https://svpow.com/2026/06/04/genuinely-my-all-time-favourite-image-mamenchisaurus-hochuanensis/
76•surprisetalk•2d ago•26 comments

Why eval startups fail (2025)

https://thomasliao.com/eval-startups
88•jxmorris12•1d ago•51 comments
Open in hackernews

GitHub shouldn't be a dependency for publishing Rust on crates.io

https://infosec.exchange/@mttaggart/116806641273303255
70•speckx•2h ago

Comments

Animats•1h ago
Sadly, that's probably correct. No outside single point of failure that can cancel users at will can be allowed to gatekeep open source projects.
sscaryterry•1h ago
Especially not now, what if they're down? ;)
veqq•22m ago
This is a big issue. https://janetdocs.org/ handles auth through GH which leads to... regular problems, unfortunately. I hope to migrate soon.
ameliaquining•1h ago
See the official project issue on this: https://github.com/rust-lang/crates.io/issues/326

TL;DR: They want to fix this, it's a lot of work that no one's being paid to do, there's a roadmap with specific tasks that need doing, volunteer contributions are welcome.

sscaryterry•1h ago
Just going to say it out loud :) Its been known for 10 years.

https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

NobodyNada•1h ago
10 years ago, GitHub had a far better reputation and the Rust ecosystem was much smaller and less load-bearing, so "what if someone doesn't have a GitHub account" was a theoretical concern for most people. So the issue was a low-priority backlog item that everyone agreed would be nice-to-have but there weren't enough people willing to volunteer their time to it over more important and more impactful work.

Obviously, the situation has changed in recent years, so it's now considered a much higher priority by many people and some of them are actively working on it. But it's a lot of work to be done by volunteers, so it takes time.

That's the reality of open-source projects: things get done when they are important enough to motivate someone to either fund it or work on in their free time, not according to idyllic roadmaps and schedules.

sscaryterry•1h ago
Wow, have you forgotten? https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

10 (edit: 8) years ago MS took over Github. The writing was on the wall then...

No need to explain OSS to me, I maintain and contribute.

ameliaquining•41m ago
crates.io was started long before the GitHub acquisition.
righthand•1h ago
Aka one of the many Rust reasons why I chose to learn C.
hmry•30m ago
Using crates.io is entirely optional, you can download a library's source code and specify the path to it in your cargo config file. (Which is not uncommon in production)

For that matter, using cargo is optional, you can compile rust code using GNU make or shell scripts if you want to. (That's what the Linux kernel does)

epage•1h ago
An RFC was recently merged to unblock this: https://github.com/rust-lang/rfcs/pull/3963

The implementation on this has started.

Something to keep in mind is https://blog.m-ou.se/rust-is-not-a-company/. Rust is mostly driven by volunteers working on what they find interesting. Boring/uninteresting tasks depend on funding, a warm body to accept the funding, and a reviewer.

echelon•33m ago
It's not just that this is boring work, but there's disagreement about Cargo and crates.io's direction. There are a lot of changes people would like to make that get turned down.

Crates.io and Cargo need namespaces, but the leadership flatly says no.

There's a big problem with name squatting, and nothing is being done about this either.

I get that there are more technically important issues around builds and reproducibility and the like, but this is pretty foundational stuff.

stymaar•16m ago
> Crates.io and Cargo need namespaces, but the leadership flatly says no.

They are favorable to crate-name-as-namespace (so that once you have the tokio crate you can use tokio as a namespace) and there's ongoing work on that. But as said above, it takes work to implement.

There's no desire for other meaning of the word "namespace" because famously nobody ever made a well-reasoned proposal (despite the amount of social media outrage over the lack of namespace).

mikey_p•38m ago
The longer I go the more I have actually come to appreciate the way Packagist works for the PHP community, there are lots of cool things it does that I wish NPM or other registries did by default, like forcing you to package from a source repository, so that you can't upload a different artifact from what you keep in source control.
ecshafer•11m ago
How does a close source package work? Depending on the language its not super helpful, but a package that is closed source should be possible.
jauntywundrkind•36m ago
The teams support may be a bit trickier/less clear to move on, but generally: this feels like a great place where atproto / bluesky support would slot in well.
androiddrew•17m ago
Welcome to Golang packaging problems. Hope you get it sorted out
sscaryterry•36m ago
Yes, and your point?
sscaryterry•1h ago
Pro tip: Using "load-bearing" is heavily associated with LLM usage :)
DrJokepu•57m ago
You could say it’s the real smoking gun. With significant blast radius.
ameliaquining•45m ago
Pangram says human: https://www.pangram.com/history/208879e5-8510-479a-b96c-a20f...
sscaryterry•36m ago
This is where I would insert the Little Britain "Computer says no" meme.
dijit•39m ago
The reason people were sounding the alarm 10 years ago is because if you tie yourself to a proprietary platform then you're at its mercy, even if it changes for the worse for everyone which is what we're seeing now.
ameliaquining•46m ago
Counterargument: https://www.astralcodexten.com/p/come-on-obviously-the-purpo...
DyslexicAtheist•1h ago
> it's a lot of work that no one's being paid to do,

aren't they like some kind of non-profit (in the legal sense) that is still able to take a lot of money (from players like Google and Co, to justify fixing this), as opposed to ... say the Zig foundation, ... that is is also "non-profit" but can't get money the same way?

jojomodding•42m ago
The non-profit (the Foundation) pays for specific things but it is not really there to hire people to work on things. It pays for infrastructure work and to pay the existing maintainers who often do review work. It also gives stipends to up-and-coming contributors for Open Source outreach programmes, but this are not really the people who you want to have immediately work on your critical infrastructure code.