failed to request key for a changed SL-name also not possible to add that key with new username to the database.

[freddii]

It's now possible in SL to change your Firstname and Lastname while keeping the UUID.
But the w-hat database is not able to give out the UUID when requesting with a changed username.

[pclewis]

Can you provide some example names/UUIDs?

We will probably need a volunteer to create and maintain something in-world to handle this reliably.

[freddii]

Jade Alpaca 588cbc30-29c5-4eb3-a7fe-b216be687a38
Aesu Alpha 782fa852-4d9f-4505-bedf-916984ba804a
Montana Banana 507dc24a-ff87-4b5f-8db6-f0e21b95df0e
Olivia Bellisserian 8db60bd3-0df1-421b-afc2-48624e584a63
Axis Cloud ec0386a6-fe03-4579-98b6-c3487356a7d2
Gloom Cloud 8941e661-80f5-40dd-8003-b14af23a4eda
Nimbus Cloud 983ac6a4-ced2-42af-bb3f-136ff6419d22
Riya Cloud b713e3c5-9e6f-4d21-abdb-2935c1cb37d0
Sound Cloud 62fc5816-3d11-4d3b-9f24-0646dfb950e3
Strife Cloud 0cc8392f-3c43-40a0-8887-0b51bb91800e
Titus Cloud 66ca3882-2acc-4c7d-965e-284395f6ad82
Winter Cloud 44dfefe8-ff4e-4134-adc2-efb28ed747a0

[freddii]

everyone with a lastname from this list: https://twitter.com/SecondLife/status/1249799210108686339

Alpaca
Alpha
Atheria
Banana
Bellisserian
Cloud
Conundrum
Covfefe
Crisp
Dallas
Damballar
Dismantled
Doge
Enchantment
Float
Heartsong
Hexem
Hijinks
Huntsman
Ichibara
Jazzhands
Kiyori
Leeder
Lemongrass
Littlepaws
Mainsail
Melodious
Mercury
Mysterious
Nimble
Nova
Pancake
Peppermint
Piggins
Plumday
Puddles
Ravenhurst
Rowley
Rumrunner
Salty
Takeda
Timmerman
Vanilla
Voxel
Whimsy
Wumpkins
Yeetly

[fly-man-]

What @freddii means is that people now can change their name in Secondlife which when they are seen by any of the inworld objects that communicate with W-Hat services is that they are being discarded because there's already a name connected with that UUID.

For example:

UUID: 507dc24a-ff87-4b5f-8db6-f0e21b95df0e
Previous name: T0n1m0ntana Resident
Current name: Montana Banana

When querying SL search, it will return the new name but the old name should also be "stored" as historical. Currently there's no way to do that without breaking.

• A possible solution would be when a key comes back with a new name then previously stored have a pointer to both the old and the new name.

[pclewis]

We already update the key2name mapping to the new name and add a new name2key mapping when we become aware of a name change. (see #3)

The problem is we have no way to become aware of those changes right now. We are receiving new names and keys faster than we can query them. Our recent downtime was essentially caused by all of our queues overflowing.

The best fix for this would be to have an in-world script using the proper APIs that anyone can run to help share the load, but we do not have anyone that can create this. I personally am banned from SL forever.