1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 2<html xmlns="http://www.w3.org/1999/xhtml" > 3<head> 4 <title>twyric.com - the poetic side of Twitter</title> 5 <meta name="description" content="Twyric.com - display short lyric produced by Twitter users - by Christian Mähler"> 6 <meta name="abstract" content="Twyric.com - display short lyric produced by Twitter users - by Christian Mähler"> 7 <meta name="author" content="Christian Mähler - LeserEins.de"> 8 <meta http-equiv="content-type" content="text/html; charset=UTF-8"> 9 <meta name="keywords" content="Twitter,Lyric,Lyrics,Poetic,Haiku,Lesereins"> 10 <link rel="alternate" type="application/rss+xml" title="twyric RSS feed" href="http://twitter.com/statuses/user_timeline/15262971.atom"> 11 <link rel="stylesheet" type="text/css" href="/twyric.css"> 12</head> 13<body> 14<div id="spannendeinfos"> 15<table> 16<tr><td valign="top" width="300"> 17<a name="imprint"><h1>Imprint / Impressum</h1></a><br/> 18 <br/> 19Christian Mähler<br/> 20Weltzienstr. 20<br/> 2176135 Karlsruhe<br/> 22Germany<br/> 23Telefon: 0177-4451209<br/> 24<br/> 25E-Mail: christian [dot] maehler [at] lesereins [dot] de <br/> 26Blog: <a href="http://www.lesereins.de" target="ext">http://www.lesereins.de</a><br/> 27Profile DE: <a href="https://www.xing.com/profile/Christian_Maehler" target="ext">Xing Profile</a><br/> 28Profile EN: <a href="http://www.linkedin.com/in/christianmaehler" target="ext">LinkedIn Profile</a><br/> 29<br/> 30Other projects:<br/> 31<a href="http://twitter.com/selfreferential" target="ext">http://twitter.com/selfreferential</a><br/> 32<a href="http://www.twitterpark.com" target="ext">http://www.twitterpark.com</a><br/> 33 <br /> 34<a href="http://twitter.com/twyric">Follow @twyric</a> 35 36</td><td valign="top"> 37<a name="about"><h1>About</h1></a> 38Twyric = Twitter + lyric. Twyric is an experiment. It has no further meaning but providing a background for contemplation. 39<br/> 40Twyric combines lyric Twitter tweets with photos from flickr in real time. <a href="http://twitter.com/twyric">Follow @twyric ...</a> 41<p> 42<b>How is it working?</b><br/> 43We get all tweets with the hashtags #haiku, #twyric, #twly, #gedicht, #poesie, #lyric, #poetry, #limerick, #poetic and #poem 44with help of Twitters reals time search. Then we split it by "/" (slash) to get the rows for displaying it. You can define 45<a href="settings.htm">your own hashtag set</a> in <a href="settings.htm">my twyric</a> 46In addition, we remove 47@<twittername> content as well as all hashtags. Because an image says more than 1000 words, we try to parse for keywords, getting 48rid of stopwords. With these keywords, the flickr API is used for a full text search of matching images. Now, the tweet with the matching image 49is displayed. 50<br/> <br/> 51<b>How can I contribute?</b><br/> 52Simply tweet with one of the hashtags mentioned above. We are using the real time search, that means that older tweets may not be found. At 53the moment, no tweets are stored. 54<br/> <br/> 55<b>How can I report errors or make suggestions?</b><br/> 56Try our <a href="http://twyric.uservoice.com" target="uservoice">UserVoice</a> at <a href="http://twyric.uservoice.com" target="uservoice">http://twyric.uservoice.com</a> 57<br/> <br/> 58<b>Technology?</b><br/> 59Twyric is build with <a href="http://php.net" target="ext">PHP</a>, Javascript and <a href="http://jquery.com" target="ext">jQuery</a>. 60<br/> 61<br/> <br/> 62<a href="/index.htm">Restart twyric ...</a> 63</p> 64</td> 65</tr></table> 66</div> 67<div id="sitename"><a href="/">twyric</a></div> 68<div id="sitediv"><a href="info.htm">About</a> | <a href="http://twyric.uservoice.com" target="uservoice">Request feature</a> | <a href="settings.htm">My twyric</a> | <a href="info2.htm">Screensaver</a><br/> 69We are not associated with Twitter.com. © <a target="lesereins" href="http://www.lesereins.de">LeserEins.de</a></div></body> 70</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.