Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: we will REQUIRE full disk access or implement a 2nd manual upload workflow #21

Closed
alexdanilowicz opened this issue Nov 29, 2020 · 2 comments

Comments

@alexdanilowicz
Copy link
Collaborator

PROS:

  • if we require full disk access, then we only have to worry about 1 technical implementation, i.e., what we currently have. (copying dbs to the Left on Read application folder.)
  • no need for user to mess around in Library applications
  • no need for user to read instructions
  • super fast (less than 1 second on my machine). It copies, creates the tables, and queries. It would be fast if user dragged to Desktop as well... but would be "slower" in the sense that the user would have to step through a lot of prerequisites to get it working

CONS:

  • the user may not trust us, and may exit the app, because there is no manual alternative

@Teddarific thoughts? @ayc19 and I have been discussing this and Alex wants your thoughts

@alexdanilowicz alexdanilowicz changed the title Discussion: we will REQUIRE full disk access or implement for a second workflow Discussion: we will REQUIRE full disk access or implement a 2nd manual upload workflow Nov 29, 2020
@alexdanilowicz alexdanilowicz added the question Further information is requested label Nov 29, 2020
@alexdanilowicz
Copy link
Collaborator Author

alexdanilowicz commented Nov 29, 2020

Actually, Alex and I just talked about this and we think we should NOT force the user to require it. Technically, would be very easy: just tell user to manually drag the Address Book folder and Chat.db to the Desktop, and we pass in different paths to existing functions. (Ofc edge cases would be a pain, i.e., if user moved wrong files), but the backend logic is resuable for either workflow.

@alexdanilowicz
Copy link
Collaborator Author

Closing this out per the above: we should NOT force the user to require it.

@alexdanilowicz alexdanilowicz added discussion and removed question Further information is requested labels Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant