-
Notifications
You must be signed in to change notification settings - Fork 129
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
Suggestion: Authorisation List should show names (as well as uuids) #877
Comments
Joy wants to be able to use names in the settings notecard instead of UUIDs. Can someone please comment on whether this is doable and if not, why not? I'm thinking it's not doable but i can't say why. |
Perhaps I should clarify.
I see two, connected, problems.
1 Access / Access List gobledegook (URLS?? I think though I don't know
what /about is about)
2 Settings NC only has the uuid, and speaking for myself, I dont have uuids
memorised so its not obvious who is in the NC.
Re #1 Access / Access List gives this result (in FS 68380, Collar is Raven
Collar BDSM v 3.0; OC v8.2.3)
https://gyazo.com/c12ed006109e528b5e725ccb21841090
Re #2 To make the NC self-documenting, would it not be possible to include
a name or nick-name or label (in similar fashion to bookmarks) eg:
Joy~93b28e2c-2b94-48b4-a916-4a286b62d94b
There would then be a choice which losting owners etc - use the tag, or use
display or legacy name, either of which is easily obtained.
I understand that using uuids as the operative item in settings is
unambiguous and permament (I gather legacy names are now ephemeral like
display names, thank you LL). But it should be possible to make things
intelligible to humans :)
Thank you ,
Joy
…On Mon, Feb 6, 2023 at 2:18 PM Silkie Sabra ***@***.***> wrote:
Joy wants to be able to use names in the settings notecard instead of
UUIDs. Can someone please comment on whether this is doable and if not, why
not? I'm thinking it's not doable but i can't say why.
—
Reply to this email directly, view it on GitHub
<#877 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APW6UF3ZJCEMAL2T4PHA6P3WWFFAVANCNFSM6AAAAAARKMX2JQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
your issue #1 is those are clickable links(URLS) in most viewers and they show up as the user name not that string, when clicked they bring up the profile, if your viewer does not have that feature you may wish to get the viewer dev team on board. issue #2 it is a doable change however it will be little more than cosmetic in use since a name can be spoofed but the key cannot. |
I don't see the usefulness of this outweighs the cost of doing it. |
Not sure what you mean by cost. The usefulness is that the uuids mean
nothing to me (well I can almost recognise my own) so I have to paste the
uuid somewhere to convert to name. Agree it may not be the highest
priority.
…On Sun, Aug 6, 2023 at 2:15 PM Silkie Sabra ***@***.***> wrote:
I don't see the usefulness of this outweighs the cost of doing it.
—
Reply to this email directly, view it on GitHub
<#877 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APW6UF5J7PFWTBHEEMOSX23XT7NKLANCNFSM6AAAAAARKMX2JQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You can use comments after # to help remember which names the uuids belong to |
What version of OpenCollar are you using? 8.2.1 / 8.2.2
What behavior did you expect? n/a
What behavior did you see instead? n/a
What steps does someone need to take to reproduce the problem? n/a
Maybe a little messy to implement (agents not in sim etc). Various options
The text was updated successfully, but these errors were encountered: