frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Astra for Law

https://openai.com/index/astra-for-law/
202•vertigoruntime•2h ago•217 comments

Bend – A language that blocks AI mistakes via proof, on CPU and GPU

https://bend-lang.com/
194•nicolas-siplis•2h ago•105 comments

Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint

https://prismml.com/news/bonsai-2-27b
100•JonSchneider•1h ago•29 comments

Hister: A private search engine for the pages you visit and the files you keep

https://github.com/asciimoo/hister
394•bookofjoe•6h ago•120 comments

Wax motor

https://en.wikipedia.org/wiki/Wax_motor
167•mhb•1d ago•37 comments

Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA

https://global.fujitsu/en-global/pr/news/2026/09/14-02
477•my123•2d ago•174 comments

Sex, AI, and the Apocalypse

https://www.iankduncan.com/personal/2026-09-16-sex-ai-and-the-apocalypse/
56•Anon84•1h ago•31 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
21•joeriddles•1h ago•9 comments

Flet 1.0 – Build cross-platform apps in Python

https://flet.dev/
23•absqueued•2h ago•3 comments

CrowdSec Source Code Leak

https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure
118•eccgecko•7h ago•34 comments

Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data

https://arxiv.org/abs/2609.18842
91•Betelbuddy•6h ago•26 comments

Rate limits on GitLab.com are changing

https://about.gitlab.com/blog/rate-limit-change-2026/
139•darkwater•7h ago•103 comments

Diplodocus, Long Thought Exclusively American, Turns Up in Spain

https://www.sci.news/paleontology/spanish-diplodocus-15064.html
10•embedding-shape•2d ago•4 comments

How Uber Protects Against Retry Storms

https://www.uber.com/us/en/blog/protecting-against-retry-storms/
12•iscmt•1h ago•8 comments

Everybody's Lost Their Minds

https://www.netmeister.org/blog/everybodys-lost-their-minds.html
257•ibobev•3h ago•173 comments

The American Religion of Self-Storage Facilities

https://www.newyorker.com/magazine/2026/09/21/the-american-religion-of-self-storage-facilities
173•pseudolus•9h ago•292 comments

TSMC revealing details about next gen A14 node

https://iedm26.mapyourshow.com/8_0/sessions/session-details.cfm?scheduleid=331
75•osnium123•2d ago•28 comments

Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI

https://zscc.ai/careers?job_id=109821
1•el_al•6h ago

How GLM built its own inference infrastructure

https://z.ai/blog/glm-built-its-inference-infrastructure
351•whiteros_e•14h ago•254 comments

Why I didn’t sign the Fields medallists’ letter

https://gowers.wordpress.com/2026/09/17/why-i-didnt-sign-the-fields-medallists-letter/
187•simianwords•14h ago•242 comments

How do we prevent mathemathics from devolving into the Medieval Era of secrecy?

https://mathoverflow.net/questions/515260/how-do-we-prevent-mathematics-from-devolving-into-the-m...
57•jjgreen•2d ago•31 comments

Show HN: Snapdrop: Instantly share files between devices. No setup, no signup

https://snapdrop.me
9•Capira•2h ago•6 comments

Canto: A speech model built for the real world

https://wisprflow.ai/canto
28•sleepypandas•4h ago•11 comments

One year of sponsored Servo development

https://servo.org/blog/2026/09/15/one-year-of-sponsorship/
338•AshleysBrain•14h ago•138 comments

Running Ubuntu on the Lenovo IdeaPad Duet

https://vhaudiquet.fr/blog/duet-ubuntu/
61•vhaudiquet•3d ago•19 comments

CCC invites all model citizens to 40C3

https://events.ccc.de/en/2026/09/12/40c3-model-citizens/
317•antonly•15h ago•175 comments

André Weil and the Hodge Conjecture

https://jiahao116.github.io/Articles/
24•caojiahao•5d ago•8 comments

The most important product decision is what you don't build

https://liamnugent.me/posts/what-you-dont-build/
11•ChrisArchitect•2h ago•5 comments

Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents

38•cat-whisperer•6h ago•43 comments

Towards Self-Driving Codebases

https://blog.detail.dev/posts/towards-self-driving-codebases/
92•wilhelmklopp•6h ago•74 comments
Open in hackernews

How Uber Protects Against Retry Storms

https://www.uber.com/us/en/blog/protecting-against-retry-storms/
12•iscmt•1h ago

Comments

aftbit•27m ago
I'd be interested to hear other strategies in this space. I've done the naive thing of allowing retries everywhere, and gotten into retry storms. When I was next presented with the problem, I tried the other naive thing of only allowing retries from the very top level service, which led me to redoing absolutely tons of work for each failure. What's a nice middle path that doesn't add too much complexity?
tregoning•15m ago
https://en.wikipedia.org/wiki/Exponential_backoff
anonymars•12m ago
https://devblogs.microsoft.com/oldnewthing/20051107-20/?p=33...
applfanboysbgon•9m ago
This is trading a good developer experience for a bad user experience. There are situations where it makes sense to force manual retry, but there's no reason to apply one universal rule to all possible situations. Lack of considering nuance for your situation is just intellectual laziness.
sroussey•9m ago
Yes, exponential back off and jitter are the first things to work on, and good if you don’t have a better signal (like loss of network).

Also, a simple signal status server or queue system helps to keep global state such that everyone doesn’t retry all at once.

If you have a central error rate server you can skip your retry based on the error rate (100% error rate, don’t retry, etc).

sroussey•14m ago
So many variables, but the simple thing is to set things up like normal rate limiting (which you would want to do anyways). The one generating the errors passes back a retry time. You can add jitter here, tell low priority requests to wait longer, etc.

BTW: do keep track of priority. It’s like having a database that gets flooded with connections and won’t allow new ones in—but will for admin users (btw, it did not used to be that way in the early days of MySQL).

otterley•9m ago
https://aws.amazon.com/blogs/developer/introducing-retry-thr... (2016 -- 10 years ago!)

https://builder.aws.com/content/3EumjoZascWd1oZiEgL8ORlv3qE/... (originally published 2020, republished 2026)

https://docs.aws.amazon.com/sdkref/latest/guide/feature-retr...

https://aws.amazon.com/blogs/developer/announcing-updated-re... (2026)

maxchisto•1m ago
I'm suspicious of load shedding not mentioned in the article. Combine that with exp backoff and you got yourself a pretty robust starting point