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

Re-evaluating sync workflow: remove org-mobile-push/pull? #296

Open
webframp opened this issue Jul 13, 2024 · 1 comment
Open

Re-evaluating sync workflow: remove org-mobile-push/pull? #296

webframp opened this issue Jul 13, 2024 · 1 comment

Comments

@webframp
Copy link
Member

I've had questions about this from the org mode maintainers a few times and I'm curious to hear what others think.

I'm sure most know this but org-mobile-push/org-mobile-pull are from the early days of syncing with MobileOrg with only webdav support. They depend on having unique UUIDs for each heading and will update your files accordingly as needed.

The more modern approach is generally to keep your org files in a cloud provider folder like iCloud or Dropbox, or to use a git repo and synchronize via git.

Is it time to deprecate these two commands? What approach makes the most sense and what challenges do you see if they didn't exist or if the behavior was drastically changed?

@webframp webframp pinned this issue Jul 13, 2024
@gitonthescene
Copy link

Maybe worth considering simply uploading to Notes/Files and letting the user handle their own syncing from there. This puts a big burden on the user, though.

I think some form of syncing is vital though. My use case is likely similar to a lot of other users. We take quick notes with MobileOrg and later on organize them when we're on a desktop. But also, it becomes a quick reference for reviewing notes we took earlier and perhaps lost track of.

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

2 participants