Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.bewatermyfriend.org/atom.xml

  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.  <title>ftblog</title>
  4.  <link rel="alternate" type="text/html"            href="http://www.bewatermyfriend.org" />
  5.  <link rel="self"      type="application/atom+xml" href="http://www.bewatermyfriend.org/atom.xml"/>
  6.  <updated>2011-05-22T12:59:01+01:00</updated>
  7.  <subtitle> :: widerstand zwecklos :: </subtitle>
  8.  <id>tag:www.bewatermyfriend.org,2011:05.22</id>
  9.  <icon>http://ft.bewatermyfriend.org/gra/favicon.png</icon>
  10.  <rights>copyleft</rights>
  11.  <generator uri="http://www.bewatermyfriend.org/posts/2006/09-01.21-01-13-blog.html">zblog</generator>
  12.      <entry>
  13.        <author>
  14.          <name>ft</name>
  15.          <email>ft@bewatermyfriend.org</email>
  16.        </author>
  17.        <title type="text">New waters</title>
  18.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/05-22.12-59-01-blog.html" />
  19.        <id>http://www.bewatermyfriend.org/posts/2011/05-22.12-59-01-blog.html</id>
  20.        <published>2011-05-22T12:59:01+01:00</published>
  21.        <updated>2011-05-22T12:59:01+01:00</updated>
  22.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  23.            <![CDATA[
  24. As of today, I'm moving my blog from `zblog' to `ikiwiki'. The new atom feed<br />
  25. URI is <a href="http://bewatermyfriend.org/index.atom">http://bewatermyfriend.org/index.atom</a>. Please update your feed reader<br />
  26. if you want to continue reading this blog.<br />
  27. <br />
  28. The old blog will still be available as <a href="http://bewatermyfriend.org/oldblog.html">http://bewatermyfriend.org/oldblog.html</a>.<br />
  29. ]]>
  30.        </content>
  31.      </entry>
  32.      <entry>
  33.        <author>
  34.          <name>ft</name>
  35.          <email>ft@bewatermyfriend.org</email>
  36.        </author>
  37.        <title type="text">beast!</title>
  38.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/05-07.12-40-33-computer.html" />
  39.        <id>http://www.bewatermyfriend.org/posts/2011/05-07.12-40-33-computer.html</id>
  40.        <published>2011-05-07T12:40:33+01:00</published>
  41.        <updated>2011-05-07T12:40:33+01:00</updated>
  42.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  43.            <![CDATA[
  44. (letrec ((f(lambda(n)(if(= n 0)1(* n(f(- n 1)))))))(f 666))<br />
  45. =&gt; 1010632056840781493390822708129876451757582398324145411340420807357413802103697022989202806801491012040989802203557527039339704057130729302834542423840165856428740661530297972410682828699397176884342513509493787480774903493389255262878341761883261899426484944657161693131380311117619573051526423320389641805410816067607893067483259816815364609828668662748110385603657973284604842078094141556427708745345100598829488472505949071967727270911965060885209294340665506480226426083357901503097781140832497013738079112777615719116203317542199999489227144752667085796752482688850461263732284539176142365823973696764537603278769322286708855475069835681643710846140569769330065775414413083501043659572299454446517242824002140555140464296291001901438414675730552964914569269734038500764140551143642836128613304734147348086095123859660926788460671181469216252213374650499557831741950594827147225699896414088694251261045196672567495532228826719381606116974003112642111561332573503212960729711781993903877416394381718464765527575014252129040283236963922624344456975024058167368431809068544577258472983979437818072648213608650098749369761056961203791265363665664696802245199962040041544438210327210476982203348458596093079296569561267409473914124132102055811493736199668788534872321705360511305248710796441479213354542583576076596250213454667968837996023273163069094700429467106663925419581193136339860545658673623955231932399404809404108767232000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000<br />
  46. <br />
  47. Yes, it's the factorial of the beast.<br />
  48. <br />
  49. <b>[</b>Update<b>]</b><br />
  50. <br />
  51. Oh, actually... you could write this shorter using a "named let":<br />
  52. <br />
  53. (let f((n 666))(if (= n 0)1(* n (f (- n 1)))))<br />
  54. ]]>
  55.        </content>
  56.      </entry>
  57.      <entry>
  58.        <author>
  59.          <name>ft</name>
  60.          <email>ft@bewatermyfriend.org</email>
  61.        </author>
  62.        <title type="text">zsh: programmierbares globbing</title>
  63.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/05-02.20-30-27-computer.html" />
  64.        <id>http://www.bewatermyfriend.org/posts/2011/05-02.20-30-27-computer.html</id>
  65.        <published>2011-05-02T20:30:27+01:00</published>
  66.        <updated>2011-05-02T20:30:27+01:00</updated>
  67.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  68.            <![CDATA[
  69. <a href="http://michael-prokop.at/blog/">Mika</a> fragte neulich, ob zsh-Globbing es zuläßt Dateien *.foo auszuwählen zu<br />
  70. denen keine *.bar Datei existiert. Klar gibt's das.<br />
  71. <br />
  72. <code>% touch abc.{foo,bar} def.foo<br />
  73. % print -l *.foo(e,'[[ ! -e ${REPLY:r}.bar ]]',)<br />
  74. def.foo<br /></code>
  75. <br />
  76. Nun mag man sagen, daß das häßlich ist und niemand das tippen wollen<br />
  77. würde. Da stimme ich zu. Geht auch kürzer.<br />
  78. <br />
  79. Bei Mika ging es darum .changes Dateien zu finden, zu denen es keine .upload<br />
  80. Datei gibt. Debian Kram. Wissenschon. Da kann dann zu einer Datei<br />
  81. `foo.changes' zum Beispiel eine Datei `foo.ftp-master.upload' gehören.<br />
  82. <br />
  83. <code>% function MC() {<br />
  84.  [[ \! -e ${REPLY:r}.${MTAG-ftp-master.}${MSUFF:-upload} ]] ]]<br />
  85. }<br />
  86. % print -l *.changes(+MC)<br /></code>
  87. <br />
  88. Das ganze ist über `$MTAG' und `$MSUFF' konfigurierbar. Standardmäßig ist<br />
  89. ersteres "ftp-master." und letzteres "upload". Mit anderen Worten: Würde man<br />
  90. <br />
  91. <code>% MTAG=''<br />
  92. % print -l *.changes(+MC)<br /></code>
  93. <br />
  94. ...machen, würden alle "*.changes" gelistet zu denen es kein "*.upload"<br />
  95. gibt. Analog kann man nun MTAG="ftp-slave." setzen wenn man nach "*.changes"<br />
  96. suchen will für die "*.ftp-slave.upload" nicht existiert.<br />
  97. <br />
  98. Das sollte einmal einen Startpunkt in diese Art von Globbing sein. Man passe<br />
  99. das an, bis es einem gefällt. Dokumentiert ist das ganze in `zshexpn(1)'.<br />
  100. Man suche mal nach "+nt" (je nach $PAGER wird man das `+' escapen müssen).<br />
  101. ]]>
  102.        </content>
  103.      </entry>
  104.      <entry>
  105.        <author>
  106.          <name>ft</name>
  107.          <email>ft@bewatermyfriend.org</email>
  108.        </author>
  109.        <title type="text">More renaming</title>
  110.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/04-14.08-25-38-computer.html" />
  111.        <id>http://www.bewatermyfriend.org/posts/2011/04-14.08-25-38-computer.html</id>
  112.        <published>2011-04-14T08:25:38+01:00</published>
  113.        <updated>2011-04-14T08:25:38+01:00</updated>
  114.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  115.            <![CDATA[
  116. Here's yet another public service announcement...<br />
  117. <br />
  118. I've registered <a href="https://www.ohloh.net/p/arename">arename with ohloh.net</a>. Feel free to submit a rating and hit<br />
  119. the "I use this" button if you do.   Oh, and also: There is a <a href="http://github.com/ft/arename/downloads">tarball up for<br />
  120. arename v4.0-rc0 at the github download page</a> (if you're not so much into VCS<br />
  121. checkouts).<br />
  122. ]]>
  123.        </content>
  124.      </entry>
  125.      <entry>
  126.        <author>
  127.          <name>ft</name>
  128.          <email>ft@bewatermyfriend.org</email>
  129.        </author>
  130.        <title type="text">arename 4.0-rc0</title>
  131.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/04-12.21-55-05-computer.html" />
  132.        <id>http://www.bewatermyfriend.org/posts/2011/04-12.21-55-05-computer.html</id>
  133.        <published>2011-04-12T21:55:05+01:00</published>
  134.        <updated>2011-04-12T21:55:05+01:00</updated>
  135.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  136.            <![CDATA[
  137. Hey there, dear target audience!<br />
  138. <br />
  139. It's been quite some time since the last <a href="http://ft.bewatermyfriend.org/comp/arename.html">arename</a> release. Version 3.0 was<br />
  140. released about one and half years ago. And it has seen only a small number of<br />
  141. minor fixes that led to v3.1 a few months later. 3.0 was a quick jump from<br />
  142. 2.0 because of broken backwards compatibility.<br />
  143. <br />
  144. And again, the upcoming release is going to be a major release for the very<br />
  145. same reason. It is going to be version 4.0. And I've just tagged a commit as<br />
  146. release candidate #0.<br />
  147. <br />
  148. Now I call upon my fierce two-person user base to give the new code a<br />
  149. serious spin! Try to break it. Find problems when upgrading. Tell me.<br />
  150. <br />
  151. There is an UPDATING file included now, which will document known<br />
  152. incompatibilities between major versions. Make *sure* you read it. Also,<br />
  153. there is a REPORTING_BUGS document, which outlines some instructions for<br />
  154. reporting bugs. Make sure you follow those when reporting anything.<br />
  155. <br />
  156. I've enabled the <a href="https://github.com/ft/arename/issues">issue tracker for arename</a> at github a while back. I don't<br />
  157. know how well that one works. So consider this a trail run. If it turns out<br />
  158. to be a pile of horse crap, I'll just disable it again.<br />
  159. <br />
  160. FWIW, I'm using the current code pretty much exclusively. It appears to work<br />
  161. fairly well so far, even though the code underwent quite substantial changes.<br />
  162. Take a look at the CHANGES file for new and changed features; and as I said,<br />
  163. tell me about anything that breaks for you.<br />
  164. <br />
  165. There is no date set for the final release. And even though this is a release<br />
  166. candidate, I would not be against adding yet another entirely awesome<br />
  167. feature. I won't be rushing this.<br />
  168. ]]>
  169.        </content>
  170.      </entry>
  171.      <entry>
  172.        <author>
  173.          <name>ft</name>
  174.          <email>ft@bewatermyfriend.org</email>
  175.        </author>
  176.        <title type="text">Excavation site</title>
  177.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/03-31.10-39-52-computer.html" />
  178.        <id>http://www.bewatermyfriend.org/posts/2011/03-31.10-39-52-computer.html</id>
  179.        <published>2011-03-31T10:39:52+01:00</published>
  180.        <updated>2011-03-31T10:39:52+01:00</updated>
  181.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  182.            <![CDATA[
  183. Yesterday evening I committed a new backend for vcs_info, which adds support<br />
  184. for the <a href="http://fossil-scm.org/">fossil scm</a>. That increases the number of supported version control<br />
  185. systems to a dozen (plus support for quilt). Yay!<br />
  186. <br />
  187. The fossil support was added by <a href="http://blog.mired.org/">Mike Meyer</a>. Thanks to him!<br />
  188. <br />
  189. I added a few minor enhancements to vcs_info, as well. But that's for another<br />
  190. time.<br />
  191. <br />
  192. Oh, and also: Hey Planet Grml! :-)<br />
  193. ]]>
  194.        </content>
  195.      </entry>
  196.      <entry>
  197.        <author>
  198.          <name>ft</name>
  199.          <email>ft@bewatermyfriend.org</email>
  200.        </author>
  201.        <title type="text">Schimpfwort des Tages #0</title>
  202.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/03-03.16-03-53-news.html" />
  203.        <id>http://www.bewatermyfriend.org/posts/2011/03-03.16-03-53-news.html</id>
  204.        <published>2011-03-03T16:03:53+01:00</published>
  205.        <updated>2011-03-03T16:03:53+01:00</updated>
  206.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  207.            <![CDATA[
  208. Armes-Deutschland-Rufer! (...und -Schreiber und -Sager und ...)<br />
  209. <br />
  210. Wer kennt sie nicht. :)<br />
  211. ]]>
  212.        </content>
  213.      </entry>
  214.      <entry>
  215.        <author>
  216.          <name>ft</name>
  217.          <email>ft@bewatermyfriend.org</email>
  218.        </author>
  219.        <title type="text">arename4 preview</title>
  220.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/02-24.11-14-26-computer.html" />
  221.        <id>http://www.bewatermyfriend.org/posts/2011/02-24.11-14-26-computer.html</id>
  222.        <published>2011-02-24T11:14:26+01:00</published>
  223.        <updated>2011-02-24T11:14:26+01:00</updated>
  224.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  225.            <![CDATA[
  226. A few weeks ago, I've started <a href="https://github.com/ft/arename">to work</a> on <a href="http://ft.bewatermyfriend.org/comp/arename.html">arename</a> again. Since then, I've tagged<br />
  227. two preview "releases" (v4.0-pre0 and v4.0-pre1). These are mainly for people<br />
  228. who would like to take an early look at arename4's major changes.<br />
  229. <br />
  230. First and foremost, that would be the big change in backend land. In earlier<br />
  231. versions, arename used three different backends to gather information from mp3<br />
  232. files, ogg and flac files. With arename4 that changes entirely. The new version<br />
  233. uses <a href="http://search.cpan.org/~agrundma/Audio-Scan-0.85/lib/Audio/Scan.pm">Audio::Scan</a>, which is able to work with many file formats on its own. That<br />
  234. simplifies the way arename fetches information, which has a positive impact on<br />
  235. code complexity. Audio::Scan is not available in debian yet. But I've been told<br />
  236. it is being worked on.<br />
  237. <br />
  238. From the user's point of view, that breaks the old hook API, since there were<br />
  239. a number of file-type specific hooks. They are not needed anymore and were<br />
  240. therefore removed. The other impact for the user is that arename now supports<br />
  241. many more file formats than before. See the manual for details.<br />
  242. <br />
  243. The second big change is the introduction of more complex expressions in<br />
  244. templates. Again, there are corner cases, in which this change may introduce<br />
  245. backwards compatibility issues. Though, with "normal, non-constructed<br />
  246. templates, that shouldn't be the case. Again, consult the manual for details.<br />
  247. <br />
  248. Because of the fundamental changes described above, breaking backwards<br />
  249. compatibility was inevitable. It is the main reason the upcoming release will<br />
  250. be yet another major version release.<br />
  251. <br />
  252. <br />
  253. Feel free to try arename4 today (I'm using v4.0-pre1 exclusively). But please<br />
  254. be extra-careful and make sure you're using the `--dryrun' option a lot, to<br />
  255. avoid surprises. If you find anything unusual or even bugs, please tell me.<br />
  256. <br />
  257. Please do not use the preview releases of arename4 as a drop-in replacement for<br />
  258. arename3. There is no documentation for upgrading yet. So just don't do that.<br />
  259. ]]>
  260.        </content>
  261.      </entry>
  262.      <entry>
  263.        <author>
  264.          <name>ft</name>
  265.          <email>ft@bewatermyfriend.org</email>
  266.        </author>
  267.        <title type="text">Grinsen 2.0</title>
  268.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/02-24.10-01-15-computer.html" />
  269.        <id>http://www.bewatermyfriend.org/posts/2011/02-24.10-01-15-computer.html</id>
  270.        <published>2011-02-24T10:01:15+01:00</published>
  271.        <updated>2011-02-24T10:01:15+01:00</updated>
  272.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  273.            <![CDATA[
  274. <a href="http://www.unicode.org/charts/PDF/Unicode-6.0/U60-1F600.pdf">Oh Boy...</a> [<a href="http://www.heise.de/-1195391.html">Quelle</a>]<br />
  275. ]]>
  276.        </content>
  277.      </entry>
  278.      <entry>
  279.        <author>
  280.          <name>ft</name>
  281.          <email>ft@bewatermyfriend.org</email>
  282.        </author>
  283.        <title type="text">Pressen!</title>
  284.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/02-06.10-05-38-computer.html" />
  285.        <id>http://www.bewatermyfriend.org/posts/2011/02-06.10-05-38-computer.html</id>
  286.        <published>2011-02-06T10:05:38+01:00</published>
  287.        <updated>2011-02-06T10:05:38+01:00</updated>
  288.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  289.            <![CDATA[
  290. <a href="http://lists.debian.org/debian-announce/2011/msg00001.html">Upgrade.</a><br />
  291. ]]>
  292.        </content>
  293.      </entry>
  294.      <entry>
  295.        <author>
  296.          <name>ft</name>
  297.          <email>ft@bewatermyfriend.org</email>
  298.        </author>
  299.        <title type="text">Congenital Abnormality 2.0</title>
  300.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/01-14.12-44-26-news.html" />
  301.        <id>http://www.bewatermyfriend.org/posts/2011/01-14.12-44-26-news.html</id>
  302.        <published>2011-01-14T12:44:26+01:00</published>
  303.        <updated>2011-01-14T12:44:26+01:00</updated>
  304.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  305.            <![CDATA[
  306. Gerade bei <a href="http://blog.fefe.de/?ts=b3ceecf2">fefe</a> gesehen. Aus <a href="http://www.tagesspiegel.de/medien/die-ard-steht-fuer-eine-allianz-gegen-google-bereit/3687510.html">einem Interview des Tagesspiegels</a> mit der WDR<br />
  307. Intendantin, die zum Jahreswechsel den ARD Vorsitz übernommen hat... Es prangt<br />
  308. der Titel "Die ARD steht für eine Allianz gegen Google bereit". Fantastisch!<br />
  309. <br />
  310. Geht aber noch weiter mit "Den Geburtsfehler des Internets - kostenlose<br />
  311. Inhalte - zu beseitigen ist aber schwierig und langwierig."; Keine weiteren<br />
  312. Fragen, euer Ehren. :)<br />
  313. ]]>
  314.        </content>
  315.      </entry>
  316.      <entry>
  317.        <author>
  318.          <name>ft</name>
  319.          <email>ft@bewatermyfriend.org</email>
  320.        </author>
  321.        <title type="text">Relax</title>
  322.        <link rel="alternate" type="text/html" href="http://www.bewatermyfriend.org/posts/2011/01-10.10-18-08-news.html" />
  323.        <id>http://www.bewatermyfriend.org/posts/2011/01-10.10-18-08-news.html</id>
  324.        <published>2011-01-10T10:18:08+01:00</published>
  325.        <updated>2011-01-10T10:18:08+01:00</updated>
  326.        <content type="html" xml:base="http://www.bewatermyfriend.org">
  327.            <![CDATA[
  328. Wer hat eigentlich das Gerücht in die Welt gesetzt, daß man sich im<br />
  329. Urlaub erholen würde? So ein Quatsch. Echt.<br />
  330. ]]>
  331.        </content>
  332.      </entry>
  333. </feed>
  334.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.bewatermyfriend.org/atom.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda