[squeak-dev] Mutter system news
charlie.robbats at gmail.com
Wed Dec 28 19:43:15 UTC 2016
All of this infrastructure is for secure mobile code, I am hoping. To
support aliased donation networks through malleable smart contracts and
build markets to help folks through squeaky flip phones with oil to
cover our faces like sunscreen. Have peace and prosper plan preventing
piss poor performance. Emoji driven distributed load/traffic balancing
across multicore, hopefully with GPIO support. Karma flows change
outside in the inbetween. To be all Kurt Vonnegut about replacing debt.
adn so we go,
On 12/28/2016 2:28 PM, Frank Shearar wrote:
> What would be super helpful is a brief description of the why, here.
> You're giving a detailed description of SOMETHING and expecting the
> reader to piece together the puzzle. Almost no one is going to do
> that, because they're busy solving their own problems.
> On Dec 28, 2016 11:22, "Charlie Robbats" <charlie.robbats at gmail.com
> <mailto:charlie.robbats at gmail.com>> wrote:
> 19 - I am thinking about merging RS FEC with blockEn/Decoding with
> a 7-bit msgChunks into 8-bit blocks, or QoS determined. That along
> with non-secret 3-way finite field key agreement ratcheting and
> contract established scoping, would mean each transaction might be
> separately islolated from every other and the contract exchange
> includes trusted observation filtering capabilities, locally
> enforced through your prioritized trees of life, liberty &
> property, and also your knowledge of good and evil.
> 20 - add a new delayed redirector, on Carol's side, so a
> remotePromise resolution will be a tree-way exchange for the
> ratchet exchange: carol -> farRef: alice -> scope internalize:
> carol -> ack redirector: alice -> wire encrypted
> 21 - group ratcheting: presence event leads to re-rendezvous with
> the qufrum, majority/super-majority online election/karma emoji
> On 12/28/2016 1:55 PM, Charlie Robbats wrote:
> 16 - pass the galaxy test:
> 17 - exchange access categories with contractual code migration
> 18 - emoji feedback
> On 12/28/2016 1:11 PM, Charlie Robbats wrote:
> Hi! Here's the master plan, always malleable; if anyone
> sees something interesting to dive into, you are welcome.
> Future Features
> 0 - fix vector corruption through pbeStorage
> 1 - java/squeak interoperability
> 2 - FEC-RS testing/repair
> 3 - define QR-coded PBE identity
> 4 - switch to SHA256/scrypt PBE for identities
> 5 - porciniz
> 6 - DNS/meta layer injection
> 7 - stack hacking/network discovery/graphing/routing
> 8 - blockchain
> 9 - support non-secret finite field key exchange
> ("Whisper-2")-Oops/add dataEncoder to EncoderData
> 10 - ratcheting/group join/leave ratcheting
> 11 - asn1derMetaPragmaEncoder/class autocreation and meta
> qufrums/qufrum construction/data replication
> 12 - thermoHarmonics3NeuralRuleGA (PV = nrT + distortion)
> 13 - Enumify Types, pass named closures, scope projection
> & protection, detach class/classVariables
> 14 - autocoerce local eventual calls to immediate sends
> with reactor pipelining
> 15 - start a Mutter system news website
> Encoder Velocities:
> DBL_AESede/asn1der: 100 KB compressed data chunks
> received: 100
> send time: 1096 ms, rate: 73 Mbs.
> receive time: 1096 ms. rate: 73 Mbs.
> DBL_AESede/bytes: 100 KB compressed data chunks received: 100
> send time: 1094 ms, rate: 73 Mbs.
> receive time: 1095 ms. rate: 73 Mbs.
> DBL_AESede,json: 100 KB compressed data chunks received: 10
> send time: 2107 ms, rate: 4 Mbs.
> receive time: 2107 ms. rate: 4 Mbs.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev