Frank Dana

@penguin-teal Sorry to pester you, but a gentle ping on this? It should solve the visual twitchiness described in #28, which was actually being caused by the wacky `:hover` styles...

@daniellandau We should also discuss changing the spec with upstream -- naming a device "Someone's Something" is INCREDIBLY common, and it seems excessively restrictive to disallow that.

https://invent.kde.org/network/kdeconnect-meta/-/issues/27 As I said there, as far as I'm concerned if someone wants to name their device "🌞Sunshine phone!🌞" that should be OK. What do we care? It's _their_ name.

@Flameancer > Appears that an update has affected the use of special characters. That's correct, it's mostly down to KDE Connect tightening their protocol definition for what's permissible to use...

> I think this should be handled in [ba00824](https://github.com/GSConnect/gnome-shell-extension-gsconnect/commit/ba0082475202655c6ac2a2b46e5078f65dccb3be) Seems to be.  (That's a composite, really the input popup would close before the modal dialog appeared.) The only case...

I also see that in the Android app, validation happens interactively while setting the name. You can't even _type_ an invalid character into the name field — it just ignores...

> I'm not sure where the list of characters came from, I believe it was inspired by some Apple restriction, possibly the one pictured in the [merge request](https://invent.kde.org/network/kdeconnect-meta/-/merge_requests/5): I may...

> > So if a new invalid ID is entered in place of an old invalid ID, the ID will still be the old invalid ID after rejection. > >...

@andyholmes Huh... you're right, sorry. I had it in my head that all of `_migrateConfiguration()` itself was only run conditionally, but I now see that's not the case. I'm not...

Yeahnope. Even after logging out and back in...  `¯\_(ツ)_/¯`