Re: [xwiki-users] esoteric features

Hi, I just saw this thread and I have to say, your requirements are really interesting. On 09/23/2013 03:08 AM, Richard Kulisz wrote: Zed Shaw discussed this in "the ACL is dead" IIRC, he was using snippets of ruby (obviously touring complete) to express security rules. Bitcoin is of course another notable example since the actual payments are expressed as bytecode and the "payment claims" are inputs which cause that code to return true. I find this use case particularly interesting since it seems you're trying to implement the same friend-to-friend model that's done with ISP peering in Internet routing. This is a very scalable model which I have spent some time studying before beginning on cjdns. The reason I think why these things don't exist is because they can't outperform dictatorships at small scale. When a programmer implements one of these brilliant ideas, the first words out of the customer's mouth are "how can I make a rule so only management group can read these pages?" and we end up using this technology to emulate the ACL. What the customer comprehends is what he asks for, what he asks for is what the programmer must provide and what the programmer provides defined the customer's view of what is possible. Of course it's a bit of a catch 22 but still the programmer has a window of opportunity to define new possibilities through his solution to the customer's problems. So then the question becomes how to redefine the features needed to solve these problems which happen at scale in terms of use cases which people know they need. As far as actual answers I'm afraid I don't have any. Thanks, Caleb