I only use RSS to convey the concept of a standardized syndication system, thus "like" being used rather than saying RSS itself....
But yes, what you say is exactly the point of what I'm talking about.
Some sites would focus on being the universal front end for casual browsing while others would focus on niche purposes such as moderation or unique content types/presentations.
The data would be stored with the user by default in my model, ensuring they have control of their content, and offloading a bunch of the delivery work from the front end site (essentially every users SSO becomes the cdn for their chunk of the content).
It has some problems but it's really not much different than now except it's easy as pie for people to get eyeballs on their content (does mean monetization has some issues, as it does now).
But yes, what you say is exactly the point of what I'm talking about.
Some sites would focus on being the universal front end for casual browsing while others would focus on niche purposes such as moderation or unique content types/presentations.
The data would be stored with the user by default in my model, ensuring they have control of their content, and offloading a bunch of the delivery work from the front end site (essentially every users SSO becomes the cdn for their chunk of the content).
It has some problems but it's really not much different than now except it's easy as pie for people to get eyeballs on their content (does mean monetization has some issues, as it does now).
Imrambling.....