![]() It seems like they're willing to hurt anyone and destroy anything if it might grant them a little more money. If I misunderstood, and you were talking about the people hiding behind the companies and industries who are destroying the environment so that they can enrich themselves at everyone's expense then I'd guess that those folks are entirely self-aware and simply don't care that they act out of malice. The attitude of "here's a simple step that will cut down your individual carbon emissions, and also please pay attention to the primary sources of the problem"? Because that attitude doesn't seem defeatist or nihilistic at all? I don't think the "profits trump everything" comment was an endorsement of that philosophy. > I don't understand how or why this defeatist, nihilistic attitude is growing in popularity. I'm talking here purely about backups vs sync though.) (I draw the distinction between backups and archives whereby backups get you to where you were most recently (pre incident), and archives let you restore to something like 'Tuesday afternoon, two weeks ago'. would the deleted photo exist on your phone, would the second photo be pre, mid, or post modifications? If your phone were then to stop working and needed replacing, would the restoration process restore your phone to before, or after, the above deletions / changes were made? ie. Would the second be propagated to each of your SaaS storage providers overwriting the existing, or renamed and situated adjacent to the original? And if you modified it in-place a second time? ![]() Is your expectation that the first would be deleted from the various places you have it backed-up? (If not, then what's your process for fully destroying a photo?) Here's a hypothetical - imagine you deleted a photo from your phone, and then modified (in place) a different photo. Yeah, I get your intent, but I think there's some conflation of backup and sync. The setup is cheap, you basically just pay for the S3 storage (currently costing me a bit under $1/month - and I guess you could use a cheaper S3-compatible alternative like Backblaze and reduce your costs further). With AWSPics, sync your photos (just a simple directory tree on your local device) to S3 (I just do it manually from time to time from my desktop, but no doubt it can be done automatically at regular intervals, and/or it can be done directly from a phone), then Lambda functions generate thumbnails and browsable galleries (as static HTML), then you can view it all via CloudFront (password-protected using Origin Access Identity).ĪWSPics isn't really being actively maintained these days. Personally I prefer the former these days, but I know that I'm in the minority here on HN. It's great IF you're comfortable with your whole photo solution being cloud-based (but you still own and control it, you're not just handing it all off to a SaaS), rather than being self-hosted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |