Jump to content

WonderPass

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

4 Neutral

About WonderPass

  • Rank
    Member
  1. So much to unpack here. Yes I did research this hence I know how it works. Dropbox being big and successful does not make them right in all of their decisions. If you’ve worked for a large company some of the worst design decisions are dressed as a feature because it’s easier than fixing the underlying issue The poor architecture is the failure to anticipate that whilst locking down access of the app it then precludes interaction with those files with other users. You may consider my position arrogant but the fact that Enpass is supposed to allow shared vaults would indicate that this architecture doesn’t fit actual use cases. That the solution is to create this hyper restricted folder indicates that the all or nothing OAUTH model is on reflection a poor design. But frankly my opinion is unimportant as I have deleted Enpass.
  2. There’s a misunderstanding here. You both need to have the same service eg Dropbox but you only need one each. Enpass would require you have one each plus another account (that you both know the username and password for) in which you put the shared vault. That is to say THREE accounts between you.
  3. Unfortunately SafeInCloud does not have shared vault support and it sticks its data files in Dropbox/App folder, the one with the most restrictive (i.e. none) share settings.
  4. Well you promised this would be fixed before 31 Jan and here we are 1 Feb, still busted. WebDAV for Box is now passed its EOL date. I have such malevolent feelings towards this product and how the development team has behaved.
  5. Lucky you! If only I could get back to v5 so I could start an orderly migration away from this mess.
  6. 1Password does not force the Vault into the App folder, so you then able to share the individual file with other users without needing a redundant third file store. Dropbox in their wisdom have locked down the App folder to be unshareable - which suggests an underlying flaw in their architecture that they have had to do that.
  7. Congrats on working out a solution that works for your setup. A multiple step self rolled file store to replace a simple commercially available log in isn’t a great alternative for, and is beyond the capability / interest level of, the average user. I don’t buy a car so I can tinker with it, I don’t pay for features so I can then build a bespoke platform to deliver them. I’m sure there will be some people who will be happy to go this route it’s not really a workable alternative for the majority.
  8. Congrats on working out a solution that works for your setup. A multiple step self rolled file store to replace a simple commercially available log in isn’t a great alternative for, and is beyond the capability / interest level of, the average user. I don’t buy a car so I can tinker with it, I don’t pay for features so I can then build a bespoke platform to deliver them. I’m sure there will be some people who will be happy to go this route it’s not really a workable alternative for the majority.
  9. I’m done with you clowns. You deleted functionality that users weee dependent on. Remove a working and realistic method of multiple vaults and instead expect users to set up redundant cloud sharing accounts. How about instead of window dressing bug fixes you restore functionality for the people that you cut off from their vaults. 28 days and I now have 6 divergent vaults on Box and no means of effectively merging these in the event you ever restore the functionality that you robbed us of. Robbery being a fair description for taking money for features that you then scrapped without warning leaving users with orphaned data.
  10. Unfortunately doesn’t help iOS users. Can you advise if the vault still works (ie is structurally coherent)
  11. The restriction behind this is that they stupidly chose to use the most restrictive set of file permissions which prevents sharing of the file from the file sharing service
  12. A total failure and destructive. Box sync removed without warning. I now have six local vaults all fragmenting away from a common truth. allegedly will be replaced by 31st Jan. this is will result in 31 days of 6 vaults diverging. Completely destroying my data. Add to this the p—poor shared vault architecture and the whole thing is a fragmented disaster now. I hate 1Password but I’m going to have to go back to it. That is how bad this rollout has been for me.
  13. This architecture of one vault per cloud service and the insistence on using non shareable folders fails to take account of how actual users work in the real world and offloads complexity unnecessarily into the user instead of working out the appropriate application architecture to support actual use cases. Multiple vaults as implemented is not workable in the real world. As a user I refuse to setup another Dropbox account in order to share vaults with my family because Enpass has setup a deficient application architecture.
×
×
  • Create New...