Home Cloud

Self-hosted cloud; at minimum this means a File Storage (and will be treated exclusively as such for the sake of this document).

Security - with the direction of our society at large and social media, I want to be able to share data with specific people and not simply on a public blog.
Ease of Use - I know many people who are non-technical and technical-adverse, so this must be as simple as iCloud or GoogleDrive.
Social Media Fatigue - generally avoid creating new accounts.

Self-hosted IdP (such as LDAP) - would have to register accounts for all friends onto each system. Issues with storing accounts that become too painful and complicated for non-technical to manage. Furthermore, this introduces too many new accounts for users.
OIDC / OAuth - would have to register each server with the provider, which is too complicated for non-technical. Still requires storing linked user identifiers to track permissions or advanced features like commenting. Also, means would be limited to certain providers that users may or may not have an account with and may or may not be desirable to link with. Not having an account introduces creating more accounts.
IndieAuth + OAuth - users provide their identity as a URI, and this can be linked to any IdP they desire. Little to no registration required. This SOLVES both the issue of non-technical (as simple as entering in a URI with no registration) as well as avoiding new accounts (re-use existing social media accounts with little registration or, if desired, limited to only one additional account). Plus there is no need to store users or linked user identifiers on any server since they will be identified by URI instead.

File-like storage mechanism that provides key cloud expectations:

Already done Proof-of-Concept (POC) for authorizing based upon an allowlist file property.

For users that do not have a social media account (next generation of people) or do not want to link one, the option to have a self-hosted identity.