Kang Lin

here. or email -- 发自我的网易邮箱手机智能版 在 2024-09-27 16:31:14，axt178178 ***@***.***> 写道： So where can I contact you? Kang Lin ***@***.***> 于2024年9月27日周五 08:30写道： > no telegram > > — > Reply to...

> I could consider the following joining features: > > * Remote wake-up > > * Control record > > * Camera preview and recording Try v0.0.28

@akallabeth Please refer to the following use cases： User case 1: Single user service: service.tld user: user password: password User case 2: Single user, More precise service service: service.tld:port user:...

> * The `service` is a namespace @akallabeth The `service` should comply with the URL scheme.

@akallabeth I think you are complicating this a bit.

> @KangLin please read: > > https://github.com/frankosterfeld/qtkeychain/blob/7668a63a3669400223c5a563928ae042f499dbf4/qtkeychain/keychain.h#L181 OK. It does not conflict with following the URL scheme. So that It should be explicitly determined by the user, rather than implicitly...

@akallabeth The `TestAppExample` is missing the `service` setting. So it caused your problem. The `service` can be configured by the user. Users can set the `service` according to the URL...

> > `TestAppExample` > > * wrong. It uses `keychain.example.project.app` > > * intended use is to have a unique `namespace` for your application to read/write/delete the secrets belonging to...

> @KangLin also, you can set anything as `service` and also as `key`. You need to create a unique identifier from that for your windows credential. you can not really...

> you can set your `namespace` however you want. like I already told you, just use an empty `key` and you're done. > > not getting your point at all,...