Self-hosting: Difference between revisions
m ISP wanted |
Worded advantages into a more consistent structure and added one more |
||
| Line 16: | Line 16: | ||
===Standalone digital services=== | ===Standalone digital services=== | ||
Messaging (such as e-mail, social networks and instant messengers), publishing (blogs, wikis, etc.), most forms of continuous data synchronization between devices and remote access of other devices are examples of services that can provide value to users by themselves, with clients widely available or unnecessary. | Messaging (such as e-mail, social networks and instant messengers), publishing (blogs, wikis, etc.), [[software as a service]], most forms of continuous data synchronization between devices and remote access of other devices are examples of services that can provide value to users by themselves, with clients widely available or unnecessary. | ||
Self-hosting such services | Self-hosting such services can be useful for privacy: for those that do not wish for their activity on these services to be transmitted to the internet at all to reduce the number of ways it can leak. | ||
Self-hosting can also provide additional resilience: the service can remain fully functional in a [[Local area network|local network]] where it's deployed — which is useful in case the [[internet service provider]] (ISP) has an outage or if an alternative public service falls under new legal restrictions (e. g. censorship) and becomes inaccessible. | |||
Self-hosting can also be a viable alternative when an existing service changes in an undesirable way (e. g. changes its [[terms of service]] in a controversial way, changes existing features, gets acquired or taken over), providing a baseline against which service providers could be forced to compete in serving the needs of their users. | |||
===Digital services for "connected" products=== | ===Digital services for "connected" products=== | ||