10:43 <DocScrutinizer05> good morning (UGT)

10:46 <viric> this is late even for UGT

10:47 <viric> I hope you had a good sleep (UGT) :)

10:48 <DocScrutinizer05> mens? you missed me?

10:48 <DocScrutinizer05> means*

10:48 <viric> no no, just greeting

10:49 <DocScrutinizer05> Universal Greeting Time. Created in #mipslinux, it is a rule that states that whenever somebody enters an IRC channel it is always morning, and it is always late when the person leaves. The local time of any other people in the channel, including the greeter, is irrelevant. http://www.total-knowledge.com/~ilya/mips/ugt.html

10:50 <DocScrutinizer05> we could discuss "enter channel"

10:51 <DocScrutinizer05> whether that's a wide definition or particularly a client action

11:16 <sb0> roh, where would you go to buy a 2.5mm thick PVC sheet in Berlin?

12:34 <wpwrak> DocScrutinizer05: yes, the concept of "entering a channel" sounds a bit like old people talking about the flocks of sparrows feeding on horse manure (from all the horse carts in the streets)

12:37 <eintopf> hi

12:50 <DocScrutinizer05> wpwrak: mhm. maybe something I can ponder about during my next few beers

12:50 <DocScrutinizer05> any hints what exactly the conversation would sound like?

13:44 <wpwrak> the discussion about the "always on" vs. "entering a channel" or the discussion of dietary choices of sparrows ? :)

14:23 <DocScrutinizer05> the latter

14:24 <DocScrutinizer05> I fail to see the analogy

14:24 <DocScrutinizer05> maybe I would when I could imagine that conversation of old men about sparrows

14:28 <DocScrutinizer05> according to my own approach that considers communication always consisting of a transmitter, a channel, and a *receiver*

14:29 <DocScrutinizer05> and transmitter should take receiver's "encoding" into account

14:31 <DocScrutinizer05> which basically forbids one-to-many conversations when the subject gets complex

14:31 <DocScrutinizer05> at least I think I'm not exactly good in such 1:many encoding

14:38 <DocScrutinizer05> while in a 1:1 communication the receiver usually decodes and acts on the info transported exactly like intended (e.g. by suggesting a number of possible meeting dates), even a 1:2 communication often causes massively differing not exactly planned reactions on same info with #2 of the two receivers

14:40 <DocScrutinizer05> (e.g. by dissecting the statement and not considering it as holding any valuable data)

14:43 <DocScrutinizer05> situation gets worse when neither of multiple receivers is aware about to whom and how many receivers the info been encoded

14:44 <DocScrutinizer05> commonly (incorrectly) attributed as "lacking context"

14:54 <DocScrutinizer05> probably too much thinking about the underlying principles completely ruined my actual communication skills ;-P

14:56 <wpwrak> hmm, so you can go on a date but you doubt you'd be able to organize a flash mob :)

14:58 <DocScrutinizer05> organizing a flashmob is simple, the subject's complexity is low and the details are pretty sharp defined in the "common dictionary"

14:58 <DocScrutinizer05> "be at location X at time Y" isn't too ambiguous

14:59 <DocScrutinizer05> IOW: the encoding is universal

15:01 <DocScrutinizer05> maybe the actual data for time and location is the part that holds most ambiguity here

15:02 <DocScrutinizer05> sender should carefully consider format and system in which those data bits get encoded

15:02 <DocScrutinizer05> AM/PM or 24h format. Which TZ. Which accuracy

15:03 <DocScrutinizer05> location is even more complex

15:03 <DocScrutinizer05> a lot of competing systems to describe a location

15:04 <DocScrutinizer05> would probably need redundancy, so every receiver can pick the system he likes best

15:04 <DocScrutinizer05> he/she

15:07 <DocScrutinizer05> picking up on original subject, I consider "enetring the channel" to be a rather fuzzy definition, and probably fuzzy on purpose

15:11 <DocScrutinizer05> for the flash mod, the channel itself is the major problem

15:11 <DocScrutinizer05> mob*