Bug 410360 - Add a "soft upair" (disconnect) option to the interface and put a warning on the permanent unpair action.
Summary: Add a "soft upair" (disconnect) option to the interface and put a warning on ...
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.4
Platform: Kubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-29 15:58 UTC by leftcrane
Modified: 2021-08-04 17:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leftcrane 2019-07-29 15:58:27 UTC
I would strongly suggest adding an "soft unpair" feature, one that merely disconnects but saves all the permissions: 

1. This would allow users to quickly unbork the app, which is important given the high failure rate of pairing. (see Bug #410316 for an illustration of just how insidious this problem is, even in the context of just one network) Unpairing usually fixes the problem - ofc the problem shouldn't exist but having some solution is better than nothing.

2. Furthermore, the current  "unpair" button is just dangerous, since users are given no warning that if they tap it all their app permissions and settings will be lost. Many users will attempt to tap it in the hopes of re-establishing the connection - I know I did and was surprised when I had to re-enable all the permissions and settings (at least 20 taps, quite tedious)


So there should be a quick toggle to disconnect and re-connect and an additional option to "unpair permanently" (the same thing as current unpair). The first option should keep all the settings in place so that the connection can be quickly resumed. The second option should warn users that they are going to lose all their settings by proceeding.
Comment 1 René 2021-08-04 17:16:44 UTC
I don't want to change the title but propose you don't call it "soft unpair". I think disconnect is sufficient. 

I agree that this feature is needed but for other reasons. What about the use of kdeconnect in a small office or household?: 

1. members want to quickly share among them a file without setting up a network share. 
2. members don't want to be permanently connected to avoid clipboard paste conflicts
3. privacy issues in Android

Concept of clipboard paste conflict can be described as follows. User A and B are paired and share the clipboard. Both are editing a document and do a lot of corrections using copy/cut and paste. User A copies a text and without knowing user B does the same right after. Then user A pastes not his own copy but that of user B and is confused.   

The privacy issue in Android I discovered while using the virtual keyboard. Just above the virtual keyboard there is an area that shows a button of recently cut/copies text from the clipbaord that allows you to paste it by tapping it. It shows a fragment of the text and it was constantly changing while I was answering a chat message. I discovered they were not the usual suggestions while you enter your text but it was copied text of  my wife while she was editing on her paired device 

In this aspect I think that kdeconnect counts too much on individual use and it does not on use in households or small office teams. There should at least be an easy disconnect option and auto-connect should be optional per device. That way you can minimally distinguish between your own devices and that of others and maintain some respect and privacy. 

Like @leftcrane explains, unpair is too drastic and something like (manual) connect and disconnect would be desirable.