![]() The other is that I see lots of empty directories named like images (e.g. One is off-topic here (re: multi-shot “images”, whatever happens with edits in Google Photos that it says are undoable, etc.) so I’ll write up another post asking about it. I set the phone’s config for this share to “send only” and that of the NAS to “receive only.” 29 GB transferred, and maybe I have a good copy of my images and videos on which for PhotoStructure to feast when I install it. Of relevance to this forum: Moving toward my hopes of trying out PhotoStructure, and wanting a copy of images on my phone that are not cycled through Google Takeout, not tied up in whatever Synology Moments does with them server-side, and not requiring me to fix whatever is going on with my Perkeep installation, I pointed Syncthing on the phone at at /storage/emulated/0/DCIM and shared it with Syncthing on the NAS. I don’t know if I got this right and have mild concern about a sort of hall-of-mirrors syncing among the various machines, but it seems to be working. I moved my Keepass database out of SpiderOak (which I never got working on Android) and Keybase FS (an old copy of the Keepass DB, to sometimes awkwardly retrieve on the phone), and started syncing it around to Linux, Mac OS, Android, and Chrome OS. ![]() With my phone’s storage rapidly approaching full, and my concern about what happens if and when I let Google Photos delete images from the phone that “are backed up” to the app’s default and opaque off-site storage facility, I gave up on that and let Syncthing do its NAT-busting, connection-finding, no-screentapping-qrcode-scanning magic. I’d been trying halfheartedly for a while to get it working over Tailscale from various devices to my NAS. If you’d rather maintain a single copy of your photos and videos, you can either opt out of automatic library organization, or you can periodically archive your Resilio backup directory (take care to not delete the files that the app uses to maintain sync state, and realize you shouldn’t archive files on dest that still exist on src, as the sync app will re-transfer everything you just archived). With respect to how I suggest people set up files, it’s up to you: I personally like to have my photos in one directory hierarchy, so I use automatic organization, but I’ve retained all my Resilio archives separately, as well (disk is cheap). If you’re using Resilio Sync, you want “Read Only-Full Sync” and “Store deleted files in folder archive” on the server folder (which should be set by default). If you’re using SyncThing, you want “send only” mode. ![]() You want the second option, so if your phone decides to “smart delete” photos that were backed up somewhere else, the backup on your NAS doesn’t synchronize those deletions. “send only” mode, where deletes on the source device are ignored. “mirror” mode, where deletes on the source device are reflected on the destination device Resilio and SyncThing both support different modes: ![]() This seems to present two problems for the upload-from-phone-to-PhotoStructure use case: 1) Changes made on the secondary device would be replicated to the phone, potentially breaking native photo apps by violating assumptions they make about naming, tagging, or organization of images, and 2) images deleted from the phone (as one often does as storage on the phone runs short) would be deleted on the secondary storage, resulting in permanent loss of images that one expected to be safely archived off-phone.ĭid you intend to suggest an alternative to uploading images from one’s phone to one’s PhotoStructure library, and for that to be a multi-step process involving 1) continuously synchronizing the images on a phone to a secondary data store on another device, and 2) arranging for PhotoStore to periodically check for new images on the secondary store, and when found, copy them to a third, PhotoStore-specific, data store? “Upload” implies a one-way transfer, generally from a smaller to larger device, which is a very different operation that synchronization. The three options presented on the page you referenced, Resilio Sync, SyncThing, and PhotoSync, appear not to simply upload images, but to synchronize multiple sets of files, such as those on one’s phone and those on another storage device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |