frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
344•zdw•3h ago•169 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
905•rafaelc•1d ago•205 comments

AI Supply Chain Security: What Canary Tokens Found

https://www.dragos.com/blog/ai-supply-chain-security-canary-tokens
50•kristianp•2h ago•4 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
975•g-b-r•17h ago•820 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
20•tamnd•2h ago•3 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
439•k__•13h ago•109 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
113•sdko•5h ago•40 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
10•kouosi•1h ago•1 comments

Sandwich Simulator

https://stulle.app/
173•subdomain•7h ago•61 comments

The Engineering Manager's role is under attack (again)

https://www.manager.dev/newsletter/the-engineering-manager-s-role-is-under-attack-again
15•fagnerbrack•54m ago•5 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
598•beginning_end•18h ago•381 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
246•jger15•1d ago•80 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
105•sebaandrada•9h ago•11 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
10•wglb•2d ago•0 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
559•soheilpro•21h ago•266 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
46•Anon84•5h ago•80 comments

Split Radiance Cascades

https://www.jacktollenaar.top/articles/split-rc.html
18•ibobev•2d ago•0 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
74•vasie•11h ago•14 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
111•f311a•13h ago•52 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
148•raphlinus•10h ago•44 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
230•fortran77•3d ago•149 comments

GnuPG Security Advisory for GPGME

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
250•gdgghhhhh•23h ago•98 comments

Shaping the Loops, Closing the Loops

https://revyl.com/blog/pattern-engineering/
21•based0x10•3d ago•9 comments

Leonida – PC Recompilation of the Xbox Version of GTA 6

https://github.com/ItsNotRexed/Leonida
136•ebrahimh•6h ago•102 comments

Show HN: Zero C# – C# without a runtime or GC

https://onurgumus.github.io/zero-csharp/index.html
152•reverseblade2•16h ago•105 comments

PostgreSQL Extensions in Go

https://jespino.github.io/gopgext/
140•valyala•14h ago•24 comments

Tasklet (YC P26) Is Hiring Product and Agent Infra Engineers

https://tasklet.ai/careers
1•mayop100•10h ago

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2405•jasondavies•1d ago•1169 comments

Verification files for the Lean proof of the Riemann Hypothesis

https://math.mit.edu/~drew/grh/
111•Bluestein•16h ago•38 comments

Together.ai: Prompt Leakage for Requests

https://www.together.ai/blog/security-event-prompt-leakage-for-requests-in-june-and-july-of-2026
21•Fe2O3•4h ago•8 comments
Open in hackernews

Garbage collection of object storage at scale

https://www.warpstream.com/blog/taking-out-the-trash-garbage-collection-of-object-storage-at-massive-scale
96•ko_pivot•1y ago

Comments

juancn•1y ago
Another possible mechanism for doing GC at scale (a variation on Asynchronous Reconciliation in the article) in some file/object store, is doing a probabilistic mark and sweep using bloom filters.

The mark phase can be done in parallel building many bloom filters for the files/objects found.

Then the bloom filters are merged (or'ed together essentially) and then a parallel sweep phase can use the bloom filter to answer the question: is this file/object live?

The bloom filter then answers either "No" with 100% certainty or "Maybe" with some probability p that depends on the parameters used for the bitset and the hash function family.

cogman10•1y ago
What does the bloom filter solve?

The expensive portion of the mark and sweep for the object store is the mark phase, not the storage of what's been marked. 100s, 1000s, or even millions of live objects wouldn't hardly take any space to keep in a remembered set.

On the other hand, querying the S3 bucket to list those 1M objects would be expensive no matter how you store the results.

But this does tickle my brain. Perhaps something akin to the generational hypotheses can be applied? Maybe it's the case that very old, very young, or very untouched objects are more likely to be garbage than not. If there's some way to divide the objects up and only look at objects whose are in "probably need to be collected" regions, then you could do minor fast sweeps semi frequently and schedule more expensive "really delete untracked stuff" infrequently.

Cicero22•1y ago
I was thinking they could use something like cloudwatch events, or something, to trigger sweeps and significantly reduce scheduled sweeps.

They could even use cost allocation tags to predict if a bucket or group of buckets should be scanned if it's growing unexpectedly. Cost isn't a perfect metric but there's definitely signal there.

juancn•1y ago
Building the set of used files or objects (which is what mark does in a mark/sweep).

Sometimes it's too expensive to mark in place, even if it's a bit that you need to write to disk and keeping a set of references may be prohibitive (or the structure holding the references is mostly/effectively immutable).

If it's all memory and mutable it doesn't (normally) really matter, but when it's not, you ideally would have some mechanism to move the code to where the data is, rather than stream the data to where the compute is (it is really wasteful for large scale data processing).

In any case, you would not be moving/scanning the files themselves, but the metadata is what you want to read for the mark phase.

The article if I understood correctly implies that the files and the metadata of the files (Kafka queues and so on) are separate, so presumably, the metadata is much much smaller than the data itself, but still potentially large.

For example if you had a large scale content addressed store (think a massive version of git's blob storage), you typically add to something like that and keep a few mutable root references to start your GC from to seed a mark/sweep.

Following the git example, the roots would be the branches, tags and reflogs, and the metadata you scan the transitive closur of the trees that are reachable from those (simplifying a bit) but not the file blobs themselves.

I use git as an example because a a CAS lends itself very well to large scale distributed systems because you can reason about it as an immutable data structure, but you can still change it effectively with sane semantics.

donavanm•1y ago
If you like big beautiful storage and probabilistic structures check out https://www.usenix.org/conference/osdi14/technical-sessions/.... The coho data folks ended up in AWS S3 a few years later.
juancn•1y ago
Thanks! I hadn't seen it and it may come handy!
deathanatos•1y ago
> Why Not Just Use a Bucket Policy?

I've heard these words so many times, it's refreshing to see someone dig into why bucket policies aren't a cure-all.

As for "Why not use synchronous deletion?" — regarding the pitfall there, what about a WAL? I.e., you WAL the deletions you want to perform into an object in the object store, perform the deletions, and then delete the WAL. If you crash and find a WAL file, you repeat the delete commands contained in the WAL.

(I've used this to handle this problem where some of the deletions are mixed: i.e., some in an object store, some in a SQL DB, etc. The object store is essentially being used as strongly consistent storage.)

(Perhaps this is essentially the same as your "delayed queue"? All I've got is an object store though, not a queue, and it's pretty useful hammer.)

telotortium•1y ago
> HN Disclaimer: WarpStream sells a drop-in replacement for Apache Kafka built directly on-top of object storage.

First time I’ve seen one of these. That’s actually a better way to advertise your product than putting it at the end.

hencq•1y ago
Yes, though I think they meant to say disclosure instead of disclaimer.
siscia•1y ago
What I see working extremely well, arguably in a setting where cost was not really an issue was a much simpler approach.

Keep compacting files at some regular cadence `t` and keep a bucket policy to delete files older than `t+delta+buffer`.

Then have an alarm for files older than `t+buffer`