Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] 打开 https://app.nextchat.dev/ 官方网址, 填入 url/key, 无脑使用就行吧? #5917

Closed
LeoLeeTech opened this issue Dec 10, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@LeoLeeTech
Copy link

🥰 需求描述

打开 https://app.nextchat.dev/ 官方网址, 填入 url/key使用就行吧?

我记得以前看过 url/key只存储在浏览器端, 不需要考虑密码之类的

我是客户端的老用户, 这次准备给别人推荐一下, 想让对方直接访问/体验

🧐 解决方案

麻烦了

📝 补充信息

No response

@LeoLeeTech LeoLeeTech added the enhancement New feature or request label Dec 10, 2024
@Issues-translate-bot
Copy link

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


Title: [Feature Request] Open the official website https://app.nextchat.dev/, fill in the url/key, just use it without thinking, right?

🥰 Description of requirements

Open the official website https://app.nextchat.dev/, fill in the url/key and use it, right?

I remember seeing before that url/key is only stored on the browser side, and there is no need to consider passwords and the like.

I am an old user of the client. This time I am going to recommend it to others. I want them to have direct access/experience.

🧐 Solution

Trouble

📝 Supplementary information

No response

@Dogtiti
Copy link
Member

Dogtiti commented Dec 10, 2024

不推荐这样,有泄露key的风险
推荐自己部署然后开启访问码即可

@Issues-translate-bot
Copy link

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


This is not recommended as there is a risk of leaking the key.
It is recommended to deploy it yourself and then enable the access code.

@LeoLeeTech
Copy link
Author

不推荐这样,有泄露key的风险 推荐自己部署然后开启访问码即可

感谢
不过我想问一下, 目前知道的会怎么泄露呢?

  1. 钓鱼网站, 读取本地的 session/key
  2. 网络抓包

@Issues-translate-bot
Copy link

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


This is not recommended as there is a risk of leaking the key. It is recommended to deploy it yourself and then enable the access code.

grateful
But I want to ask, how will what is known so far be leaked?

  1. Phishing website, read local session/key
  2. Network packet capture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants