Editing Talk:Distributed Consumerium

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 33: Line 33:
::The above is very good.  We are now identifying some responsibilities that the [[Consumerium Governance Organization]] might take, or might have to load in the [[Consumerium License]], and some [[software requirements]] like this 'shut down if they are doing things we dislike and not paying us enough to make up for it' [[lockout]].  Which means we must look at [[shareware license]] examples that 1. rely only on [[code-based enforcement]] 2. are popular anyway 3. are [[self-funding]].  Some [[Consortium license]] are also of this nature but without code enforcement or [[lockout]] since usually it's source that is being distributed and the lockout is easy to remove.
::The above is very good.  We are now identifying some responsibilities that the [[Consumerium Governance Organization]] might take, or might have to load in the [[Consumerium License]], and some [[software requirements]] like this 'shut down if they are doing things we dislike and not paying us enough to make up for it' [[lockout]].  Which means we must look at [[shareware license]] examples that 1. rely only on [[code-based enforcement]] 2. are popular anyway 3. are [[self-funding]].  Some [[Consortium license]] are also of this nature but without code enforcement or [[lockout]] since usually it's source that is being distributed and the lockout is easy to remove.


::Of course there can be hacked versions of each bit of software without the [[lockout]], but, it's quite hard if there is authentication of each part of the network in the [[protocol requirements]], so that, you can't actually get a hacked module to cooperate with anything else.  I can see this is a hot potato too, but, can't be avoided:  there's no way that [[Gus Kouwenhoven]] is going to just sit back and watch his "business" get trashed if he can pay a hacker a few hundred bucks and insert [[greenwash]] directly into the [[Consumerium buying signal]]s about his vile products.
::Of course there can be hacked versions of each bit of software without the [[lockout]], but, it's quite hard if there is authentication of each part of the network in the [[protocol requirements]], so that, you can't actually get a hacked module to cooperate with anything else.  I can see this is a hot potato too, but, can't be avoided:  there's no way that [[Gus Kouwenhouven]] is going to just sit back and watch his "business" get trashed if he can pay a hacker a few hundred bucks and insert [[greenwash]] directly into the [[Consumerium buying signal]]s about his vile products.
Please note that all contributions to Consumerium development wiki are considered to be released under the GNU Free Documentation License 1.3 or later (see Consumerium:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)
Return to "Distributed Consumerium" page.