NextChat
NextChat copied to clipboard
ChatGPTNextWeb
[Feature] 关于webdav同步拆分为上传和下载两个按钮
为了提高交流效率，我们设立了官方 QQ 群和 QQ 频道，如果你在使用或者搭建过程中遇到了任何问题，请先第一时间加群或者频道咨询解决，除非是可以稳定复现的 Bug 或者较为有创意的功能建议，否则请不要随意往 Issue 区发送低质无意义帖子。
亲身使用的效果，同步功能有些鸡肋。主要在于，每次同步完全不知道是下载还是上传。希望拆分为两个按钮功能，一个负责上传，一个负责下载，这样能完美解决多端同步的需求。
这个功能与现有的问题有关吗？ 如果有关，请在此列出链接或者描述问题。
你想要什么功能或者有什么建议？
希望拆分为两个按钮功能，一个负责上传，一个负责下载，这样能完美解决多端同步的需求。
有没有可以参考的同类竞品？ 可以给出参考产品的链接或者截图。
其他信息 可以说说你的其他考虑。
Bot detected the issue body's language is not English, translate it automatically.
Title: [Feature] About webdav synchronization split into two buttons: upload and download
In order to improve communication efficiency, we have set up an official QQ group and QQ channel. If you encounter any problems during use or construction, please join the group or channel for consultation as soon as possible, unless it is a bug that can be stably reproduced or More creative feature suggestions, otherwise please do not send low-quality and meaningless posts to the Issue area.
From the results of personal use, the synchronization function is a bit useless. The main thing is that every time you synchronize, you don't know whether it is downloading or uploading. I hope to split it into two button functions, one responsible for uploading and one responsible for downloading, which can perfectly solve the needs of multi-end synchronization.
**Is this feature related to an existing issue? ** If relevant, please list the link here or describe the problem.
**What features do you want or have any suggestions? **
I hope to split it into two button functions, one responsible for uploading and one responsible for downloading, which can perfectly solve the needs of multi-end synchronization.
**Are there any similar competing products that we can refer to? ** Links or screenshots of reference products can be given.
other information Can you tell me about your other considerations.
附上一些使用的截图应证——
这是我16点50分的一次同步，增加了一个对话窗口。
但实际上，webdav 仅有一次4分钟之前的同步数据，没有这份数据——
Bot detected the issue body's language is not English, translate it automatically.
Attached are some screenshots used to prove——
This is my synchronization at 16:50, adding a dialogue window.
But in fact, webdav only has one synchronization data 4 minutes ago, and does not have this data——
我刚才进行了一次同步，试图将自定义了5个面具的数据，同步到一个完全空白的网页chat. 但结果却是，这个空白数据chat覆盖了我的5个面具的数据，并且主动删除掉，导致我的使用数据全部丢失。
Bot detected the issue body's language is not English, translate it automatically.
I just performed a synchronization, trying to synchronize the data of 5 customized masks to a completely blank web chat. But the result was that this blank data chat covered the data of my five masks and was actively deleted, resulting in the loss of all my usage data.
Bot detected the issue body's language is not English, translate it automatically.
Generally, the data is fully covered. In theory, if you switch to device 2, the data modification time will be old, but if you open a new one, the blank data time will be new, so it is covered. It seems that the conversation will not be deleted, so it is no problem, but your mask is a setting, not a conversation, so it is gg. The solution is to refresh the old data after a new start and then get new data. This is the pitfall of the sync button.
一般就是数据全覆盖，理论上你切到设备2数据修改时间是旧的，但是你完全新开了一个那空白数据时间就新了，所以就覆盖了。好像对话不会删除所以是没问题的，但是你面具是设置不是对话所以就gg了。办法就是新开之后再刷刷旧的数据的时间再弄新的，这就是同步按钮的坑，
我现在的办法，是手动下载webdav的数据导入，然后删除webdav的数据，再进行同步。 很笨，但避免了很多麻烦。其实，也就等同于使用本地备份和恢复，再上传云盘备份一份。
Bot detected the issue body's language is not English, translate it automatically.
Generally, the data is fully covered. In theory, if you switch to device 2, the data modification time is old, but if you open a new one, the blank data time will be new, so it is covered. It seems that the conversation will not be deleted, so it is no problem, but your mask is a setting, not a conversation, so it is gg. The solution is to refresh the old data after a new start and then get new data. This is the pitfall of the sync button.
My current method is to manually download and import the webdav data, then delete the webdav data, and then synchronize it. Very stupid, but saved a lot of trouble. In fact, it is equivalent to using local backup and recovery, and then uploading a cloud disk backup.
Bot detected the issue body's language is not English, translate it automatically.
+1, synchronization also requires automatic synchronization.
Bot detected the issue body's language is not English, translate it automatically.
+1, now a lot of problems can be solved by simply splitting them up. Eventually, I hope to achieve a synchronization method similar to FLOCCUS.
Bot detected the issue body's language is not English, translate it automatically.
+1 The current synchronization mechanism is really confusing. I have no idea how it will synchronize after clicking the button.