#qi-hardware IRC log for Wednesday, 2014-04-16

DocScrutinizer05good morning (UGT)10:43
viricthis is late even for UGT10:46
viricI hope you had a good sleep (UGT) :)10:47
DocScrutinizer05mens? you missed me?10:48
viricno no, just greeting10:48
DocScrutinizer05Universal 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.html10:49
DocScrutinizer05we could discuss "enter channel"10:50
DocScrutinizer05whether that's a wide definition or particularly a client action10:51
sb0roh, where would you go to buy a 2.5mm thick PVC sheet in Berlin?11:16
wpwrakDocScrutinizer05: 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:34
DocScrutinizer05wpwrak: mhm. maybe something I can ponder about during my next few beers12:50
DocScrutinizer05any hints what exactly the conversation would sound like?12:50
wpwrakthe discussion about the "always on" vs. "entering a channel" or the discussion of dietary choices of sparrows ? :)13:44
DocScrutinizer05the latter14:23
DocScrutinizer05I fail to see the analogy14:24
DocScrutinizer05maybe I would when I could imagine that conversation of old men about sparrows14:24
Action: DocScrutinizer05 has a certain suspicion that 99% of own statements are similarly obscure to 99% of audience14:27
DocScrutinizer05according to my own approach that considers communication always consisting of a transmitter, a channel, and a *receiver*14:28
DocScrutinizer05and transmitter should take receiver's "encoding" into account14:29
DocScrutinizer05which basically forbids one-to-many conversations when the subject gets complex14:31
DocScrutinizer05at least I think I'm not exactly good in such 1:many encoding14:31
DocScrutinizer05while 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 receivers14:38
DocScrutinizer05(e.g. by dissecting the statement and not considering it as holding any valuable data)14:40
DocScrutinizer05situation gets worse when neither of multiple receivers is aware about to whom and how many receivers the info been encoded14:43
DocScrutinizer05commonly (incorrectly) attributed as "lacking context"14:44
DocScrutinizer05probably too much thinking about the underlying principles completely ruined my actual communication skills ;-P14:54
wpwrakhmm, so you can go on a date but you doubt you'd be able to organize a flash mob :)14:56
DocScrutinizer05organizing 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 ambiguous14:58
DocScrutinizer05IOW: the encoding is universal14:59
DocScrutinizer05maybe the actual data for time and location is the part that holds most ambiguity here15:01
DocScrutinizer05sender should carefully consider format and system in which those data bits get encoded15:02
DocScrutinizer05AM/PM or 24h format. Which TZ. Which accuracy15:02
DocScrutinizer05location is even more complex15:03
DocScrutinizer05a lot of competing systems to describe a location15:03
DocScrutinizer05would probably need redundancy, so every receiver can pick the system he likes best15:04
DocScrutinizer05picking up on original subject, I consider "enetring the channel" to be a rather fuzzy definition, and probably fuzzy on purpose15:07
DocScrutinizer05for the flash mod, the channel itself is the major problem15:11
--- Thu Apr 17 201400:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!