今日已更新 133 条资讯 | 累计 37382 条内容
关于我们

标签:#chat

找到 96 篇相关文章

AI 资讯

ChatGPT Now Guesses Your Age — and Restricts You by Default if It Thinks You're Under 18

Open ChatGPT this week and, without any announcement in the chat window, it may already have formed an opinion about how old you are. From 18 August, OpenAI began rolling out “age prediction” on its consumer plans: a system that guesses whether your account belongs to someone under 18 and, if it decides you’re a minor, quietly switches you into a restricted version called ChatGPT for Teens. You are not asked. If the guess lands on “teenager,” the guardrails go up by default. Answer first, because the mechanism matters more than the alarm: the guess is behavioural, and it is admittedly imperfect. By OpenAI’s own account the system reads “general topics you talk about, the times of day you use ChatGPT, how and when your account is used, and how long your account has existed.” And the way to make it stop guessing is not a toggle. It is to prove your age to a third-party verifier called Persona, with a live selfie, a government ID, or both. The choice on offer isn’t whether to be identified. It’s how. None of this arrives from nowhere, and we’ll be fair about why in a moment. But a change that infers a protected characteristic from the content of your conversations, applies real restrictions on the strength of a guess, and offers identity verification as the only exit is worth reading slowly — especially for the adults who will be misclassified, because OpenAI says plainly that some will be. What OpenAI actually switched on The launch has two parts. The visible one is ChatGPT for Teens , announced on 18 August: a version with study-focused features and stronger safety defaults for under-18s. The consequential one is age prediction , the system that decides who gets dropped into it. In OpenAI’s words, “If our system estimates someone is under 18 or they state their age is between 13 and 17, they are automatically placed into ChatGPT for Teens.” It is rolling out globally, with the EU following “in the coming weeks” to fit regional rules. What does the teen experience act

2026-08-27 原文 →
AI 资讯

OpenAI Is Testing a Button to Reset ChatGPT’s Limits — For $8

OpenAI is quietly testing a feature that lets ChatGPT users pay to undo their own usage limits. Hit the weekly cap on a $20 Plus plan and, for some users, a prompt now appears offering to restore the allowance to full for roughly $8. On the $200 Pro plan, the equivalent reset is reported to run up to about $80. The company never announced it; it was discovered by a subscriber who ran into it at the point of being locked out, and an OpenAI spokesperson later confirmed the company is exploring ways for capped users to buy more usage . The answer-first version: your flat monthly subscription now has a pay-to-continue button, and it shows up at the worst possible moment. The reset restores your usage to 100% and pushes the next weekly renewal about seven days out. It is cheaper than upgrading, which is the point — but it is also a new charge that did not exist a month ago, applied to a limit most users cannot see coming, offered at the instant they are least able to say no. What OpenAI is actually testing The mechanics, as reported, are straightforward. When a ChatGPT Plus subscriber exhausts their weekly message allowance, instead of only being told to wait, some accounts now see an option to pay to reset. Redeeming it restores usage to full and resets the weekly clock. The price sits at around $8 for Plus; on Pro it scales up to roughly $80, still framed as a stopgap against a full plan change. The feature was first surfaced by a Reddit user on the $20 plan who described a black prompt appearing at login once their allowance ran dry — not a setting they went looking for, but one that found them. That detail — a user, not a press release, breaking the news of a paid feature — is itself worth noting: the first public account of how OpenAI plans to charge for extra usage came from someone who had already been charged the inconvenience of being locked out. OpenAI has not disputed the reports. A spokesperson described the effort as exploring ways for people who exhaust the

2026-08-21 原文 →
AI 资讯

The Problem With AI “Memory”

“Memory” is the feature everyone asked for and few thought through. The pitch is lovely: the assistant remembers your preferences, your projects, your writing style , the fact that you are vegetarian and allergic to long emails, so you never have to repeat yourself. In practice, it is one of the most consequential privacy decisions in consumer AI, dressed up as a convenience toggle, and most people flipped it on without reading past the word “remember.” Convenience and surveillance are the same feature The uncomfortable truth is that there is no version of persistent memory that is not also a growing personal record. For the assistant to remember your details, it has to store your details. The thing that makes it feel like it knows you is a file — structured or otherwise — accumulating what you have told it, and inferring more from what you did not. The warmth and the dossier are not two features. They are one feature seen from two angles. A system that remembers everything you tell it is, definitionally, a system that keeps a record of everything you tell it. The friendliness is the interface; the record is the substance. The profile that shapes what you are shown A stored model of who you are does not sit there inertly; it starts to shape the responses you get. That is the entire selling point — a memory-enabled assistant tailors its answers to what it believes about you. But tailoring cuts both ways. Once the system has decided you are a particular sort of person, with particular views and particular tastes, it begins to give you the version of the world it thinks you want, and you lose the ability to know what it would have said to someone it had profiled differently. The personalisation that feels like being understood is also, quietly, a narrowing. We have seen this film before, with recommendation feeds that learned our preferences and then fed them back to us until the preferences hardened into a cage. A memory-driven assistant risks the same dynamic applied

2026-08-16 原文 →
AI 资讯

Mastering Turn-Taking in Group Chat: How Two Characters Share One Thread

Mastering Turn-Taking in Group Chat: How Two Characters Share One Thread Building a seamless group chat experience where two characters share a single thread can be surprisingly tricky. While one-on-one conversations with AI are relatively straightforward, introducing a second AI persona into the same chat thread raises a fundamental question: when a user speaks, who answers? We recently launched multi-character rooms on AmorLink, and this article delves into the turn-taking logic we developed. You'll discover why the majority of this logic deliberately avoids calling a language model and explore the contextual challenges that proved more complex than the routing itself. The Pitfalls of Simple Solutions The most intuitive approach is to have "everyone answer every message." However, this quickly devolves into a "press conference" scenario. Imagine asking, "How was your day?" and receiving two stacked paragraphs, each completely unaware of the other. This method also doubles inference costs and increases the time-to-first-token for every turn. Another common, yet flawed, strategy is to "pick at random." While cheaper, it's often more frustrating. If a user asks, "Iris, what do you think?" and the other character answers, the illusion of intelligent conversation shatters instantly. Randomness offers no improvement as the conversation scales. A Ladder Approach to Turn-Taking The key insight is that turn-taking isn't a single problem but a stack of them. The vast majority of these problems have unambiguous solutions. For instance, if a message explicitly names a character or is very short and follows a reply, the decision is clear. Only a minority of turns genuinely require complex judgment. Therefore, our policy is structured as a ladder, prioritizing cost-effective solutions for easy cases and reserving the more expensive AI model for the difficult ones. Our five-rung ladder works as follows, with the first matching condition determining the response: Exactly one memb

2026-08-15 原文 →
AI 资讯

别再手写图表了!用AI轻松搞定数据可视化

图表不会画?跟AI说句话就行 写代码画图这件事,劝退过不少人。编辑器打开了,文件是空的,脑子里想的是"画个折线图",手却不知道往哪放。查文档、调参数、处理日期格式、挪图例……折腾半小时,数据还没理清楚。我太懂了,因为我自己就是这么过来的。 现在情况不一样了。ChatGPT、Claude、Copilot,随便挑一个,你跟它说"我想看什么样的图表",它就把代码给你写好了,而且一次跑通的概率不低。这不是什么科幻设定,我天天这么干活。 AI到底在干嘛? 说白了,AI不负责画图,它负责把你想画的东西翻译成代码。你说人话,它出Python、R或者JavaScript,然后你的数据就变成图了。常用的搭配大概是这些: Python配Matplotlib或Seaborn,做静态图、论文插图,稳 Python配Plotly,要交互、能缩放能悬停的那种 R配ggplot2,学术界和统计人的心头好 JavaScript配ECharts或D3,网页上动的图 老板只要Excel图?AI也能写VBA宏 API不用背,你直接说:"我有个CSV,两列,一列日期一列销售额,帮我画折线图加趋势线,中文标题,X轴标签转45度,存成PNG。"代码马上给你。 关键是说人话 AI给不给力,很大程度看你问得清不清楚。我总结了一个公式,特别好用: 要干什么 + 数据啥样 + 用啥工具 + 图长啥样 + 存成啥格式 举个例子。你手上有个sales.csv,里面是月份和金额,想做柱状图,红色边框,高清图。 你要是说"帮我画个图",谁也帮不了你。 但你要是说:"用Python读sales.csv,第一列是月份,第二列是销售额。用matplotlib画柱状图,柱子天蓝色,边框红色,柱子上方标数值,标题写'月度销售额',保存成300dpi的png。"AI给的代码基本就是能直接跑的。 一个真实的操作过程 拿Python举例,整个过程就三步。 第一步,让AI先读数据。"我有个data.csv,三列:date、product、revenue,格式是2024-01-01这种,写段Python代码读进来并打印前五行。" import pandas as pd df = pd . read_csv ( ' data.csv ' , parse_dates = [ ' date ' ]) print ( df . head ()) 跑一下,确认数据没错。 第二步,画图。"用Seaborn画每个月的总收入折线图,x轴月份,y轴收入,带数据点标记,标题'月度收入趋势',图例去掉。"AI会一次性给你把分组聚合和绘图代码都写好。 第三步,跑,报错就贴给AI,改完再跑。五分钟搞定。 别把脑子扔了 AI写代码,你得把关。至少得看得懂它在干嘛:数据读得对不对,列名有没有搞错;按月求和还是逐条画,逻辑对不对;坐标轴排序有没有问题,标签重没重复;输出路径能不能找到。 AI有时候会一本正经地胡说八道——编个不存在的参数,或者用了个过时的库版本。这时候你得会看报错,会去查文档。说到底,AI是加速器,不是方向盘。 还能让AI干点别的 有时候图难看,真不怪画图代码,是数据太脏。你可以直接让AI洗数据:"revenue列空值填0,删掉product列里带'测试'的行,日期列转成标准格式。"一行提示词,pandas代码给你安排好。 你也可以把一部分数据贴给AI,问它:"这是我用户的年龄分布,你觉得用啥图展示比较合适?"它会跟你推荐直方图、箱线图或者小提琴图,还会解释为什么——等于白嫖一个懂行的顾问。 各家AI怎么选 ChatGPT(GPT-4系列),综合能力强,中文对话舒服,解释得很细,适合从零开始 Claude(Opus或者Sonnet),写代码比较稳,长代码上下文不容易丢,调试的时候给力 GitHub Copilot,装在编辑器里,你写它补,适合本来就在写项目的人 通义灵码、文心快码,国产的,中文响应快,跟国内开发环境更搭 哪个最强不好说,顺手最重要。我自己习惯先用ChatGPT把框架搭出来,再用Copilot改细节。 几个常见的坑 Matplotlib默认不认识中文,画出来全是方块,得加 plt.rcParams['font.sans-serif'] = ['SimHei'] 和 axes.unicode_minus = False 。 Windows路径里反斜杠容易转义出错,让AI用正斜杠,或者加个 r 前缀,再不行就上 pathlib 。 列名里带空格或特殊字符的话,AI可能写成 df.Revenue ,其实得 df['Revenue (M)'] 。把列名原样粘给AI,别让它猜。 Plotly在Jupyter里死活不显示?那是renderer没设置。 批量出图,才是真省事 文件多的时候,让AI写个循环。比如"文件夹里一

2026-08-15 原文 →
AI 资讯

Compatible API Alternatives for Chatbot Apps: One-Key US/EU Test Plan

Short answer: the least risky alternative to a single-provider OpenAI-compatible API is a thin routing layer with one internal contract, a small Python adapter, and an eval set that measures answer quality before price. Treat “cheapest” as a workload result, not a label. A US/EU chatbot also needs a deliberate data-residency decision before a key or SDK enters production. The attractive story is easy: one API key, one SDK, and a familiar chat-completions shape. Measure it. The production story has more edges. Provider-specific tool calls, token accounting, streaming events, retention settings, and regional routing can differ while the first text response still looks fine. That is how an in-app chatbot passes a demo and fails an eval. Consider a support bot that retrieves three passages, answers in a stream, and offers an escalation tool. A compatibility test that checks only the final sentence can miss an empty retrieval marker, a tool argument that is valid text but invalid JSON, a stream terminator that the client never handles, and a fallback that sends the same user request to a second region. The transcript still looks plausible in a screenshot. The trace tells a different story. I've learned to make those states explicit in the adapter before tuning a model. I build RAG and agent features in Python, so my first question is not “which model wins?” It is “which contract can I test?” The app should own that contract. A provider adapter should translate it at the boundary, and the rest of the application should never know whether the request went to an OpenAI-compatible endpoint, a Claude-style API, a Gemini-style API, or a local service. How can an app chatbot compare compatible API alternatives across US and EU? Start with the request that matters to the user: a message plus retrieved context, a latency budget, a maximum output, and a trace ID. Record the selected region and provider in server-side metadata, but don't send a secret to the browser. “One API key”

2026-08-12 原文 →
AI 资讯

Presentation: Keeping ChatGPT Fast as AI Development Accelerates

Martin Spier explains how agentic workflows dramatically increase code change volume at OpenAI. He discusses the hidden systemic performance costs of rapid shipping beyond GPUs, and shares how deploying always-on AI agents automates profiling, regression detection, and continuous optimization to maintain product speed and scalability at massive global scale. By Martin Spier

2026-08-08 原文 →