Think Together

// Would it be possible to make it so, that other organisations could set up membership-based websites on top of Ooo

Yeah, [Ruta], in fact it is very possible to make a category into a domain, like medium.com has been domain, allowing users to set their domain, however, sharing single database. I'm still considering best initial way to implement communities functionality, and think about it. :)

// create "oo" communities functionality

Hello! I'm curious about this. Would it be possible to make it so, that other organisations could set up membership-based websites on top of Ooo and pay a monthly tax (based on their revenue from memberships) to 0oo for providing such infrastructure? What would be customisable? Could it be made so, that these views - Homepage, User Profiles, Project page - are customisable?

I'd be interested in this as KOKONO. Also, if clear documentation provided on how to customise the design (even for design/development colleagues), I believe many micro organisations who facilitate online learning and online communities would be interested in this too. At the moment, tools like Discord, WordPress, Kajabi, Circle, ... are used.

Actually, this would not require the problems be in-game, it is enough that click-through is hard, and those, who are able to get thought, get rewarded (think: "click-through prizes"), essentially, just a new type of conversion, but potentially with a requirement for specialized widgets to assist the entry of complex answers, and a verification end.

I'm thinking, now that we have 0oo.li/blog for news as community blog, we could try to produce interesting and more abstract content just by stripping existing news from their proper nouns...

Like an opportunity engine, so we can filter those opportunities (advices), right? However, usually, opportunity engines are not free. For example, silos charge for matches. Ideally, we could just add ratings and look up for matches, occasionally with anonymized identities (when surprise is the expected product).

Umm, however, how would this really work? This idea doesn't have substance, it's more like a wishful thinking, which I agree with, but it more belongs to the Questions then.

I'd like to feed all my data into a machine. All my skills, talents, abilities, personal demographics. Have the computer whizz on various opportunities for me based on my skills. The data could be community submitted. I call it advice engine.

P.S. I enjoy using my project space as a Twitter feed, sharing puzzles, which will eventually become a final product. I'd like to see other creators puzzles too! That -- interacting with puzzles -- sparks cocreation.

Storyline update!

"We are all Moms". The book ends when a character realises they are a Mom, when they raise brainchildren through the symbiosis with Life, and thus a character becomes the Universe*.

*Symbiosis with life as exploration input and creation output.

**Observer and observed .. creating reality

Notes:

Every moment we birth life (no matter genders or other boxes) when a constructive thought leads to life, while destructive - to death as decay, compost. And so, there is a dance of life and death! Regeneration as a micro habit of how we think and where thinking leads us.

So the storyline goes from escape, solo to togetherness to realise that we are her (as a metaphor for creativity as a value).

Right... Since computers are good at storing and sifting through lots of data, the only thing we humans need from them, is discovering, collecting, weighting, and sorting opportunities with respect to world's things, regarding the desired futures ;)

Where are those perfectly matched: friends, partners, projects, products (services), work and help opportunities, that optimize value of our time?

I think, specific low level algorithms are already mostly there, and the main question is in scaling the higher level of their organization, data and computing resource sharing: anyone can run a closed silo to answer some important questions for fees, but transcending silos with deeper public resources is challenging.

// Visual Basic [...]

It was for programmers, not for end users. What this idea is about, is a tool for end users, obsoleting app UIs, so in the future apps don't need their own UIs.