site_graphlogo
  -   Terms of Use and Privacy
Dream | Journal | Memory | Subject
site_graphlogo
  -   Terms of Use and Privacy
Dream | Journal | Memory | Subject

<<   <   >   >>

2019-10-27 | Journal | Too Complicated?

When I found my old entries, at Sean's insistence, and reconstructed my old journals last year, I never was able to find this entry:

It has been laying around in my home directory for years. It serves as both a reminder and as a symbol of loss of content due to my thrashing. This was one of the prettiest versions of my journal software. The entries were stored in a steganographic image using a routine I created of my own design. I enjoyed the feature of storing the article in an image, because it was easy to share an image as a journal entry, but it was kind of private at the same time. The harvesting engines of our online lives would find it difficult. It wasn't intended to be secure, just difficult. At that point I had tried for many years to get anybody to see the beauty of the journal. I figured that the reason I didn't get more interest is because my journal system was too complicated. Over the years I created 100 or so videos that tried to explain the journal system.

There are likely other factors to this, I understand now, besides assuming it was too complicated. First off, people don't have the time. Even when they do have the time, there are also issues when people don't understand a different idea. Through all of my ID/obscurity and other related technical features over the years of MCJ, I got the feeling that nobody really got it the same way. There were some good ideas in this particular journal design. One of the fabulous things that it allowed is that the main entry could be copy/pasted right into an email. The formatted text was utf-8, so you could gain tags and visual context easily. My mistake was in assuming anything at all based on the reception by those I knew. Interest has nothing to do with value. Understanding has nothing to do with value. If I thought it was beautiful, I should have continued along that route rather than abandon and go with the simplified interface. That is the reminder.

The thing that crystalized this for me a bit, is that I know that my ouroboros idea has value. It is good through history, and it is needed now. It will be needed during systemic collapse (of any system). It doesn't exist in the form I envision, yet. It is actually very simple, but, unfortunately, I will need to build the whole thing first before I can use it, because people in general will not be able to understand how truly simple it is unless I can show them. I really just want to implement these ideas somewhere in some IT shop, but now I have to build the bridge in order to land that job. The benefit of this approach is that I will have it fully documented as well, so the ideas can persist.

ouroboros mcj

Articles tagged with ouroboros on Mud Hut Club:

2020-06-15: Rogue Spread
2020-05-24: The Big Lie

Articles tagged with ouroboros on O.R.N.G.:

2019-08-07: Knowledge
2019-08-03: Bits of Tree
2019-06-27: Straight Down the Line
2019-05-19: Triple Tree
2019-05-18: Honeycomb Start
2019-05-11: Ouroboros Tree
2018-08-12: Data
2018-07-10: Woman Emerging from Manhole
2018-03-07: Braid of Life
2018-01-11: Train Circle
2017-11-05: Wu-Tang Clan
2017-10-23: proust
2017-10-11: risk of frameworks
2017-08-06: Finger Divine
2017-06-25: 1279 BC
2014-05-15: Circle
2010-11-02: Do you see?
2006-08-03: Information Markup

Articles tagged with mcj on Mud Hut Club:

2020-06-07: First Week & Jalapeños
2020-05-18: Climbing Reset

Articles tagged with mcj on O.R.N.G.:

2019-07-20: Roll On
2019-07-13: New CMS
2019-04-15: Malignant Punishment
2018-06-16: Are Images Like Amazon?
2018-05-09: Puzzling Glimpses
2017-06-23: Lingering in the Stairwell
2017-06-08: Blank Page
2016-11-28: Starting Overish
2011-05-21: Wireless MCJ
2011-01-17: Trouble in Mind
2010-11-19: New Release: MCJ 2.7.5
2010-08-06: Id Climb
2010-06-11: Future Share
2010-05-15: VMware Running
2009-07-10: Metaphors in the Open
2006-04-30: MCJ Push