MiMo-V2-Pro早就取消免费了，今天扫一眼调用量总榜仍然能排第四，而且价格并不算很便宜 14 个帖子 - 11 位参与者 阅读完整话题
今天深度体验了opus4.7之后，直接取消了后续订阅。 全身都是另外两家的臭毛病，兼顾了chatgpt的不说人话和gemini的金鱼记忆，debuff拉满了。 codex和gemini两个大善人可以白嫖，它还这么多破事。 果然，现在的AI发展已经触顶了，真的拉完了。 7 个帖子 - 6 位参与者 阅读完整话题
今天凌晨的时候还有灰度资格的： 然后睡醒天塌了，没有了： 9 个帖子 - 7 位参与者 阅读完整话题
IT之家 4 月 17 日消息，据德媒 Golem 今天报道，德国联邦法院裁定流媒体平台 Netflix 一项用户条款违反《民法典》，属无效合同，消费者协会最终获胜。 根据该条款， 用户只有在账号余额 全部用完后才能取消会员订阅 。法院认为， Netflix 的此种规定是“霸王条款” ，对消费者权益构成不利影响。 因此法院最终支持消费者协会。该组织代表 Jana Brockfeld 表示：“通常情况下，Netflix 用户应该可以随时取消会员。这种规定实际上是想把用户长时间绑死在会员合同中，对消费者来说不利”。 此前，柏林高等法院曾驳回该诉讼，但允许上诉至联邦法院。当时法院认为，流媒体订阅条款在法律上的界定存在歧义， 目前还没有统一标准判定其是“服务合同”（最长订阅时间不得超过 2 年）还是“租赁合同”（IT之家注：无订阅时间限制） 。 不过联邦法院最终裁定其属于“服务合同”，争议条款可能导致取消订阅在数月甚至更久后才生效，极端情况下甚至可能延迟至 39 个月之后。
看了一下好不容易京东云能买了，然后本来首单应该是19.9，结果给我减了个寂寞，活动取消了还是到期了吗 1 个帖子 - 1 位参与者 阅读完整话题
opus4.7可能真的是Claude Mythos (Preview)特调版…… 我让它帮我做头脑风暴，之前胡编乱造，然后我让它看原文，它来了这个。 chatgpt不说人话；gemini金鱼记忆。 opus4.7可好，又不说人话又金鱼记忆。 拉完了。 已连夜取消续订…… 2 个帖子 - 2 位参与者 阅读完整话题
还有当时一起薅的其他软件 3 个帖子 - 2 位参与者 阅读完整话题
以前不懂 ip 乱跳 + 信息随便填导致 paypal 被封了，现在想在其他 paypal 账号上绑卡发现不能重复绑，原来的账号又无法直接注销和解绑银行卡，要怎么办呢？找客服注销吗 5 个帖子 - 5 位参与者 阅读完整话题
咱就是说，我不要你的4.7了，你能把kyc给取消掉吗 3 个帖子 - 3 位参与者 阅读完整话题
RT，昨天中午使用pp开通，今天就被封了，有什么能够取消续订的办法吗？ 6 个帖子 - 3 位参与者 阅读完整话题
我有个新lite，不够用，想收个老套餐。如果收了这个自动续费这怎么改？取消再开自动？还是在哪修改？改完了还是没周限吗？有成功收过老套餐的佬友介绍一下吗？ 1 个帖子 - 1 位参与者 阅读完整话题
已经不支持续订了，好像连200档也不能续订了。 看来厂家都觉得coding plan是赔钱货。 但是你能用的就一个glm5也并不好用啊，还是转战gpt吧 2 个帖子 - 2 位参与者 阅读完整话题
为啥已经取消了订阅还显示有next payment啊，不会真扣钱吧 1 个帖子 - 1 位参与者 阅读完整话题
GPT的plus 想取消自动续费，但取消订阅时出错 怎么办？ 手机端和web端如图尝试都失败了。 欢迎感谢各位佬解答！ 1 个帖子 - 1 位参与者 阅读完整话题
又收紧了免费政策 另外个人说一句, qwen code的工程真的太烂了, 我就是懒了点, 居然连上下文都不顾了 还有这个编辑工具调用失败的情况真是太常见了, ACE也经常分不清是哪个mcp提供的 同样是三四百B参数的模型, GLM几乎是99%的工具调用成功率 4 个帖子 - 3 位参与者 阅读完整话题
蹬蹬看看限额 开的时候收到了这个 看起来确实是GPT取消付费的那个挽留 改了token 1 个帖子 - 1 位参与者 阅读完整话题
订阅成功后，需不需要在gpt端取消订阅，我只在paypal里取消了自动付款，会出事吗 9 个帖子 - 5 位参与者 阅读完整话题
把次数砍一半，大家应该能接受吧？反正国外御三家砍起来和丝滑。 接受 不接受 点击以查看投票。 4 个帖子 - 3 位参与者 阅读完整话题
IT之家 4 月 13 日消息，据科技媒体 neowin 昨天报道，微软今年 1 月取消了 Win10/11 和 Office 的电话激活功能，用户拨打微软电话尝试激活时，接线的不再是人工，而是机器语音提示：“产品激活已转移至线上。您可以访问 aka.ms/aoh 以快捷、方便地激活产品”。 随后微软确认， 自 2025 年 12 月 31 日起 ， 用户无法在完全没有连接互联网的电脑上 ， 以电话方式激活 Windows 。 微软官方今天在官网发布支持文章，详细解释全新激活门户如何使用，并解释沿用 24 年的电话激活为何被砍。 IT之家附微软官方发文如下： 微软正在对永久许可激活体验进行现代化升级。自 2025 年 12 月 31 日起，基于电话的自动化激活流程已转移至线上........ 新的数字化流程提供更安全 、 可靠 、 易用的体验 ， 有助于防止欺诈 。 虽然流程有变，但新系统仍然可以离线激活，依赖传统电话激活的客户可以无缝迁移至新系统，无需改变现有环境........ 产品激活门户支持多种用户许可产品激活，同时支持联网与不联网设备。我们确保激活流程依然简单、可靠，同时为所有用户提供现代化、精简的界面。 值得注意的是，微软的全新激活门户还引入了人机验证机制，呼应公司强调的“反欺诈”。
github.com/anthropics/claude-code Cache TTL silently regressed from 1h to 5m around early March 2026, causing quota and cost inflation 已打开 01:49AM - 12 Apr 26 UTC 已关闭 10:15AM - 12 Apr 26 UTC seanGSISG bug has repro area:cost api:anthropic # Cache TTL appears to have silently regressed from 1h to 5m around early March … 2026, causing significant quota and cost inflation ## Summary Analysis of raw Claude Code session JSONL files spanning Jan 11 – Apr 11, 2026 shows that Anthropic appears to have **silently changed the prompt cache TTL default from 1 hour to 5 minutes sometime in early March 2026**. Prior to this change, Claude Code was receiving 1-hour TTL cache writes — which we believe was the intended default. The reversion to 5-minute TTL has caused a **20–32% increase in cache creation costs** and a measurable spike in quota consumption for subscription users who have never previously hit their limits. This appears directly related to the behavior described in #45756. --- ## Data Session data extracted from `~/.claude/projects/` JSONL files across **two machines** (Linux workstation + Windows laptop, different accounts/sessions), totaling **119,866 API calls** from Jan 11 – Apr 11, 2026. Each assistant message includes a `usage.cache_creation.ephemeral_5m_input_tokens` / `ephemeral_1h_input_tokens` breakdown that makes the TTL tier per-call observable. Having two independent machines strengthens the signal — both show the same behavioral shift at the same dates. ### Phase breakdown | Phase | Dates | TTL behavior | Evidence | |-------|-------|--------------|----------| | 1 | Jan 11 – Jan 31 | **5m ONLY** | `ephemeral_1h` absent/zero — likely predates 1h tier availability in the API | | 2 | Feb 1 – Mar 5 | **1h ONLY** | `ephemeral_5m = 0`, `ephemeral_1h > 0` across **33+ consecutive days** on both machines — near-zero exceptions | | 3 | Mar 6–7 | **Transition** | First 5m tokens re-appear, small volumes, 1h still present | | 4 | Mar 8 – Apr 11 | **5m dominant** | 5m tokens surge to majority; 1h becomes minority or disappears entirely | We believe Phase 2 represents Anthropic's **intended default behavior** — 1h TTL was rolled out as the Claude Code standard around Feb 1 and held consistently for over a month across two independent machines on two different accounts. January's all-5m data most likely predates the 1h TTL tier being available in the API. The regression began **around March 6–8, 2026**. No client-side changes were made between phases. The same Claude Code version and usage patterns were in place throughout. The TTL tier is set server-side by Anthropic. ### Day-by-day TTL data showing the regression (combined, both machines) ``` Date | 5m-create | 1h-create | Behavior ------------|------------|------------|---------- 2026-02-01 | 0.00M | 1.70M | 1h ONLY ← 1h default begins 2026-02-09 | 0.00M | 7.95M | 1h ONLY 2026-02-15 | 0.00M | 13.61M | 1h ONLY ← heaviest day, 100% 1h 2026-02-28 | 0.00M | 16.15M | 1h ONLY ← 16M tokens, still 100% 1h 2026-03-01 | 0.00M | 0.12M | 1h ONLY 2026-03-04 | 0.00M | 8.12M | 1h ONLY 2026-03-05 | 0.00M | 6.55M | 1h ONLY ← last clean 1h-only day | | | 2026-03-06 | 0.29M | 0.22M | MIXED ← first 5m tokens reappear 2026-03-07 | 4.56M | 0.50M | MIXED ← 5m surging 2026-03-08 | 16.86M | 3.44M | MIXED ← 5m now dominant (83%) 2026-03-10 | 10.55M | 0.51M | MIXED 2026-03-15 | 19.47M | 1.84M | MIXED 2026-03-21 | 21.37M | 1.70M | MIXED ← 93% 5m 2026-03-22 | 13.48M | 2.85M | MIXED ``` The transition is visible to the day: **March 6 is when 5m tokens first reappear** after 33 days of clean 1h-only behavior. By March 8, 5m tokens outnumber 1h by 5:1. This is consistent with a server-side configuration change being rolled out gradually then completing around March 8. --- ## Cost impact Applying official Anthropic pricing (rates.json, updated 2026-04-09): Combined dataset (119,866 API calls, two machines): **claude-sonnet-4-6** (`cache_write_5m = $3.75/MTok`, `cache_write_1h = $6.00/MTok`, `cache_read = $0.30/MTok`): | Month | Calls | Actual cost | Cost with 1h TTL | Overpaid | % waste | |-------|-------|-------------|-----------------|----------|---------| | Jan 2026 | 2,639 | $78.99 | $37.54 | $41.45 | **52.5%** | | Feb 2026 | 27,220 | $1,120.43 | $1,108.11 | $12.32 | **1.1%** ← nearly 0 on 1h | | Mar 2026 | 68,264 | $2,776.11 | $2,057.01 | $719.09 | **25.9%** | | Apr 2026 | 21,743 | $1,193.01 | $1,016.78 | $176.23 | **14.8%** | | **Total** | **119,866** | **$5,561.17** | **$4,612.09** | **$949.08** | **17.1%** | **claude-opus-4-6** (`cache_write_5m = $6.25/MTok`, `cache_write_1h = $10.00/MTok`, `cache_read = $0.50/MTok`): | Month | Calls | Actual cost | Cost with 1h TTL | Overpaid | % waste | |-------|-------|-------------|-----------------|----------|---------| | Jan 2026 | 2,639 | $131.65 | $62.57 | $69.08 | **52.5%** | | Feb 2026 | 27,220 | $1,867.38 | $1,846.85 | $20.53 | **1.1%** ← nearly 0 on 1h | | Mar 2026 | 68,264 | $4,626.84 | $3,428.36 | $1,198.49 | **25.9%** | | Apr 2026 | 21,743 | $1,988.35 | $1,694.64 | $293.71 | **14.8%** | | **Total** | **119,866** | **$9,268.97** | **$7,687.17** | **$1,581.80** | **17.1%** | February — the month Anthropic was defaulting to 1h TTL — shows only **1.1% waste** (trace 5m activity from one machine on one day). Every other month shows 15–53% overpayment from 5m cache re-creations. The cost difference is explained entirely by TTL tier, not by usage volume. The **percentage waste is identical across model tiers** (17.1%) because it is driven purely by the 5m/1h token split, not by per-token price. ### Why 5m TTL is so expensive in practice With 5m TTL, any pause in a session longer than 5 minutes causes the entire cached context to expire. On the next turn, Claude Code must re-upload that context as a fresh `cache_creation` at the write rate, rather than a `cache_read` at the read rate. The write rate is **12.5× more expensive** than the read rate for Sonnet, and the same ratio holds for Opus. For long coding sessions — which are the primary Claude Code use case — this creates a compounding penalty: the longer and more complex your session, the more context you have cached, and the more expensive each cache expiry becomes. Over the 3-month period analyzed: - **220M tokens** were written to the 5m tier - Those same tokens generated **5.7B cache reads** — meaning they were actively being used - Had those 220M tokens been on the 1h tier, re-accesses within the same hour would be reads (~$0.30–0.50/MTok) instead of re-creations (~$3.75–6.25/MTok) --- ## Quota impact Users on Pro/subscription plans are quota-limited, not just cost-limited. Cache creation tokens count toward quota at full rate; cache reads are significantly cheaper (the exact coefficient is under investigation in #45756). The silent reversion to 5m TTL in March is the most likely explanation for why subscription users began hitting their 5-hour quota limits for the first time — including the author of this issue, who had never hit quota limits before March 2026. --- ## Hypothesis The data strongly suggests that **1h TTL was the intended default for Claude Code** and was in place as of early February 2026. Sometime between Feb 27 and Mar 8, 2026, Anthropic silently changed the default to 5m TTL — either intentionally as a cost-saving measure, or accidentally as an infrastructure regression. Evidence supporting "1h was the intended default": - Phase 2 (1h ONLY) shows *zero* 5m tokens across **14 separate active days** spanning 3+ weeks — this is not noise or partial rollout, it is consistent deliberate behavior - The February cost profile is the only month with 0% overpayment — it represents what users should have been paying all along - The March reversion immediately produced the largest 5m-tier days in the entire dataset (30M tokens on Mar 22 alone), suggesting a sudden configuration flip rather than gradual drift - Subscription users began hitting 5-hour quota limits **for the first time** in March — directly coinciding with the reversion The most likely sequence of events: 1. **~Feb 1 and prior**: Anthropic defaulted to 1h TTL for Claude Code subscription users 2. **~Mar 6**: 5m tokens begin reappearing — gradual rollout of the change or partial infrastructure flip 3. **~Mar 8**: 5m TTL becomes dominant — the regression is fully in effect across both tested machines and accounts 4. **Mar 8+**: Mixed behavior continues, suggesting either incomplete rollout, A/B testing, or regional infrastructure variance The 33-day window of clean 1h-only behavior (Feb 1 – Mar 5) across two independent machines and two separate accounts makes this one of the strongest available signals that **1h TTL was Anthropic's deliberate default**, not a fluke. --- ## Request 1. **Confirm or deny** whether Anthropic made a server-side TTL default change in early February 2026 and reverted it in early March 2026 2. **Clarify the intended TTL behavior** for claude-code sessions — is 5m the intended default, or was 1h intended to be permanent? 3. **Consider restoring 1h TTL as the default** for Claude Code sessions, or exposing it as a user-configurable option. The 5m TTL is disproportionately punishing for the long-session, high-context use case that defines Claude Code usage 4. **Disclose quota counting behavior for cache_read tokens** (ref #45756) so users can make informed decisions about their usage patterns --- ## Methodology - Source: raw `~/.claude/projects/**/*.jsonl` session files (Claude Code stores per-message API responses including full `usage` objects) - Extraction: filtered for `type: "assistant"` entries with `message.usage.cache_creation` field - No external tools or proxies involved — this data comes directly from Claude Code's own session logs - Analysis tool: [cnighswonger/claude-code-cache-fix](https://github.com/cnighswonger/claude-code-cache-fix) `quota-analysis --source` mode (added to support this investigation) - Pricing: official Anthropic rates from `rates.json` (updated 2026-04-09) 来自Anthropic员工的回应： 我说我的号明明是max5,但是接在sub2api里面却一直缓存过期，原来是被A÷暗改了 9 个帖子 - 5 位参与者 阅读完整话题