Front-page articles summarized hourly.
The piece catalogs fifteen years of C++ standard-library walk-backs and deprecations, arguing that the committee repeatedly ships features only to preserve ABI stability. It notes std::function's legacy status and its replacements: std::move_only_function (C++23), std::copyable_function (C++26), and std::function_ref (C++26). Changes appear in three tiers: formal walk-backs, widely-avoided features, and stubborn, non-deprecated defaults (std::unordered_map, std::map, std::list, std::vector<bool>, std::regex, std::deque). Because of ABI-level stability, these cannot be removed, leaving production code reliant on non-standard libraries. The takeaway: learn to read the pattern and avoid common traps.
“His nibs” is a mildly derisive mock title for a self-important man in authority, modeled on “his lordship.” It first appears in print around 1820; early glossaries say it means the person referred to, but a deprecatory sense develops later. Nibs is a variant of nabs from the 1790s, with related forms nab, nib, nob/knob, and neb; vowel sounds vary. Possible links include imagery of heads or noses or aristocratic airs; nob may come from noble/nobleman, but this is unsettled. The general outline is clear, but the full etymology remains unresolved.
Could not summarize article.
This article analyzes the C64 Dead Test cartridge font, a stand‑alone ROM font used by the Ultimax cartridge (Rev. 718220) that omits the C64’s built‑in character ROM. It implements 58 characters (screen codes 0x00–0x39): uppercase A–Z, digits and select punctuation, in a boxy MICR‑inspired style. The odd 0x21 glyph is the MICR transit symbol as an Easter egg. Font data sits at $EAD8; the cartridge uses Ultimax mode via GAME/XROM. A disassembly is provided and ROMs for C64, PET, VIC‑20 (including katakana) are downloadable.
A WordPress.com 429 error indicates a minor system issue and instructs users to refresh the page and contact support if the problem persists.
The Verge chronicles how Bambu Lab’s push to lock down its 3D‑printer ecosystem sparked a backlash after Paweł Jarczak shared a way to run third‑party tooling with Bambu hardware. Bambu privately messaged Jarczak to remove his code and warned of a DMCA threat; Jarczak removed it and publicized the tense exchange. Open‑source advocates and YouTubers pledged funds to defend Jarczak, forked Bambu Studio (and OrcaSlicer), and the Software Freedom Conservancy began a project to reverse‑engineer Bambu’s code. The dispute centers on AGPL obligations, security, and whether Bambu’s cloud should be open.
Buildcraft reframes complex skill/support interactions as a small compiler pipeline. Authored content (skills, supports, items, statuses) emits runtime facts: stat modifiers and behavior changes, which are folded into derived caches for combat. The pipeline flows: support definitions -> active slot mask -> stat-modifier rows -> behavior-emission rows -> dirty-domain checks -> skill caches -> delivery resolution. Rows carry provenance (skill_slot, support_slot) and scopes (entity vs skill). Tag-based applicability replaces a giant matrix, and rule rewrites separate from stat math. Incremental rebuilding via dirty flags avoids stale output. The aim: a data-driven, testable, bounded system rather than ad-hoc special cases.
Grothendieck redirected 20th-century math by focusing on hidden structures and a new language of spaces. He generalized Riemann–Roch (1957) and, at the 1958 ICM, proposed “schemes” to remake algebraic geometry, showing equations could be studied independent of the base number system. He introduced sheaves, stalks, then later topoi, stacks, motives, and étale cohomology, tying geometry to number theory, topology and logic. Schemes let math import geometric methods into algebra; they aided progress on Weil conjectures. Grothendieck led an ascetic life from 1970, dying in 2014.
After four years at AWS, the author is leaving (fired), relieved by the change as the company shifts toward Generative AI and organizational changes. They criticize treating employees as fungible, a customer-obsession decline, and a push to use AI for rapid, sometimes unnecessary content. A highlight was helping reinstate a suspended Northern Africa customer’s AWS account and restoring their resources, though leadership showed little interest. Layoffs and health stress followed. The piece ends with returning to open source roots and questions about AI access and hardware costs.
Chrome’s Declarative Partial Updates introduce out-of-order HTML streaming via new APIs to deliver content without waiting for the whole document. The <template for> API uses processing instructions (<?marker>, <?start>, <?end>) to replace placeholders as content streams in. Static and streaming insertion methods (setHTML, replaceWithHTML, before/after/append/prepend) and their unsafe variants, with an optional sanitizer and script support, enable dynamic partials. Polyfills exist while standardization progresses. Use cases include island architectures, streaming large content, and injecting partials in SPAs.
France’s Paris Appeals Court found Air France and Airbus guilty of manslaughter in the 2009 AF447 crash, ruling they were solely responsible for the disaster that killed 228 people when the Rio–Paris flight stalled in a storm and plunged into the Atlantic. The verdict overturns a 2023 acquittal; each company faces a maximum €225,000 fine. Both plan to appeal; investigators cited sensor icing and pilot error, with training and sensor upgrades since then.
Procedural Fascicle Revised 7 of the Scheme Large Edition documents the Revision 7 Scheme report with Working Group 2 editors and editors of earlier reports. It notes substantial copying from previous reports, credits former editors, and states this does not imply endorsement. The fascicle is released for free, and may be copied or adapted; implementors are urged to use it as a starting point and modify as needed. Some sections are adapted from sources with attribution requirements; see the legal section for details.
Advances a new severity model based on collision count: standard severity for a single report; higher severity when two or more researchers report the same bug; if a working exploit with PoC exists, the patch window becomes days (P0). It discusses the independent researcher problem and urges filing reports with attached patches to speed fixes. For corporates, it calls for faster, deeper defense: supply-chain discipline, defense in depth, continuous runtime checks, and architectural controls (egress lockdown, ephemeral infra, sandboxing, circuit breakers). It also addresses AI-assisted discovery, false positives, and the need for fast, safe deploy rails.
Finite VC dimension exactly captures learnability. The post proves the equivalence of uniform convergence, agnostic PAC, realizable PAC, and finite VC dimension. With VC dimension d, the VC generalization bound gives uniform convergence: Pr[sup_h |L_S(h)−L_D(h)|>ε] ≤ 4 Π_H(2m) e^{−mε^2/8} ≤ 4 (2em/d)^d e^{−mε^2/8}, yielding m = O((d + log(1/δ))/ε^2). Sauer–Shelah bounds the growth function by Φ(m,d) = ∑_{i=0}^d binom(m,i). No-Free-Lunch: infinite d ⇒ not learnable. Part 2 previews Rademacher refinements.
Twixt.GAMES offers a daily word puzzle: transform a start word into an end word in exactly four moves, using each move type once in any order: Anagram, Verb form, Homophone, and Compound. Rules require a unique solution, no repeated words, and ending on the end word; moves can be undone. A new puzzle appears daily at local midnight. Hints reveal the move type, and a second hint reveals the correct word. Sharing shows time and rank, and mobile adds an image. Achievements include turning the start word into the end word in four moves.
Clock changes can trigger ping’s “taking countermeasures” by producing negative RTTs. The post explains ping’s timing: two modes—old wall-clock using gettimeofday and a newer network-time mode via SO_TIMESTAMP; RTT is derived from a send timestamp embedded in the ICMP payload and a receive timestamp from CMSG. Timekeeping quirks like vdso, leap seconds, and DST complicate debugging. The author demonstrates fault-injection with strace and LD_PRELOAD to fake time, notes CAP_NET_RAW blocks preloads, and advises ensuring NTP health to avoid countermeasures.
Scammers have exploited an internal Microsoft email address used for legitimate alerts to send spam-looking messages, posing as Microsoft. They create new Microsoft accounts and use [email protected] to send emails with subject lines mimicking official notices and links to scam sites. The abuse has been ongoing for months, per The Spamhaus Project, which notified Microsoft. Microsoft is investigating, tightening detection and blocking, and removing violating accounts. This mirrors other recent incidents of attackers abusing company systems for phishing.
An AI-assisted security review of a microservice that serves uploaded HTML uncovers critical risks and mitigations. Key flaw: /api/pages/:id/content returns raw HTML, enabling stored XSS; mitigations include strict Content-Security-Policy, X-Content-Type-Options nosniff, sandboxed iframe, and app-shell headers; CSP built with trusted CDN origins. Medium risks include no upload/report throttling; rate limiting now uses a secret, HMAC hashes of IP+UA and subject stored in Netlify Blobs with Sentry logging. Admin delete token risk discussed; origin check added to deletion workflow. Validation tightened with parse5 and 2MB cap. Conclusion: more robust, still some gaps; code available.
Made by Johno Whitaker using FastHTML