Monday, February 8, 2016

Finally...

About an hour ago, I finally got three Client Devices (two Agent Devices and an administrator client) to maintain a set of three stable synapses between each other.

I'm going to go to my Alma Mater to have a go at selling my idea tomorrow. Maybe perhaps someone will be receptive to what I've got to show.

Thursday, January 7, 2016

Still here.

I'm still here. Still getting this Clique Space(TM) thing to work.

However, I fear that the things I'm working on at this point in time are not protected by my patent. They feel significantly different to the scheme published in the patents that I think disclosing them on this blog at this point in time would risk letting ideas escape into the public domain.

The patents (3 of them covering the Australian, US and New Zealand jurisdictions) talk of what components would need to form the bases of a real-time communications medium capable of representing individuals as a collection of devices that each operate. These patents form the shell of the idea.

I feel that the development of these ideas has created mechanisms that go deeper than the shell of these ideas; that I have penetrated this shell into the soft inner form to which I had only faith in the shell's containment as a guide.

I had faith because I had no idea of what was within when I put my ideas to a patent. I thought the ideas disclosed a simple system; maybe it is a system that is too simple for me to comprehend. Although I am now navigating a world where contingent ideas to those disclosed in the patent dominate, my faith hasn't wavered yet. I guess I might never finish. I may chase my tail to my end.

Thursday, September 17, 2015

Data model.

I've decided to disclose a data model for Clique Space. This has come about because of a discussion I had with someone who advised me to provide some pictures that help the reader understand the Jericho document I disclosed in my last post.
If Clique Space(TM) is a thing that is good, I want it to be known that I came up with it. Hence, this entry is me making a pre-emptive claim to this concept.
Although this isn't a full disclosure, perhaps the disclosure that I do provide is enough for someone else who has more money than myself to take and make even more money from. Perhaps such a person doesn't wish to let this world know that they have taken my ideas and claimed them as their own.

I know... I'm perhaps a bit paranoid. I think I'm dealing with it. Let Clique Space be mine or let it be no one's. If it is any good, what good would it do to continue to keep it away from this world.

Monday, September 14, 2015

Jericho Identity Commandments.

I have been trying to find a way to express my concept to others who might be thinking of similar things. I did some research recently and found this site and this site refer to a list of use-cases that people would generally like to see in a system that conveys identity.

I made general enquiries to these groups and someone from the second group got back to me. They directed my attention to the Jericho Identity Commandments and invited me to answer this wish list with solutions as I saw them in terms of Clique Space.

You can view my answers here.

Note also that I'm going to try to publish newer versions of this document when (or if) I receive constructive feedback from people who read it. That feedback could be from you. Your name could end up in the table of changes, or I will certainly honour your wish not to publish your name. Let me know.

Thursday, September 10, 2015

Pulse

In deliberating how Clique Space(TM) aware devices (Agent Devices(TM) and other Client Devices(TM) capable of generating viscera Participants), I had to entertain the communications method (synchronous/asynchronous) by which knowledge of state is spread amongst a subset of all Client Devices which are members (or subscribers) to any given subscription.

I have arrived at the notion that a subscription needs both synchronous and asynchronous communication.

A cluster of devices comprising a subscription dynamically grows and shrinks, but any given subscription is managed by a single device known as the given subscription's possessor device. The possessor may cede its authority to another device (this is theoretically though not currently possible), but for any subscription to maintain a stable existence, a subscription must have a single possessor which is known to be the possessor by all other subscribers.

A subscription grows by acquiring subscribers and shrinks by discarding subscribers. The possessor is the first member of a newly created subscription, and the last member of a subscription before it is destroyed. In having this special position in a subscription, the possessor is also responsible for coordinating the synchronous component of the subscription - its pulse.

At set intervals, an instance of the possessor's "pulse motor" emits a pulse message that spreads first to the possessor's nearest subscribers (those with whom the possessor shares synapses with). This pulse message is then relayed in turn to further distant subscribers until every subscriber is informed of the pulse. The pulse contains information about the state being subscribed to, the subscription's membership, and the length of time to wait for the next pulse.

As soon as a subscriber relays its pulse message, it sends a pulse reply. Each pulse reply reverberates around the subscription so every subscriber device knows that every other subscriber device has received the pulse message. This information helps every subscriber device determine whether they want to remain in the subscription or whether they wish to invite or remove other devices.

Updating the subscription's membership is the asynchronous component because any subscriber can assert the addition of any non-subscribing device, or the removal of any currently-subscribing device at any time. These messages, called "assertions" are remembered for between one and two pulse intervals.

The possessor decides whether an assertion will succeed. If this happens, the subscriptions membership will be updated. If the assertion was a member addition, the given subscriber will receive the next and subsequent pulses unless or until another assertion to have it removed succeeds. If the assertion was the removal of a member, the subscriber relating to the assertion will not receive the next or subsequent pulses unless or until another assertion to have it added succeeds.

So, subscriptions have both a synchronous and an asynchronous component, and both these components are vitally important to maintaining a stable cluster of devices which are observing some phenomenon.

Sunday, July 12, 2015

Chasing... no following leads.

That's what thinking is about.

When you are searching your mind, when you are finding a solution to a problem, when you are thinking about anything, you are moving through the landscape of facts following leads which appear interesting.

I've created a structure; an abstract class called Lead which is extended into two final classes: PrincipleLead and LimitingConstraintLead. Both classes implement a variation of the verb "to follow": PrincipleLead::follow(Class<q>qualeType) and LimitingConstraint::follow().

Very interesting... Although I wanted to get CliqueSpace(TM) to function in this way, I didn't have any leads on how this might be done in 2004. I've followed many leads since then.

Sunday, June 28, 2015

Does it work yet?

Ooh ahhh!

About 4 minutes ago, I just believe I finalised the architecture that is used to engage an administrator client, and have hence, all but filled out the body for the same architecture to enable two Agent Devices to engage.

There is still much to resolve around co-ordinating message transmissions, but I believe this is a very important milestone in the implementation.