The best Hacker News stories from All from the past day
Latest posts:
Copyparty – Turn almost any device into a file server
Visa and Mastercard are getting overwhelmed by gamer fury over censorship
Enough AI copilots, we need AI HUDs
Claude Code weekly rate limits
Hi there,<p>Next month, we're introducing new weekly rate limits for Claude subscribers, affecting less than 5% of users based on current usage patterns.<p>Claude Code, especially as part of our subscription bundle, has seen unprecedented growth. At the same time, we’ve identified policy violations like account sharing and reselling access—and advanced usage patterns like running Claude 24/7 in the background—that are impacting system capacity for all. Our new rate limits address these issues and provide a more equitable experience for all users.<p>What’s changing:
Starting August 28, we're introducing weekly usage limits alongside our existing 5-hour limits:
Current: Usage limit that resets every 5 hours (no change)
New: Overall weekly limit that resets every 7 days
New: Claude Opus 4 weekly limit that resets every 7 days
As we learn more about how developers use Claude Code, we may adjust usage limits to better serve our community.
What this means for you:
Most users won't notice any difference. The weekly limits are designed to support typical daily use across your projects.
Most Max 5x users can expect 140-280 hours of Sonnet 4 and 15-35 hours of Opus 4 within their weekly rate limits. Heavy Opus users with large codebases or those running multiple Claude Code instances in parallel will hit their limits sooner.
You can manage or cancel your subscription anytime in Settings.
We take these decisions seriously. We're committed to supporting long-running use cases through other options in the future, but until then, weekly limits will help us maintain reliable service for everyone.<p>We also recognize that during this same period, users have encountered several reliability and performance issues. We've been working to fix these as quickly as possible, and will continue addressing any remaining issues over the coming days and weeks.<p>–The Anthropic Team
Claude Code weekly rate limits
Hi there,<p>Next month, we're introducing new weekly rate limits for Claude subscribers, affecting less than 5% of users based on current usage patterns.<p>Claude Code, especially as part of our subscription bundle, has seen unprecedented growth. At the same time, we’ve identified policy violations like account sharing and reselling access—and advanced usage patterns like running Claude 24/7 in the background—that are impacting system capacity for all. Our new rate limits address these issues and provide a more equitable experience for all users.<p>What’s changing:
Starting August 28, we're introducing weekly usage limits alongside our existing 5-hour limits:
Current: Usage limit that resets every 5 hours (no change)
New: Overall weekly limit that resets every 7 days
New: Claude Opus 4 weekly limit that resets every 7 days
As we learn more about how developers use Claude Code, we may adjust usage limits to better serve our community.
What this means for you:
Most users won't notice any difference. The weekly limits are designed to support typical daily use across your projects.
Most Max 5x users can expect 140-280 hours of Sonnet 4 and 15-35 hours of Opus 4 within their weekly rate limits. Heavy Opus users with large codebases or those running multiple Claude Code instances in parallel will hit their limits sooner.
You can manage or cancel your subscription anytime in Settings.
We take these decisions seriously. We're committed to supporting long-running use cases through other options in the future, but until then, weekly limits will help us maintain reliable service for everyone.<p>We also recognize that during this same period, users have encountered several reliability and performance issues. We've been working to fix these as quickly as possible, and will continue addressing any remaining issues over the coming days and weeks.<p>–The Anthropic Team
VPN use surges in UK as new online safety rules kick in
Claude Code is a slot machine
Return of wolves to Yellowstone has led to a surge in aspen trees
Paper: <a href="https://www.sciencedirect.com/science/article/pii/S0378112725004499?via=ihub" rel="nofollow">https://www.sciencedirect.com/science/article/pii/S037811272...</a>
When we get Komooted
Tom Lehrer has died
<a href="https://archive.ph/gY3Xa" rel="nofollow">https://archive.ph/gY3Xa</a><p>Also: <a href="https://apnews.com/article/tom-lehrer-son-satirist-mathematician-dies-9caa7ee01faf4fbfb793d7ba984c179d" rel="nofollow">https://apnews.com/article/tom-lehrer-son-satirist-mathemati...</a>
Ask HN: What are you working on? (July 2025)
What are you working on? Do you have any new ideas you're thinking about?
Ask HN: What are you working on? (July 2025)
What are you working on? Do you have any new ideas you're thinking about?
4k NASA employees opt to leave agency through deferred resignation program
Dumb Pipe
Dumb Pipe
Performance and telemetry analysis of Trae IDE, ByteDance's VSCode fork
Hi HN,
I was evaluating IDEs for a personal project and decided to test Trae, ByteDance's fork of VSCode. I immediately noticed some significant performance and privacy issues that I felt were worth sharing. I've written up a full analysis with screenshots, network logs, and data payloads in the linked post.<p>Here are the key findings:<p>1. Extreme Resource Consumption:
Out of the box, Trae used 6.3x more RAM (~5.7 GB) and spawned 3.7x more processes (33 total) than a standard VSCode setup with the same project open. The team has since made improvements, but it's still significantly heavier.<p>2. Telemetry Opt-Out Doesn't Work (It Makes It Worse):
I found Trae was constantly sending data to ByteDance servers (byteoversea.com). I went into the settings and disabled all telemetry. To my surprise, this didn't stop the traffic. In fact, it increased the frequency of batch data collection. The telemetry "off" switch appears to be purely cosmetic.<p>3. What's Being Sent:
Even with telemetry "disabled," Trae sends detailed payloads including:
Hardware specs (CPU, memory, etc.)
Persistent user, device, and machine IDs
OS version, app language, user name
Granular usage data like time-on-ide, window focus state, and active file types.<p>4. Community Censorship:
When I tried to discuss these findings on their official Discord, my posts were deleted and my account was muted for 7 days. It seems words like "track" trigger an automated gag rule, which prevents any real discussion about privacy.<p>I believe developers should be aware of this behavior. The combination of resource drain, non-functional privacy settings, and censorship of technical feedback is a major red flag. The full, detailed analysis with all the evidence (process lists, Fiddler captures, JSON payloads, and screenshots of the Discord moderation) is available at the link. Happy to answer any questions.
Performance and telemetry analysis of Trae IDE, ByteDance's VSCode fork
Hi HN,
I was evaluating IDEs for a personal project and decided to test Trae, ByteDance's fork of VSCode. I immediately noticed some significant performance and privacy issues that I felt were worth sharing. I've written up a full analysis with screenshots, network logs, and data payloads in the linked post.<p>Here are the key findings:<p>1. Extreme Resource Consumption:
Out of the box, Trae used 6.3x more RAM (~5.7 GB) and spawned 3.7x more processes (33 total) than a standard VSCode setup with the same project open. The team has since made improvements, but it's still significantly heavier.<p>2. Telemetry Opt-Out Doesn't Work (It Makes It Worse):
I found Trae was constantly sending data to ByteDance servers (byteoversea.com). I went into the settings and disabled all telemetry. To my surprise, this didn't stop the traffic. In fact, it increased the frequency of batch data collection. The telemetry "off" switch appears to be purely cosmetic.<p>3. What's Being Sent:
Even with telemetry "disabled," Trae sends detailed payloads including:
Hardware specs (CPU, memory, etc.)
Persistent user, device, and machine IDs
OS version, app language, user name
Granular usage data like time-on-ide, window focus state, and active file types.<p>4. Community Censorship:
When I tried to discuss these findings on their official Discord, my posts were deleted and my account was muted for 7 days. It seems words like "track" trigger an automated gag rule, which prevents any real discussion about privacy.<p>I believe developers should be aware of this behavior. The combination of resource drain, non-functional privacy settings, and censorship of technical feedback is a major red flag. The full, detailed analysis with all the evidence (process lists, Fiddler captures, JSON payloads, and screenshots of the Discord moderation) is available at the link. Happy to answer any questions.
EU age verification app to ban any Android system not licensed by Google
EU age verification app to ban any Android system not licensed by Google
Why MIT switched from Scheme to Python (2009)