Difference between revisions of "RawringTwenties"

From Cibernética Americana
 
(211 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="background-color: gainsboro;"><br><br>
+
<div style="background-color: gainsboro;"><br>
<blockquote><center><blockquote style="font-weight: 600;width: 60%;color: white; background-color: black; border-top: 1px solid #e1cc89; border-bottom: 1px solid #e1cc89; margin: 5px;  text-indent: 23px;"><br>
+
<blockquote><center><blockquote style="font-weight: 600;width: 70%;color: white; background-color: black; border-top: 1px solid #e1cc89; border-bottom: 1px solid #e1cc89; margin: 5px;  text-indent: 23px;">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Presentation</span>]</span><br>
+
<p style="position: relative; left: 15px;"> [[Temporality|<span style="color: yellow;">4720-30</span>]] Agenda (2022-2032 [[:en:Common Era|<span style="color: yellow;"><i>Era Vulgaris</i></span>]])</p>
<p style="position: relative; left: 15px;">Windmills I tilt at in [[Temporality|<span style="color: yellow;">4718-28</span>]] (the 2020s [[:en:Common Era|<span style="color: yellow;">XE</span>]]):</p><br>
+
<span style="font-size: 10px;color: cyan;">Personal improvement takes precedence. Failing that success in projects moot, if it succeeds failures in them are tolerable / temporary.</span>
 
<p>
 
<p>
#<html><a href=https://sameboat.dom title="only works if you're routing my alt root">.dom</a></html> &mdash; my [[Alt root|TLD]]
+
#<html><a onclick="return checkRouting();" href=https://sameboat.dom title="only works if you're routing my alt root">.dom</a></html> &mdash; my [[Alt root|TLD]] AKA Domain Space
# <span class=plainlinks>[https://sameboat.live <span style="color: yellow;"> C-六</span>]</span> &mdash; php/python  nexus
+
# <span class=plainlinks>[https://github.com/RenRenJuan/Green-Travel-Carbon-App <span style="color: yellow;">GT2</span>] personal carbon accounting domain (<span style="font-size: 10px;color: yellow;">[http://market.android.com/details?id=app.greentravel.gt2 <span style="color: yellow;">android</span>] [https://apps.apple.com/ao/app/gt2-green-travel-carbon-app/id1583117880 <span style="color: yellow;">iOS</span>]</span></span>)
# GT2 &mdash; personal carbon accounting app, begun as the <span class=plainlinks>[https://play.google.com/store/apps/developer?id=Juan+Daugherty <span style="color: yellow;">Green Travel Calculator</span>]</span> at start of prior decade
+
# <span class=plainlinks>[https://eg.meansofproduction.biz/index.php/C-Liu <span style="color: yellow;"> C-六</span>]</span> &mdash; php/python Domain CMS
# [[MCP|<span style="color: yellow;">MCP/DCP</span>]] &mdash; distributed AI oriented OS concept, in part an homage to the Burroughs systems
+
# TASKPM <b>tl;dr</b>&trade; &mdash;  taskwarrior, MS Project, etc.  for DS users
# TASKPM &mdash; <b>tl:dr</b>&trade; integration and planning for taskwarrior and MS Project
+
# <span class=plainlinks>[https://github.com/RenRenJuan/YAS3FS <span style="color: yellow;">YAS3</span>]</span> &mdash; yet another S3 client  
# <span class=plainlinks>[https://github.com/RenRenJuan/YAS3FS <span style="color: yellow;">YAS3</span>]</span> &mdash; x-platform simple storage system client  
+
# [[MCP|<span style="color: yellow;">MCP/DCP</span>]] &mdash; intelligent OS with mannerisms in homage to mainframes&sup1;
 
</p>
 
</p>
<div style="position: relative; left: 10px;"><hr width="70%" ></div>
+
<div style="position: relative; left: 30px;"><hr width="50%" ></div>
Domain driven development, artificial intelligence, [[worker capitalism]] are among the interwoven themes.
+
<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp;  &nbsp;<span class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Impressum</span>]</span>&nbsp; &nbsp; <br><br>&nbsp;&nbsp; &nbsp; Domain engineering, &nbsp; mecha intelligence, &nbsp;and &nbsp; [[sovereign Praxis|sovereign praxis]] &nbsp; are &nbsp;leitmotifs.
  
AC and db/ft are conversational agent and video conf designations, respectively.
+
AutoConsult, doorbell/Ft: legacy labels for intelligent conversational agent and videoconf efforts, respectively.
 +
 +
tl;dr&trade; and sameboat name app and C-六 based affinity/social networking product lines, respectively.
  
redvant, dcms< (dcms-bra), and dcms> (dcms-ket), are designations of technology packaging in support of the above.
+
redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), are designations of support layers.
  
tl:dr and sameboat are designations for an app product line (with GT2,TASKPM) and applications of the C-六 django/drupal hybrid, respectively.
+
<br></blockquote>
 +
<table width=70% style="position: relative; top: -30px; " cellspacing=0>
 +
<tr><td valign=top style="font-weight: 600;width: 67%;color: white; background-color: black; margin: 5px;  text-indent: 5px;">
 +
<blockquote style="text-align: justify;">
 +
MCP/DCP is the central project, mature in conception at the start but not in realization until the end of this period. While every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release my original sources for the OS product at least in this decade. Everything else is maintained in open source form and can be the basis of various development opportunities. Open source here (as opposed to my github) means available at some level of entitlement either simple capitation (AKPERSON) or devops levels.<br>
  
<br><br>
+
Source code of C-, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles  for bespoke apps/services using various supports but themselves are basically feature static after 4719/20 with change limited to utilization of our or or 3rd party new infrastructure.
<div style="text-align: justify;width: 600px;">
+
</blockquote ></td><td valign=middle width=33% align=left style="font-weight: 600;color: white; background-color: black; margin: 1px;  text-indent: 5px;"><blockquote
I suppose in the way people talk at this writing, MCP/DCP is my passion, the central project and while every 3rd party package I use is made available here in the form I've found it, I don't intend to release my original sources for the OS product at least in this decade. Everything else is maintained in open source form and can be the basis of various development service offerings. Open source here means in my domains and for some sources a higher level of entitlement than mere capitation (AKPERSON) may be required.
+
style="position: relative;left: -15px;text-align: justify;">
 
+
For the value of the interaction, I remain open to joining a group, optionally deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the reserve army of labor/FOSS commons to fusion with a smaller group has a presumed low but unknown expected value in this period. As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.</blockquote>
The supporting code and services here for GT2, YAS3, and C-六 can be the basis of bespoke or independently developed applications with support for either at the appropriate base capitation level. No entitlement is required for accessing or the base code sets, any actually known and authenticated user may. At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required.  
+
</td>/tr>
 
+
<tr><td colspan=2 style="background-color: black;"><blockquote><hr>&sup1; <font size=1>Mainly Burroughs, with a nod to VM/CMS.</font></blockquote></td></tr></table><br>
Until and if sales moot it, I remain open to joining a firm/shop/whatever, postponing my projects for a year or two, but acknowledging the unlikeliness, I've stopped looking.  
+
<br>
</div>
 
<br><br>
 
<br><br>
 
</blockquote>
 
<br><br>
 
 
</div>
 
</div>

Latest revision as of 17:49, 17 October 2021


4720-30 Agenda (2022-2032 Era Vulgaris)

Personal improvement takes precedence. Failing that success in projects moot, if it succeeds failures in them are tolerable / temporary.

  1. .dom — my TLD AKA Domain Space
  2. GT2 personal carbon accounting domain (android iOS)
  3. C-六 — php/python Domain CMS
  4. TASKPM tl;dr™ — taskwarrior, MS Project, etc. for DS users
  5. YAS3 — yet another S3 client
  6. MCP/DCP — intelligent OS with mannerisms in homage to mainframes¹



                   Impressum   

     Domain engineering,   mecha intelligence,  and   sovereign praxis   are  leitmotifs.

AutoConsult, doorbell/Ft: legacy labels for intelligent conversational agent and videoconf efforts, respectively.

tl;dr™ and sameboat name app and C-六 based affinity/social networking product lines, respectively.

redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), are designations of support layers.


/tr>

MCP/DCP is the central project, mature in conception at the start but not in realization until the end of this period. While every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release my original sources for the OS product at least in this decade. Everything else is maintained in open source form and can be the basis of various development opportunities. Open source here (as opposed to my github) means available at some level of entitlement either simple capitation (AKPERSON) or devops levels.

Source code of C-六, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles for bespoke apps/services using various supports but themselves are basically feature static after 4719/20 with change limited to utilization of our or or 3rd party new infrastructure.

For the value of the interaction, I remain open to joining a group, optionally deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the reserve army of labor/FOSS commons to fusion with a smaller group has a presumed low but unknown expected value in this period. As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.


¹ Mainly Burroughs, with a nod to VM/CMS.