<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Notes</title>
    <link>https://aleb.ro/post/</link>
    <description>Recent content in Posts on Notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Feb 2025 08:30:00 +0100</lastBuildDate>
    <atom:link href="https://aleb.ro/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Practical intro to fiber-optic networks</title>
      <link>https://aleb.ro/post/2025-02-28-fiber-optic-networks-practical-intro/</link>
      <pubDate>Fri, 28 Feb 2025 08:30:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2025-02-28-fiber-optic-networks-practical-intro/</guid>
      <description>&lt;p&gt;I was looking into how to link a remote point in my mansion to the network and checked how it could work with a fiber-optic connection, since the router had a SFP+ socket.&lt;/p&gt;&#xA;&lt;p&gt;TL/DR: I&amp;rsquo;ll go with a SFP+ bidi single-mode connection.&lt;/p&gt;&#xA;&lt;p&gt;First of all, stay safe. Don&amp;rsquo;t look directly into a fiber with your eye. The light/laser is not powerful, but why do it? You won&amp;rsquo;t see anything anyway, as the light is in the infrared.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Installing Fedora on MacBook Air A1369</title>
      <link>https://aleb.ro/post/2022-11-28-installing-fedora-on-macbook-air-a1369/</link>
      <pubDate>Mon, 28 Nov 2022 19:38:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2022-11-28-installing-fedora-on-macbook-air-a1369/</guid>
      <description>&lt;p&gt;Apple is a marketing company. Once the device is not supported anymore, it&amp;rsquo;s&#xA;called &amp;ldquo;vintage&amp;rdquo;. You should go buy a new one otherwise the experience heavily&#xA;degrades. But these old laptops are still quite powerful―this MacBook Air 2011&#xA;model, for example, has an i7 CPU and an SSD, FFS. Luckily they can be given a&#xA;new life with Linux.&lt;/p&gt;&#xA;&lt;p&gt;TL/DR: Installing Fedora 37 on a MacBook Air A1369 (2011) at the end of 2022 is&#xA;tricky and close to impossible for normal users.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fixing the function keys of a Kinesis keyboard</title>
      <link>https://aleb.ro/post/2022-09-14-fixing-kinesis-function-keys/</link>
      <pubDate>Wed, 14 Sep 2022 00:15:00 +0200</pubDate>
      <guid>https://aleb.ro/post/2022-09-14-fixing-kinesis-function-keys/</guid>
      <description>&lt;p&gt;The Kinesis Advantage series of keyboards has a row of tiny function keys at the top. These cheap rubber keys are the shame of the expensive Kinesis keyboards. The latest version in this series, model KB600, has the tiny function keys made out of plastic, no more rubber―feels better.&lt;/p&gt;&#xA;&lt;p&gt;The Esc key in my ancient KB133 Kinesis was registering key presses only when I was pressing very hard. The Kinesis support was very responsive but they said they don&amp;rsquo;t have replacement parts for this old keyboard model. Long story short, they hate contributing to e-waste but that &amp;ldquo;seems to be the next step&amp;rdquo;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Refurbishing a Kinesis Classic KB133</title>
      <link>https://aleb.ro/post/2022-09-08-refurbishing-kinesis-KB133/</link>
      <pubDate>Thu, 08 Sep 2022 01:00:00 +0200</pubDate>
      <guid>https://aleb.ro/post/2022-09-08-refurbishing-kinesis-KB133/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been using a Kinesis Classic keyboard since 2007 when I got one at Google. I did notice some minor issues every few months, but it started to be somewhat annoying only after reading Michael&amp;rsquo;s list of the issues Kinesis keyboards have. Thanks Michael!&lt;/p&gt;&#xA;&lt;p&gt;I probably flirted with the idea of replacing the keyboard&amp;rsquo;s controller following Michael&amp;rsquo;s instructions for two or three years. But why do it, really.. Things changed last winter when the &lt;code&gt;Esc&lt;/code&gt; key stopped working. I switched to a normal totally-boring keyboard I found in the basement. Then I fell in love with the big and accessible Gui key!&lt;/p&gt;</description>
    </item>
    <item>
      <title>FOSDEM impressions</title>
      <link>https://aleb.ro/post/2019-02-27-fosdem-impressions/</link>
      <pubDate>Wed, 27 Feb 2019 10:50:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2019-02-27-fosdem-impressions/</guid>
      <description>&lt;p&gt;Earlier this month I got to &lt;a href=&#34;https://fosdem.org/&#34;&gt;FOSDEM&lt;/a&gt; in Brussels&#xA;for the first time. Below is how I remember it. Overall it has been&#xA;great.&lt;/p&gt;&#xA;&lt;p&gt;I quickly learned to look for a different room when there was a queue at&#xA;the door. But this once I decided to wait in queue, hoping somebody&#xA;would get out so I can enter. I and the person in front of me got close&#xA;to the door, but unfortunately we did not get in. Luckily the next&#xA;speaker and his colleague were also waiting, so we got a 1-1 (or more&#xA;accurately 2 on 2) on quantum computing. That was quite cool.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Polishing Pitivi&#39;s viewer</title>
      <link>https://aleb.ro/post/2019-02-15-polishing-pitivis-viewer/</link>
      <pubDate>Fri, 15 Feb 2019 00:38:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2019-02-15-polishing-pitivis-viewer/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;http://www.pitivi.org/&#34;&gt;Pitivi&lt;/a&gt; video editor, the viewer is&#xA;quite important, as it shows the video. Our viewer also shows a discreet&#xA;frame around a clip selected in the timeline, making it easy to &lt;a href=&#34;https://lubosz.wordpress.com/2016/09/26/making-viewer-uis-for-pitivi/&#34;&gt;resize&#xA;and position the video of the clip by&#xA;dragging&lt;/a&gt;.&#xA;Below is the story of the viewer updates in the past year.&lt;/p&gt;&#xA;&lt;h2 id=&#34;easy-resizing&#34;&gt;Easy resizing&lt;/h2&gt;&#xA;&lt;p&gt;It was a bit cumbersome to have to drag both the left and bottom margins&#xA;of the viewer container to resize it. We thought it would be easier to&#xA;resize the viewer by simply dragging the bottom-left corner of its&#xA;container. Harish Fulara made time at the end of his GSoC 2018&#xA;internship for this, after he finished his main task, and it works&#xA;great! &amp;mdash;&#xA;&lt;a href=&#34;https://gitlab.gnome.org/GNOME/pitivi/commit/25609f3ab7996e865ec275298c70a384823cabe3&#34;&gt;25609f3a&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Polishing Pitivi&#39;s ruler</title>
      <link>https://aleb.ro/post/2016-01-23-polishing-pitivis-ruler/</link>
      <pubDate>Sat, 23 Jan 2016 03:28:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2016-01-23-polishing-pitivis-ruler/</guid>
      <description>&lt;p&gt;In Pitivi, the ruler is displayed above the timeline to show the times&#xA;corresponding with the current view. A series of H:MM:SS.XXX timestamps&#xA;on a ruler might leave the impression that only trained professionals&#xA;are supposed to use it. I had trouble reading the timestamps and looked&#xA;for ways to make the ruler more useful. Read below for the story.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://aleb.ro/post/2016-01-23-polishing-pitivis-ruler/2012.11.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Pitivi ruler, Dec 2013&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h2 id=&#34;relevant-parts&#34;&gt;Relevant parts&lt;/h2&gt;&#xA;&lt;p&gt;Around the New Year 2013-2014 I thought about highlighting the relevant&#xA;parts in the timestamp. For example, if you have 0:00:05.000 and then&#xA;0:00:10.000, you have to look quite a bit until you notice what changes&#xA;from one to the other. In this case the &amp;ldquo;10&amp;rdquo; should be highlighted&#xA;because that&amp;rsquo;s different than the previous timestamp. This way it&amp;rsquo;s&#xA;easier to see what an interval represents. Jeff liked the idea and the&#xA;commit &lt;a href=&#34;https://gitlab.gnome.org/GNOME/pitivi/commit/a7cb639b8ac8750edd44125a7ea0a3fd0601a5bf&#34;&gt;went&#xA;in&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to use the x264 encoding presets when rendering an XGES project</title>
      <link>https://aleb.ro/post/2015-11-08-how-to-use-x264-encoding-presets-when/</link>
      <pubDate>Sun, 08 Nov 2015 01:11:00 +0100</pubDate>
      <guid>https://aleb.ro/post/2015-11-08-how-to-use-x264-encoding-presets-when/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.videolan.org/developers/x264.html&#34;&gt;x264&lt;/a&gt; has a few generic&#xA;encoding presets you can use when rendering. You can see the list of&#xA;presets and exactly what encoding options they specify by running&#xA;&lt;code&gt;x264 --fullhelp&lt;/code&gt;.&#xA;You&amp;rsquo;ll most probably notice the following presets: &lt;code&gt;ultrafast&lt;/code&gt;, &lt;code&gt;superfast&lt;/code&gt;,&#xA;&lt;code&gt;veryfast&lt;/code&gt;, &lt;code&gt;faster&lt;/code&gt;, &lt;code&gt;fast&lt;/code&gt;, &lt;code&gt;medium&lt;/code&gt;, &lt;code&gt;slow&lt;/code&gt;, &lt;code&gt;slower&lt;/code&gt;, &lt;code&gt;veryslow&lt;/code&gt;.&#xA;Ideally you&amp;rsquo;d always use &lt;code&gt;veryslow&lt;/code&gt;&#xA;when rendering, but you can&#39;t always wait for it to finish, so you go&#xA;for faster ones. The ffmpeg wiki summarizes the &lt;a href=&#34;https://trac.ffmpeg.org/wiki/Encode/H.264#FAQ&#34;&gt;difference between&#xA;these presets&lt;/a&gt;:\&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pitivi moves from Bugzilla to Phabricator</title>
      <link>https://aleb.ro/post/2015-10-20-pitivi-moves-from-bugzilla-to/</link>
      <pubDate>Tue, 20 Oct 2015 17:31:00 +0200</pubDate>
      <guid>https://aleb.ro/post/2015-10-20-pitivi-moves-from-bugzilla-to/</guid>
      <description>&lt;p&gt;Using Bugzilla to manage &lt;a href=&#34;http://www.pitivi.org/&#34;&gt;Pitivi&lt;/a&gt; was a bit&#xA;painful and we were looking for a replacement. Many projects seemed to&#xA;switch to Phabricator lately, which looked like a very good platform for&#xA;managing projects. We experimented migrating Bugzilla bugs to&#xA;Phabricator, and we are pretty content with the result. The UI is nicer,&#xA;we have a better search function, and the Git integration (with the&#xA;&lt;a href=&#34;https://phabricator.freedesktop.org/diffusion/&#34;&gt;code review&lt;/a&gt; component&#xA;&lt;a href=&#34;https://phabricator.freedesktop.org/diffusion/GITPHAB/&#34;&gt;works great&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;We decided to make the switch official, so we updated the documentation on the&#xA;&lt;a href=&#34;http://wiki.pitivi.org/&#34;&gt;wiki&lt;/a&gt; and &lt;a href=&#34;http://www.pitivi.org/&#34;&gt;website&lt;/a&gt;&#xA;to link to &lt;a href=&#34;https://phabricator.freedesktop.org/tag/pitivi/&#34;&gt;Phabricator&lt;/a&gt;,&#xA;closed the Pitivi Bugzilla &amp;ldquo;product&amp;rdquo; and closed the remaining bugs in&#xA;Bugzilla with a custom made script. The script also linked each bug to&#xA;the proper task in Phabricator.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The War Against Deadlocks, part 2: GNonLin’s reincarnation (the other thousand Deadlocks)</title>
      <link>https://aleb.ro/post/2015-10-15-the-war-against-deadlocks-part-2/</link>
      <pubDate>Thu, 15 Oct 2015 17:20:00 +0200</pubDate>
      <guid>https://aleb.ro/post/2015-10-15-the-war-against-deadlocks-part-2/</guid>
      <description>&lt;p&gt;Read the first part on Jeff&amp;rsquo;s blog: &lt;a href=&#34;http://jeff.ecchi.ca/blog/2014/10/03/an-update-from-the-pitivi-2014-summer-battlefront/&#34;&gt;The&#xA;War Against Deadlocks, part 1: The story of our new thread-safe mixing&#xA;elements&#xA;implementation&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gnonlin/html/&#34;&gt;GNonLin&lt;/a&gt;&#xA;has served our cause well for a number of years, but was left with&#xA;indelible marks from the Old World. We grew increasingly worried with&#xA;GNonLin&amp;rsquo;s common affiliation with Deadlocks, to the point where it was&#xA;known as &amp;ldquo;the Baron of Deadlocks&amp;rdquo; by our battalion. We tried correcting&#xA;it, tried reasoning with it, but alas&amp;mdash;we only got &amp;ldquo;not-negotiated&amp;rdquo;&#xA;caps errors.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up Supybot with the Bugzilla plugin</title>
      <link>https://aleb.ro/post/2011-06-18-setting-up-supybot-with-the-bugzilla-plugin/</link>
      <pubDate>Sat, 18 Jun 2011 15:59:00 +0200</pubDate>
      <guid>https://aleb.ro/post/2011-06-18-setting-up-supybot-with-the-bugzilla-plugin/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://supybot.com/&#34;&gt;Supybot&lt;/a&gt; is an IRC bot, an application which can&#xA;connect to a specific IRC channel and do stuff there. For example, with&#xA;the &lt;a href=&#34;http://code.google.com/p/supybot-bugzilla/&#34;&gt;Bugzilla plugin&lt;/a&gt;,&#xA;Supybot can report on the channel whenever a new bug is filed, or if&#xA;somebody mentions &amp;ldquo;bug 1234&amp;rdquo; in the conversation, it will print&#xA;details about bug 1234.&lt;/p&gt;&#xA;&lt;h2 id=&#34;install-supybot&#34;&gt;Install supybot&lt;/h2&gt;&#xA;&lt;p&gt;First, you have to install Supybot. If you are using Arch Linux, &lt;a href=&#34;https://aur.archlinux.org/packages/supybot/&#34;&gt;get&#xA;supybot from AUR&lt;/a&gt;,&#xA;otherwise read the&#xA;&lt;a href=&#34;http://sourceforge.net/p/supybot/code/?branch=ref%2Fmaster&#34;&gt;INSTALL&lt;/a&gt;&#xA;file.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
