I posted this idea long ago, but perhaps not many people got what I was on about. I have a tendency to be long winded so I will try to keep this succinct as possible.
The main motivation is that fact is you don't now what use cases are going to appear in the future. You are not going to be able to please everyone with set in stone permissions, roles, groups, etc. Also there is is strong expectation within a user base, of a specific use case for things to work a certain way. In other word wave agnostic. Also there is admission that the current permission proposal they are not worry about how they are going to federate it (which I think is repeating the mistakes of the past) My idea is for the creator of a wave to add one "public via proxy" group/permission (which can be a condition of publication). This allows all the participant interaction to moderated through that proxy. Effectivly providing access controll on other interaction control fefac to without needing predefined roles. It is is not after the fact like a robot but before. How is is federated? When you federate there is a trust relationship. mailserver are no different. if they abuse that trust then you don't deal with them. It is as much as a problem as dealing with individuals. So therefore the proxy could be in the form of distributed agent code sent to each service. Distributed agent code is another idea I have which deserved its own post. However basics: browser use distributed agent code in a sandboxed environment it is called client code or javascript/ ECMAScript (which is the obvious choice). The Caja doodad in effect provides distributed gent code to the client interface, albient in a non elegant way. In theory providing distributed agent capabilities such as spelly or rosie, with performance robots couldn't compete with. This would be federate simply by virtue of begin included in the doc, and of course requiring an uptake of the feature. You can also have distributed agent code sent to the server itself. the proxy is a special case of this type of agent code. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
