Editing Network services/Current approaches
From WikiDotMako
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
What are the approaches that people are using to try to address | |||
webservices. These might include: | |||
=== Abstention === | |||
For certain classes of applications that have functionally equivalent | |||
distributed or non-service version or analogs, one can avoid inherent | |||
power dynamics that inherently disadvantage users by avoiding the use of | |||
applications. See Richard Stallman's essay sent over email for more | |||
information on this position. | |||
=== Extending copyleft to web services === | |||
Quite a few projects have attempted | |||
=== Others === | |||
Other ideas might include: | |||
* Cooperative hosting solutions. | |||
* Contracts and accountability for hosting providers | |||
** Ensure that the services provide you with a way to leave (freedom to leave) | |||
* A Network Services "Bill of Rights" (e.g., [http://www.oreillynet.com/pub/wlg/3266a][http://www.camworld.com/archives/001226.html]) | |||
* Increased monitering ability for hosting providers | |||
Other license based approaches are described in depth on [[Network services/Licensing approaches to network services]]. |