frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
724•pcompeau•5h ago•119 comments

Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use

https://xusheng.dev/posts/windows-coding-agent-telemetry/
234•cwaffles•2h ago•111 comments

BugMeNot has closed

https://www.bugmenot.com/
319•lode•4h ago•160 comments

Optimizely Compromised, Served Malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
105•kristjansson•2h ago•64 comments

OpenCode Browse

https://opencode.ai/product/browse
121•mfiguiere•4h ago•55 comments

How to Break into Security, Ptacek Edition (2012)

https://krebsonsecurity.com/2012/06/how-to-break-into-security-ptacek-edition/
73•ronfriedhaber•3h ago•19 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
108•sebg•5h ago•36 comments

Formal Verification Is Not Verifiable

https://alperenkeles.com/posts/formal-verification-is-not-verifiable/
64•zdw•2d ago•9 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
296•geerlingguy•9h ago•209 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
309•burntsushi•9h ago•74 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
215•PaulHoule•8h ago•222 comments

Do Repeat Yourself

https://arcentry.com/blog/do-repeat-yourself/
26•max_sendfeld•13h ago•7 comments

Show HN: Sutra-OS – A self-hosted ontology platform

https://github.com/0nelight/sutra-os
28•0nelight•2h ago•11 comments

Technical issue at JPMorgan Chase triggers online banking delays for US banks

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
715•samk3nny•7h ago•593 comments

New open source C4 Diagram tool

https://www.youtube.com/watch?v=ZCAHP50Zly8
10•oliveralbertini•1d ago•2 comments

Running coding agents without handing them my credentials

https://blog.antonio.cx/running-agents-with-lend
7•antoniomika•35m ago•2 comments

Squircles

https://linebender.org/wiki/curves/squircle/
131•raphlinus•17h ago•39 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
184•speckx•5h ago•120 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

25•arshpatankar•5h ago•10 comments

United Airlines experiencing a widespread system outage, airline says

https://www.cnn.com/2026/11/16/us/united-airlines-outage
171•bearsyankees•3h ago•86 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
221•Bender•12h ago•161 comments

My Quest to push native Three.js quality match AAA Game Engines

https://ben3d.ca/blog/building-the-aaa-lighting-pipeline-in-threejs
92•bhouston•4h ago•35 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
298•sammatilda•14h ago•115 comments

How to Intercept HTTP/3 Traffic: QUIC and Qpack

https://interceptsuite.com/blog/intercept-http3-traffic-quic-qpack-explained/
60•anof-cyber•6h ago•7 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
103•maufl•8h ago•51 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
91•speckx•8h ago•41 comments

Pentagon fails ninth straight audit despite progress in organizing finances

https://www.reuters.com/business/aerospace-defense/pentagon-fails-ninth-straight-audit-despite-pr...
24•petethomas•1h ago•1 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
97•michaelsbradley•9h ago•30 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
839•DeepLogin•12h ago•510 comments

Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
105•rossant•7h ago•232 comments
Open in hackernews

Achieveing lower latencies with S3 object storage

https://spiraldb.com/post/so-you-want-to-use-object-storage
31•znpy•1y ago

Comments

jmull•1y ago
> Roughly speaking, the latency of systems like object storage tend to have a lognormal distribution

I would dig into that. This might (or might not) be something you can do something about more directly.

That's not really an "organic" pattern, so I'd guess some retry/routing/robustness mechanism is not working the way it should. And, it might (or might not) be one you have control over and can fix.

To dig in, I might look at what's going on at the packet/ack level.

nkmnz•1y ago
I don't know what you mean by the word "organic", but I think lognormal distributions are very common and intuitive: whenever the true generative mechanism is “lots of tiny, independent percentage effects piling up,” you’ll see a log‑normal pattern.
jmull•1y ago
You can think of a network generally as a bunch of uniform nodes with uniform connections each with a random chance of failure, as a useful first approximation.

But that’s not what they really are.

If you’re optimizing or troubleshooting it’s usually better to look at what’s actually happening. Certainly before implementing a fix. You really want to understand what you’re fixing, or you’re kind of doing a rain dance.

pyfon•1y ago
How do you do that for an abstract service like S3? I see how you could do that for your own machines.
anorwell•1y ago
The article posts a table of latency distributions, but the latencies are simulated based on the assumption that latencies are lognormal. I would be interested to read the article comparing the simulation to actual measurements.

The assumption that latencies are lognormal is a useful approximation but not really true. In reality you will see a lot of multi-modality (e.g. cache hits vs misses, internal timeouts). Requests for the same key can have correlated latency.

MasterIdiot•1y ago
I think the distribution he uses is pretty close to the paper he links "Exploiting Cloud Object Storage for High-Performance Analytics" https://www.durner.dev/app/media/papers/anyblob-vldb23.pdf
tossandthrow•1y ago
The hedging strategies all seem to assume that latency for an object is an independent variable.

However, I would assume dependency?

Eg. if. a node holding a copy of the object is down and traffic needs to be re-routed to a slower node. Indifferently of how many requests I send, the latency will still be high?

(I am genuinly curious of this is the case)

n_u•1y ago
It’s not addressed directly but I do think the article implies you hope your request latencies are not correlated. It provides a strategy for helping to achieve that

> Try different endpoints. Depending on your setup, you may be able to hit different servers serving the same data. The less infrastructure they share with each other, the more likely it is that their latency won’t correlate.

addisonj•1y ago
S3 scale is quite massive with each object spread across a large number of nodes via erasure encoding.

So while you could get unlucky and routed to same bad node / bad rack, the reality is that it is quite unlikely.

And while the testing here is simulated, this is a technique that is used with success.

Source: working on these sort of systems

jmpman•1y ago
Lots of areas left for exploration.
up2isomorphism•1y ago
S3 is a bad choice if you need low latency to begin with.
mannyv•1y ago
They have both ssd and platter based storage now. So that's not a true statement anymore.
up2isomorphism•1y ago
The problem of s3 latency is never about hdd or ssd to begin with.

This a big problem of so called modern “data pipeline”; public cloud providers will anything and a lot of people will believe it.

mannyv•1y ago
No, sorry.
sgarland•1y ago
Network-based storage is a bad choice if you need low latency, period. You’re not going to beat data locality.
UltraSane•1y ago
It is kinda of crazy how much work is done to mitigate the very high latency of S3 when we have NVMe SSDs with access latency of microseconds.
addisonj•1y ago
Yeah, engineering high scale distributed data systems on top the cloud providers a very weird thing at times.

But the reality is that as large enterprise move to the cloud, but still need lots of different data systems, it is really hard to not play the cloud game. Buying bare metal and direct connect with AWS seems a reasonable solution... But it will add years to your timeline to sell to any large companies.

So instead, you work in the constraints the CSPs have, and in AWS, that means guaranteeing durability cross zone, and at scale, that means either huge cross az network costs or offloading it to s3.

You would think this massive cloud would remove constraints, and in some ways that is true, but in others you are even more constrained because you don't directly own any of it and are the whims of unit costs of 30 AWS teams.

But it is also kind of fun

UltraSane•1y ago
If cross AZ bandwidth was more reasonably priced it would enable a lot of design options like running something like MinIO on nothing but directly connected NVMe Instance store volumes.
jen20•1y ago
The very first sentence of this article contains an error:

> Over the past 19 years (S3 was launched on March 14th 2006, as the first public AWS service), object storage has become the gold standard for storing large amounts of data in the cloud.

While it’s true that S3 is the gold standard, it was not the first AWS service, which was in fact SQS in 2004.

hermanradtke•1y ago
I thought S3 was first as well.

This is the source Wikipedia uses: https://web.archive.org/web/20041217191947/http://aws.typepa...

adam_gs•1y ago
author here - took that quote from this[1] blog post by an AWS VP/distinguished engineer, the use of "public service" might have some loosely defined meaning in this context.

[1] https://www.allthingsdistributed.com/2025/03/in-s3-simplicit...

jen20•1y ago
Interesting source - looks like it means “GA” service, rather than “public” per se. The SQS beta was also available to the public.
n_u•1y ago
What I’ve always been curious about is if you can help the S3 query optimizer* in any way to use specialized optimizations. For example if you indicate the data is immutable[1] does the lack of a write path allow further optimization under the hood? Replicas could in theory serve requests without coordination.

*I’m using “query optimizer” rather broadly here. I know S3 isn’t a DBMS.

[1] https://aws.amazon.com/blogs/storage/protecting-data-with-am...