feat(client): dynamic name for dynamic keys

[murka]

FYI: Jigsaw-Code/outline-server#1561

[murka]

So, initial idea it was fetch and store keys name before connecting, but I have another idea, what about if hash-name is will be primary name, and we will take dynamic-key-name by fetch for each of session?

[murka]

wdyt: @fortuna @daniellacosse @sbruens @jyyi1

[fortuna]

Danil, could you please clarify what's the value of this feature? What is it that you are trying to accomplish, and why does the existing hash doesn't work for you?

…

On Mon, Sep 2, 2024 at 3:46 PM Danil Shaymurzin ⚡️ ***@***.***> wrote: wdyt: @fortuna <https://github.com/fortuna> @daniellacosse <https://github.com/daniellacosse> @sbruens <https://github.com/sbruens> @jyyi1 <https://github.com/jyyi1> — Reply to this email directly, view it on GitHub <#2195 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3XHLRCKEXY5ZIVFKECL3ZUS6ADAVCNFSM6AAAAABNQ2AUXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRVGI2DIMZSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[murka]

So, the existing hash system is not dynamic for key names, I gonna use this feature for information user, for example:

1. Quota in GB
2. Subscription info

The current hash system is not working for this use cases.

[fortuna]

I see. So the feature you really need is a way to communicate quota usage! Or perhaps a generic message.
I think it would be better to have a focused feature rather than hack the name. Changing the name of an existing service can be very confusing! Let's discuss in the issue.