https://bugs.kde.org/show_bug.cgi?id=498778
Bug ID: 498778
Summary: New, more-strict device ID requirements exclude
current GSConnect IDs
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: ferd...@gmail.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
A few days ago, @albertvaca changed[1] the KDE Connect protocol specification
for device ID format, with the message:
~~~~~~~~
Enforce ID format
All implementations have been using UUIDs as device IDs for a while, so we can
start validating and enforcing this format.
~~~~~~~~
The new format is expected to match this RegEx: /^[a-zA-Z0-9_]{32,38}$/
While GSConnect HAS been using UUIDs as device ID for some time now, we've been
using *real* UUIDs, with hyphens instead of underscores.
In the interest of not forcing all of our users to have to regenerate their
device IDs (and then re-pair all of their devices, and re-apply preferences),
would it be possible for the format to be expanded so that it also accepts
hyphen-separated UUID strings?
See also:
https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1910
[1]:
https://invent.kde.org/network/kdeconnect-meta/-/commit/e4f93eecb876dccf1f35e6db4944d536a8b9bc53
--
You are receiving this mail because:
You are watching all bug changes.
