| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| PostgreSQL MVCC, Byte by Byte |
| |
| |
PostgreSQL's MVCC stores two 32-bit XIDs per tuple - xmin and xmax. The transaction snapshot decides visibility per tuple. Updates append new tuples and mark the old with xmax. VACUUM reclaims versions only when no active snapshot can see them. Long-running REPEATABLE READ snapshots pin versions and cause bloat.
Why it matters: Long-running REPEATABLE READ snapshots pin tuple versions. Teams must watch idle transactions and tune autovacuum or switch isolation levels to avoid bloat and extra I/O. |
|
| |
|
| |
|
| |
| How The Heck Does Shazam Work? (An Interactive Exploration) ✅ |
| |
| |
A phone captures audio and runs a Fast Fourier Transform (FFT) on short windows. It builds a spectrogram and extracts peaks. Nearby peak pairs form compact hashes (two frequencies + time delta). An inverted index maps those hashes to songs, and timing validates matches.
Most services run lookups on servers against vast databases. On-device systems trade coverage for lower latency, better privacy, and curated models. |
|
| |
|
| |
|
| |
| The AWS Lambda 'Kiss of Death' |
| |
| |
| A Galera writer node froze after InnoDB undo history ballooned. Pooled AWS Lambda connections left transactions open and pinned MVCC read views. The team killed stalled sessions, enabled innodbundologtruncate, and capped innodbmaxundologsize. They also set session transactionisolation=READ-COMMITTED. That shrinks MVCC read views and speeds purge. |
|
| |
|
| |
|
| |
| I Decompiled the White House's New App |
| |
| |
A React Native app built with Expo SDK 54 runs Hermes. It talks to a WordPress REST backend and bundles a 5.5MB Hermes bytecode.Its WebView injects JavaScript to strip cookies, GDPR prompts, and paywall dialogs.
The build includes OneSignal's fused-location pipeline, polling at 4.5 and 9.5 minutes and syncing lat/lng.
It loads remote JS from a personal GitHub Pages site and Elfsight widgets.
It still ships dev artifacts: localhost URLs and the Expo dev client. |
|
| |
|
| |
|
| |
| Why are top university websites serving p0rn? It comes down to shoddy housekeeping. |
| |
| |
Researcher Alex Shakhov found scammers commandeering stale CNAME records. They hijack university subdomains (eg. berkeley.edu, columbia.edu, washu.edu) and serve p0rn and scam pages.
Shakhov found hundreds of abused subdomains across at least 34 universities. He counted thousands of hijacked pages indexed by Google.
This isn't exotic but a cleanup failure.
What matters: Universities must enforce DNS deprovisioning and record cleanup to block subdomain takeover via stale CNAME entries. |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
