@lobehub/chat 1.3.2 → 1.3.4

package/CHANGELOG.md

@@ -2,6 +2,56 @@
 
 # Changelog
 
+### [Version 1.3.4](https://github.com/lobehub/lobe-chat/compare/v1.3.3...v1.3.4)
+
+<sup>Released on **2024-07-09**</sup>
+
+#### ♻ Code Refactoring
+
+- **misc**: Support disable clientFetch by default.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### Code refactoring
+
+- **misc**: Support disable clientFetch by default, closes [#3133](https://github.com/lobehub/lobe-chat/issues/3133) [#3108](https://github.com/lobehub/lobe-chat/issues/3108) ([4415652](https://github.com/lobehub/lobe-chat/commit/4415652))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
+### [Version 1.3.3](https://github.com/lobehub/lobe-chat/compare/v1.3.2...v1.3.3)
+
+<sup>Released on **2024-07-09**</sup>
+
+#### 🐛 Bug Fixes
+
+- **misc**: Allow user to use their own WebRTC signaling.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **misc**: Allow user to use their own WebRTC signaling, closes [#3182](https://github.com/lobehub/lobe-chat/issues/3182) ([c7f8f38](https://github.com/lobehub/lobe-chat/commit/c7f8f38))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 1.3.2](https://github.com/lobehub/lobe-chat/compare/v1.3.1...v1.3.2)
 
 <sup>Released on **2024-07-09**</sup>

package/docs/self-hosting/advanced/webrtc.mdx

@@ -0,0 +1,80 @@
+# LobeChat WebRTC Sync
+
+## Introduction to WebRTC
+
+WebRTC (Web Real-Time Communication) is a technology that enables peer-to-peer communication between browsers. In LobeChat, we experimentally implemented real-time data synchronization between devices based on WebRTC and YJS, without relying on traditional server databases. This solution offers high privacy, zero conflicts, and provides a real-time session synchronization experience.
+
+## Configuring WebRTC for Synchronization
+
+To use the WebRTC synchronization feature in LobeChat, you need to complete the following steps:
+
+<Steps>
+
+### Deploy Signaling Server
+
+Deploy a WebRTC signaling server with one click using the Zeabur platform:
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/templates/MY0JZG?referralCode=arvinxx)
+
+Alternatively, you can view the [source code](https://github.com/lobehub/y-webrtc-signaling) and deploy it on your own.
+
+After deployment, you will receive a URL, for example: `https://my-signaling-server.zeabur.app`.
+
+### Enable WebRTC Sync in the Deployment Instance
+
+The WebRTC sync feature in LobeChat is hidden by default and needs to be enabled by adding the environment variable `FEATURE_FLAGS=+webrtc_sync`.
+
+### Configure WebRTC Sync Settings in LobeChat
+
+1. Open LobeChat settings -> Data Sync
+2. Enter the signaling server address in the WebRTC sync section;
+3. Set the sync channel name and password
+
+<Image
+  alt={'LobeChat Data Sync Settings Page'}
+  height={356}
+  inStep
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/bf86bf1e-87fb-4015-8587-15ff28bb9c24'}
+/>
+
+### Repeat the Above Configuration on Devices that Need to Sync
+
+Ensure all devices use the same signaling server, channel name, and password. Once configured, the devices should automatically start syncing data.
+
+</Steps>
+
+## Limitations and Known Issues
+
+Although WebRTC has the advantages of no database and flexibility, after extensive community testing, the following limitations and known issues have been identified:
+
+### Requirement for Devices to be Online Simultaneously
+
+WebRTC requires devices to be online simultaneously to synchronize, meaning changes cannot be made on one device while offline and then synced later on another device.
+
+This limitation is due to the communication nature of WebRTC. In a pure frontend, serverless scenario, data synchronization between two devices can only be achieved through peer-to-peer communication. When one device is online and the other is offline, it is impossible to determine where the data should come from. Only when both devices are online can data communication occur. This mode is more like an online chat room where everyone needs to be online to see each other's data and achieve synchronization.
+
+Therefore, in certain situations, WebRTC's pure peer-to-peer approach may not fully meet users' needs (e.g., one device is a work computer, and the other is a home computer), and there are also some issues with data synchronization.
+
+### Network Issues Leading to Sync Failures
+
+Due to the implementation mechanism of WebRTC, its peer-to-peer communication has strict network requirements. Many of our users have reported:
+
+- Syncing between PCs is possible, but syncing between a mobile device with a SIM card and a PC is not, although syncing is possible when using the same WIFI as the PC;
+- Syncing fails when switching networks.
+
+### Stability and Performance Issues
+
+- Some users have reported ICE connection failures on the Firefox browser: [WebRTC Data Sync Feedback](https://github.com/lobehub/lobe-chat/issues/1683#issuecomment-2094745907)
+- For extremely long text or large amounts of conversation records, the synchronization process may slow down or become unstable: [When the model outputs a very long conversation, the end of the conversation will contain synchronization-related content tags, leading to sync failures](https://github.com/lobehub/lobe-chat/issues/1962)
+
+## Our Recommendations
+
+Considering the above reasons, we recommend users treat the WebRTC sync feature as experimental and regularly back up important data.
+
+We have already released a more stable and user-friendly server database synchronization solution ([deployment guide](/docs/self-hosting/advanced/server-database)). We recommend users prioritize using the server database synchronization solution.
+
+<Callout type={'warning'}>
+  Please note that we have officially announced the archiving of this sync feature in [PR
+  3182](https://github.com/lobehub/lobe-chat/pull/3182), and the above issues will no longer be
+  considered for fixes.
+</Callout>

package/docs/self-hosting/advanced/webrtc.zh-CN.mdx

@@ -0,0 +1,87 @@
+---
+title: LobeChat WebRTC 同步配置指南
+description: 在 LobeChat 中实现基于 WebRTC 和 YJS 的设备间实时数据同步。了解如何配置 WebRTC 并开启同步功能，以及使用局限性和已知问题。
+tags:
+  - YJS
+  - 信令服务器
+---
+
+# LobeChat WebRTC 同步
+
+## WebRTC 简介
+
+WebRTC (Web Real-Time Communication) 是一项实现浏览器之间点对点通信的技术。在 LobeChat 中,我们实验性地基于 WebRTC 和 YJS 实现了设备间的实时数据同步,无需依赖传统的服务器数据库。这种方案具有高度隐私性、零冲突性，并能提供实时会话同步体验。
+
+## 配置 WebRTC 并实现同步
+
+要使用 LobeChat 的 WebRTC 同步功能,需要完成以下步骤:
+
+<Steps>
+
+### 部署信令服务器
+
+使用 Zeabur 平台一键部署 WebRTC 信令服务器：
+
+[![Deploy on Zeabur](https://zeabur.com/button.svg)](https://zeabur.com/templates/MY0JZG?referralCode=arvinxx)
+
+或者查看 [源码](https://github.com/lobehub/y-webrtc-signaling) 自行部署。
+
+部署完成后，可以得到一个 URL，例如：`https://my-signaling-server.zeabur.app`。
+
+### 在部署实例中开启 WebRTC 同步
+
+LobeChat 默认隐藏了 WebRTC 同步功能，需要通过添加环境变量 `FEATURE_FLAGS=+webrtc_sync` 来开启 WebRTC 同步特性。
+
+### 配置 LobeChat 的 WebRTC 同步设置
+
+1. 打开 LobeChat 设置 -> 数据同步
+2. 在 WebRTC 同步中填写信令服务器地址；
+3. 设置同步频道名称和密码
+
+<Image
+  alt={'LobeChat 数据同步设置页'}
+  height={356}
+  inStep
+  src={'https://github.com/lobehub/lobe-chat/assets/28616219/bf86bf1e-87fb-4015-8587-15ff28bb9c24'}
+/>
+
+### 在需要同步的设备上重复以上配置
+
+确保所有设备使用相同的信令服务器、频道名称和密码，完成配置后,设备间应该可以开始自动同步数据。
+
+</Steps>
+
+## 使用局限性和已知问题
+
+虽然 WebRTC 具有无数据库、比较灵活的特性，但目前该功能经过大范围社区测试，存在以下局限性和已知问题：
+
+### 设备同时在线要求
+
+WebRTC 要求设备同时在线才能进行同步，这意味着无法在一台设备离线时在另一台设备上进行更改并稍后同步。
+
+这是 WebRTC 本身的通信特性有关系，由于在纯前端、无服务端的情况下，两个设备的数据同步只能通过点对点通信的形式达成。当一个设备在线，一个设备离线的情况下，我们无从感知数据到底应该从哪来，只有当两台设备都在线的时候，双发数据才能通信。其实这种模式更像是一个在线聊天室，大家都在线时才能看到对方的数据，然后达成同步。
+
+因此 WebRTC 这种纯点对点的方式在某些情况下并无法完全满足用户的诉求（例如一个是公司电脑，一个是家里电脑），同时也存在一些数据同步层面的问题。
+
+### 网络问题可能导致同步失败
+
+由于 WebRTC 的实现机制，其点对点通信对于网络要求非常苛刻，我们的很多用户反馈：
+
+- 在 PC 上可以互相同步、 手机 sim 卡无法和 PC 同步、但是换成和PC一样的WIFI可以和 PC 同步；
+- 任何切换网络都无法同步；
+
+### 稳定性与性能问题
+
+- 部分用户报告在 Firefox 浏览器上遇到 ICE 连接失败的问题：[WebRTC Data Sync Feedback](https://github.com/lobehub/lobe-chat/issues/1683#issuecomment-2094745907)
+- 对于超长文本或大量对话记录,同步过程可能变慢或不稳定：[当模型输出超长对话时，对话末尾会出现同步相关的内容标签，导致同步失败](https://github.com/lobehub/lobe-chat/issues/1962)
+
+## 我们的建议
+
+鉴于以上原因，我们建议用户将 WebRTC 同步功能视为实验性功能,并定期备份重要数据。
+
+目前我们已经发布了更稳定、更用户友好的服务端数据库同步方案（[部署指南](/zh/docs/self-hosting/advanced/server-database)），我们建议用户优先考虑使用服务端数据库同步方案。
+
+<Callout type={'warning'}>
+  请注意，我们已经在 [PR 3182](https://github.com/lobehub/lobe-chat/pull/3182)
+  中正式宣布归档该同步特性，上述问题将不再考虑进行修复。
+</Callout>

package/docs/usage/tools-calling/groq.zh-CN.mdx

@@ -1,12 +1,19 @@
 ---
-title: Groq Tool Calling
+title: Groq Tools Calling
+description: >-
+  了解 Groq 平台模型 Tools Calling的能力一览，包括LLAMA3 70B、LLAMA3
+  8B和Mixtral-8x7B的简单和复杂指令调用情况。
+tags:
+  - Groq 平台模型
+  - Tools Calling
+  - LLAMA3 70B
+  - LLAMA3 8B
+  - Mixtral-8x7B
 ---
 
 # Groq 平台模型 Tools Calling 评测（Llama 3/Mistral）
 
-<Callout type={'info'}>
-  由于 Groq 本身不支持 stream，因此 Tools Calling 的调用是普通请求。
-</Callout>
+<Callout type={'info'}>由于 Groq 本身不支持 stream，因此 Tools Calling 的调用是普通请求。</Callout>
 
 Groq 平台的模型 Tools Calling 能力一览：
 
@@ -16,7 +23,6 @@ Groq 平台的模型 Tools Calling 能力一览：
 | LLAMA3 8B    | ✅                 | ❌              | ✅               | 🌟🌟         | 🌟       |
 | Mixtral-8x7B | ✅                 | ❌              | ✅               | ⛔           | 🌟🌟     |
 
-
 ## LLAMA3 70B
 
 ### 简单调用指令：天气查询
@@ -120,7 +126,7 @@ LLAMA3 8B 在 DallE 的输出场景下，只会输出 1 张图片，而不是像
 POST /api/chat/groq 200 in 2517ms
 ```
 
-  </details>
+</details>
 
 ## Mixtral-8x7B
 

package/locales/ar/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "نظام التشغيل غير معروف"
     },
     "warning": {
-      "message": "هذه الميزة لا تزال تحت التجربة وقد تكون هناك حالات غير متوقعة أو غير مستقرة، في حال واجهت مشكلة، يرجى تقديم ردود فعل في الوقت المناسب."
+      "tip": "بعد فترة اختبار عامة طويلة، قد لا يكون تزامن WebRTC مستقرًا بما يكفي لتلبية احتياجات التزامن العامة. يرجى <1>نشر خادم الإشارة</1> بنفسك قبل الاستخدام."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "اتصال البيانات النقطي الفوري يتطلب تواجد الأجهزة معًا للمزامنة",
       "enabled": {
-        "invalid": "الرجاء إدخال اسم قناة المزامنة قبل تشغيلها",
+        "invalid": "الرجاء ملء اسم خادم الإشارة واسم القناة المتزامنة قبل تمكينها",
         "title": "تمكين المزامنة"
       },
+      "signaling": {
+        "desc": "سيستخدم WebRTC هذا العنوان للتزامن",
+        "placeholder": "الرجاء إدخال عنوان خادم الإشارة",
+        "title": "خادم الإشارة"
+      },
       "title": "WebRTC مزامنة"
     }
   },

package/locales/bg-BG/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Неизвестна операционна система"
     },
     "warning": {
-      "message": "Тази функция в момента е експериментална и може да има неочаквано или нестабилно поведение. Ако срещнете някакви проблеми, моля, изпратете незабавна обратна връзка."
+      "tip": "След дълъг период на обществено тестване, синхронизацията на WebRTC може да не бъде стабилна за общите изисквания за синхронизация на данни. Моля, <1>инсталирайте сигналния сървър</1> и го използвайте след това."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Комуникацията на данни в реално време между партньори изисква всички устройства да бъдат онлайн за синхронизиране.",
       "enabled": {
-        "invalid": "Моля, въведете име на канал за синхронизиране, преди да активирате",
+        "invalid": "Моля, попълнете адреса на сигналния сървър и името на синхронизиращия канал, преди да го активирате.",
         "title": "Активиране на синхронизиране"
       },
+      "signaling": {
+        "desc": "WebRTC ще използва този адрес за синхронизация",
+        "placeholder": "Моля, въведете адреса на сигналния сървър",
+        "title": "Сигнален сървър"
+      },
       "title": "WebRTC синхронизиране"
     }
   },

package/locales/de-DE/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Unbekanntes Betriebssystem"
     },
     "warning": {
-      "message": "Diese Funktion ist derzeit experimentell und kann unerwartete oder instabile Situationen aufweisen. Bitte geben Sie bei Problemen rechtzeitig Feedback ab."
+      "tip": "Nach einer längeren Phase des Community-Tests kann die WebRTC-Synchronisierung möglicherweise nicht stabil genug sein, um allgemeine Synchronisierungsanforderungen zu erfüllen. Bitte <1>richten Sie einen Signalisierungsserver ein</1> und verwenden Sie ihn dann."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Echtzeit, Punkt-zu-Punkt-Datenkommunikation, bei der die Geräte gleichzeitig online sein müssen, um synchronisiert zu werden",
       "enabled": {
-        "invalid": "Bitte geben Sie zuerst den Synchronisierungskanalnamen ein, bevor Sie die Synchronisierung aktivieren",
+        "invalid": "Bitte geben Sie zuerst den Signalisierungsserver und den Synchronisierungskanal an, bevor Sie dies aktivieren.",
         "title": "Synchronisierung aktivieren"
       },
+      "signaling": {
+        "desc": "WebRTC wird diese Adresse für die Synchronisierung verwenden",
+        "placeholder": "Bitte geben Sie die Adresse des Signalisierungsservers ein",
+        "title": "Signalisierungsserver"
+      },
       "title": "WebRTC-Synchronisierung"
     }
   },

package/locales/en-US/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Unknown OS"
     },
     "warning": {
-      "message": "This feature is currently experimental and may have unexpected or unstable behavior. If you encounter any issues, please submit feedback promptly."
+      "tip": "After a long period of community testing, WebRTC synchronization may not reliably meet general data synchronization needs. Please <1>deploy a signaling server</1> before use."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Real-time, peer-to-peer data communication requires all devices to be online for synchronization.",
       "enabled": {
-        "invalid": "Please enter a sync channel name before enabling",
+        "invalid": "Please fill in the signaling server and synchronization channel name before enabling.",
         "title": "Enable Sync"
       },
+      "signaling": {
+        "desc": "WebRTC will use this address for synchronization",
+        "placeholder": "Enter signaling server address",
+        "title": "Signaling Server"
+      },
       "title": "WebRTC Sync"
     }
   },

package/locales/es-ES/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Sistema operativo desconocido"
     },
     "warning": {
-      "message": "Esta función todavía está en fase experimental y puede presentar situaciones inesperadas o inestables. Si encuentras algún problema, por favor envía tus comentarios de inmediato."
+      "tip": "Después de un largo período de pruebas comunitarias, la sincronización WebRTC puede no ser capaz de satisfacer de manera estable las demandas generales de sincronización de datos. Por favor, <1>implementa tu propio servidor de señalización</1> antes de usarlo."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Comunicación de datos en tiempo real y punto a punto. Los dispositivos deben estar en línea simultáneamente para sincronizarse",
       "enabled": {
-        "invalid": "Por favor, introduce el nombre del canal de sincronización antes de activar",
+        "invalid": "Por favor, completa la información del servidor de señalización y el nombre del canal de sincronización antes de habilitarlo",
         "title": "Activar sincronización"
       },
+      "signaling": {
+        "desc": "WebRTC utilizará esta dirección para la sincronización",
+        "placeholder": "Introduce la dirección del servidor de señalización",
+        "title": "Servidor de señalización"
+      },
       "title": "Sincronización WebRTC"
     }
   },

package/locales/fr-FR/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Système d'exploitation inconnu"
     },
     "warning": {
-      "message": "Cette fonctionnalité est actuellement expérimentale et peut présenter des comportements inattendus ou instables. En cas de problème, veuillez soumettre vos commentaires rapidement."
+      "tip": "Après une longue période de test communautaire, la synchronisation WebRTC peut ne pas répondre de manière stable aux besoins généraux de synchronisation des données. Veuillez <1>déployer votre propre serveur de signalisation</1> avant utilisation."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Communication de données en temps réel et en pair-à-pair. Les appareils doivent être en ligne simultanément pour se synchroniser",
       "enabled": {
-        "invalid": "Veuillez entrer un nom de canal de synchronisation avant d'activer",
+        "invalid": "Veuillez saisir l'adresse du serveur de signalisation et le nom du canal de synchronisation avant d'activer.",
         "title": "Activer la synchronisation"
       },
+      "signaling": {
+        "desc": "WebRTC utilisera cette adresse pour la synchronisation",
+        "placeholder": "Veuillez entrer l'adresse du serveur de signalisation",
+        "title": "Serveur de signalisation"
+      },
       "title": "Synchronisation WebRTC"
     }
   },

package/locales/it-IT/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Sistema operativo sconosciuto"
     },
     "warning": {
-      "message": "Questa funzione è attualmente sperimentale e potrebbe comportare comportamenti imprevisti o instabili. In caso di problemi, invia tempestivamente un feedback."
+      "tip": "Dopo un lungo periodo di test della comunità, la sincronizzazione WebRTC potrebbe non essere in grado di soddisfare in modo stabile le esigenze generali di sincronizzazione dei dati. Si prega di <1>configurare un server di segnalazione</1> prima di utilizzarlo."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Comunicazione dati in tempo reale punto a punto, entrambi i dispositivi devono essere online per sincronizzarsi",
       "enabled": {
-        "invalid": "Per favore, inserisci un nome per il canale di sincronizzazione prima di abilitarlo",
+        "invalid": "Si prega di inserire l'indirizzo del server di segnalazione e il nome del canale di sincronizzazione prima di abilitare.",
         "title": "Abilita la sincronizzazione"
       },
+      "signaling": {
+        "desc": "WebRTC utilizzerà questo indirizzo per la sincronizzazione",
+        "placeholder": "Inserisci l'indirizzo del server di segnalazione",
+        "title": "Server di segnalazione"
+      },
       "title": "Sincronizzazione WebRTC"
     }
   },

package/locales/ja-JP/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "不明なOS"
     },
     "warning": {
-      "message": "この機能は現在実験的なものであり、予期しない不安定な状況が発生する可能性があります。問題が発生した場合はフィードバックを提出してください。"
+      "tip": "コミュニティの長期にわたる公開テストの結果、WebRTC 同期は一般的なデータ同期要求を安定して満たすことができない可能性があります。 <1>シグナリングサーバーをデプロイ</1> してからご使用ください。"
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "リアルタイムでピアツーピアのデータ通信を行い、デバイスが同時にオンラインである必要があります",
       "enabled": {
-        "invalid": "同期チャネル名を入力してから有効にしてください",
+        "invalid": "シグナリングサーバーと同期チャネル名を入力してから有効にしてください",
         "title": "同期を有効にする"
       },
+      "signaling": {
+        "desc": "WebRTC はこのアドレスを使用して同期します",
+        "placeholder": "シグナリングサーバーのアドレスを入力してください",
+        "title": "シグナリングサーバー"
+      },
       "title": "WebRTC 同期"
     }
   },

package/locales/ko-KR/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "알 수 없는 OS"
     },
     "warning": {
-      "message": "이 기능은 현재 실험적인 기능으로 예기치 않거나 불안정한 상황이 발생할 수 있으며 문제가 발생하면 즉시 피드백을 제출해 주세요."
+      "tip": "커뮤니티 베타 테스트를 거친 후, WebRTC 동기화는 일반 데이터 동기화 요구를 안정적으로 충족시키지 못할 수 있습니다. <1>시그널링 서버를 배포</1>한 후 사용하십시오."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "실시간, 피어 투 피어 데이터 통신으로 장치가 동시에 온라인 상태여야만 동기화할 수 있습니다",
       "enabled": {
-        "invalid": "동기화 채널 이름을 입력한 후에 활성화하세요",
+        "invalid": "시그널링 서버와 동기화 채널 이름을 입력한 후에 활성화하십시오.",
         "title": "동기화 활성화"
       },
+      "signaling": {
+        "desc": "WebRTC는 이 주소를 사용하여 동기화합니다.",
+        "placeholder": "시그널링 서버 주소를 입력하세요",
+        "title": "시그널링 서버"
+      },
       "title": "WebRTC 동기화"
     }
   },

package/locales/nl-NL/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Onbekend besturingssysteem"
     },
     "warning": {
-      "message": "Deze functie is momenteel experimenteel en kan onverwachte of onstabiele situaties veroorzaken. Als u problemen ondervindt, geef dan tijdig feedback."
+      "tip": "Na een lange periode van openbare tests in de community, kan WebRTC-synchronisatie mogelijk niet stabiel voldoen aan algemene synchronisatiebehoeften. Gelieve zelf een <1>signaleringsserver implementeren</1> voordat u het gebruikt."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Realtime, point-to-point datacommunicatie, apparaten moeten tegelijkertijd online zijn om te synchroniseren",
       "enabled": {
-        "invalid": "Schakel de synchronisatie in nadat u de synchronisatiekanaalnaam heeft ingevuld",
+        "invalid": "Vul eerst de signaleringsserver en synchronisatiekanaalnaam in voordat u deze inschakelt",
         "title": "Synchronisatie inschakelen"
       },
+      "signaling": {
+        "desc": "WebRTC zal dit adres gebruiken voor synchronisatie",
+        "placeholder": "Voer het adres van de signaleringsserver in",
+        "title": "Signaleringsserver"
+      },
       "title": "WebRTC Synchronisatie"
     }
   },

package/locales/pl-PL/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Nieznany system"
     },
     "warning": {
-      "message": "Ta funkcja jest obecnie eksperymentalna i może działać nieprzewidywalnie lub niestabilnie. W przypadku problemów prosimy o natychmiastowe zgłoszenie opinii."
+      "tip": "After a long period of community testing, WebRTC synchronization may not be able to reliably meet general data synchronization needs. Please <1>deploy a signaling server</1> before use."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Bezpośrednia, punkt-do-punktu komunikacja danych w czasie rzeczywistym, wymaga jednoczesnej obecności urządzeń online do synchronizacji",
       "enabled": {
-        "invalid": "Wprowadź nazwę kanału synchronizacji przed włączeniem",
+        "invalid": "Please fill in the signaling server and synchronization channel name before enabling.",
         "title": "Włącz synchronizację"
       },
+      "signaling": {
+        "desc": "WebRTC will use this address for synchronization",
+        "placeholder": "Enter signaling server address",
+        "title": "Signaling Server"
+      },
       "title": "Synchronizacja WebRTC"
     }
   },

package/locales/pt-BR/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Sistema operacional desconhecido"
     },
     "warning": {
-      "message": "Esta função ainda é experimental e pode apresentar comportamento inesperado ou instável. Se encontrar problemas, envie um feedback imediatamente."
+      "tip": "Após um longo período de testes comunitários, a sincronização WebRTC pode não atender de forma estável às demandas gerais de sincronização de dados. Por favor, <1>implante um servidor de sinalização</1> antes de usar."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Comunicação de dados em tempo real ponto a ponto. Os dispositivos precisam estar online simultaneamente para sincronizar",
       "enabled": {
-        "invalid": "Por favor, insira o nome do canal de sincronização antes de ativar",
+        "invalid": "Por favor, preencha o endereço do servidor de sinalização e o nome do canal de sincronização antes de ativar.",
         "title": "Ativar sincronização"
       },
+      "signaling": {
+        "desc": "O WebRTC usará este endereço para sincronização",
+        "placeholder": "Insira o endereço do servidor de sinalização",
+        "title": "Servidor de Sinalização"
+      },
       "title": "Sincronização WebRTC"
     }
   },

package/locales/ru-RU/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Неизвестная система"
     },
     "warning": {
-      "message": "Эта функция в настоящее время является экспериментальной и может работать нестабильно или непредсказуемо. Если вы столкнетесь с проблемами, пожалуйста, отправьте отзыв."
+      "tip": "После длительного общественного тестирования синхронизация WebRTC может не надежно удовлетворять общие потребности в синхронизации данных. Пожалуйста, <1>разверните собственный сигнальный сервер</1> перед использованием."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Реальное время, точка-точка передачи данных, устройства должны быть онлайн одновременно для синхронизации",
       "enabled": {
-        "invalid": "Пожалуйста, введите имя канала синхронизации перед включением",
+        "invalid": "Пожалуйста, введите адрес сигнального сервера и имя канала синхронизации перед включением.",
         "title": "Включить синхронизацию"
       },
+      "signaling": {
+        "desc": "WebRTC будет использовать этот адрес для синхронизации",
+        "placeholder": "Введите адрес сигнального сервера",
+        "title": "Сигнальный сервер"
+      },
       "title": "WebRTC синхронизация"
     }
   },

package/locales/tr-TR/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Bilinmeyen Sistem"
     },
     "warning": {
-      "message": "Bu özellik şu anda deneysel bir özellik olup, beklenmedik veya kararsız durumlar yaşanabilir. Sorunla karşılaşırsanız lütfen geri bildirimde bulunun."
+      "tip": "WebRTC'nin uzun bir topluluk beta testinden sonra, genel veri senkronizasyon ihtiyaçlarını kararlı bir şekilde karşılayamayabileceği uyarısı. Lütfen <1> sinyal sunucusunu dağıtın </1> ve ardından kullanın."
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "Gerçek zamanlı, noktadan noktaya veri iletişimi, senkronizasyon için cihazların aynı anda çevrimiçi olması gerekir",
       "enabled": {
-        "invalid": "Lütfen senkronizasyon kanalı adını girdikten sonra etkinleştirin",
+        "invalid": "Lütfen sinyal sunucusu ve senkronizasyon kanal adını girerek etkinleştirin",
         "title": "Senkronizasyonu Etkinleştir"
       },
+      "signaling": {
+        "desc": "WebRTC senkronizasyon için bu adresi kullanacak",
+        "placeholder": "Lütfen sinyal sunucusu adresini girin",
+        "title": "Sinyal Sunucusu"
+      },
       "title": "WebRTC Senkronizasyonu"
     }
   },

package/locales/vi-VN/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "Hệ điều hành không xác định"
     },
     "warning": {
-      "message": "Chức năng này hiện vẫn đang trong thử nghiệm, có thể gặp phải tình huống ngoài dự kiến hoặc không ổn định, nếu gặp vấn đề vui lòng gửi phản hồi ngay lập tức."
+      "tip": "经过较长一段时间社区公测，WebRTC 同步可能无法稳定满足通用的数据同步诉求。请自行 <1>部署信令服务器</1> 后使用。"
     },
     "webrtc": {
       "channelName": {
@@ -361,7 +361,6 @@
       },
       "desc": "Truyền thông dữ liệu thời gian thực, điểm-điểm, cần thiết bị cùng online mới có thể đồng bộ",
       "enabled": {
-        "invalid": "Vui lòng nhập tên kênh đồng bộ trước khi bật",
         "title": "Bật đồng bộ"
       },
       "title": "WebRTC Đồng bộ"
@@ -407,5 +406,15 @@
       "store": "Cửa hàng tiện ích"
     },
     "title": "Công cụ mở rộng"
+  },
+  "webrtc": {
+    "enabled": {
+      "invalid": "请填写信令服务器和同步频道名称后再开启"
+    },
+    "signaling": {
+      "desc": "WebRTC sẽ sử dụng địa chỉ này để đồng bộ",
+      "placeholder": "Vui lòng nhập địa chỉ máy chủ tín hiệu",
+      "title": "Máy chủ tín hiệu"
+    }
   }
 }

package/locales/zh-CN/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "未知系统"
     },
     "warning": {
-      "message": "本功能目前仍为实验性功能，可能存在预期外或不稳定的情况，如遇到问题请及时提交反馈。"
+      "tip": "经过较长一段时间社区公测，WebRTC 同步可能无法稳定满足通用的数据同步诉求。请自行 <1>部署信令服务器</1> 后使用。"
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "实时、点对点的数据通信，需设备同时在线才可同步",
       "enabled": {
-        "invalid": "请填写同步频道名称后再开启",
+        "invalid": "请填写信令服务器和同步频道名称后再开启",
         "title": "开启同步"
       },
+      "signaling": {
+        "desc": "WebRTC 将使用该地址进行同步",
+        "placeholder": "请输入信令服务器地址",
+        "title": "信令服务器"
+      },
       "title": "WebRTC 同步"
     }
   },

package/locales/zh-TW/setting.json

@@ -345,7 +345,7 @@
       "unknownOS": "未知系統"
     },
     "warning": {
-      "message": "本功能目前仍為實驗性功能，可能存在預期外或不穩定的情況，如遇到問題請及時提交反饋。"
+      "tip": "經過較長一段時間社區公測，WebRTC 同步可能無法穩定滿足通用的資料同步需求。請自行 <1>部署信令伺服器</1> 後使用。"
     },
     "webrtc": {
       "channelName": {
@@ -361,9 +361,14 @@
       },
       "desc": "實時、點對點的數據通信，需裝置同時在線才可同步",
       "enabled": {
-        "invalid": "請填寫同步頻道名稱後再開啟",
+        "invalid": "請填寫信令伺服器和同步頻道名稱後再啟用",
         "title": "開啟同步"
       },
+      "signaling": {
+        "desc": "WebRTC 將使用該地址進行同步",
+        "placeholder": "請輸入信令伺服器地址",
+        "title": "信令伺服器"
+      },
       "title": "WebRTC 同步"
     }
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lobehub/chat",
-  "version": "1.3.2",
+  "version": "1.3.4",
   "description": "Lobe Chat - an open-source, high-performance chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Supports one-click free deployment of your private ChatGPT/LLM web application.",
   "keywords": [
     "framework",

package/src/app/(main)/settings/sync/features/Alert.tsx

@@ -1,11 +1,13 @@
 'use client';
 
 import { Alert } from '@lobehub/ui';
+import Link from 'next/link';
 import { memo } from 'react';
-import { useTranslation } from 'react-i18next';
+import { Trans } from 'react-i18next';
 import { Flexbox } from 'react-layout-kit';
 
 import { MAX_WIDTH } from '@/const/layoutTokens';
+import { WEBRTC_SYNC_DOCUMENTS } from '@/const/url';
 import { useUserStore } from '@/store/user';
 import { preferenceSelectors } from '@/store/user/selectors';
 
@@ -13,7 +15,6 @@ interface ExperimentAlertProps {
   mobile?: boolean;
 }
 const ExperimentAlert = memo<ExperimentAlertProps>(({ mobile }) => {
-  const { t } = useTranslation('setting');
   const [hideSyncAlert, updatePreference] = useUserStore((s) => [
     preferenceSelectors.hideSyncAlert(s),
     s.updatePreference,
@@ -25,7 +26,20 @@ const ExperimentAlert = memo<ExperimentAlertProps>(({ mobile }) => {
         <Alert
           banner={mobile}
           closable
-          message={t('sync.warning.message')}
+          message={
+            <Trans i18nKey="sync.warning.tip" ns={'setting'}>
+              经过较长一段时间测试，WebRTC 同步可能无法稳定满足通用的数据同步诉求。请自行
+              <Link
+                aria-label={'Webrtc Sync deployment'}
+                href={WEBRTC_SYNC_DOCUMENTS}
+                style={{ color: 'inherit', textDecoration: 'underline' }}
+                target="_blank"
+              >
+                部署信令服务器
+              </Link>
+              后使用。
+            </Trans>
+          }
           onClose={() => {
             updatePreference({ hideSyncAlert: true });
           }}

package/src/app/(main)/settings/sync/features/WebRTC/index.tsx

@@ -25,9 +25,16 @@ const WebRTC = memo(() => {
   useSyncSettings(form);
 
   const channelName = AntForm.useWatch(['sync', 'webrtc', 'channelName'], form);
+  const signaling = AntForm.useWatch(['sync', 'webrtc', 'signaling'], form);
 
   const config: SettingItemGroup = {
     children: [
+      {
+        children: <Input placeholder={t('sync.webrtc.signaling.placeholder')} />,
+        desc: t('sync.webrtc.signaling.desc'),
+        label: t('sync.webrtc.signaling.title'),
+        name: ['sync', 'webrtc', 'signaling'],
+      },
       {
         children: <ChannelNameInput form={form} />,
         desc: t('sync.webrtc.channelName.desc'),
@@ -46,14 +53,14 @@ const WebRTC = memo(() => {
         name: ['sync', 'webrtc', 'channelPassword'],
       },
       {
-        children: !channelName ? (
-          <Tooltip title={t('sync.webrtc.enabled.invalid')}>
-            <Switch disabled />
-          </Tooltip>
-        ) : (
-          <Switch />
-          // <SyncSwitch />
-        ),
+        children:
+          !channelName || !signaling ? (
+            <Tooltip title={t('sync.webrtc.enabled.invalid')}>
+              <Switch disabled />
+            </Tooltip>
+          ) : (
+            <Switch />
+          ),
 
         label: t('sync.webrtc.enabled.title'),
         minWidth: undefined,

package/src/config/modelProviders/index.ts

@@ -70,6 +70,11 @@ export const filterEnabledModels = (provider: ModelProviderCard) => {
   return provider.chatModels.filter((v) => v.enabled).map((m) => m.id);
 };
 
+export const isProviderDisableBroswerRequest = (id: string) => {
+  const provider = DEFAULT_MODEL_PROVIDER_LIST.find((v) => v.id === id && v.disableBrowserRequest);
+  return !!provider;
+};
+
 export { default as AnthropicProviderCard } from './anthropic';
 export { default as AzureProviderCard } from './azure';
 export { default as BaichuanProviderCard } from './baichuan';

package/src/config/modelProviders/qwen.ts

@@ -18,14 +18,16 @@ const Qwen: ModelProviderCard = {
       tokens: 32_000,
     },
     {
-      description: '通义千问千亿级别超大规模语言模型，支持中文、英文等不同语言输入，当前通义千问2.5产品版本背后的API模型',
+      description:
+        '通义千问千亿级别超大规模语言模型，支持中文、英文等不同语言输入，当前通义千问2.5产品版本背后的API模型',
       displayName: 'Qwen Max',
       enabled: true,
       id: 'qwen-max',
       tokens: 8000,
     },
     {
-      description: '通义千问千亿级别超大规模语言模型，支持中文、英文等不同语言输入，扩展了上下文窗口',
+      description:
+        '通义千问千亿级别超大规模语言模型，支持中文、英文等不同语言输入，扩展了上下文窗口',
       displayName: 'Qwen Max LongContext',
       id: 'qwen-max-longcontext',
       tokens: 30_000,
@@ -50,6 +52,7 @@ const Qwen: ModelProviderCard = {
     },
   ],
   checkModel: 'qwen-turbo',
+  disableBrowserRequest: true,
   id: 'qwen',
   modelList: { showModelFetcher: true },
   name: 'Qwen',

package/src/const/url.ts

@@ -21,6 +21,7 @@ export const DOCKER_IMAGE = 'https://hub.docker.com/r/lobehub/lobe-chat';
 export const DOCUMENTS = urlJoin(OFFICIAL_SITE, '/docs');
 export const USAGE_DOCUMENTS = urlJoin(DOCUMENTS, '/usage');
 export const SELF_HOSTING_DOCUMENTS = urlJoin(DOCUMENTS, '/self-hosting');
+export const WEBRTC_SYNC_DOCUMENTS = urlJoin(SELF_HOSTING_DOCUMENTS, '/advanced/webrtc');
 
 export const WIKI = urlJoin(GITHUB, 'wiki');
 export const WIKI_PLUGIN_GUIDE = urlJoin(USAGE_DOCUMENTS, '/plugins/development');

package/src/database/client/core/sync.ts

@@ -48,14 +48,7 @@ class DataSync {
   };
 
   connect = async (params: StartDataSyncParams) => {
-    const {
-      channel,
-      onSyncEvent,
-      onSyncStatusChange,
-      user,
-      onAwarenessChange,
-      signaling = 'wss://y-webrtc-signaling.lobehub.com',
-    } = params;
+    const { channel, onSyncEvent, onSyncStatusChange, user, onAwarenessChange, signaling } = params;
     // ====== 1. init yjs doc ====== //
 
     await this.initYDoc();

package/src/locales/default/setting.ts

@@ -348,7 +348,7 @@ export default {
       unknownOS: '未知系统',
     },
     warning: {
-      message: '本功能目前仍为实验性功能，可能存在预期外或不稳定的情况，如遇到问题请及时提交反馈。',
+      tip: '经过较长一段时间社区公测，WebRTC 同步可能无法稳定满足通用的数据同步诉求。请自行 <1>部署信令服务器</1> 后使用。',
     },
     webrtc: {
       channelName: {
@@ -364,10 +364,14 @@ export default {
       },
       desc: '实时、点对点的数据通信，需设备同时在线才可同步',
       enabled: {
-        invalid: '请填写同步频道名称后再开启',
-        // desc: 'WebRTC 将使用此名创建同步频道，确保频道名称唯一',
+        invalid: '请填写信令服务器和同步频道名称后再开启',
         title: '开启同步',
       },
+      signaling: {
+        desc: 'WebRTC 将使用该地址进行同步',
+        placeholder: '请输入信令服务器地址',
+        title: '信令服务器',
+      },
       title: 'WebRTC 同步',
     },
   },

package/src/store/user/slices/modelList/selectors/modelConfig.test.ts

@@ -109,6 +109,25 @@ describe('modelConfigSelectors', () => {
       } as UserSettingsState) as unknown as UserStore;
       expect(modelConfigSelectors.isProviderFetchOnClient('azure')(s)).toBe(true);
     });
+
+    // Qwen provider not work in broswer request. Please skip this case if it work in future.
+    // Issue: https://github.com/lobehub/lobe-chat/issues/3108
+    // PR: https://github.com/lobehub/lobe-chat/pull/3133
+    it('client fecth should be disabled if provider is disable broswer request', () => {
+      const s = merge(initialSettingsState, {
+        settings: {
+          languageModel: {
+            qwen: { fetchOnClient: true },
+          },
+          keyVaults: {
+            qwen: {
+              apiKey: 'apikey',
+            },
+          },
+        },
+      } as UserSettingsState) as unknown as UserStore;
+      expect(modelConfigSelectors.isAutoFetchModelsEnabled('qwen')(s)).toBe(false);
+    });
   });
 
   describe('getCustomModelCardById', () => {

package/src/store/user/slices/modelList/selectors/modelConfig.ts

@@ -1,3 +1,4 @@
+import { isProviderDisableBroswerRequest } from '@/config/modelProviders';
 import { UserStore } from '@/store/user';
 import { GlobalLLMProviderKey } from '@/types/user/settings';
 
@@ -18,6 +19,9 @@ const providerWhitelist = new Set(['ollama']);
 const isProviderFetchOnClient = (provider: GlobalLLMProviderKey | string) => (s: UserStore) => {
   const config = getProviderConfigById(provider)(s);
 
+  // If the provider already disable broswer request in model config, force on Server.
+  if (isProviderDisableBroswerRequest(provider)) return false;
+
   // If the provider in the whitelist, follow the user settings
   if (providerWhitelist.has(provider) && typeof config?.fetchOnClient !== 'undefined')
     return config?.fetchOnClient;

package/src/store/user/slices/sync/action.ts

@@ -46,7 +46,7 @@ export const createSyncSlice: StateCreator<
     // double-check the sync ability
     // if there is no channelName, don't start sync
     const sync = syncSettingsSelectors.webrtcConfig(get());
-    if (!sync.channelName) return false;
+    if (!sync.channelName || !sync.signaling) return false;
 
     const name = syncSettingsSelectors.deviceName(get());
 

package/src/types/sync.ts

@@ -23,7 +23,7 @@ export interface StartDataSyncParams {
   onAwarenessChange: OnAwarenessChange;
   onSyncEvent: OnSyncEvent;
   onSyncStatusChange: OnSyncStatusChange;
-  signaling?: string;
+  signaling: string;
   user: SyncUserInfo;
 }