The ones who understand where their photos are or attach significance to them will make the effort. The remainder tend to work exclusively out of Facebook or iOS Camera Roll, which is why iCloud now backs that up.
I actually figured out every photo I take has
- one copy on the SD card
- two mirrored copies on my raid
- 3 copies on S3
- 3 copies on flickr (I believe)
for a total of 9!Flash memory depends more on write/erase cycles. Infrequently used media can theoretically last for decades, and is much more resilient with respect to storage and handling. Then again, in 25 years, how easy will it be to find a USB reader?
The only reason someone would not use this approach and opt for one of the services mentioned is marketing. There is no marketing for storing files in a "non-proprietary" format. It's simply a matter of not knowing how to do it.
What's funny is the proprietary approaches ultimately can make things more difficult for novices. At least it's more they have to learn: different rules for each service. How often I have heard novices wanting to know how to convert/export/transfer files to/from these services.
Compare this with learning the jpeg format, IPTC and EXIF. You only need to learn one set of rules. And every service uses jpeg. That's unlikely to change anytime soon.
It's a battle against the "lowest common denominator" in the interest of creating a strategic advantage via incompatibility and proprietary formats. But it seems always some compromise is necessary. All those services work with lowest common denominator formats like jpeg. They don't each have their own proprietary image formats, though they could. Compromise is made.
The entire web is built on "lowest common denominators": e.g., IP, UDP, TCP. To allow things to flourish you have to have some lowest common denominators that everyone can develop on top of. But let the battle continue. We the users all suffer inconvenience as a result.
I feel the only reasonable approach is to have the original jpegs layed out in a simple date-encoded directory tree, title/comment them with IPTC, add EXIF geotags and archive that. Backs up to S3 (even though if I got hit by a bus I doubt my family could figure out how to restore them).
Actually, SD cards are so cheap these days I don't even reuse them. So I have that backup, minus comments and geotags as well