Plugins is inherently incompatible with the security demands of a password manager. ![]() We find that encouraging users to install untested (and often quickly-abandoned) third-party Have never been (and probably never will be) fixed, and none of them are as thoroughly tested and reviewed as we test and reviewĬode that goes into our main application. Many KeePass2 plugins are barely maintained (if at all), some have known vulnerabilities that Need third-party plugins in KeePass2, so for most things you don't even need plugins, nor should you ever want them. KeePassXC already provides many of the features that Feel free to due none or all of course.No, KeePassXC does not support plugins at the moment and probably never will. My suggestion to you would be to create an issue here about improving Mega Performance (and reference this issue), ask the MegaAPIClient dev person if the Mega API allows for not retrieving all the metadata, and / or ask Mega to have the API allow for partial metadata retrieval. So, assuming the current implementation is correct, performance could be improved if the MegaAPIClient allows for not all metadata to be retrieved or the Mega API is changed to allow this. That seems to be an issue with the Mega API at the moment, per what the main dev said here or the implementation of the gpailler/MegaApiClient, which is being used to access Mega. ![]() The only quick fix to fix it at the moment is to create a new account just for the keepass db (but not the ideal case use) Its acceptable for me, b'cause when reopen a database, the app uses the local cache and works faster.īut my question is, Will this feature be optimized in the future? about 60~80 seconds for the first database open and another 60~70 seconds on a database save. I have about ~90 GB of files on my Mega storage and can report that the performance of the keepass2droid app to be quite slow on that account. Im testing the 1.09d-r0 release, specifically the Mega integration feature. Hello everyone, congrats for the app, its amazing. Mega (unlike Drive, pCloud and others) has Camera Upload like Dropbox, which automatically uploads photos and videos from the phone and rename them to YYYY-mm-DD HH-MM-SS.Mega user interface is more user-friendly than Dropbox.Mega offers a reasonably sized small plan of 400GB.Mega free plan is 20GB (was 50GB when I opened my account).Dropbox is suffering from several bugs (the desktop app is randomly silently crashing, the team accounts gets randomly silently disconnected).Dropbox user interface is ugly and clunky. ![]() Dropbox free plan has recently introduced a limit of 3 connected devices.Dropbox does not offer a plan smaller than 2TB.Reasons why I migrated from Dropbox to Mega. Changes on the phone are synchronized instantly to the computer. The only downside of using this approach is that the minimum synchronization interval is 5 minutes, so to get the changes made on the computer synchronized to the phone I either need to wait that time or trigger a manual synchronization, which is not that big of a deal after all. Same here: I make a change from the computer, wait until the file is uploaded to Mega, open Keepass2Android, I see Source file and cache are synchronized, once I enter the database I cannot see the change made from the computer.Īs temporary workaround I rolled back to the Google Play version, used Autosync for MEGA - MegaSync (thank you to keep a local database on my phone in sync with the one on Mega and then open my database from Keepass2Android with System file picker. ![]() I am using 1.09d-r0, and I have sync issue with mega.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |