https://bugs.kde.org/show_bug.cgi?id=386200
--- Comment #10 from PhobosK <phob...@fastmail.fm> --- (In reply to Ivan Čukić from comment #8) > The reason this is not in the UI is that I don't find the use-case of > syncing with other computers via a public cloud service a particularly > secure practice. > > I'm open to being convinced otherwise. Well my purpose will not be to convince you in something ;) It's your application and so your decision how to do the things :) But in my case I have a couple of Vaults in other places in my home folder... They are created either by directly using the cli of encfs or by other applications like cryptkeeper, kencfs-plasma etc.... I want them to be listed and accessible in one interface though - preferably a KDE app and I want them to stay where they are (not to be moved to some hidden folder)... Sadly kencfs has problems, so I was happy when I first saw Vault. But next the lack of adding already existing vaults was a turn off.. So having Vaults in other places locally is a valid use case IMHO... Even if that place is not local but a cloud... no matter of the security implications.. it should be a valid case too... 'cause I think one of the most important reasons users still stay in KDE is the vast options of configuration of almost all things in it... as opposed to GNOME.. where it's more like a disaster when trying to configure something ... > > The feature exists for more tech savvy users that are willing to dig a bit > into it. One thing that I plan to do is to collect all these things in the > Vault docs on the userbase (when I create the Vault docs on the userbase). If you ask me KDE is all about tech savvy users :) But this dbus call... well it is too tech savvy.. People either have to go through the code carefully, or have to see this bug report where you mention the dbus call ;) or of course go through all the dbus interface of kded5.. Anyway as @Nate Graham said.. why do something so functional that would stay deeply hidden ;) Sorry for the long post... It has nothing to do with bug reporting I know... but couldn't help expressing my opinion... -- You are receiving this mail because: You are watching all bug changes.
