frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
227•zaik•4h ago•56 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
313•ilreb•3h ago•106 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
239•hspeiser•7h ago•125 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
175•zdw•6h ago•227 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
103•aillia•5h ago•24 comments

Preserving 30 years of Salon journalism

https://blog.archive.org/2026/11/12/preserving-30-years-of-salon-journalism/
128•CharlesW•7h ago•37 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
262•bcye•10h ago•51 comments

The Miracle Cure: In 1977, a drug rejected by doctors became a sensation

https://slate.com/technology/2026/11/doctor-medicine-cancer-cure-pill-history.html
29•mutexjp•2d ago•15 comments

A short explainer on how El Niño works [video]

https://www.youtube.com/watch?v=7_JF3etiAv8
212•nharada•11h ago•91 comments

Stop Filming in Log

https://digitalfilms.wordpress.com/2026/11/15/stop-filming-in-log/
15•dabinat•1h ago•5 comments

Handwriting, as a Font

https://ductus.sorenblank.com
209•coinfused•10h ago•44 comments

Do we still have to denormalize? Have your schema and search it too

https://www.paradedb.com/blog/joins
49•philippemnoel•2d ago•6 comments

The MacBook Pro's OLED PWM problem

https://macanorak.com/the-macbook-pros-oled-pwm-problem-when-a-better-display-becomes-worse-to-use/
451•MacAnorak•16h ago•255 comments

Crows make decisions faster than we can

https://www.nytimes.com/2026/11/15/science/birdbrain-crows-birds-research-decision.html
207•gumby•12h ago•145 comments

Tell HN: HN is being scraped for emails to scam

58•eks391•3h ago•10 comments

Claude Code and Codex reverse engineered my 1994 Jeep's ECU over a $3 Arduino [video]

https://www.youtube.com/watch?v=WPj3aQ-xxpI
396•envoked•4d ago•196 comments

WebGL Flight Simulator with seed generated terrain

https://baron.by.dai.studio/
113•ranger_danger•9h ago•21 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
51•nerdypepper•6h ago•14 comments

Coles hit by a cybersecurity incident

https://www.colesgroup.com.au/updates/
83•sagunsh•4h ago•59 comments

Simple 8085 Computer

https://www.hackster.io/mit41301/simple-8085-computer-9fe156
14•AlexeyBrin•3d ago•1 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
24•artooro•1h ago•0 comments

Things That Turbo Pascal Is Smaller Than (2011)

https://prog21.dadgum.com/116.html
219•ksec•16h ago•116 comments

Skydio's asymmetrical F10 Lightrunner solves a problem with fixed-wing drones

https://spectrum.ieee.org/skydio-f10-lightrunner-asymmetrical-drone
25•Gaishan•6h ago•1 comments

Artificial Intelligence for the Z80

https://www.dfsantos.com/en/libro-ia-z80
18•AlexeyBrin•2d ago•2 comments

Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests

https://www1.wdr.de/nrw/rheinland/rhein-erft-kreis/technischer-defekt-chlor-phantasialand-100.html
474•DeepLogin•11h ago•201 comments

A quest to create the perfect whiskey glass

https://www.nytimes.com/2026/11/13/dining/drinks/kurt-josef-zalto-whiskey-glass.html
60•Kaibeezy•2d ago•60 comments

1900s How do you Wash a Kimono?

https://www.oldphotosjapan.com/photos/877/laundry-washing-clothes-meiji-19th-century-vintage-albu...
42•Matrixik•2d ago•10 comments

Eclipse Mosquitto – An open source MQTT broker

https://github.com/eclipse-mosquitto/mosquitto
83•gregsadetsky•11h ago•30 comments

Clice v1.0 Released: Welcome to Modern C++

https://ykiko.me/en/articles/2105384023094834022/
125•molenzwiebel•12h ago•76 comments

SpaceX catches the Starship to end Flight 15

https://www.spacex.com/launches/starship-flight-15
1669•ls612•1d ago•1253 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...