Group items tagged

"Joe celebrates a history of grandiose business failures: a ski resort built in the Sahara, a knowledge-enhancing computer chip implanted in the brain; a teleportation booth to solve the problem of rush hour commuting; the dispersion of aphrodisiacs during battle in an effort to harmlessly distract the enemy."

I HIGHLY recommend Joe Frank in general and this piece specifically. If you want my stance on go go gettem capitalism and motivational psychology, just listen to "An Enterprising Man"

Also, for the topic of being qualified to do what you attempt, try listening to "Ascent to K2" from Joe Frank. If you make a free acct on his site you can find this one in the online stuff.

Ya'll come and give us your opinion.

Agree with Frank. There is no use in letting Barney tell us where he lives, if we want to use the map gadget to choose a good place for a meatspace meeting. So this particular wave, given its intent, should have been restricted to the group. In many cases, I think it could be harmless to open a wave to the public: the crowd can contribute good things, we all know that... But I still think that, by default, wave access should be restricted to group members. It would maximize the sharing of relatively private or "sensitive" information within the group. It would also help keeping the discussions on topic (side-tracking is very easy in all forum discussions and the more people you have in the conversation the more side-tracking you get). Now of course anyone in the group can invite anyone, even "Public" into the wave: just like anyone who has access to a private document can copy it and paste it on a blog or any public place.

Yes F1 (Francois, I will be F2)!! i think we can use the wave structures to keep things private and the fact that any of us can add anyone can be moderated by convention and the trust we have begun to build with each other. plus the reinforcement from the system, in that we all can see who has added whom. Plus the ability to delete participants will come along eventually. Thanks F1!!!

Server server model - not thin client - server Content is on owned server - published out with privacy and pay wrapper When you want to you can 'sell' content to services - you still control it they get it by call out Ajax left behind at presentation service We build reference front end Own the means of production ie a server Tyrant would make it illegal for anyone to own a server (printing press) On the welcome page we can redirect new users for ISP and personal server host, take cut Just collect all the producers together and tell them they can own and control evthg they publish, period, then publishing services will come running Take a vig on the pay wrapper /kdl

note that all elements of this model (structure (relations and aspects), content, presentations) have a privacy and value exchange wrapper on them and can be 'bought and sold' using a value exchange model, this may be everything from rick/frank/twain agreeing to exchange content for content straight up to a start up firm valuing all aspects of contribution to the start up, including things like commitment, deliverables, ip, validation, ideas etc.

safe of gold...gold is for suckers!! i have a safe full of CHOCOLATE!!!! Serious though, i see the structure and i am becoming more enamored with the concept.