Tuesday, October 9, 2018

Attaching windows to the join machine

My next thing.
The screen is a directed graph of widgets, possibly screen squares. Dots will descend into child windows, Commas step through daughter in the current window. The attachment has complete freedom to format the window portions. The app mostly implements the Append method required by the join.

This is simple in python, even simple with console text and indents. But that is the format of the new search engines, totally distributed, autonomous secure bots. A screen display and sellers of state can dump it into sandbox in JSON format, from stocks and bonds to eggs and butter. Users all have search applications generating complex search bots.

Speed searching.
It is all about prep in the attachments, making a good pass at separating out key words and their order.  There is a lot of code that does that well,  it can use a preformatted, rough sketch of the article tree, in proper order.  The search graphs all have a local attachment that works well with the search graphs, refining down the search according to the search graph junique tree. We can run these searches at extremely high speed, and you still get paid..

Micro pricing is key, it structures the bot queues, intelligently, because bogts can respond o congestion.  In aggregate, like the auto markets, the semantic network is far more intelligent than any human user.

We need this to overlay the pure cash layer. Still, easily secured. The bots can carry around public keys issued by card holders.  When you join an 'App', it is about agreeing on a contract, which will be directed graph, JSON with secure contract managements everywhere, like mners. No better way to do this.

The other thing about micro pricing (besides congestion control), we get a calculus, a method of successive refinement in our searches, from end to end.  A sequence of joins, they connect. We don't need book marks, we have our tree of search graphs, graphs that knows our idioms. Our idioms remain private.

No comments: