RFC: Abandon Command Usage for Conversation

[MaikoTan]

Summary 概述

As a chatbot plugin, using a command to invoke the conversation seems to be weird nowadays. Since we have appellations and prefixes to invoke the conversations, I think it is time to abandon the command usage for invoking a conversation.

作为一个聊天机器人，在现在使用指令调起对话是奇葩的。自从我们有称谓和前缀用于调起对话，我想是时候放弃指令用途作为对话。

Expectaion 期望

• Command chatgpt 指令 chatgpt

  This would become the "managing" command for the plugin, like "resetting thread" (implemented), "maintaining a character design", etc.

  这将会成为插件的“管理”指令，比如“重置线程”（已实现），“维护一个人物设定”，等等。

• Appellations and prefixes 称谓和前缀

  This would still invoke conversations as always. But under the hood, we should update our code to request the API directly in the middleware.

  这将会和一直以来依旧调起对话。但在下面，我们应该更新我们的代码在中间件里来直接请求API。

Feel free to comment your thoughts here! 在这里自由地评论你的想法！

---

cc @Anillc @Shigma @TimeBather

[shigma]

我觉得没问题。当然也可以保留一个子指令用于唤起对话，例如 chatgpt/chat。

[MaikoTan]

我觉得没问题。当然也可以保留一个子指令用于唤起对话，例如 chatgpt/chat。

sounds make sense, would do as soon as possible.

[MaikoTan]

I noticed that there are much people using the command style, as we don't have a changelog currently, how do we announce people that we are going to abandon this?

我注意到那里有不少人们使用指令样式，既然我们目前没有更新记录，我们应该如何通告人们我们将要废弃这个？

[shigma]

如果要保持现有兼容性，可以不移除指令，新功能通过子指令实现，例如 chatgpt.setting, chatgpt.reset 等。