Easier consumption is pretty much it, yes. Specifically, it'd make it easier to stay engaged with publishers and communities even if they aren't part of a centralized platform, which means that people who develop publishing and community apps will have an easier time growing their user base.
> Users would still depend on centralized services to publish content, and there's little to no chance that these companies would interoperate using a standard protocol.
All you need is a blog/newsletter platform like substack, ghost, wordpress etc. They may not aggregate your social posts into another feed for you, but you can use a separate service to generate and host the feed, then link to it from your main site.
> Users should have full control over the data they produce, and be free to migrate it to any other node without losing access to the service they're interested in.
> Users would still depend on centralized services to publish content, and there's little to no chance that these companies would interoperate using a standard protocol.
All you need is a blog/newsletter platform like substack, ghost, wordpress etc. They may not aggregate your social posts into another feed for you, but you can use a separate service to generate and host the feed, then link to it from your main site.
> Users should have full control over the data they produce, and be free to migrate it to any other node without losing access to the service they're interested in.
RSS and email do this pretty well I think!