Latest Postshttp://yes-again-we-can.wikidot.com
yes-again-we-can Re-organized in ComComized mailing list! We can be Re-organized such that no one could turn a bottom-up organization into a top-downWed, 19 Dec 2018 09:46:18 +0000http://yes-again-we-can.wikidot.com/term-and-conditionsTranslations of the comcomized.com Term And Conditionshttp://yes-again-we-can.wikidot.com/term-and-conditions
<p>Here are the Translations of <a href="https://comcomized.com/term-and-conditions/">https://comcomized.com/term-and-conditions/</a> (as <a href="http://yes-again-we-can.wdfiles.com/local--files/term-and-conditions/The%20Term%20and%20Conditions%20of%20Holding%20Shares%20in%20Common%20Company%20%28ComCom%29.pdf">pdf</a>) in this <a href="http://comcomist.wdfiles.com/local--files/comcomized-groups-functional-requirements/comcom%20agreement.1.pdf">form</a></p>
<ul>
<li><a href="http://namzezam.wikidot.com/blog:38#comcom">English</a></li>
<li><a href="http://yes-again-we-can.wdfiles.com/local--files/start%3Alists/Arabic%20translation.pdf">Arabic</a></li>
<li><a href="http://namzezam.wikidot.com/blog:37#comcom">Hebrew</a></li>
<li><a href="http://yes-again-we-can.wikidot.com/local--files/term-and-conditions/TE%CC%81RMINOS%20Y%20CONDICIONES%20DE%20LAS%20ACCIONES%20EN%20EMPRESAS%20COMUNES.docx">Spanish</a></li>
</ul>
<p style="text-align: center;">Changed to be made:</p>
<table class="wiki-content-table">
<tr>
<th>from</th>
<th>to</th>
</tr>
<tr>
<td>A Common company (ComCom) ownership agreement is an unchangeable agreement of ownership between the company’s owners.</td>
<td>A Common company (ComCom) ownership agreement is an agreement of ownership between the company’s owners. The agreement, or the qualified majority required to change it, is unchangeable</td>
</tr>
</table>
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212777" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Wed, 22 Apr 2015 14:02:39 +0000
Here are the Translations of https://comcomized.com/term-and-conditions/ (as pdf) in this form

]]>
http://yes-again-we-can.wikidot.com/create-your-comcom-user-page-your-group-s-contract-and-its-rCreate your ComCom user page, your group's contract and its recordhttp://yes-again-we-can.wikidot.com/create-your-comcom-user-page-your-group-s-contract-and-its-r
<ul>
<li><strong>1st</strong> After having your <a href="http://comcomized-net.wikidot.com">ComCom user page</a>, you can join existing group or create the unchangeable contract of the Common Company (ComCom) of your new group (see also the <a href="http://is-with.wikidot.com#c2">Terms &amp; Conditions</a> of such contruct). This will guide you in creating your group's corntract:</li>
</ul>
<ul>
<li>and <strong>2nd</strong> then, after having the contact <a href="http://yes-again-we-can.wikidot.com/start:contract">published</a>, request, as a member of this group, the group's activation , but only after you guarantee updating its arguments.</li>
</ul>
<p>Finally see also <strong><a href="http://yes-again-we-can.wikidot.com/about-mapping-and-logos">this</a></strong> about mapping and logos and here are <strong><a href="http://yes-again-we-can.wikidot.com/start:contract">some already made comcom contracts</a></strong>:</p>
<p><em>Note:</em> After creating the contract (1st step) the user creates the rec (2nd step) on rec-req and then the <a href="http://yes-again-we-can.wikidot.com/main:contact">admin</a> here approves the new record by moving the page from <a href="http://comcomized.com/feed/pages/pagename/start%3Alists/category/rec-req/order/updated_at+desc/limit/20/t/Latest+Posts">rec-req:</a> to <a href="http://comcomized.com/feed/pages/pagename/start%3Alists/category/rec/order/updated_at+desc/limit/20/t/Latest+Posts">rec:</a></p>
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212777" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Fri, 20 Dec 2013 11:14:36 +0000

1st After having your ComCom user page, you can join existing group or create the unchangeable contract of the Common Company (ComCom) of your new group (see also the Terms & Conditions of such contruct). This will guide you in creating your group's corntract:

and 2nd then, after having the contact published, request, as a member of this group, the group's activation , but only after you guarantee updating its arguments.

]]>
http://yes-again-we-can.wikidot.com/about-mapping-and-logosAbout Mapping And Logoshttp://yes-again-we-can.wikidot.com/about-mapping-and-logos
<p>On your request we are mapping your site (of which name ends in a dot) to comcomized.com so then you can use our <a href="http://comcomist.wdfiles.com/local--files/nav%3Aside/comcomized.png">logo</a> + the <a href="http://namzezam.wdfiles.com/local--files/blog%3A11/ComComIzed.Com.pdf">print (2*14 on A4)</a>. If your site is a free wikidot one (which you could start just by <a href="http://www.wikidot.com/doc:clone-module">clone</a> some other site you would like to begin with), go to its /_admin</p>
<ul>
<li>On Custom Domain fill your new url on comcomized.com
<ul>
<li>On Appearance-&gt;Themes-&gt;External usrl=/admin:themes/code/1</li>
<li>go to iits /admin:themes and add this code</li>
</ul>
</li>
</ul>
<div class="code">
<pre>
<code>@import url(http://themes.wikidot.com/sky-blue/code/3);
#header h1{background:url('http://comcomist.wdfiles.com/local--files/nav%3Aside/comcomized.png') no-repeat center top;}</code>
</pre></div>
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212777" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Mon, 13 Oct 2014 06:26:59 +0000
On your request we are mapping your site (of which name ends in a dot) to comcomized.com so then you can use our logo + the print (2*14 on A4). If your site is a free wikidot one (which you could start just by clone some other site you would like to begin with), go to its /_admin

Unlimited accumulation of power is the biggest problem! And when this problem appears in a competitive environment. it can only create few evil powers constantly destroying all others who would not serve them. Comcomized unit is designed for becoming a bad pill for the big ones to take. It creates a recursion for the value of the damage for breaking the agreement. here is the prototype of the contract, need ironing yet.

The idea is to build small units holding bigger, until that which would have the trademark to give the buyers a card for some discount in the small business. The power of buyers can then be used to shift their traffic from big to small business for later working with the small ones as ordinary owners partnering with the buyers being the peer ones in their comcom. more...

The problem: The bigger the group of equal individuals is the weaker is the power of each individual.The solution: Each individual owns equal part of the group's assets and evaluates it as a whole when leaving the group. Hence, when such small groups equally own bigger ones, the movement of the individual does not harm the bigger, making the solution scalable.

becoming free in a group is the first condition for any honest evaluation,

becoming equal is the first condition for any morality, solidarity, authentic sharing and/or being more supportive and less manipulative in that group,

equal ownership in a group provides to each of its members, as individuals or minorities, a new power over the group and its representatives,

when the chain is the will of the members, the weakest member, as its ring, defines its strength, and

when small groups equally own together a bigger group, the movement of members between the small ones don't break the bigger one, so building up, in many layers and from the smaller to the bigger, can only better serve the groups' members.

if you are an authentic producer, such as an artist developer reporter, researcher etc, you can get unite to force your distributer to be aligned with your values, even while distinguishing individuals as you by different contracts with the distributer.

Conclusion: Either I am represented in my democratic state and hence what it does is in my responsiblity, or I become peer owner in the texture of entities constituting my state.

]]>
http://yes-again-we-can.wikidot.com/test-create-yourTest Creating your ComCom user page, your group's contract and its recordhttp://yes-again-we-can.wikidot.com/test-create-your
<p>First, create your comcom user page <a href="http://comcomized-net.wikidot.com/test-create-your">here</a> then, create the unchangeable contract of the Common Company (ComCom) of your group (see also the <a href="http://is-with.wikidot.com#c2">Terms &amp; Conditions</a> of such contruct). This will guide you in creating your group's corntract:</p>
<p>and then, as a member of this group request activation for the record of that group, only after <a href="http://yes-again-we-can.wikidot.com/start:contract">presenting</a> the group's contract and after you guarantee updating the arguments of the record of your group.</p>
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212777" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Mon, 30 Dec 2013 15:12:07 +0000
First, create your comcom user page here then, create the unchangeable contract of the Common Company (ComCom) of your group (see also the Terms & Conditions of such contruct). This will guide you in creating your group's corntract:

and then, as a member of this group request activation for the record of that group, only after presenting the group's contract and after you guarantee updating the arguments of the record of your group.

]]>
http://yes-again-we-can.wikidot.com/comcomized-maling-listsComcomized Maling Lists Hostshttp://yes-again-we-can.wikidot.com/comcomized-maling-lists
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212777" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Mon, 17 Sep 2012 02:32:43 +0000
by comcomist
]]>
http://yes-again-we-can.wikidot.com/ssm-secure-storage-methodssm - a Secure Storage Methodhttp://yes-again-we-can.wikidot.com/ssm-secure-storage-method
<p>see also<br />
<a href="https://launchpad.net/comcomized-membership">https://launchpad.net/comcomized-membership</a><br />
<a href="http://comcomism-admins.wikidot.com/comcomized-mailing-services">http://comcomism-admins.wikidot.com/comcomized-mailing-services</a></p>
<p>The <strong>ssm</strong> (secure storage method), while using encryption methods such as the gnupg (which, as any known other, is finally breakable by our big brothers), is not only about securing the communication between peers (and although moving the data) but is mainly about providing a <span style="text-decoration: underline;">storage mechanism</span> in a cluster of units (cloud computing) <span style="text-decoration: underline;"><em>for data able to be stored more securely with more of its movement and doing so as much as such security is desired</em></span> (in a price, which is proportional to the number of movements, of slower fetching due to a longer decryption ).</p>
<p>It does so by simply combining the movement of data between some units (so that it is harder to locate it) while re-encrypting the data before each such move (so that is is harder to decode it).</p>
<p>Such data is moved between <strong>dip</strong> (data ip) units storing the re-encrypted data, where the dip units are not mixed with another group of units: the <strong>kip</strong> (key ip), in each of which some keyring are kept and where both groups (the dip and kip) are not mixed with another third group: the <strong>sip</strong> (server ip) providing the services in relation to such data.</p>
<table class="wiki-content-table">
<tr>
<th>In Dip</th>
<th>shall be done</th>
</tr>
<tr>
<td>when</td>
<td>As desired (use cron from kip) in writing. As required from sip in reading.</td>
</tr>
<tr>
<td>The access</td>
<td>Writing only from kip. Reading only from sip.</td>
</tr>
<tr>
<td>what</td>
<td>in writing each data's move between dip is only after first being Re-encrypted in kip.</td>
</tr>
<tr>
<td>where</td>
<td>The data in its deepest encrypted state is only in ONE dip known to sip for reading.</td>
</tr>
<tr>
<td>The keys</td>
<td>are never on dip.</td>
</tr>
</table>
<p>|<span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">&#8212;|<br />
| kip |Always per each reading |<br />
| |re-decrypting while |<br />
|</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span>|<br />
| sip |serving both reading and writing for the user |<br />
|<span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span><span style="text-decoration: line-through;">-</span>&#8212;|</p>
<p>If id==x, then the data is ready for be decrypted by the private key of the user and as such is sent to the sip, otherwise the id is of the key able to decrypt the data but only in the corresponding kip.</p>
<p>If ip ==y, then the key shall be processed in the current ip (mostly decrypting the data and than, depend on the id, sending the data to sip when id==x, or to kip corresponding to the new id), otherwise, when ip!=y, the data shall be moved to be processed to the ip, where such ip are only kip.</p>
<p>In each re-encryption at the additional 4 byte being expanded at the end of the data sits the id of the last key which encrypted it (unless id==x).</p>
<p>In each of the kip and in at-least one of the sip units, one table of id(key) -&gt; encrypted(ip(process_to_decrypt_with_the_key)) is used, but such table is not necessarily identical, where x or y are kept secret and even they can be changed between some hubs of such units.</p>
<p>only last dip is stored in sip &lt;&#8212;moment</p>
<p>see also <a href="http://iswith.info/admin/-c-/page/a-secure-cloning-system">http://iswith.info/admin/-c-/page/a-secure-cloning-system</a></p>
<p>by <span class="printuser avatarhover"><a href="http://www.wikidot.com/user:info/comcomist" ><img class="small" src="http://www.wikidot.com/avatar.php?userid=9424&amp;amp;size=small&amp;amp;timestamp=1545212778" alt="comcomist" style="background-image:url(http://www.wikidot.com/userkarma.php?u=9424)" /></a><a href="http://www.wikidot.com/user:info/comcomist" >comcomist</a></span></p>
Sun, 08 Jul 2012 17:37:04 +0000
see alsohttps://launchpad.net/comcomized-membershiphttp://comcomism-admins.wikidot.com/comcomized-mailing-services

The ssm (secure storage method), while using encryption methods such as the gnupg (which, as any known other, is finally breakable by our big brothers), is not only about securing the communication between peers (and although moving the data) but is mainly about providing a storage mechanism in a cluster of units (cloud computing) for data able to be stored more securely with more of its movement and doing so as much as such security is desired (in a price, which is proportional to the number of movements, of slower fetching due to a longer decryption ).

It does so by simply combining the movement of data between some units (so that it is harder to locate it) while re-encrypting the data before each such move (so that is is harder to decode it).

Such data is moved between dip (data ip) units storing the re-encrypted data, where the dip units are not mixed with another group of units: the kip (key ip), in each of which some keyring are kept and where both groups (the dip and kip) are not mixed with another third group: the sip (server ip) providing the services in relation to such data.

In Dip

shall be done

when

As desired (use cron from kip) in writing. As required from sip in reading.

The access

Writing only from kip. Reading only from sip.

what

in writing each data's move between dip is only after first being Re-encrypted in kip.

where

The data in its deepest encrypted state is only in ONE dip known to sip for reading.

If id==x, then the data is ready for be decrypted by the private key of the user and as such is sent to the sip, otherwise the id is of the key able to decrypt the data but only in the corresponding kip.

If ip ==y, then the key shall be processed in the current ip (mostly decrypting the data and than, depend on the id, sending the data to sip when id==x, or to kip corresponding to the new id), otherwise, when ip!=y, the data shall be moved to be processed to the ip, where such ip are only kip.

In each re-encryption at the additional 4 byte being expanded at the end of the data sits the id of the last key which encrypted it (unless id==x).

In each of the kip and in at-least one of the sip units, one table of id(key) -> encrypted(ip(process_to_decrypt_with_the_key)) is used, but such table is not necessarily identical, where x or y are kept secret and even they can be changed between some hubs of such units.