News for hackers. Stuff that matters.

maxignol

To truly live as a couple, not as two individuals together I'd say then ?
Currently, only claude code and codex in cli, soon Claude Desktop as well.
> And one of the hardest optimization problems of being human is deciding who to love.

I truly agree. But then what do you look for in a relationship ? Cause to any optimization problems there are constraints and an objective function to push the metaphor ?

Re:Show HN: Draw from your friends' Claude quota on Wednesday October 07, 2026 @10:35AM (#49993458)
Well, the software for now is designed for trusted groups of users, so appart from making sure users can't access sessions of others in the same pool, there's not much.

For context, it's sent in every request of claude code and codex (only in http, not websocket) so we don't have to handle anything, the server just rewrites the auth headers of the request, keeping it intact out of that.

Re:Show HN: Draw from your friends' Claude quota on Wednesday October 07, 2026 @10:31AM (#49993405)
We've not found a way to make it completely legal yet but working on it lol
Hope you'll find someone with whom this will be different
Thank you for the reply
Re:Show HN: Share Claude Code rate-limits between friends on Tuesday September 29, 2026 @12:24PM (#49895958)
Hi ! It's been a few months since with my best friend (and cofounder) we were really getting sick of one rate limiting while the other had plenty of "tokens" left on his Claude subscription. So we made this. And we find it cool so we share it to you.

Please give us feedback, that'd be really appreciated, negative or positive ;)

Author here. Two things that are worth repeating up front: corpus A is 84% of the pooled bill, so the pooled −0.01% is pretty much "corpus A plus noise" so read it per-rows instead. And p_fire is a lower bound because of the detector's sensitivity taken as 1 (which it obviously isn't). Caveman's real fire rate is somewhat higher than 50.6%. Code and commands: github.com/jaynapp/jayn-caveman
Re:LinkedIn CringeBot 3000 on Wednesday August 12, 2026 @04:34AM (#49269384)
> I don't know if engaging with that button means I'm less likely to be served such content, or whether it's cleaning up everyone's feeds.

I would guess it's both cause I've been having less AI slop on LinkedIn for the past few weeks (yet not none).

Re:LinkedIn CringeBot 3000 on Wednesday August 12, 2026 @04:32AM (#49269367)
Been laughing for the past 10 minutes, thanks for this one. (I tried the death of my cat by car in front of my house in a Go Girl manner, absolute cinema)
Optimizing speed is really the way to go. Yet 24GB is not what everyone can afford. Maybe we could take some of those 56tk/s and transfer into some free RAM space using MoE loading ? I'd be glad with a less than 10GB and more than 6tk/s model.
Is the model picked through the router only for the first user turn or is there multi-turn routing (or planned to be added) ?
I'm really excited about what's been happening couple last weeks for local inference. I feel like it all started after colibri [1] was released. Great work !

Anyone got recommendation about what local model to use for what purpose ? I feel like (as they were saying in moonshot blog post [2]) each llm can be an expert in its own categories and with several small local we might get good coverage for decent usage, granted each one is specialized enough.

[1] : https://github.com/JustVugg/colibri [2] : https://fireworks.ai/blog/kimik3-fable

Re:Kimi-K3 Releases on HuggingFace 7/27 on Monday July 27, 2026 @06:16AM (#49067434)
I dont quite understand why GGUF is better optimized. Are the performances better for the same amount of VRAM ?
> I’d suspect the harness to massively affect token use and optimisation

Yes they do according to databricks -> https://www.databricks.com/blog/benchmarking-coding-agents-d...

That's why I find comparing models on benchmarks only gives the tendency. We should be comparing model x harness to have accurate metrics.

What is your harness with every model ?
> my use cases stop aligning to swebench pro around 50% accuracy, and more closely align with DeepSWE.

What do you mean by that ? If the model is higher than 50% on swebench pro then it tends to drift from what you like it to do, like DeepSWE benchmarks ?

Re:Qwen3.8 is launching and going open-weight soon on Sunday July 19, 2026 @06:36AM (#48966724)
Shouldn’t we fear they start doing only close source like most us labs once they catch up in market shares ?
Re:Kimi K3 is now live on Friday July 17, 2026 @02:06PM (#48950345)
Well, I had not heard of RLM before, just read the paper, thank you for introducing me to your lazy version !
Re:Kimi K3 is now live on Friday July 17, 2026 @05:12AM (#48945014)
I’ve never seen the Id approach before, that’s a good idea ! Though I was wondering how do you manage to keep costs low within the 7 agents ?
Re:Inkling: Our Open-Weights Model on Thursday July 16, 2026 @03:35AM (#48931407)
Giving the accuracy-token graph and not the accuracy-cost graph, thus we cannot easily compare costs with other models, is not a way to gain my trust
Re:Show HN:Getting GLM 5.2 running on my slow computer on Friday July 10, 2026 @05:21AM (#48857672)
I’m truly impressed by your work ! I don’t know if this is planned for near future, but how about adding energy efficiency benchmarks ? Because running locally is a great feeling, but the electricity bill should not be forgotten
Well, had a meeting with a VC that literally brought his note taking 3rd person to the meeting, did not even say hello. Tbh, I still find it creepier than an AI transcriber.
This seems really bad…

Older »