“To die with elation is a crappy way of dying… A warrior dies the hard way. His death must struggle to take him. A warrior does not give himself to it.”
Carlos Castaneda

Tales of Power

On Ceptr and Wagn and WordPress

n

This post, in addition to its subject matter, is offered as an experiment / demonstration for:

  1. This format of communication / expression (even though it isn’t published where it should be) as having intrinsic value as a collaborative tool.
  2. Coordinated, distributed and asyncronous work while potentially reducing the need for yet another meeting (face-to-face or online).
  3. If this was discussed in (yet another) meeting, the contents may have not made it into this written form and been available only to the participants of the meeting,
  4. That the written and published form creates a referencable / sharable / discussion point resource for others who would not have attended the (yet another) meeting.

This is a followup to a conversation with Arthur and Jarod about creating a collaborative work (codenamed: make.ceptr.org)

Personally

I’d like to clarify that in an ideal situation I would prefer to not get involved “under the hood”. I enjoy applying these tools more than creating them. I’ve been using WordPress for 10 years and have formed a satisfactory relationship with it, in that empowers me to express myself and create things I’d like to see in the world (that no one else has created or will create for me). Given that there aren’t technical resources available in the Ceptr team, I am offering to create what I can.

Wagn

I am curious about Wagn and what it can do. I apperciate the approach it takes and maybe in another context (not after a year of challenging coding work) I would be interested in exploring what can be done with it. However it feels to me like a technology and not yet a usable tool. I can imagine that for someone who is closer to a developer mindset it is more of a tool. But I am not of that mindset.

Lets assume that an in depth suitability analysis of Wagn as a technology to create a clearly outlined solution were conducted and gave a clear resounding yes. If I am the one who has to now create with it I would have to enter a learning curve which 1) I am not interested in and 2) would divert energy from creating a solution for Ceptr, to investing in Wagn.

I do, however, want to dedicate a few more sentences to Wagn as a technological manifestation.

Solutions and Technologies

Wagn highlights a fault-line I have been observing for many years in IT and more endemically in open-source. A technology is not a product. An engine is not a car. Technology is only one dimension of creating good applications that provide valuable solutions. RSS was an oh-so-simple protocol/technology for connecting people that wasn’t properly productized. Facebook did fill that void with an exploitative product.

I would like to avoid this shortcoming in Ceptr.

I realize that Ceptr & Holochain ARE technologies. Ceptr & Holochain are on par with developing an operating system like Linux. For Linux to “succeed” it took many others who built upon it distributions that were targeted for more specific contexts / applications.

My understanding is that a similar view is currently shaping Ceptr & Holochain. That others will adopt Holochain and build solutions upon it. But I am not convinced that can happen, or that if even if it did, that it would necessarily be be a good thing.

Yes Ceptr can be framed, for example, as a Blockchain alternative. But, in my mind, that isn’t true. Ceptr is designed for a different mindset … heck … lets say it out loud … to a different heart-set. Those who see and embrace it as a Blockchain alternative will not be manifesting that different heart-set. They will be applying pressure to get Holochain to do their bidding. The question is what will give? Will Holochain bend their mind-set and bring them closer to its mindset? Or will Holochain itself be bent to be framed into their expectations?s

This is why I believe that it is up to us, the makers of Ceptr & Holochain to also create applied solutions to really give them life. When we do, please, please, please … lets avoid making Wagns.

For anyone interested in reading more on this I recommend The Inmates are Running the Asylum by Alan Cooper.

WordPress

I would like to keep this short:

  1. WordPress, in addition to being an application / product has been, for me, a vivid example of distributed collaboration. I have enjoyed watching (though not as an active participant) how it grew as a collaborating community. WordPress, to a large extent, was used to create itself. I would like to bring that morphic field into Ceptr.
  2. Part of what I bring with WordPress is … what I bring with WordPress … the way I personally create with and use it. I would like to try to demonstrate the difference between engineering a theoretical process vs. a gradual unfolding and emergence of process. This can happen when we enter a cycle in which 1) a tool is being used; 2) the usage provides feedback; 3) the feedback can be converted in short iterations into changing the tool itself.
  3. If the unfolding experience pleases us we can apply it with other online contexts (websites and what not) because WordPress can be used for those too.
  4. WordPress, in my experience, brings with it many subtle assets. If we opt to use it I will try to make a conscious effort to highlight them as we encounter them. This touches on what it truly takes to elevate a technology into a solution.
  5. WordPress is fully open and documented, lock-in to it comes not from it but from the gains and satisfaction of using it. It is not the Hotel California or Google … you can always leave.
  6. WordPress can potentially be an agile, living mockup-tool for us to experiment in what we want collaboration to look like … so that when the time comes we can be better informed about how to build alternatives in Holochain.

Actionables

  1. Review the beginning of this post and reflect on its format as a collaborative tool.
  2. Communicate contents to others who you feel are vested in the next question.
  3. Do you feel you have sufficient information to make a decision about using WordPress to create a collaborative work space? If not, what is missing?
  4. Do you want to move forward with this experiment?
This entry was posted in Ceptr, outside. You are welcome to add your comment