[Feature] Cloud Sync via WebDAV

[chennishizhu]

能否增加对WebDav的支持，让用户使用自己的网盘实现消息记录的自动备份与同步。像坚果云、Dropbox、InfiniCLOUD等等，随便支持一个都可以。

[Yidadaa]

在计划中。

[ChasLui]

目前我的解决办法是用chrome插件localStorage manager手动导入导出.

[adevjoe]

在计划中。

请问计划用什么方式实现

[ChasLui]

目前我的解决办法是用chrome插件localStorage manager手动导入导出.

更新, 目前使用自部署的 cookiecloud 同步localStorage

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Currently my solution is to use the chrome plugin localStorage manager to manually import and export.

Update, currently use self-deployed cookiecloud to sync localStorage

[daiaji]

移动版上只能依靠ChatGPT-Next-Web 的原生实现了。
这玩意是存在Root权限才能访问的地方。
而Firefox android没有相关扩展可用。
chrome就别说了。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

The mobile version can only rely on the native implementation of ChatGPT-Next-Web.
This thing is a place where Root permissions can only be accessed.
And Firefox android has no relevant extensions available.
Let alone chrome.

[ckt1031]

就像ChatGPT一样, 不可能同时向多装置Stream输出，但是可以在云端档案中，添加状态元数据，在该讯息ID底下，发送讯息，先向云端查询是否正在Stream，完成后，添加记录并且进行云端储存。在另一个装置底下，对话可以与云端进行日期对比。
同时亦可以添端对端加密的功能，在网盘环境对话内容完全不可见。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Just like ChatGPT, it is impossible to stream to multiple devices at the same time, but you can add status metadata to the cloud file, send a message under the message ID, first query the cloud whether it is Streaming, and then add a record and proceed cloud storage. Under another device, conversations can be dated against the cloud.
At the same time, the function of end-to-end encryption can also be added, and the content of the conversation in the network disk environment is completely invisible.

[Yidadaa]

大多数 webdav 服务均没有开启 cors，无法在网页中直接使用，此特性开发暂时搁置。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Most webdav services do not have cors enabled and cannot be used directly in web pages. The development of this feature is temporarily on hold.

[daiaji]

大多数 webdav 服务均没有开启 cors，无法在网页中直接使用，此特性开发暂时搁置。

使用云盘的api呢？

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Most webdav services do not have cors enabled and cannot be used directly in web pages. The development of this feature is temporarily on hold.

What about using cloud disk APIs?

[imzhoukunqiang]

可否考虑一下用后端服务转发到webdav呢？

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Can you consider using the backend service to forward to webdav?

[Endlessworld]

#2176 我在这个里面描述的可能不够清楚、
这个功能
应该叫基于web3的多端同步

从用户使用效果上来说
1 设置里有个 【开启多端共享】之类的选项 选中即开启 开启后 可选是否 设置【访问密码】 可通过【访问密码】加密解密数据
2 效果1 添加浏览器书签 清空浏览缓存数据 打开书签地址 聊天记录 设置信息依旧存在 除非手动重置。
3 效果2 另一设备通过旧设备当前链接或其二维码打开相同链接 聊天记录、设置信息 与旧设备相同
4 效果3 多设备在相同链接地址同时进行聊天时 刷新页面可同步最新消息记录

从开发者使用角度来说 可以在环境变量设置一个稳定的Web3节点服务商、如cloudflare（有免费额度）
实现思路：
参考这里#2176
1 开启选项后 将当前用户聊天记录与配置选项信息 根据随机字符或用户设置的【访问密码】进行可逆的简单加密 ；
2 将加密后的用户信息 pin到web3供应商例如 cloudflare（ https://www.cloudflare.com/zh-cn/web3/#）
3 pin数据到供应商将获取一个CID,简单理解为数据Hash不同数据Hash值不同，因此随着数据内容变化CID会不断变化、因此需要将CID发布到IPNS IPNS即是一个最新版本的CID固定访问链接。
4 更新当前localtion.href ，query参数附带 IPNS及访问密码
5 页面初始化检测是否携带IPNS 有则提取用户数据 对用户数据进行恢复

这个功能还可能为本项目 增加一点有意思社交属性 例如 AI多人在线聊天
哈哈

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

#2176 What I described here may not be clear enough,
this function
It should be called multi-terminal synchronization based on web3

From the perspective of user effect

1. There is an option such as [Enable multi-terminal sharing] in the settings. Select it to enable it. After enabling it, you can choose whether to set the [Access Password] to encrypt and decrypt data through the [Access Password]
   2 Effect 1 Add browser bookmark, clear browsing cache data, open bookmark address, chat history, setting information still exists unless manually reset.
   3 Effect 2 Another device opens the same link through the current link of the old device or its QR code. The chat history and setting information are the same as the old device
   4 Effect 3 When multiple devices are chatting at the same link address today, refresh the page to synchronize the latest message records

From the perspective of developers, you can set a stable Web3 node service provider in the environment variable, such as cloudflare (with free quota)
Implementation idea:
Refer here #2176
1 After the option is turned on, the current user's chat history and configuration option information will be reversibly and simply encrypted according to random characters or the [Access Password] set by the user;
2 Pin the encrypted user information to a web3 provider such as cloudflare (https://www.cloudflare.com/zh-cn/web3/#)
3 pin data to the supplier will obtain a CID, which is simply understood as different data Hash values, so as the data content changes, the CID will continue to change, so it is necessary to publish the CID to IPNS IPNS is the latest version of CID fixed access Link.
4 Update the current localtion.href, query parameter with IPNS and access password
5 The page is initialized to detect whether it carries IPNS, and if so, extract user data and restore user data

[daiaji]

#2176 我在这个里面描述的可能不够清楚、 这个功能 应该叫基于web3的多端同步

从用户使用效果上来说 1 设置里有个 【开启多端共享】之类的选项 选中即开启 开启后 可选是否 设置【访问密码】 可通过【访问密码】加密解密数据 2 效果1 添加浏览器书签 清空浏览缓存数据 打开书签地址 聊天记录 设置信息依旧存在 除非手动重置。 3 效果2 另一设备通过旧设备当前链接或其二维码打开相同链接 聊天记录、设置信息 与旧设备相同 4 效果3 多设备在相同链接地址同时进行聊天时 刷新页面可同步最新消息记录

从开发者使用角度来说 可以在环境变量设置一个稳定的Web3节点服务商、如cloudflare（有免费额度） 实现思路： 参考这里#2176 1 开启选项后 将当前用户聊天记录与配置选项信息 根据随机字符或用户设置的【访问密码】进行可逆的简单加密 ； 2 将加密后的用户信息 pin到web3供应商例如 cloudflare（ https://www.cloudflare.com/zh-cn/web3/#） 3 pin数据到供应商将获取一个CID,简单理解为数据Hash不同数据Hash值不同，因此随着数据内容变化CID会不断变化、因此需要将CID发布到IPNS IPNS即是一个最新版本的CID固定访问链接。 4 更新当前localtion.href ，query参数附带 IPNS及访问密码 5 页面初始化检测是否携带IPNS 有则提取用户数据 对用户数据进行恢复

这个功能还可能为本项目 增加一点有意思社交属性 例如 AI多人在线聊天 哈哈

前沿技术总是很有趣，听起来是cf提供了储存节点和网关？
看cf自己的说明，数据会被放到全球数据中心，那看起来容灾不错。
每个月50g的配额完全够用了。
对于探索IPFS和WEB3的应用也是有利的。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

#2176 What I described here may not be clear enough, this function should be called multi-terminal synchronization based on web3

From the point of view of the user's use effect, 1. There is an option such as [Enable Multi-terminal Sharing] in the settings, and it will be enabled. After opening, you can choose whether to set the [Access Password] to encrypt and decrypt data through the [Access Password] 2. Effect 1. Add browser bookmarks Clear browsing cache data, open bookmark address, chat record setting information still exists unless manually reset. 3 Effect 2 Another device opens the same link through the current link of the old device or its QR code. The chat history and setting information are the same as the old device. 4 Effect 3 When multiple devices chat at the same link address at the same time, refresh the page to synchronize the latest message records

From the perspective of developers, you can set a stable Web3 node service provider, such as cloudflare (with free quota) in the environment variables. Implementation ideas: Refer to here #2176 1 After the option is enabled, the current user chat history and configuration option information will be randomly selected. Characters or [Access Password] set by the user for reversible simple encryption; 2 Pin the encrypted user information to web3 providers such as cloudflare ([https://www.cloudflare.com/zh-cn/web3/#)] (https://www.cloudflare.com/zh-cn/web3/#%EF%BC%89) 3 pin data to the supplier will get a CID, simply understood as different data Hash values ​​are different, so with Data content changes CID will change constantly, so it is necessary to publish CID to IPNS IPNS is a fixed access link of the latest version of CID. 4 Update the current localtion.href, the query parameter comes with IPNS and access password 5 Initialize the page to detect whether it carries IPNS, if so, extract user data and restore user data

This function may also add some interesting social attributes to this project, such as AI multiplayer online chat haha

Frontiers are always interesting, sounds like cf provides storage nodes and gateways?
According to cf's own description, the data will be placed in the global data center, which looks good for disaster recovery.

[2-3-5-7]

我看到 https://github.com/ztjhz/BetterChatGPT 使用 GoogleDrive 实现的同步，是否可以参考一下？

[2-3-5-7]

@ChasLui 问一下，移动端有自动同步 localstorage 的方法吗？我试了 android 手机 kiwi 浏览器装 cookiecloud，无法同步，但是 PC 端是没问题的

[ttimasdf]

别整那些花里胡哨的什么web3。那东西没有任何意义。

当你提出解决方案的时候，花时间想想自己要解决的是什么问题。

当我们说同步的时候，我们的需求是：一个隐私、可内网或公网部署 、高速、省空间的同步服务。

IPFS 没有解决以上任何一点，甚至与之背道而驰🙄

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Don't fix those fancy web3. That stuff doesn't make any sense.

When you come up with a solution, take the time to think about the problem you are trying to solve.

When we talk about synchronization, our requirement is: a privacy, intranet or public network deployment, high-speed, space-saving synchronization service.

IPFS doesn't solve any of the above, and even runs counter to it 🙄

[ZacharyJia]

考虑支持S3存储怎么样？S3使用很广泛，不管是原版的，还是各种兼容S3 API的对象存储服务都有，也可以使用MinIO自建。
像Cloudflare也提供了免费的10G存储, 100万次写，1000万次读操作 ( https://www.cloudflare.com/zh-cn/products/r2/ )，个人用户应该是足够的。也提供了CORS支持(https://developers.cloudflare.com/r2/buckets/cors/)

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

How about considering support for S3 storage? S3 is widely used, whether it is the original version or a variety of object storage services compatible with the S3 API, you can also use MinIO to build yourself.
Cloudflare also provides free 10G storage, 1 million writes and 10 million reads ( https://www.cloudflare.com/zh-cn/products/r2/ ), which should be enough for individual users. CORS support is also provided (https://developers.cloudflare.com/r2/buckets/cors/)

[daiaji]

同步能不能普通的做成
https://chatgpt.xn--b6gac.eu.org/
这种简单的基于导入导出的同步？
？
这样还能导出成json或者压缩过的json。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Sync ngbung common made
https://chatgpt.xn--b6gac.eu.org/
This simple import-export based synchronization?
?
This can also be exported as json or compressed json.

[821869798]

尝试用了下 BetterChatGPT GoogleDrive方式的同步，还可以，能否能支持下同步消息。

[leoweyr]

既然ChatGPT-Next-Web存在服务端和客户端关系，是否可以把聊天记录数据选择直接储存在服务端特定位置，在客户端可设定是否同步服务端指定的聊天记录。这样一来就不需要依靠第三方云服务了。（<- 个人使用）但是如果说是分发商直接提供这种服务，那么服务端得有数据容器去储存不同客户的客户端聊天记录，还得是加密的、防止数据泄露

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Since ChatGPT-Next-Web has a relationship between the server and the client, whether it is possible to choose to store the chat record data directly in a specific location on the server, and set whether to synchronize the chat records specified by the server on the client. This eliminates the need to rely on third-party cloud services. But if the distributor directly provides this service, then the server must have a data container to store the client chat records of different customers, and it must be encrypted to prevent data leakage

[yunwuu]

我有一个想法，但是代码能力渣渣，完整实现尚未完成，不知道有没有大佬可以考虑实现一下：

1. 与其使用WebDav，不如使用 Redis，避免了cors的问题的同时可以更便捷的合并冲突的数据。 Redis实例可以直接使用 Upstash ，有足够的免费额度，且无论是 Redis URL 还是 @upstash/redis 库提供支持的 URL+Token的验证方式，都无需繁琐的配置。
2. 对Redis的相关读写操作可以利用 Edge Functions 来完成。
3. Redis中设两个Hash键值对，messages 和 sessions ，分别存放消息和会话，在新消息/会话创建完成后通过 edge function直接把消息/会话上传到数据库，而设置中的同步按钮则可以进行云端数据的拉取和本地全部数据的上传。
4. 数据库拥有全部 messages 和 sessions 的信息后，只需要进行简单的合并就能构造出存储在localStorage中的格式（或许也可以直接调用zustand或已有的方法，没有仔细研究过，应该是可行的）

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I have an idea, but the code ability is sloppy, and the complete implementation has not been completed. I don’t know if there are any big guys who can consider implementing it:

1. Instead of using WebDav, it is better to use Redis, which can avoid the problem of cors and merge conflicting data more conveniently. The Redis instance can directly use Upstash, there is enough free quota, and no matter it is the Redis URL or @upstash/redis supported URL+Token verification method, there is no need cumbersome configuration.
2. The relevant read and write operations on Redis can be done using Edge Functions.
3. There are two Hash key-value pairs in Redis, messages and sessions, which store messages and sessions respectively. After the new message/session is created, the message/session is directly uploaded to the database through the edge function, and the setting The sync button can pull cloud data and upload all local data.
4. After the database has all the messages and sessions information, it only needs to perform a simple merger to construct the format stored in localStorage (maybe you can also directly call zustand or an existing method, there is no After careful research, it should be feasible)

[Yidadaa]

Done #2819

[lovitus]

webdav服务提供商大部分都提供了cors设置吧,
通配,
或者认证和域名枚举

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Most webdav service providers provide cors settings, right?
wildcard,
Or authentication and domain name enumeration