| 421. | Things I learned making a game engine | (joelotter.com) |
|
I’ve spent the last few years building my own game engine from scratch. Here are some of the things I learned. | |
| 3 points by JayOtter 2 days ago | 0 comments |
| 422. | England Historic Aerial Photo Explorer | (historicengland.org.uk) |
|
|
||
| 4 points by davemateer 6 days ago | 1 comments |
| 423. | Skin-roasted peanut consumption improves brain vascular function and memory | (clinicalnutritionjournal.com) |
|
|
||
| 3 points by PaulHoule 6 days ago | 0 comments |
| 424. | Purdue University Approves New AI Requirement for All Undergrads | (forbes.com) |
|
Purdue University will begin requiring that all of its undergraduate students meet an AI competency requirement starting with freshmen who enter the university in 2026. | |
| 4 points by rmason 2 days ago | 0 comments |
| 425. | Revolutions of 1989 | (en.wikipedia.org) |
|
||
| 3 points by thunderbong 1 day ago | 0 comments |
| 426. | Nvidia-backed Starcloud trains first AI model in space, orbital data centers | (cnbc.com) |
|
The company's Starcloud-1 satellite is running Gemma, an open model from Google, marking the first time in history that an LLM has been trained in outer space. | |
| 5 points by walterbell 1 day ago | 1 comments |
| 427. | The Eerie Parallels Between AI Mania and the Dot-Com Bubble | (wsj.com) |
|
|
||
| 3 points by JumpCrisscross 1 day ago | 0 comments |
| 428. | I couldn't find a logging library that worked for my library, so I made one | (hackers.pub) |
|
|
When I started building Fedify, an ActivityPub server framework, I ran into a problem that surprised me: I couldn't figure out how to add logging. Not because logging is hard—there are dozens of mature logging libraries for JavaScript. The problem was that they're primarily designed for applications, not for libraries that want to stay unobtrusive. I wrote about this a few months ago, and the response was modest—some interest, some skepticism, and quite a bit of debate about whether the post was AI-generated. I'll be honest: English isn't my first language, so I use LLMs to polish my writing. But the ideas and technical content are mine. Several readers wanted to see a real-world example rather than theory. The problem: existing loggers assume you're building an app Fedify helps developers build federated social applications using the ActivityPub protocol. If you've ever worked with federation, you know debugging can be painful. When an activity fails to deliver, you need to answer questions like: Did the HTTP request actually go out? Was the signature generated correctly? Did the remote server reject it? Why? Was there a problem parsing the response? These questions span multiple subsystems: HTTP handling, cryptographic signatures, JSON-LD processing, queue management, and more. Without good logging, debugging turns into guesswork. But here's the dilemma I faced as a library author: if I add verbose logging to help with debugging, I risk annoying users who don't want their console cluttered with Fedify's internal chatter. If I stay silent, users struggle to diagnose issues. I looked at the existing options. With winston or Pino, I would have to either: Configure a logger inside Fedify (imposing my choices on users), or Ask users to pass a logger instance to Fedify (adding boilerplate) There's also debug, which is designed for this use case. But it doesn't give you structured, level-based logs that ops teams expect—and it relies on environment variables, which some runtimes like Deno restrict by default for security reasons. None of these felt right. So I built LogTape—a logging library designed from the ground up for library authors. And Fedify became its first real user. The solution: hierarchical categories with zero default output The key insight was simple: a library should be able to log without producing any output unless the application developer explicitly enables it. Fedify uses LogTape's hierarchical category system to give users fine-grained control over what they see. Here's how the categories are organized: CategoryWhat it logs["fedify"]Everything from the library["fedify", "federation", "inbox"]Incoming activities["fedify", "federation", "outbox"]Outgoing activities["fedify", "federation", "http"]HTTP requests and responses["fedify", "sig", "http"]HTTP Signature operations["fedify", "sig", "ld"]Linked Data Signature operations["fedify", "sig", "key"]Key generation and retrieval["fedify", "runtime", "docloader"]JSON-LD document loading["fedify", "webfinger", "lookup"]WebFinger resource lookups …and about a dozen more. Each category corresponds to a distinct subsystem. This means a user can configure logging like this: await configure({ sinks: { console: getConsoleSink() }, loggers: [ // Show errors from all of Fedify { category: "fedify", sinks: ["console"], lowestLevel: "error" }, // But show debug info for inbox processing specifically { category: ["fedify", "federation", "inbox"], sinks: ["console"], lowestLevel: "debug" }, ],}); When something goes wrong with incoming activities, they get detailed logs for that subsystem while keeping everything else quiet. No code changes required—just configuration. Request tracing with implicit contexts The hierarchical categories solved the filtering problem, but there was another challenge: correlating logs across async boundaries. In a federated system, a single user action might trigger a cascade of operations: fetch a remote actor, verify their signature, process the activity, fan out to followers, and so on. When something fails, you need to correlate all the log entries for that specific request. Fedify uses LogTape's implicit context feature to automatically tag every log entry with a requestId: await configure({ sinks: { file: getFileSink("fedify.jsonl", { formatter: jsonLinesFormatter }) }, loggers: [ { category: "fedify", sinks: ["file"], lowestLevel: "info" }, ], contextLocalStorage: new AsyncLocalStorage(), // Enables implicit contexts}); With this configuration, every log entry automatically includes a requestId property. When you need to debug a specific request, you can filter your logs: jq 'select(.properties.requestId == "abc-123")' fedify.jsonl And you'll see every log entry from that request—across all subsystems, all in order. No manual correlation needed. The requestId is derived from standard headers when available (X-Request-Id, Traceparent, etc.), so it integrates naturally with existing observability infrastructure. What users actually see So what does all this configuration actually mean for someone using Fedify? If a Fedify user doesn't configure LogTape at all, they see nothing. No warnings about missing configuration, no default output, and minimal performance overhead—the logging calls are essentially no-ops. For basic visibility, they can enable error-level logging for all of Fedify with three lines of configuration. When debugging a specific issue, they can enable debug-level logging for just the relevant subsystem. And if they're running in production with serious observability requirements, they can pipe structured JSON logs to their monitoring system with request correlation built in. The same library code supports all these scenarios—whether the user is running on Node.js, Deno, Bun, or edge functions, without extra polyfills or shims. The user decides what they need. Lessons learned Building Fedify with LogTape taught me a few things: Design your categories early. The hierarchical structure should reflect how users will actually want to filter logs. I organized Fedify's categories around subsystems that users might need to debug independently. Use structured logging. Properties like requestId, activityId, and actorId are far more useful than string interpolation when you need to analyze logs programmatically. Implicit contexts turned out to be more useful than I expected. Being able to correlate logs across async boundaries without passing context manually made debugging distributed operations much easier. When a user reports that activity delivery failed, I can give them a single jq command to extract everything relevant. Trust your users. Some library authors worry about exposing too much internal detail through logs. I've found the opposite—users appreciate being able to see what's happening when they need to. The key is making it opt-in. Try it yourself If you're building a library and struggling with the logging question—how much to log, how to give users control, how to avoid being noisy—I'd encourage you to look at how Fedify does it. The Fedify logging documentation explains everything in detail. And if you want to understand the philosophy behind LogTape's design, my earlier post covers that. LogTape isn't trying to replace winston or Pino for application developers who are happy with those tools. It fills a different gap: logging for libraries that want to stay out of the way until users need them. If that's what you're looking for, it might be a better fit than the usual app-centric loggers. | |
| 3 points by todsacerdoti 4 days ago | 0 comments |
| 429. | The Secret Life of Moles: What They're Up to Underground | (thenaturenetwork.co.uk) |
|
|
||
| 5 points by debo_ 5 days ago | 0 comments |
| 430. | Linux System Calls | (matheusmoreira.com) |
|
|
Everything I know about Linux system calls. | |
| 4 points by enz 2 days ago | 1 comments |
| 431. | The end of the kernel Rust experiment | (lwn.net) |
|
|
||
| 35 points by rascul 6 days ago | 9 comments |
| 432. | Updated Gemini 2.5 Flash Native Audio Model | (blog.google) |
|
An upgraded Gemini 2.5 Native Audio model across Google products and live speech translation in the Google Translate app. | |
| 5 points by pretext 4 days ago | 0 comments |
| 433. | Oliver Sacks fabricated key details in his books | (boingboing.net) |
|
Oliver Sacks admitted in journals that he gave patients "powers which they do not have." Some details were invented. | |
| 5 points by paulpauper 1 day ago | 1 comments |
| 434. | Australian teens lose access to social media as ban takes effect | (bbc.com) |
|
The social media accounts of Australians aged under-16 must be deactivated, with companies facing fines for not complying. | |
| 5 points by tartoran 7 days ago | 0 comments |
| 435. | The state of the kernel Rust experiment | (lwn.net) |
|
|
||
| 6 points by birdculture 2 days ago | 0 comments |
| 436. | When Would You Ever Want Bubblesort? | (buttondown.com) |
|
There are very few universal rules in software engineering, but there are are a lot of near-universal principles. Things like "prefer composition to... | |
| 14 points by atan2 5 days ago | 3 comments |
| 437. | OpenEvolve: Teaching LLMs to Discover Algorithms Through Evolution | (algorithmicsuperintelligence.ai) |
|
|
Algorithmic SuperIntelligence Labs - AI that invents the next generation of algorithms. We deploy AI-discovered algorithms that set real world records — faster, safer and more reliable. | |
| 3 points by codelion 6 days ago | 0 comments |
| 438. | Show HN: GPULlama3.java Llama Compilied to PTX/OpenCL Now Integrated in Quarkus | () |
|
|
||
| 3 points by mikepapadim 5 days ago | 1 comments |
| 439. | Faster Double-to-String Conversion | (vitaut.net) |
|
|
content | |
| 4 points by todsacerdoti 3 days ago | 0 comments |
| 440. | The Well: 15TB of Physics Simulations | (github.com) |
|
|
A 15TB Collection of Physics Simulation Datasets. Contribute to PolymathicAI/the_well development by creating an account on GitHub. | |
| 3 points by punnerud 2 days ago | 0 comments |
| 441. | Sid Meier: More Than Just Civilization | (boilingsteam.com) |
|
|
Linux Gaming, Steam Deck Gaming | Boiling Steam | |
| 5 points by ekianjo 5 days ago | 0 comments |
| 442. | Sperm donor with cancer-causing gene fathers nearly 200 children | (scienceclock.com) |
|
A Danish sperm donor carrying a rare genetic mutation linked to a very high risk of cancer has fathered at least 197 children across Europe, according to an | |
| 8 points by ashishgupta2209 3 days ago | 1 comments |
| 443. | 'A hostile climate for workers': US labor movement struggles under Trump | (theguardian.com) |
|
National Labor Relations Board, the federal watchdog for workers’ rights, has been rendered toothless as employees grapple with corporations | |
| 5 points by robtherobber 10 hours ago | 0 comments |
| 444. | Huge undersea wall dating from 5000 BC found in France | (bbc.com) |
|
The 120 metre wall was either a fish-trap or a dyke for protection against rising sea-levels, archeologists believe. | |
| 5 points by neversaydie 5 days ago | 0 comments |
| 445. | HyperCard on the Macintosh | (stonetools.ghost.io) |
|
How do we approach the challenge of helping non-programmers build software? Do we throw up our hands at today's complexity and say, "Just let an AI do it." Or, do we make tools so *compelling* a novice can build something interesting almost by accident. We had that once. Let's see what was lost. | |
| 4 points by rcarmo 2 days ago | 1 comments |
| 446. | The Z3 Theorem Prover | (github.com) |
|
|
The Z3 Theorem Prover. Contribute to Z3Prover/z3 development by creating an account on GitHub. | |
| 8 points by benoitg 6 days ago | 0 comments |
| 447. | Long Covid involves activation of proinflammatory and immune exhaustion pathways | (nature.com) |
|
Long COVID (LC) involves a spectrum of chronic symptoms after acute severe acute respiratory syndrome coronavirus 2 infection. Current hypotheses for the pathogenesis of LC include persistent virus, tissue damage, autoimmunity, endocrine insufficiency, immune dysfunction and complement activation. We performed immunological, virological, transcriptomic and proteomic analyses from a cohort of 142 individuals between 2020 and 2021, including uninfected controls (n = 35), acutely infected individuals (n = 54), convalescent controls (n = 24) and patients with LC (n = 28). The LC group was characterized by persistent immune activation and proinflammatory responses for more than 180 days after initial infection compared with convalescent controls, including upregulation of JAK-STAT, interleukin-6, complement, metabolism and T cell exhaustion pathways. Similar findings were observed in a second cohort enrolled between 2023 and 2024, including convalescent controls (n = 20) and patients with LC (n = 18). These data suggest that LC is characterized by persistent activation of chronic inflammatory pathways, suggesting new therapeutic targets and potential biomarkers of disease. Long COVID (LC) involves a spectrum of chronic symptoms after resolution of acute severe acute respiratory syndrome coronavirus 2 infection. Barouch and colleagues show that LC is characterized by persistent activation of chronic inflammatory pathways and T cell exhaustion. | |
| 6 points by bookofjoe 1 day ago | 0 comments |
| 448. | Stacked Diffs on GitHub | (twitter.com) |
|
|
||
| 4 points by pryz 1 day ago | 1 comments |
| 449. | Ask HN: Best back end to run models on Google TPU? | () |
|
|
||
| 4 points by vood 1 day ago | 0 comments |
| 450. | Days since last GitHub incident | (github-incidents.pages.dev) |
|
|
||
| 19 points by AquiGorka 5 days ago | 5 comments |