Saturday, October 15, 2016

The better message server

It does very little, it is more like a packet router. Y sends to X, the server hold the message until X logged in, the message is sent, then deleted.  The message server is un-programmable, it can only be hacked by riggin a new installation, and inside job.

Why not? Each device for each person can have a very nice pythin message handler, as good as Facebook.  There is no reason to put programability in many of these servers, they should remain simple request/response.  They do not need to hold data that is not generally accessable.

Smart card fixes much of this stuff, it can be an honest price taker of corporate information.  Tap your card on the message icon, the bots will determine what needs deletion and what stays.  They stay on guard, they know how to track information that is straggling or stuck.

OK, I can create the clearance protocol.  It is the message set used by the local python task to access the servers to clear and/or extract personal information  Make it simple, every device, including servers, get the protocol.  It is direct, extract and/or delete.  The bare message server knows the protocol, its the only thing it knows, save until and extract and/or delete.  Why does this simple idea work?   Your smart card has your security profile, it can price and clear your personal information.  It is the python on your other computer that does the work. Your home computer, its text exchanger, in the lower left icon.  Tap it with your smart card, clear your stuff from the web.

The mathematics is simple.
The sender offers to sell you information for a price, like blackmail.  You, at the other end, can accept or delete, paying the price or not.  The ultimate outcome is either both parties delete and the message moved on, or the offer declined, the message is deleted.  The server is not going to manage multiple bid cycles, the sender can resend with a different price.

No comments: