Jeff 🏈

🚨Quarterbacks expected to start in #NFL Week 9: Joe Fagnano - #Ravens Joe Milton - #Eagles JJ McCarthy - #Giants Gardner Minshew - #Cardinals Shedeur Sanders - #Browns Drew Lock - #Seahawks

I worked for a startup where the boss kept saying "We're not a company, we're family." Family until payday. Payday comes. No salary. He says "Family understands, we're building something. Be patient." Next day he posts a photo of his new car. Caption: "God is good. Hard work pays." Bro, OUR hard work paid for YOUR car. Where is our salary? I asked him "When are we getting paid?" He said "Don't have a poverty mindset. Money will come." I left that "family" 2 weeks later. Family doesn't starve you while dad buys a new Benz.

I "read" all ~120 Hacker News comments on @posthog moving its warehouse off DuckDB so you don't have to. The best bits: 1/ Scope the author and the founder both showed up to say ClickHouse wasn't replaced. This was the warehouse product, used by a handful of pilot customers. The author admits the post "left out the context." 2/ The number the blog didn't give. most customers had pods at 46 vCPUs / 360GB "and asked for more." 3/ Then: "Imagine when a query is running for 12h ... and then another 10 from the same customer come in :)" 4/ Why not Iceberg + Trino from day one? One commenter asked three times. Another replied: "It's the third time you've probed this question bud." The author's answer: "We tried Iceberg and it was too slow writing data." 5/ Trino isn't there to be fast. "We are using it for long running data modelling jobs or nightly ETLs." 6/ Quack, DuckDB's client-server protocol, can't do "anything that looks remotely like distributed querying." 7/ Most honest line in the thread: "we spent too much time not rethinking our approach but sunken cost fallacy." 8/ Best history lesson: "The 2026 equivalent of 2016's 'Why Uber Engineering Switched from Postgres to MySQL'!" (lol) 9/ Best prediction: "6 months from now: We are moving our warehouse off of Trino + HogLake to newer technology XXX." (re-lol) 10/ Best agent-era advice: "Tell your agent to identify a list of databases and try them all, in prod, until it finds a good one. Be sure to tell it 'no outages'." PostHog's old goal was to delay a company's first data engineer hire. A commenter: "Ironically a good data engineer should probably let them avoid needing 3 different data warehouse systems within a year."

We have had the sanity engineering blog out for about a quarter, and here's how it went: Six posts by the engineers who did the work. Everything is hand-typed¹. About 16k folks behind browsers have read them, and our companion reddit posts are passing 75k views. We see folks signing up to @sanity_io after, going to our career pages, and even leave a response in our "contact sales" form. And we published some real goodreads: → How we cut our self-hosted @grafana Mimir bill 48% with Arm CPUs and fewer zonal hops (Josh McConnell) → Why em-sized spinners wobble in Safari, and the CSS round() fix (@cody__olsen). It hit #1 on r/css. → How well coding agents actually use a design system, after four months of daily evals (@jabberingme) → The 0.5-second agent, built on @typesafeai Jev (@johnsicili) → "Hi S": the harness behind 70+ agents in our Slack (@even, @rostimelk) → What real-time MCP events could look like, and what stands in the way (@ai_ftw_) sanity.io/engineering (and make sure to sign up for the newsletter version - because you want more email, right?) ¹ there might traces of meat proxy leaks here and there and it's probably all my fault.

NEW POD: The OFFICIAL Power Rankings of Record™️ for Week 9, with a shakeup in the top 5! Plus we recap MNF with Jeffery Simmons making a statement in his Bears debut: 📺youtu.be/_7W8jy3Lh4A 🎧podcasts.apple.com/us/podcas… 🎧open.spotify.com/episode/4k8…

Ubuntu finally has fixes for the Linux kernel bug everyone has been yelling about. There's a catch, though: you have to go and get them yourself. CVE-2026-98432 is a use-after-free in how the kernel sets up IPv4 TCP connections. It has been there since Linux 4.4 and is rated CVSS 9.8. Anthropic says it generated a working exploit for it with AI but hasn't released it. Weeks after the CVE went public on October 15, Ubuntu's LTS kernels were still listed as vulnerable, and a Hacker News thread called "Ubuntu still has not released patch for Linux 0day RCE in almost 3 weeks" took off. Canonical's Luci Stanescu now says fixed kernels are in the -proposed pocket: 5.15.0-203.213 for 22.04, 6.8.0-149.149 for 24.04 and 7.0.0-43.43 for 26.04. 26.10 is already fixed in 7.3.0-10.10. The kernels are still being tested "on more than 2,000 certified servers and devices" before they reach regular updates. For 20.04 and older, the fix is still pending. Canonical also pushed back on the popular "disable MPTCP" workaround: "The Ubuntu Security Team believes that security updates are the only appropriate mitigation." On oss-security, CIQ kernel engineer Sultan Alsawaf agreed that disabling MPTCP alone isn't enough, "since the bug is in plain IPv4 TCP."

What was Brian Fleury thinking?!! 6:30 left down 10… and they looked lethargic. The drive had zero urgency. No hurry-up, no tempo, no life… • Run-run-stall turns a comeback into a timeout • Sack happens after the routes take too long • Penalty saves the drive… then comes the interception Is this an OC problem, or just players not executing? #NFL #FootballAnalysis #GameManagement PHOTOS: Steven Bisig-Imagn Images

Behind every fast query, smart filter, or scalable database lies a powerful data structure. These 20 structures aren’t just theory, they’re the backbone of real-world systems that power search engines, time-series storage, blockchain, and more. 1. Indexing Structures Hash Index, B-Tree, Skiplist, Bitmap Index, Trie These are the go-to structures for fast data access. Whether it’s quick key-value lookups in memory or sorted traversals on disk, these structures form the core of query performance in most databases. 2. Search & Pattern Matching Inverted Index, Suffix Tree, Segment Tree, R-Tree Designed for deep searches — from documents and strings to spatial queries — these structures support full-text search, multi-dimensional lookups, and real-time analytics. 3. Write-Optimized Storage LSM Tree, SSTable, Bloom Filter High-ingestion databases like Cassandra and RocksDB rely on these to optimize write speed while managing data compaction and fast approximate lookups with minimal memory overhead. 4. Spatial & Range Indexing Quad Tree, Z-order Curve, Segment Tree Used in applications like maps, game engines, and time-series systems — these structures help partition and access multi-dimensional or sequential data efficiently. 5. Advanced Use Cases Merkle Tree, Suffix Tree, Bloom Filter From verifying blockchain transactions to bioinformatics and deduplication in distributed systems — these data structures are built for reliability and integrity at scale. Knowing these structures and more importantly, where they’re used - helps you design database systems that are optimized, reliable, and scalable. What will you add to this?

Our radio call on huge run by Tyler Allgeier on 2nd of back to back 50+ yard runs. Have a day Tyler Allgeier #nfl | #arizona | #cardinals | #RiseUpRedSea  | #football @AZCardinals @HFroholdt @tylerallgeier25 @jpshadrick @jimohms

Update on the 9.8 CVSS TCP/IP RCE in the Linux kernel (CVE-2026-98432): we've detected what appears to be a threat actor activity scanning the entire internet for exposed affected systems. Our own scanning also suggests that the number of potential targets is high, therefore there is an increased likelihood of threat actors attempting to develop exploits for the vulnerability. while CVE-2026-98432 is believed to require MPTCP to be enabled in the kernel, as well as a listening app/service which binds an MPTCP socket, which many have suggested should be rare, several kernels including Debian enable MPTCP by default. Additionally, Go 1.24+ binds MPTCP sockets by default if the option is enabled in the kernel, so anything built on top of Go (including Caddy) will create the required MPTCP listener. The mitigation of setting net.mptcp.enabled=0 disabled MPTCP, but does not apply to existing sockets, so any applications that have bound MPTCP sockets need to be restarted, otherwise the system remains exploitable. You can check if your server is running any MPTCP listeners with the following command: sudo ss -Mlnp On 2026-10-30 our preliminary internet-wide scan of port 443 confirmed that there are approximately 2,102,043 servers that are successfully reachable via an MPTCP connection. A deeper scan which attempts to connect to each endpoint on port 443 and negotiate a full TLS connection with MPTCP enabled returned about 762,774 systems. Neither scan can confirm that these are unpatched kernels, just total exposure, but it's a lot more systems than expected. Since a valid HTTP connection is not required to exploit the vulnerability, the total attack surface is likely closer to the 2.1 million number than the 763k one. As of today (2026-11-02), we've picked up several residential proxies and VPNs scanning the internet on port 443 using MPTCP-enabled connections. Since regular scanners do not negotiate MPTCP by default, and no data is being sent to the HTTP server over 443, we strongly suspect this activity is scanning for CVE-2026-98432 specifically. The use of residential proxies and RU-based VPN servers suggests that this is likely threat actor scanning, rather than security researchers. Currently there are no known publicly available remote code execution exploits, but there are several denial of service proof-of-concepts floating around. This code gives threat actors a starting point to begin attempting to weaponize the vulnerability. Building exploits for the vulnerability is reported to be extremely difficult, but several state-sponsored threat actors likely have the resources required to succeed.

"I sat there afterwards, and I was thinking in all my days covering this team (since 1984), this loss might stick out to be one of the, if not the worst, I think I've ever witnessed." @Spags52 weighs in on the Cowboys' stunning OT loss to the Cardinals on @OThankKevin and @inthemageors

THIS IS F**KING INSANE FOUND 3 OPEN SOURCE HACKING TOOLS THAT MAKE OSINT INVESTIGATIONS LOOK LIKE A SPIDER WEB. Stop jumping between tabs. These tools help you connect the dots, follow digital footprints and uncover relationships between online identities and infrastructure. FLOWSINT → Visual graph based investigations → Pivots across domains, IPs, emails and usernames → DNS, WHOIS, TLS and social account enrichment SPIDERFOOT → 200+ OSINT modules → Automated data collection and correlation → Web interface, CLI and multiple export formats RECON-NG → Modular web reconnaissance framework → Metasploit style command interface → Workspaces and module marketplace Three tools. Different approaches to mapping digital footprints and gathering intelligence. Only investigate targets you own or have permission to assess. REPO BELOW