For those who have more money than time, Synology NAS devices include mobile apps for common use cases, e.g. photo sharing. There's apparently an open-source clone called XPenology. For simple photo backup, Photosync works on all major desktop/mobile operating systems and can sync to a wide range of local or cloud storage.
After 2 decades and billions of investment in web services, it's not realistic to expect a generic "home server" to serve all possible use cases. Those that work best are usually based on an open protocol (e.g. WebDAV, SSH/SCP, SMB).
> did you put my new portfolio pictures on the site yet?
As an example, the UX for client-side workflow for blog publishing (WordPress, Jekyll, Hugo) is likely independent of the infrastructure for blog hosting (VPS, self-hosted, WordPress.com, GitHub Pages, etc.
> After 2 decades and billions of investment in web services, it's not realistic to expect a generic "home server" to serve all possible use cases. Those that work best are usually based on an open protocol (e.g. WebDAV, SSH/SCP, SMB).
Surely HTTP is the common, open protocol here? Other than email, at least. Is anyone using SMB-from-the-cloud for network file systems? Are they serious? :)
The most widely deployed "home server", FreeNAS, is historically based on NAS/LAN protocols. Most home users want to share file storage across multiple devices, which historically has been SMB/NFS/DLNA. Over time, NAS devices have added cloud/WAN protocols, like WebDAV, S3, etc.
The most expensive aspect of server software development is data integrity/availability, e.g. ZFS or other high-integrity filesystem. Services atop the storage layer are usually built by different teams, often from different eras.
"home server" here was intended to mean "network-facing http and maybe smtp server", not "server for domestic duties". Sorry if that wasn't more clear.
of course, no reason why the same box couldn't do both.
After 2 decades and billions of investment in web services, it's not realistic to expect a generic "home server" to serve all possible use cases. Those that work best are usually based on an open protocol (e.g. WebDAV, SSH/SCP, SMB).
> did you put my new portfolio pictures on the site yet?
As an example, the UX for client-side workflow for blog publishing (WordPress, Jekyll, Hugo) is likely independent of the infrastructure for blog hosting (VPS, self-hosted, WordPress.com, GitHub Pages, etc.