Users should have the freedom to choose where their data resides and who is allowed to access it by decoupling content from the application itself.
Because applications are decoupled from the data they produce, users will be able to avoid vendor lock-in by seamlessly switching the apps and personal data storage servers, without losing any data or social connections.
Specifically, Solid is:
- A tech stack -- a set of complementary standards and data formats/vocabularies that together provide capabilities that are currently available only through centralized social media services (think Facebook/Twitter/LinkedIn/many others), such as identity, authentication and login, authorization and permission lists, contact management, messaging and notifications, feed aggregation and subscription, comments and discussions, and more.
- A Specifications document that describes a REST API that extends those existing standards, contains design notes on the individual components used, and is intended as a guide for developers who plan to build servers or applications.
- A set of servers that implement this specification.
- A test suite for testing and validating Solid implementations.
- An ecosystem of social apps, identity providers and helper libraries (such as solid.js) that run on the Solid platform.
- A community providing documentation, discussion (see the solid gitter channel), tutorials and talks/presentations.
https://solid.mit.edu/
https://github.com/solid/solid
List of Available Self-Hosted Applications - https://github.com/Kickball/awesome-selfhosted
No comments:
Post a Comment