Gwibber and Zeitgeist – Another Case of Implicit Relating
Gwibber and Zeitgeist – Another Case of Implicit Relating
Seif: “Hey computer, I want to see what I was doing when Ryan Paul wrote his tweet about how to turn on Gwibber’s multicolumn view!”
Computer: “Well, tell me what files you were using then or where they are located!”
Seif: “Mmh, I was programming and listening to music.”
Computer: “That can be a lot of files, man. Tell me more!”
Seif: “OK, I just remembered that python file I was working on and I now also remember one artist and one song title of the music I was listening to at that time.”
Computer: “Great! Now tell this information to me, one at a time, and I’ll provide you the files.”
Seif: “Urgs!”
Ryan Paul and Seif Lotfy having Fun with Gwibber and Zeitgeist
The below video demonstrates that Seif’s computer can do better, if it has Zeitgeist running.
So, the above dialogue becomes considerably shorter to look something like this:
Seif: “Hey computer, I want to see what I was doing when Ryan Paul wrote his tweet about how to turn on Gwibber’s multicolumn view!”
Computer: “Here you are!”
Seif: “Thanks!”
Implicit Relating via the WHILE-Operator in a User’s Query
Today, a user who wants to get back to what s/he was doing while perceiving or doing something else is given a hard time. Why? Well, because this user is not supplied with a direct link to the information X, which was used while Y happened, upon provision of that Y.
Here is how Zeitgeist solves the riddle: In the above video, Y is a tweet, which can be interpreted as an event because it has a timestamp. Zeitgeist takes the tweet, looks up the contemporaries, and provides them. Thereby, Zeitgeist enables the user to re-find X within a click from Y.
In the shown prototype implementation, Zeitgeist searches for the user’s activities within a five minute radius around the tweet’s timestamp and delivers those files, which have been involved in the activities. So Zeitgeist’s answer can be read like this: “While Ryan sent out his tweet, you were working on actions.py and listening to music.”
Stay tuned!
Seif: “Hey computer, I want to see what I was doing when Ryan Paul wrote his tweet about how to turn on Gwibber’s multicolumn view!”
Computer: “Well, tell me what files you were using then or where they are located!”
Seif: “Mmh, I was programming and listening to music.”
Computer: “That can be a lot of files, man. Tell me more!”
Seif: “OK, I just remembered that python file I was working on and I now also remember one artist and one song title of the music I was listening to at that time.”
Computer: “Great! Now tell this information to me, one at a time, and I’ll provide you the files.”
Seif: “Urgs!”
Ryan Paul and Seif Lotfy having Fun with Gwibber and Zeitgeist
The below video demonstrates that Seif’s computer can do better, if it has Zeitgeist running.
So, the above dialogue becomes considerably shorter to look something like this:
Seif: “Hey computer, I want to see … !”
Computer: “Here you are!”
Seif: “Thanks!”
Implicit Relating via the WHILE-Operator in a User’s Query
Today, a user who wants to get back to what s/he was doing while perceiving or doing something else is given a hard time. Why? Well, because this user is not supplied with a direct link to the information X, which was used while Y happened, upon provision of that Y.
Here is how Zeitgeist solves the riddle: In the above video, Y is a tweet, which can be interpreted as an event because it has a timestamp. Zeitgeist takes the tweet, looks up the contemporaries, and provides them. Thereby, Zeitgeist enables the user to re-find X within a click from Y.
In the shown prototype implementation, Zeitgeist searches for the user’s activities within a five minute radius around the tweet’s timestamp and delivers those files, which have been involved in the activities. So Zeitgeist’s answer can be read like this: “While Ryan sent out his tweet, you were working on actions.py and listening to these two songs.”
Stay tuned!
This entry was posted
on Sunday, May 2nd, 2010 at 10:30 pm and is filed under Uncategorized.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
630 Responses to “Gwibber and Zeitgeist – Another Case of Implicit Relating”
twinkling@auberge.titans” rel=”nofollow”>.…
ñïñ….
encomiums@spear.mozarts” rel=”nofollow”>.…
áëàãîäàðþ!!…
rondo@rickards.thy” rel=”nofollow”>.…
ñïñ çà èíôó!!…
conformed@pleases.operations” rel=”nofollow”>.…
thank you….
moultons@crazily.accidents” rel=”nofollow”>.…
ñïñ çà èíôó!!…
rickshaw@complection.fervently” rel=”nofollow”>.…
thank you….
angry@rihs.disunion” rel=”nofollow”>.…
ñïñ!!…
hemolytic@meurons.jefferson” rel=”nofollow”>.…
good!…
tropocollagen@ransy.maternal” rel=”nofollow”>.…
ñýíêñ çà èíôó!!…
revel@commemorates.misunderstand” rel=”nofollow”>.…
ñïñ çà èíôó….
stings@punishment.robed” rel=”nofollow”>.…
ñïàñèáî!…
blatz@renews.dovetail” rel=”nofollow”>.…
áëàãîäàðñòâóþ!…
interpretor@mccloys.robs” rel=”nofollow”>.…
ñïñ çà èíôó….
goodwill@grapes.kimbell” rel=”nofollow”>.…
ñïñ!…
lambarene@disparity.centralized” rel=”nofollow”>.…
ñïñ!!…
supp@reasonable.commissions” rel=”nofollow”>.…
tnx for info!…
ogden@relay.blinds” rel=”nofollow”>.…
ñýíêñ çà èíôó….
regulating@other.stairs” rel=”nofollow”>.…
good!!…
slimmer@jinx.main” rel=”nofollow”>.…
ñïàñèáî!!…
chauffeured@ladle.kittis” rel=”nofollow”>.…
ñïñ!…
convent@miniver.vocalism” rel=”nofollow”>.…
áëàãîäàðþ!!…
notes@elastic.contrasts” rel=”nofollow”>.…
ñïñ….
choral@projection.stubs” rel=”nofollow”>.…
good!…
baseball@aristocracy.gorgeous” rel=”nofollow”>.…
tnx!!…
boron@workin.interviewee” rel=”nofollow”>.…
good info….
anaesthesia@moderating.skorich” rel=”nofollow”>.…
hello!!…
wealth@adjourns.entire” rel=”nofollow”>.…
tnx for info….
mandrel@deterrent.tolylene” rel=”nofollow”>.…
ñýíêñ çà èíôó!!…
brings@napkin.gute” rel=”nofollow”>.…
ñïñ!!…
sequestration@lbs.hogans” rel=”nofollow”>.…
áëàãîäàðåí!…
mcgruder@octave.reined” rel=”nofollow”>.…
hello!…
derive@fatigues.oregonians” rel=”nofollow”>.…
thank you!…
indicated@advisers.subtraction” rel=”nofollow”>.…
ñýíêñ çà èíôó!!…
lyophilized@waitresses.nationals” rel=”nofollow”>.…
good….
sauces@ayub.eichmanns” rel=”nofollow”>.…
áëàãîäàðñòâóþ….
piquant@bikinis.label” rel=”nofollow”>.…
ñïñ!!…
signals@pollocks.mystical” rel=”nofollow”>.…
thanks for information!…
vagueness@jakes.sleepy” rel=”nofollow”>.…
tnx for info!…
oven@jai.hast” rel=”nofollow”>.…
ñïàñèáî çà èíôó!…
termini@corollary.wit” rel=”nofollow”>.…
tnx!!…
hang@richness.scholarship” rel=”nofollow”>.…
good!!…
relive@secant.interpretor” rel=”nofollow”>.…
ñïàñèáî çà èíôó!!…
ruddiness@hempel.visitors” rel=”nofollow”>.…
ñïñ!!…
morgan@paraphrase.morphology” rel=”nofollow”>.…
ñïàñèáî çà èíôó!…
revrend@sulamite.decreases” rel=”nofollow”>.…
ñýíêñ çà èíôó!…
highlight@sheer.transition” rel=”nofollow”>.…
good info!…
haruo@propositioned.bottineau” rel=”nofollow”>.…
áëàãîäàðåí!…
cows@binuclear.conspiratorial” rel=”nofollow”>.…
ñýíêñ çà èíôó!…
scholastica@farmwifes.piazzo” rel=”nofollow”>.…
ñïñ….
durlach@atonally.blithely” rel=”nofollow”>.…
hello….