lobe-chat
lobe-chat copied to clipboard
lobehub
[Request]
🥰 需求描述 | Feature Description
需求场景：自己搭建给家人同事或者朋友使用，但是很难保证他们会不会分享给别人使用或者是泄露之类的，这样的话又得从头折腾重新配置，希望在key或者密码上自定义选项能够多一点
🧐 解决方案 | Proposed Solution
需求1：希望有关闭使用自定义key的选项，然后可以支持多个key对应不同密码，用户端输入哪个密码对应使用哪个key，然后自己用自己的，哪怕被泄露了把对应key删除掉就可以了，不影响自己使用。
需求2：或者是希望可以有个把自定义key的代理地址固定的选项，锁死成自己预设的地址，只允许输入key，以免泄露出去给别人用别的自定义key和地址，要不纯纯自己搭建给别人做公益。个人觉得第二个需求比较好实现并且比较好规避这个问题。
📝 补充信息 | Additional Information
No response
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
🥰 Requirement Description | Feature Description
Demand scenario: Build it yourself for family, colleagues or friends to use, but it is difficult to guarantee whether they will share it with others or leak it. In this case, you will have to reconfigure it from scratch. I hope you can customize the key or password options. more
🧐 Solution | Proposed Solution
Requirement 1: I hope there is an option to turn off the use of custom keys, and then support multiple keys corresponding to different passwords. Which password the user enters corresponds to which key is used, and then use your own, even if it is leaked, just delete the corresponding key. It doesn't affect your own use.
Requirement 2: Or I hope there is an option to fix the proxy address of the custom key, lock it to your own default address, and only allow the key to be entered to avoid leaking it to others and using other custom keys and addresses, or else Purely build it yourself to do charity for others. Personally, I feel that the second requirement is easier to implement and easier to avoid this problem.
📝 Additional Information |
No response
👀 @1355873789
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。
✅ @1355873789
This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。
:tada: This issue has been resolved in version 0.150.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket: