<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>El Tramo</title>
  <subtitle>Remko Tronçon's Homepage</subtitle>
  <link href="http://el-tramo.be/feed" rel="self" type="application/rss+xml"/>
  <link href="http://el-tramo.be/"/>
  <updated>2012-05-17T10:53:22+02:00</updated>
  <id>http://el-tramo.be/</id>
  <author>
    <name>Remko Tronçon</name>
    <uri>http://el-tramo.be/about/</uri>
  </author>
  
  <entry>
    <title>Swift Hackathon Roundup</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-hackathon-roundup"/>
    <updated>2012-05-06T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-hackathon-roundup</id>
    <content type="html">&lt;p&gt;Last sunday, we finished our week-long &lt;a href=&quot;http://swift.im/hackathon&quot;&gt;Swift Hackathon&lt;/a&gt;, and it was
a great success, leading to &lt;a href=&quot;http://swift.im/releases/swift-2.0beta1/&quot;&gt;Swift 2.0-beta1&lt;/a&gt;! Here&amp;rsquo;s a list of the
things we achieved during that week.&lt;/p&gt;

&lt;!-- more --&gt;


&lt;p&gt;First of all, the goal of the week was to find and fix as many bugs as possible. This
is what our &amp;lsquo;hackathon bug count dials&amp;rsquo; were displaying at the end of the week:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/swift-hackathon-roundup/hackathon-bug-counter.png&quot; alt=&quot;Hackathon Week Bug Counter&quot; /&gt;&lt;/p&gt;

&lt;p&gt;In only one week, we found 19 bugs, and fixed 64! Not a bad result for our first
hackathon, don&amp;rsquo;t you think? As you can see from the trend, we put a big dent in the
list of open bugs:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/swift-hackathon-roundup/hackathon-bug-trend.png&quot; alt=&quot;Hackathon Week Bug Trend&quot; /&gt;&lt;/p&gt;

&lt;p&gt;And if fixing all these bugs wasn&amp;rsquo;t enough, we found the time to do some other things
on the side as well during the week:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Together with &lt;a href=&quot;http://qa.debian.org/developer.php?login=olly@survex.com&quot;&gt;Olly Betts&lt;/a&gt;, we finished our Debian packages, and submitted
  them to Debian. So, expect both Swift and Swiften to be available from the
  official Debian repositories soon!&lt;/li&gt;
&lt;li&gt;We set up a build for the brand new Ubuntu 12.04 (Precise Pangolin)&lt;/li&gt;
&lt;li&gt;We started fixing and cleaning up translation strings&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Thanks again to all the people who have helped us during this excellent week!&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Swift 2.0-beta1 Released</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-2-0beta1"/>
    <updated>2012-05-04T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-2-0beta1</id>
    <content type="html">&lt;p&gt;After another year of development, we&amp;rsquo;re happy to announce that we released
our &lt;a href=&quot;http://swift.im/releases/swift-2.0beta1&quot;&gt;first Swift 2.0 beta&lt;/a&gt;! We encourage everyone who is interested
in helping us with testing to try out this new release, as it has many bugfixes and
enhancements (see the &lt;a href=&quot;http://swift.im/releases/swift-2.0beta1&quot;&gt;release notes&lt;/a&gt; for more details).&lt;/p&gt;

&lt;p&gt;Thanks to the
&lt;a href=&quot;http://swift.im/hackathon&quot;&gt;hackathon&lt;/a&gt; week (of which details will be posted shortly), we believe this first
beta to be pretty stable. Nevertheless, should you find some bugs, please come and
&lt;a href=&quot;http://swift.im/discussion/&quot;&gt;tell us about it&lt;/a&gt;!&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Steve Jobs would not appr o ve</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/ios-keming"/>
    <updated>2012-05-01T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/ios-keming</id>
    <content type="html">&lt;p&gt;In his famous &lt;a href=&quot;http://www.youtube.com/watch?v=D1R-jKKp3NA&quot;&gt;2005 Stanford Commencement Speech&lt;/a&gt;, Steve Jobs
explained how his interest in typography &lt;a href=&quot;http://www.planet-typography.com/news/typo/steve-jobs.html&quot;&gt;played a fundamental role in creating
the first Macintosh computer&lt;/a&gt;, and how the beautiful typography set
the Mac apart from other personal computers out there. He was obviously passionate
about these things, going as far as pixel-perfectionism about fonts and icons.
That&amp;rsquo;s why I was a bit shocked when I started noticing bad kerning
(aka &lt;a href=&quot;http://www.ironicsans.com/2008/02/idea_a_new_typography_term.html&quot;&gt;keming&lt;/a&gt;) in the iOS 5 status bar. Could it be that these are the first
artifacts of the post-Steve Jobs World? (&lt;em&gt;Update:
&lt;a href=&quot;https://twitter.com/#!/cheungpat/status/197328235581800448/photo/1/large&quot;&gt;No&lt;/a&gt;&lt;/em&gt;)&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Spoiler alert&lt;/em&gt;: As &lt;a href=&quot;http://xkcd.com/1015/&quot;&gt;XKCD points out&lt;/a&gt;, recognizing bad kerning is
something you may not want to learn about. If you like your iOS status bar, consider
not reading on.&lt;/p&gt;

&lt;!-- more --&gt;


&lt;p&gt;Have a look at the battery level indicator of the iOS screenshot below:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/ios-keming/44.png&quot; alt=&quot;Battery Indicator: 44%&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Now compare that 44 with the one from the clock. Doesn&amp;rsquo;t look right, does it?
How about something a bit more obvious: charge your iDevice to 100%, and you
see the following:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/ios-keming/100.jpg&quot; alt=&quot;Battery Indicator: 100%&quot; /&gt;&lt;/p&gt;

&lt;p&gt;That 1 in the battery level almost looks like it&amp;rsquo;s coming from a different font?!
Still not convinced? How about anything in the 10-19% range?&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/ios-keming/18.png&quot; alt=&quot;Battery Indicator: 18%&quot; /&gt;
&lt;img src=&quot;/blog/ios-keming/15.jpg&quot; alt=&quot;Battery Indicator: 15%&quot; /&gt;&lt;/p&gt;

&lt;p&gt;You have to admit that this is much worse than pixel-imperfectionisms. Even if this was
post-Steve, or Steve always had his battery level indicator turned off, you would
have come to expect &lt;em&gt;someone&lt;/em&gt; at Apple must be annoyed by this, surely?&lt;/p&gt;

&lt;p&gt;I know I&amp;rsquo;m nitpicking, but the problem is that, if you noticed it once, you will
notice it every time you look at your status bar. The only solution: disable
the battery level indicator.&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Swift Hackathon Update</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-hackathon-update"/>
    <updated>2012-04-26T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-hackathon-update</id>
    <content type="html">&lt;p&gt;We&amp;rsquo;re just halfway through our &lt;a href=&quot;http://swift.im/hackathon&quot;&gt;Swift Hackathon&lt;/a&gt;, so we thought we'ld update you about the  progress we&amp;rsquo;ve made so far.  &lt;!-- more --&gt; In fact, a screenshot of our &lt;a href=&quot;http://swift.im/hackathon&quot;&gt;live hackathon week bug counter&lt;/a&gt; sums this up quite well:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/blog/swift-hackathon-update/hackathon-bug-counter.png&quot; alt=&quot;Hackathon Week Bug Counter&quot; /&gt;&lt;/p&gt;

&lt;p&gt;That&amp;rsquo;s right: in merely a couple of days, we managed to fix 50 (more than half!) of the open bugs, and found 17 new bugs. And what&amp;rsquo;s more: we still have the whole weekend ahead of us, so you still have a chance to join us in fixing, testing, and improving Swift!&lt;/p&gt;

&lt;p&gt;A big thank you to all the people who have been helping us out so far!&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Google Summer of Code 2012</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-gsoc-2012"/>
    <updated>2012-04-25T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-gsoc-2012</id>
    <content type="html">&lt;p&gt;It&amp;rsquo;s that time of year again: Google &lt;a href=&quot;http://google-opensource.blogspot.com/2012/04/students-announced-for-google-summer-of.html?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A+GoogleOpenSourceBlog+%28Google+Open+Source+Blog%29&quot;&gt;announced&lt;/a&gt; which students they are going to sponsor for contributing to open source projects. This year, we have the pleasure of welcoming 3 students at &lt;a href=&quot;http://swift.im&quot;&gt;Swift&lt;/a&gt;, who will be working on some very exciting projects.&lt;/p&gt;

&lt;!-- more --&gt;


&lt;p&gt;This summer, you&amp;rsquo;ll see the following new faces hanging around the Swift room:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cătălin Badea will finally bring us the long awaited &amp;ldquo;Conversation History&amp;rdquo; support, using the
newly minted &lt;a href=&quot;http://xmpp.org/extensions/xep-0313.html&quot;&gt;Message Archive Management XEP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Mateusz Piękos will be adding shared whiteboarding functionality&lt;/li&gt;
&lt;li&gt;Yoann Blein is going to implement screen sharing using &lt;a href=&quot;http://xmpp.org/about-xmpp/technology-overview/jingle/&quot;&gt;Jingle&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Since Kevin and I could only mentor Cătălin and Mateusz, and we &lt;em&gt;really&lt;/em&gt; wanted to have Yoann join us as well, we decided to bring in some extra help this year. Tobias, who not only has participated in GSoC 4 times as a student, but also is a top Swift contributor, and authored practically all of the Swift Jingle code during GSoC last year, will be mentoring Yoann in the screen sharing project.&lt;/p&gt;

&lt;p&gt;As you can see: great times ahead!&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Swift Hackathon</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-hackathon"/>
    <updated>2012-04-11T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-hackathon</id>
    <content type="html">&lt;p&gt;All the cool kids are doing it, and so are we: starting Monday April 23rd,
we&amp;rsquo;re holding a week long &lt;a href=&quot;http://swift.im&quot;&gt;Swift&lt;/a&gt; hackathon! We will be focusing for a whole
week on bugfixes, and at the end of that week release the first beta of
Swift 2.0, the next major Swift release. Everyone is invited to join us
online in our chatroom at &lt;a href=&quot;xmpp:swift@rooms.swift.im?join&quot;&gt;swift@rooms.swift.im&lt;/a&gt;, and start
hacking with us. And if you can&amp;rsquo;t or don&amp;rsquo;t want to fix bugs,
we also need plenty of people to help us with testing Swift extensively
that week.&lt;/p&gt;

&lt;p&gt;(Thanks to &lt;a href=&quot;http://ayena.de&quot;&gt;Tobias&lt;/a&gt; for suggesting this).&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Experimental File Transfer support hits Swift </title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-experimental-ft"/>
    <updated>2011-09-25T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-experimental-ft</id>
    <content type="html">&lt;p&gt;It&amp;rsquo;s been a busy summer for &lt;a href=&quot;http://ayena.de&quot;&gt;Tobias Markmann&lt;/a&gt;, one of the &lt;a href=&quot;http://xmpp.org/2011/04/xsf-welcomes-google-summer-of-code-2011-students/&quot;&gt;XMPP Standards Foundation’s 2011 Google Summer of Code students&lt;/a&gt;. He has been working on implementing File Transfer support for &lt;a href=&quot;http://swift.im&quot;&gt;Swift&lt;/a&gt;, using the fresh Jingle XMPP protocols. I&amp;rsquo;m happy to announce that we integrated &lt;a href=&quot;http://swift.im/git/swift/commit/?id=4f62e5ec4b42929fe3c1a68667e63cb1b7a35509&quot;&gt;Tobias’s work&lt;/a&gt; as an experimental feature into the main Swift branch, where it will be further developed and brushed off before being enabled in our nightly builds and releases.&lt;/p&gt;

&lt;!--more--&gt;


&lt;p&gt;For those interested in the nitty gritty protocol details: file transfers are negotiated through the Jingle File Transfer protocol (&lt;a href=&quot;http://xmpp.org/extensions/xep-0234.html&quot;&gt;XEP-0234&lt;/a&gt;), using SOCKS5 (&lt;a href=&quot;http://xmpp.org/extensions/xep-0260.html&quot;&gt;XEP-0260&lt;/a&gt;) as the main transport, and In-Band Bytestreams (&lt;a href=&quot;http://xmpp.org/extensions/xep-0261.html&quot;&gt;XEP-0261&lt;/a&gt;) as fallback. To improve connectivity, we use both the &lt;a href=&quot;http://files.dns-sd.org/draft-cheshire-nat-pmp.txt&quot;&gt;NAT Port Mapping Protocol&lt;/a&gt; and the &lt;a href=&quot;http://www.upnp.org/&quot;&gt;UPnP Internet Gateway Device protocols&lt;/a&gt; to allow connections through most firewalls, and &lt;a href=&quot;http://xmpp.org/extensions/xep-0065.html#mediated&quot;&gt;SOCKS5 relaying proxies&lt;/a&gt; in case all else fails.&lt;/p&gt;

&lt;p&gt;The new feature has been tested for interoperability against (slightly modified) development versions of both &lt;a href=&quot;http://pidgin.im&quot;&gt;Pidgin&lt;/a&gt; and &lt;a href=&quot;http://gajim.org&quot;&gt;Gajim&lt;/a&gt;, which, together with the Pidgin-based &lt;a href=&quot;http://adium.im&quot;&gt;Adium&lt;/a&gt;, cover a large XMPP user base. After both clients update their protocols to track the newly published Draft specification versions, all 3 should be able to exchange files seamlessly.&lt;/p&gt;

&lt;p&gt;What still remains to be done is lots of testing (both internal testing, user testing, reliability testing, and interop testing), bugfixing, and some refactoring here and there to clean up some of the code (which already is in very good shape). Our end goal is to reach a rock solid implementation, with a near guarantee that file exchange will always work (which experience teaches us is far from trivial).&lt;/p&gt;

&lt;p&gt;To conclude, we’ld like to thank Tobias for contributing this great new feature to Swift, for providing valuable protocol feedback to the XSF, and for laying the foundation to other exciting Jingle-based features (including voice/video conferencing).&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>TwitCoop: A Desktop Cage for Twitter Mobile Web</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/twitcoop"/>
    <updated>2011-05-25T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/twitcoop</id>
    <content type="html">&lt;p&gt;The official &lt;a href=&quot;http://itunes.apple.com/us/app/twitter/id409789998?mt=12&quot;&gt;Twitter for Mac&lt;/a&gt; app gives a great interface for &lt;a href=&quot;http://twitter.com&quot;&gt;Twitter&lt;/a&gt;: lightweight, compact, no bloat, and it looks great. Unfortunately, amongst the hundreds of Twitter clients already existing, I couldn&amp;rsquo;t find anything similar for Linux or Windows. Instead of creating yet another client (which &lt;a href=&quot;http://arstechnica.com/software/news/2011/03/twitter-tells-third-party-devs-to-stop-making-twitter-client-apps.ars&quot;&gt;Twitter doesn&amp;rsquo;t like&lt;/a&gt; anyway), I did a bit of &lt;a href=&quot;http://qt.nokia.com&quot;&gt;Qt&lt;/a&gt; WebKit coding, and created a small desktop client around the (current) Twitter Mobile Web interface.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;
Update: The mobile Twitter website was updated, and doesn&amp;rsquo;t work as well anymore with TwitCoop. I will try to upgrade TwitCoop to work with the new interface, but it is currently not clear whether this is at all possible.
&lt;/em&gt;&lt;/p&gt;

&lt;!--more--&gt;


&lt;p&gt;First, some screenshots:&lt;/p&gt;

&lt;p style='text-align: center'&gt;
&lt;a href=&quot;twitcoop.png&quot;&gt;&lt;img src=&quot;twitcoop.png&quot; alt=&quot;&quot; title=&quot;TwitCoop&quot; width=&quot;202&quot; height=&quot;492&quot; class=&quot;wp-image-1134&quot; /&gt;&lt;/a&gt;&lt;a href=&quot;twitcoop-menu.png&quot;&gt;&lt;img src=&quot;twitcoop-menu.png&quot; alt=&quot;&quot; title=&quot;TwitCoop (Menu)&quot; width=&quot;202&quot; height=&quot;495&quot; class=&quot;wp-image-1135&quot; /&gt;&lt;/a&gt;&lt;a href=&quot;twitcoop-compact.png&quot;&gt;&lt;img src=&quot;twitcoop-compact.png&quot; alt=&quot;&quot; title=&quot;TwitCoop (Compact)&quot; width=&quot;202&quot; height=&quot;494&quot; class=&quot;wp-image-1136&quot; /&gt;&lt;/a&gt;
&lt;/p&gt;


&lt;p&gt;Features of this desktop interface include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compact&lt;/li&gt;
&lt;li&gt;Provides an &amp;ldquo;official&amp;rdquo;, consistent Twitter interface&lt;/li&gt;
&lt;li&gt;Automatically refreshes when new tweets are available (with a higher refresh rate than the default mobile web interface)&lt;/li&gt;
&lt;li&gt;Opens external (i.e. non-Twitter) links in your preferred web browser&lt;/li&gt;
&lt;li&gt;Allows you to hide the Tweet box, when screen real estate is a problem (e.g. on netbooks)&lt;/li&gt;
&lt;li&gt;Allows you to customize the zoom level&lt;/li&gt;
&lt;li&gt;Automatically logs you into your previous Twitter session on startup&lt;/li&gt;
&lt;li&gt;Supports &amp;ldquo;kinetic scrolling&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Works on Windows and Linux&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Note that some of these features may become obsolete once the &lt;a href=&quot;http://blog.twitter.com/2011/05/better-app-for-your-mobile-browser.html&quot;&gt;new mobile interface&lt;/a&gt; becomes available to everyone, and maybe some stuff will break, so I will need to update this then. The mobile web application isn&amp;rsquo;t as responsive as a real native client, but this may change with the new mobile interface as well.&lt;/p&gt;

&lt;p&gt;You can try it out for yourself by &lt;a href='/files/twitcoop/TwitCoop-win32.zip'&gt;downloading the Windows version&lt;/a&gt; (requires the &lt;a href=&quot;http://www.microsoft.com/downloads/en/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&quot;&gt;Microsoft Visual C++ 2008 Redistributable&lt;/a&gt;, which may already be installed on your system), or by building it yourself from &lt;a href=&quot;/git/twitcoop&quot;&gt;the development repository&lt;/a&gt;.&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Summer of Swift Code 2011</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-gsoc-2011"/>
    <updated>2011-04-26T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-gsoc-2011</id>
    <content type="html">&lt;p&gt;Yesterday, Google &lt;a href=&quot;http://google-opensource.blogspot.com/2011/04/students-announced-for-2011-google.html&quot;&gt;announced&lt;/a&gt; the 1116 students that were accepted for this year&amp;rsquo;s edition of the Google Summer of Code, &lt;a href=&quot;http://xmpp.org/2011/04/xsf-welcomes-google-summer-of-code-2011-students/&quot;&gt;5&lt;/a&gt; of which will be working with the XMPP Standards Foundation. We&amp;rsquo;re very happy to welcome both  Tobias Markmann and Vlad Voicu, who will be working full-time on Swift this summer, implementing file transfer support and conversation history respectively.&lt;/p&gt;

&lt;p&gt;We have to mention that these weren&amp;rsquo;t the only proposals we received. Most of the proposals we received this year were of good quality: we suspect that the teaser tasks we put up for potential students made it possible for both the students and us to get an idea up front of what should be expected. However, based on experience from previous years, we decided we should only accept 2 students, to ensure that we could give our full attention to making all projects successful (including fast integration into a Swift release). We&amp;rsquo;re convinced that both Vlad and Tobias will live up to their expectations, and implement some of the most requested Swift features today!&lt;/p&gt;
</content>
  </entry>
  
  <entry>
    <title>Swift 1.0 Released</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/swift-1-0"/>
    <updated>2011-04-18T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/swift-1-0</id>
    <content type="html">&lt;p&gt;Finally! After 2 years of development, we&amp;rsquo;re happy to finally announce the &lt;a href=&quot;http://swift.im/releases/swift-1.0&quot;&gt;first full release&lt;/a&gt; of the Swift IM client! In this first release, we have focused on building a user-friendly messaging client, with all the basic features you would typically need for having real-time conversations. In future versions (which are already in the works as we speak), we will be extending Swift with more features.&lt;/p&gt;

&lt;p&gt;We would like to thank &lt;a href=&quot;http://isode.com&quot;&gt;Isode&lt;/a&gt; for sponsoring time for Kevin to work on Swift, &lt;a href=&quot;http://flosoft.biz&quot;&gt;Flosoft&lt;/a&gt; for providing our download infrastructure, Dave Cridland for the logo, all the translators who helped us make Swift available in different languages, all the code contributors, all of whom should be listed on our &lt;a href=&quot;http://swift.im/about/&quot;&gt;About page&lt;/a&gt;, and all our beta testers for giving us feedback and bugreports throughout the whole development period!&lt;/p&gt;
</content>
  </entry>
  
</feed>

