It’s also available via public libraries in USA via Libby if your local library system pays for a subscription, so it’s a way to support the magazine indirectly, since your local taxes pays for your library. The downside for weekly is you have to read it that week, no archive access.
The New Yorker posts digital articles in advance of the release of the print edition.
At the bottom of this article it says: Published in the print edition of the April 13, 2026, issue, with the headline “Moment of Truth.”
As someone who reads the print magazine every week, I always scroll down to check if the article will be published and skip it if so (so I can read it when my magazine arrives).
Thanks. Can confirm the print edition is assigned a date that is 5 days after it becomes available in the Press Reader app in the UK (not sure why) and the article is in that edition.
This looks interesting. What I don't understand is: how was it implemented without a server relay. I am no expert in WebRTC (or P2P for that matter) but I always assumed that there needs to be a central location for users to exchange their addresses and only then a P2P connection can be established. This must be the case here as well right? Or am I mistaken?
That is exactly the case, there is a server in the background responsible for maintaining sessions and setting up WebRTC connections(ICE handshakes), when all clients are connected - messages are sent p2p
> This project was born out of the need for a lightweight analytics tool to track internal services on a resource-constrained VPS. Most SaaS analytics products either lack the scalability or exceed their free tier limits when tracking millions of events per month. Minimalytics addresses this gap by offering a minimalist, high-performance solution for resource-constrained environments.
I recently did a Show HN which you can find on my profile.
This is an interesting use case. I can definitely see how a colored cell in a grid can serve as a visual indicator to monitor health of infrastructure. Thanks for sharing this.
They want more users, not more utilization. Utilization is the effect of users not its cause. They are happy to have utilization increase as long as they keep getting more users. If the utilization increases while number of users remain constant because people (like OP) are using CPU intensive programs then that is not in their interest.
reply