返回 2026-10-04 编辑版
原始行动中文优先 · EN 原文待分类

Simon Willison 发布:Dot 与普通 ChatGPT 的使用边界仍不清晰

既然我们已经使用它几天了,人们是如何区分 Dot 和普通 ChatGPT 的? 我很难决定什么时候应该使用 Dot 提示,什么时候使用 ChatGPT——我的 Dot 似乎只能进行一次对话,但我希望能够在多个线程中控制我的上下文

查看英文原文

Now that we've had a few days with it, how are people differentiating between Dot and regular ChatGPT? I'm having trouble deciding when I should prompt Dot vs using ChatGPT - my Dot seems to afford a single conversation, but I like controlling my context across multiple threads

Now that we've had a few days with it, how are people differentiating between Dot and regular ChatGPT? I'm having trouble deciding when I should prompt Dot vs using ChatGPT - my Dot seems to afford a single conversation, but I like controlling my context across multiple threads

Dot 与普通 ChatGPT 的上下文边界等待真实用户对账

早期使用反馈指出单一对话与跨线程上下文控制存在摩擦,但仍只有一名用户的观察。

原始出现与传播对照

1 条出现 · 本次 AIHOT 未精确命中

原始行动

既然我们已经使用它几天了,人们是如何区分 Dot 和普通 ChatGPT 的? 我很难决定什么时候应该使用 Dot 提示,什么时候使用 ChatGPT——我的 Dot 似乎只能进行一次对话,但我希望能够在多个线程中控制我的上下文

既然我们已经使用它几天了,人们是如何区分 Dot 和普通 ChatGPT 的? 我很难决定什么时候应该使用 Dot 提示,什么时候使用 ChatGPT——我的 Dot 似乎只能进行一次对话,但我希望能够在多个线程中控制我的上下文

查看英文原文

Now that we've had a few days with it, how are people differentiating between Dot and regular ChatGPT? I'm having trouble deciding when I should prompt Dot vs using ChatGPT - my Dot seems to afford a single conversation, but I like controlling my context across multiple threads

Now that we've had a few days with it, how are people differentiating between Dot and regular ChatGPT? I'm having trouble deciding when I should prompt Dot vs using ChatGPT - my Dot seems to afford a single conversation, but I like controlling my context across multiple threads

直接发布标题Simon Willison@simonw打开该层出处 ↗

Now that we've had a few days with it, how are people differentiating between Dot and regular ChatGPT? I'm having trouble deciding when I should prompt Dot vs using ChatGPT - my Dot seems to afford a single conversation, but I like controlling my context across multiple threads

来源
X @simonw · x-simonw
证据角色
x_project_network
时间状态
known
用户判决
未判
查看该来源原文raw/x-simonw.jsonfeaf84afdc0f34c7efccbac20eec8b059e3f8d786c38dfb77ea5a72cdc44f0ea
Cluster IDevt_7b1e220d8c76f4f3448160c1精确去重依据canonical_url事件状态未判