I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)
on
Which general topic do you have
Hello,
I noticed that when you register several remote devices and authorize the same app on each of them, like DavX5, there will be several entries in the list of authorized devices that look and read all the same, which will make it nearly impossible to delete a specific device later.
Therefore I suggest that more data is used to identify an authorized device, like the smartphone model type, its serial number, or any data that can help to tell one device from another later in the list of devices.
If this feature request is not in the right place, I kindly ask the admin(s) to move it to a more appropriate place. Thank you!
Unless you define the app passwords yourself (and then you can rename it as you wish), it is the app setting up the connection. So it would be within their repositories to ask for more specific information.
Browsers and some other software might not want to leak to much too specific information, so they use a minimum per default. And asking a user when setting up, might be a bit disturbing for less experienced users or those who don’t need it.
I had the problem in the past with one machine, and I just renamed the app names (you see when they were active the last time, so I triggered some action and went to the top of the list).
I understand your points there. But on the other hand: as I said, it can become very difficult to keep track of all the authorised devices in the list.
When you do it the way you’re describing, it’s easy to label a device. But I think the majority of authorising procedures go like this: you enter the url in an app, the app connects to NC, your browser opens and NC asks, if that device is to be authorised.
At that point there is no possibility to set a customised label. Maybe that could be changed, so users can opt to enter their own identifier at that situation?