Yesterday, I was in the process of looking for a fitting logo for my new-established minikin company. Me thought it was an interesting idea to look for a Unicode / UCS character that would be fit to represent the logo I had in mind. So I grabbed the gucharmap tool and looked for such a thing. Sad enough, there was no such character in all the 100.000 Unicode chars I searched through. But I saw some other interesting Unicode alongside and I thought you readers might have fun with ’em too:

character image character
code point
name
comment


U+0B87
TAMIL LETTER I
Ain’t this crazy? Looks like a snake trying to mimic a pretzel.

U+0BEB
TAMIL DIGIT FIVE
A new Version of “@”, with a Greek “pi” in it rather than an “a”.

U+0E5B
THAI CHARACTER KHOMUT
Just a letter, but … hihihi. A snake contributing to modern art. It’s the funniest character I know of. It is used in Thailand to mark end of chapter or document.

U+2627
CHI RHO
The Christogramm. Didn’t know it’s also in Unicode. Might come in handy some time 🙂

U+A00E
YI SYLLABLE UOP
A real smiley … but oh, it’s pronounced “uop”.

U+17D9
KHMER SIGN PHNAEK MUAN
Khmer sign that indicates the beginning of a book or a treatise. See also the next character.


U+17DA
KHMER SIGN KOOMUUT
Khmer sign that indicates the end of a book or treatise, used in conjunction with the previous one. Interesting idea, you Khmer people … .

U+20E0
COMBINING ENCLOSING CIRCLE
BACKSLASH
A special thing: a combining character that means “prohibition”. You can print it on top of everything else to prohibit it. Prohibit. Some examples, but I don’t known if your browser will show them correctly:

  • a prohibited lowercase “a”: a⃠
  • divorce prohibited: ⚮⃠

U+25A7
SQUARE WITH UPPER LEFT TO LOWER
RIGHT FILL
Wherefore do I need this? If you do, we could exchange some characters. Perhaps you have some I need … .

U+2668
HOT SPRINGS
Partial Java logo, I think.

U+26AF
UNMARRIED PARTNERSHIP SYMBOL
Though I think that marriage is the only valid and the best form of sexual partnership, I like this sign. I could hijack it to mean other forms of  partnership, namely “community”. And use it in the logo of my yet-to-be-founded missional mobile community … .

U+27E1
WHITE CONCAVE-SIDED DIAMOND
This means “never”, as a mathematical modal operator; I now just need to find a Unicode character for “day” or better “everyday” and I can write my blog’s name with only two letters.

U+3293
CIRCLED IDEOGRAPH SOCIETY
This is used to mean “company”. Cool corporate logo element in Germany because nobody understands it!

U+32AF
CIRCLED IDEOGRAPH ALLIANCE
Also a possible logo element for community logo.

U+32AD
CIRCLED IDEOGRAPH ENTERPRISE
Looks like (and probably is) an encircled little house … cut graphic, like it. Cool for corporate logos … .

Start date: 2008-01-18
Post date: 2008-01-19
Version date: 2008-01-20 (for last meaningful change)

Für meine mobile Wohnung und Weltreise plane ich zur Zeit fleißig an einem geeigneten Basisfahrzeug. Das treibt manchmal komische Blüten. Vor einigen Wochen z.B. habe ich einen ganzen Abend damit zugebracht, im Internet nach einem Amphibienfahrzeug als Basisfahrzeug zu forschen. Gerade räume ich meine Dokumente wieder auf, und dieser Abschnitt fliegt raus. Vielleicht kann ja jemand anders (… reicheres) damit etwas anfangen. Also, hier meine Ergebnisse.

Vorteile

Mit einem amphibischen Expeditionsfahrzeug sind überflutete Brücken usw. kein Hindernis mehr, und Flüsse und Küstenlinien können als Verkehrswege in unwegsamem Gelände verwendet werden, z.B. im Regenwald. Außerdem kann so die gesamte Welt außer dem Übergang nach Amerika selbständig bereist werden, nämlich wo nötig durch »Inselhopping«. (Dadurch kann man auch interessante unbewohnte Inseln erreichen …).

Einführung

Eine erste Einführung gibt Wikipedia: http://de.wikipedia.org/wiki/Amphibienfahrzeug.

Die beste Sammlung existierender Amphibienfahrzeuge: http://www.amphibiousvehicle.net.

Für ein amphibisches Expedititionsfahrzeug wird ein Lkw als Basis benötigt. Weltweit wurden nur sehr wenige amphibische, geländegängige Lkw gebaut, und von diesen sind manche völlig veraltet, wurden durch Demilitarisierung unbrauchbar (z.B. M520 »Goer«) oder sind im Straßenverkehr nicht brauchbar (wie M520 »Goer« wegen Überbreite, oder Alvis Stalwart (vgl. auch die englische Wikipedia) wegen fehlenden Differentialen.

Ergebnis: ZiL-4906

Unter allen in 2007-06 auf amphibiousvehicle.net (inkl. der In Production Vehicles Seite) gelisteten Modellen wurden im Wesentlichen drei gefunden, die als Basis für ein amphibisches Expeditionsfahrzeug geeignet sind:

Andere amphibische geländegängige Lkws

Today, some funny image happened to me when trying to improve the contrast of some digital facsimile scans for a neighbor of mine. Dear neighbor, can u guess in a comment the worksheet number where this image belongs to? And to the other guys and gals out there: what might that be? Jus’ crazy, isn’t it. Here is how I made it, with the “local adaptive threshold” option of the nice free software tool  “convert” from ImageMagick:

convert -lat 30×30+20% infile.jpg outfile.jpg


Start date: 2007-12-07
Post date: 2007-12-07
Version date: 2007-12-07 (for last meaningful change)

Wie wäre es mit einer neuen sportlichen Disziplin: dem Wikipedia Racing 🙂 Ein Protokoll meiner ersten (heutigen) Rally findet sich unten. Warum sowas? Also:

Ich beobachte dass meine Gedanken (z.B. in Blog-Posts) sich fast ausschließlich aus Verbindungen dessen ergeben was ich weiß, genauer: was ich über Funktionszusammenhänge weiß, nicht über einzelne Fakten und Details. Eigentlich weiß ich aber nicht viel über Funktionszusammenhänge: meine Gedanken könnten weitaus besser werden wenn ich hier mehr lerne. Das ist einfach: z.B. 100 Stunden in der (englischen) Wikipedia lesen.

Insbesondere wird dieses Lernen auch helfen, mich besser ausdrücken zu können, und so auch wieder, besser denken zu können: ich erhalte neue Wörter (bes. aus Wikipedia), und damit auch neue Analogien. Interessante neue Konzepte und Funktionszusammenhänge die ich heute aus Wikipedia gelernt habe:

Interessant waren dabei nicht die Details (die ich jetzt schon wieder vergessen habe und auch wieder nachschlagen kann), sondern dass mir Wikipedia zu einem fundamentalen Verständnis von Proteinstruktur, DNA-Wirkungsweise, Karten (als Manifolds = mathematische Mannigfaltigkeiten) und der groben Gliederung der Mathematik (gar nicht so wild wie ich dachte) verholfen hat. Immer wenn man die äußeren Grenzen eines Bereichs kennt (wie jetzt die der Mathematik) verliert ein Bereich viel von seiner Faszination: außer in »model theory« beschäftigt sich die Mathematik eben doch mit sehr »bedeutungslosen« Dingen wie Zahlen und Ordnungsbeziehungen, mit sehr primitiven Grundelementen.

If you like being creative, you add additional problems to your
life:
how do you manage your ideas, how do you sort and archive and utilize
them efficiently? I’ve discussed this topic lately and promised there
to write something about my current style of idea management. So, here
it is.

Principles

  1. Esteem and cherish your ideas. If you don’t, you will
    become less creative. If you do, your creativity rises. You do so by at
    least writing down all your ideas, even those which deem you
    nonsense. And by publishing those ideas on the internet which don’t
    seem fit for any other utilization. As known from brainstorming
    techniques, filtering ideas too early blocks good thoughts to arise and
    being uttered.
  2. Divide into ideas you pursue and those you don’t. Time
    is a rare resource, so don’t give yourself to the illusion that you can
    put more than 5% of your ideas into practice. After the initial idea
    came to you, decide if you want to pursue it or not. Those you want to
    pursue will be put into documents where topically related ideas reside
    and begin to form a “grand whole”. Those you don’t want to pursue are
    best put into a simple chronological document.
  3. Freely you got, freely give. It is totally
    understandable that people are hesitant to publish their precious ideas
    to everybody – just as with stuff you have lieing around, it might come
    the day where you need exactly that idea. From experience, I can
    contribute that this day never comes: with most ideas, it is obvious
    right away if you have a realistic chance to utilize them commercially.
    If this isn’t the case, there’s no harm in publishing them: you can use
    your idea anyway, sometimes even commercially, just not for
    patenting it. Ideas did not cost you anything, they came to you … and
    by publishing “unneeded” ideas on the internet, you give people the
    chance to find an inspiration or idea they need.
  4. Accept work in progress. Idea management can become a
    stressy issue if you are perfectionist and want all your ideas reside
    in perfect verbalization and perfectly elaborated. But memorize that
    your idea documents are mainly meant to keep you from forgetting about
    them … those ideas you eventually put into practice don’t need
    documents anyway, as they became real and tangible. Even documents with
    orchestrated collections of many ideas are better seen as “draft under
    development”, as it takes too much time to keep up higher standards of
    order. I made good experiences with using a paragraph style for to-do
    sections, placing in them just notes to memorize later what I mean.
  5. Avoid redundancy. Every idea has its perfect place …
    some in the chronological archive of ideas you don’t pursue, some in
    other documents, depending on the kind of idea. Under all
    circumstances, avoid redunancy: no idea should go to two places, as
    later additions to one copy would create inconsistency.
  6. Use multiple forms of note-taking for different situations.
    Of course, the ideal way is to immediately store the idea in the place
    where it should go, but this is only possible whenever you sit in front
    of your computer or have your computer nearby. For situations where you
    are on the road or in other people’s home, use a PDA to take quick text
    notes. Be disciplined and do not use handwritten notes, neither on
    paper nor on screen, except for diagrams – as you’d need to transcribe
    them later. For situations where note-taking must be very quick, use a
    digital dictaphone – you need to transcribe your audio notes later, but
    at least your ideas did not get lost.
  7. Let ideas mature. Among those ideas you want to pursue
    will be some that can be orchestrated to bigger ideas. These ideas deal
    often with issues in your areas of special interest. It is a good idea
    to be patient (even for months, sometimes years) before putting ideas
    into practice, as it happens more often than not that your initial
    ideas are overthrown by revisions or revolutionary ideas. Before
    starting to realize your ideas, overthrowing can be done with ease and
    relatively effortless.

My current technical implementation

My system currently consists of the following components. I must
admit that it is a rather improvised system far from working really
efficiently, and I hope to replace this system with one that is
designed from ground up. But anyway:

  • PC. I use a notebook, so that I can type ideas directly
    into the right place even when I’m in other places for some days,
    taking my notebook with me.
  • PDA. I use a Sony Clié PEG-TG50 (at eBay for 50-60 EUR
    currently) to take voice and text notes on the road. I experimented for
    some weeks now what is the best solution, and arrived at this: where
    necessary, I take voice notes and tranfer the .wav files to a folder on
    my PC’s desktop for later transcription, which might be delayed for
    some days or weeks; where possible, I take text notes, using the to-do
    list of the PDA for that. Compared to the text note program of the PDA,
    this has the enormous advantage that synchronizing (better: moving to)
    with my PIM software at the PC creates tasks there. That way, I never
    forget to move the text notes to the right place. By the way, I use the
    Linux software kontact from KDE as PIM software, with korganizer for the
    to-do list part. I tried the Gnome alternative but found no better
    solution than kontact yet.
  • Inventions log. All the technical ideas I do not want to
    pursue go to a simple text file. It has no formatting as it does not
    need this: that’d complicate idea logging and perhaps take so much time
    that it is no longer fun to record every single idea. I publish my
    inventions log from time to time on the internet as PDF and text files.
    The first publication was done in my blog in the post “Read
    these 1364 inventions
    “. I know that there are web portals that are
    much better for making your inventions known, but again: if I had to
    enter every of these 1300+ ideas into a web form, it’d be no longer fun
    and I’d probably stop collecting ideas.
  • Tasks. All ideas for things I want to do go into my
    kontact to-do list, including all ideas I want to realize (or at least
    references to them). The most efficient way to order them is not to use
    categories (to much clicks …) but instead, to start the task title
    with a hierarchical, colon-separated list of keywords. Then, simple
    alphabetic ordering of the taks gives a good topical overview of what
    tasks are open yet (and don’t have a due date assigned). In my case,
    task titles might start e.g. with “Homepage: Blogging: Blog-Post:
    […]” or “Homepage: Blogging: Software: […]” or “Computer: new
    installation: […]” or “Fitness: […]” or “Job: […]”. Whenever I
    decide that I don’t want to realize a specific task any longer, it
    becomes a subtask of the task “idea store”. That way, it’s out of my
    way without deleting it.
  • Blog post drafts. Many of my ideas deal with upcoming
    posts for my blog. I collect them in the description part of tasks in
    my kontact to-do list. When the  draft has matured and integrated
    many ideas already, I write the post, reordering and reworking the
    draft content and then publishing it. I found it a helpful practice to
    verbalize as much as possible as tasks in kontact’s to-do list. This
    makes it a central and general solution and you need to search in fewer
    places when you don’t know where a specific idea has gone.
  • Mindmaps. Mindmapping software was introduced to me by a
    brother of mine, and I became a big friend of it. I use the software freemind, a very well
    developed and efficient tool with good import and export filters. All
    things that are just considerations and information but no concrete
    tasks go to mindmaps. Currently, I have the following mindmaps:
    • identity mindmap (who I wanna be and have some day, and the
      long-term steps in that direction)
    • ideas around intentional community
    • job organization
    • mindmaps for concrete jobs I’m involved in
  • Computer FAQ. When working with computers, it is very
    handy to document solutions you’ve found, including command snippets
    for later copy&paste. I think that a simple text file that contains
    simply a collection of questions and answers is the most efficient
    alternative to use here. To find a solution I once worked out, I use
    the search function and type in a specific keyword.
  • Specific realization documents. While realizing bigger
    ideas, you need more specific means to orchestrate your thoughts and
    ideas. What is adequate here depends completely on the kind of ideas
    you’re working on. Try to find a ergonomic, single structuring element
    to be used for the whole document – this makes it easy to insert new
    thoughts and ideas. One example: I’m currently developing a personal
    equipment that contains everything necessary from IT to clothing, in
    most lightweigth and compact form. The structuring element I use for
    this document is a commented packaging list.

Towards the ideal system

You see that my current idea management system is quite heterogenous
and unintegrated, and therefore not really efficient. There is an idea
in my mind how this could change, but I’m not aware of any existing
software that I could use for that purpose. Here is what it would need
to do, in my opinion:

It is a general “think support software”, providing all the
externalizations which help in intensive brain work. Especially, it
must allow to work on many larger ideas at the same time, adding to
them whenever new thoughts arise, over an extended period of time. This
system should need no synchronisation at all, i.e. you’d take your one
and only PC with you everywhere you go. That’s possible with an UMPC. The software would
provide a generic management of idea artefacts, including voice, text
and graphic notes, and would offer “pipelines” to convert / transcribe
and move the fragments until they arrive at their destination places.
You could use even very short, previously unuable free and latency
times to do your idea management with that software, so idea management
would not add more stress to a busy life. To that end, the software
must be freehand usable, e.g. by voice commands, voice recording and
speech recognition when driving car. And for those people who are
engaged in writing scientific texts, a literature management system
needs to be included, featuring the documents in full-text, digital
highlighting etc..


Start date: 2007-11-11
Post date: 2007-11-11
Version date: 2007-11-11 (for last meaningful change)

Well folks, I need to communicate better. For years, I want some
sort of people to understand and accept some elements of my lifestyle,
but was not successful. They even cannot see what I’m talking about, or
what might be the sense. So I need to communicate better, and will
train this in this post somewhat. For example, I want people to
understand my “technical approach” to many (not all) problems in life.
So, what is the technical approach, communicated in a way that
non-technical people will understand, and so that they get a chance to
accept what is said.

The technical approach is whenever things are esteemed more
important than people. But this is always for a limited time, and only
because people decided beforehand that it should be that way.
For example, whereever people decide that they want to have / build /
create / modify something, the technical approach is about
getting this done the most efficient way. At times, the practical
execution of this approach might seem extreme and strange to socially
minded people; so it’s important for tham to keep in mind that it’s
just about what people wanted.

Doing things the technical way exhibits some common characteristics:

  • You must be interested how things work, not just how you can deal
    with people.
  • While in the technical area, people have to adapt to technology
    and, at times, obey technology. For example, to extend a software
    system, you need to use the programming language it was written in, not
    the one you are enthusiastic about.
  • When interfacing with technology, it is best to work without
    emotions, “mechanically”, just like the technology itself. For example,
    nothing gets better if you get impatient with technology and throw it
    against the wall. Likewise, fear of destroying something blocks you
    from learning more about technology.
  • At times, even the interfacing between people should be done in a
    “technical way”, without emotions and typical expressions of humanity.
    To get things done, it is in most cases the most efficient way if you
    behave as technology would. For example, military forces use a special
    “command language” to communicate with each other in a tank and between
    tanks over radio systems. Here, it is prescribed what words to use for
    what purpose, and misunderstandings are greatly limited that way.
    Abstractly, this expresses that the “thing” of gaining victory in a
    fight is more important than the people who are involved in it.
  • You must judge problems the technical way. When dealing with
    people, the importance of (social) problems is measured by each one’s
    subjective measure, and then it is negotiated what is to be done. When
    dealing with technology, the importance of (technical) problems has to
    be measured by objective, technical measures: according to its effects
    on technology.

Start date: 2007-10-19
Post date: 2007-10-20
Version date: 2007-10-20 (for last meaningful change)

I don’t wanna sound proud and I do.
I’m building my own world right now.

A world without houses, but with homes.
A world without streets.
A world without passenger cars.
A world where 4-10 people live on 13m², with a living room of 148,939,100,000,000 m².
A world where one can work from anywhere in this living room.
A world with a space station moving in this spacy living room.
A world without furniture.
A world without DVD player, desktop PC, notebook, PDA, TV, alarm clock, mobile phone, landline phone, SIP phone, dictaphone, remote controls, MP3 player, stereo music equipment.
(That’s due to convergence.)

A world with brothers and sisters around, not just acquaintances or “just” family or just nobody.

A world where you know your Father and why you are around here.

If you are interested, keep tuned.

Some day, a HowTo will appear here which explains how you can build such a world. It has 90+ pages now and needs some more 🙂

Update as of 2011-05-09: The “HowTo” finally made it online and can be found at my “Documents: Main” page as the EarthOS document. Note that it’s called “idea pools” as I simply lack the time to finish and polish all that … . If you like the idea, check out Open Source Ecology, a group pursueing a similar approach, but they got practical already.