|
policy
Hiveware
policy consists of the following where hive stands for
Hyperstructured
Interactive Virtual Environment
software:
Hives are created by signing an Sdcdc Domain Contract. Optionally,
each new hive may be for-profit or non-profit. For-profit hives
automatically maintain a digital bank account from which revenues and
obligations may be received and disbursed. The setting up of this account
is part of the SignupAuthentication procedure.
Any member of any hive may sign someone else up as a member of his hive
providing that the new person agrees to their hive's rules of order.
Becoming a member of a particular hive conveys rights to patents and
trademarks. The new subscriber has the right and capability to receive immediate
and continual updates from any and all of the hive's authors.
Any hive member may create a contract with any new subscriber for the
establishment of a new hive using the provided
Sdcdc Domain
Contract
where Sdcdc stands for
Synchronous
Distributed Context Distributed Content
.
Each hive member can obtain technical and customer support from any or
designated members of his hive regarding his hive's content and behavior.
Should his hive's technical and customer support not be sufficient, he may
obtain support from his ancestor hive. Likewise, each hive can obtain
technical and customer support from the hive who signed his hive up
referrred to as his current ancestor hive.
Each hive may augment his ancestor's Hiveware policy but not
substantively alter it. Each hive may augment his ancestor's inherited code
behavior, but not substantially alter it.
Termination is defined as ceasing to have the right to further continual updates from a hive's authors. Termination does not affect already received structure and content. Each Hiveware author or subscriber is entitled to a time-stamped export in ISO 8879 SGML format. Termination criteria are set forth by the hive's rules and order. A subscriber's payment agreement with his hive will stop within 30 days after he unchecks the Hiveware Control tray menu item Always On.
policy for choosing a hive
· May not be one of the top hives as listed in ‘top hiveware domains’.
· All new for-profit hives are automatically 20-80 contracts (20% to ancestors and siblings) and are content only meaning the owner or members may signup any number of new members to their hive.
· Descendant content hives may negotiate at any time with their ancestor hive to change the percentage-to-ancestor ratio.
· Descendant content hives may negotiate at any time with their ancestor hive to be converted to a context hive, which has a dashboard and gives the owner the capability for creating new descendant hives. These hives are also default 20-80 contracts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Nov 22, 2023, you can now follow development of Hiveware's built-in apps. Just go to top Hiveware domains, then find and click on (DEV). This will show you a pdf of and history of these projects development from a GUI perspective.
- June 15, 2021, Presented CableLabs with Hiveware Inc and Microsoft findings that their DOCSIS 3.1 gateway modem specifications have not led to ISP venders implementing IPv6 end point to end point Reachability. Local Reachability succeeds, but both Intra-ISP and Inter-ISP cable modem Reachability fail.
- Sept 15, 2020, Determined that ISPs that offer Ipv6 like Cox and Comcast, are not inter-connectable. See my explanation, which means Microsoft's socket library, Winsock2, is not to blame.
- May 18, 2020, Hiveware Ipv6-Ipv6/Ipv4-Ipv4 connectability succeeded Debug and Release. This breaks the stranglehold NAT has on Hiveware residential deployability (but only for intra-ISP comms for now, fx, XfinityWifi does not work where the problem lies with either Microsoft, Xfinity or Cox).
- March 17, 2020 opens Hiveware for Ipv4Ipv6Comms initial hive offering until June 19th, 2020.
- March 16, 2020, Hiveware for MyFiles private Digital Asset App Offering closed and March 17th, 2020, Hiveware for MyFiles public Digital Asset App Offering opens and will close again on June 19th, 2020.
- March 16, 2020, Hiveware BigBang Test 2-PC Basic succeeded again, but this time using Ipv6. This is the '1' of the decentralized '3-2-1 persistence' model.
- March 17, 2019, Hiveware for MyFiles public ICO began and ended June 16th, 2019
- December 17, 2019, Hiveware for MyFiles private Digital Asset App Offering began and closes March 16th, 2020.
- January 17, 2019, Hiveware BigBang Test 2-PC Basic succeeded. This is the '1' of the decentralized '3-2-1 persistence' model.
- October 1, 2018, Hiveware LittleBang preview running again, this time using production engine code
- August 17, 2018, Hiveware for MyFiles private ICO will begin
- July 17, 2018, Hiveware ICO ended. SoftCap not reached.
- Jun 3, 2018, first to file for Securities Act of 1933 compliance regarding HVW-generating dapp ownership ICO sale
- May 11, 2018, Microsoft delivers native MFC (C++) on ARM64, opening mobile devices and market up to Hiveware code
- April 17, 2018, Hiveware ICO began
- April 13, 2018, white paper published
- Dec 27, 2017, Hiveware engine (4th rewrite) POC done
|
|
|
|
|
|
|