<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Articles on Björn Schießle - I came for the code but stayed for the freedom</title>
    <link>https://schiessle.eu/en/articles/</link>
    <description>Recent content in Articles on Björn Schießle - I came for the code but stayed for the freedom</description>
    <generator>Hugo -- gohugo.io</generator>
    
    
    
    <language>en-US</language>
    
    
    
    <managingEditor>bjoern@schiessle.org (Björn Schießle)</managingEditor>
    <webMaster>bjoern@schiessle.org (Björn Schießle)</webMaster>
    <copyright>Creative Commons Attribution-ShareAlike 4.0 International License.</copyright>
    <lastBuildDate>Mon, 16 Dec 2024 08:00:00 +0200</lastBuildDate>
    <atom:link href="https://schiessle.eu/en/articles/" rel="self" type="application/rss+xml" />
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Nextcloud and OpenID-Connect</title>
      <link>https://schiessle.eu/en/articles/2023/07/04/nextcloud-and-openid-connect/</link>
      <pubDate>Tue, 04 Jul 2023 08:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2023/07/04/nextcloud-and-openid-connect/</guid>
      
      <image>https://schiessle.eu/img/nextcloud.png</image>
      
      
      
      <category>Nextcloud</category>
      
      <category>openid</category>
      
      
      
      <description>&lt;p&gt;This is a updated version of a &lt;a href=&#34;https://schiessle.eu/articles/2020/07/26/nextcloud-and-openid-connect/&#34;&gt; old blog post from 2020&lt;/a&gt;. The guide here was tested with Nextcloud Hub 5 and Keycloak 21.1.2.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Please keep in mind&lt;/strong&gt;, the main goal of this article is to get Keycloak up  and running quickly to test the Nextcloud OIDC connector. It is not a detailed guide how to setup Keycloak for production! It is quite likely that I missed some important security setting which you would like to enable for a live system.&lt;/p&gt;
&lt;h2 id=&#34;get-a-openid-connect-provider&#34;&gt;Get a OpenID Connect provider&lt;/h2&gt;
&lt;p&gt;First step was to get an OpenID-Connect provider, sure I could have chosen one of the public services. But why not have a small nice provider running directly on my machine? &lt;a href=&#34;https://www.keycloak.org&#34;&gt;Keycloak&lt;/a&gt; makes this really simple. By following their &lt;a href=&#34;https://www.keycloak.org/guides#getting-started&#34;&gt;Getting Started Guide&lt;/a&gt; I could setup a OpenID-Connect provider in just a few minutes and run it directly on my local demo machine. I will show you how I configured Keycloak as an OpenID-Connect provider for Nextcloud.&lt;/p&gt;
&lt;p&gt;After installing Keycloak we go to &lt;code&gt;http://localhost:8080/admin&lt;/code&gt; which is the default URL in &amp;ldquo;standalone&amp;rdquo; mode and login as admin. The first thing we do is to configure a new Realm in the &amp;ldquo;Realm Settings&amp;rdquo;. We only set a Realm name, no &amp;ldquo;resource file&amp;rdquo; needed:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/realm-settings.png&#34; /&gt;
&lt;p&gt;Next we move on to the &amp;ldquo;Clients&amp;rdquo; tab, and created a new client. In the dialog we first set a random &amp;ldquo;Client ID&amp;rdquo;, I have chosen &amp;ldquo;nextcloud&amp;rdquo; in this example.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/add-client.png&#34; /&gt;
&lt;p&gt;On the second page we enable &amp;ldquo;Client authentication&amp;rdquo;&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/add-client-1.png&#34; /&gt;
&lt;p&gt;and on the last page we set the &amp;ldquo;Root URL&amp;rdquo; to the Nextcloud, in this case &amp;ldquo;&lt;a href=&#34;http://nextcloud.local&#34;&gt;http://nextcloud.local&lt;/a&gt;&amp;rdquo;.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/add-client-2.png&#34; /&gt;
&lt;p&gt;All other settings are already set correctly, this is now the final client setting looks like:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/client.png&#34; /&gt;
&lt;p&gt;Finally we create a user who should be able to login to Nextcloud later.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/user.png&#34; /&gt;
&lt;p&gt;While technically the &amp;ldquo;Username&amp;rdquo; is enough I directly set email address, first- and second name. Nextcloud will reuse this information later to pre-fill the users profile nicely. Don&amp;rsquo;t forget to go to the &amp;ldquo;Credentials&amp;rdquo; tab and set a password for your new user.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s it, now we just need to get the client secret fot the final Nextcloud configuration. We can find this in the credential tab of the &amp;ldquo;nextcloud&amp;rdquo; client settings:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/client-secret.png&#34; /&gt;
&lt;h2 id=&#34;nextcloud-setup&#34;&gt;Nextcloud setup&lt;/h2&gt;
&lt;p&gt;Before we continue, make sure to have the following two lines in your config.php:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;&amp;#39;allow_local_remote_servers&amp;#39; =&amp;gt; true,
&amp;#39;debug&amp;#39; =&amp;gt; true,
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Otherwise Nextcloud will refuse to connect to Keycloak on localhost through a unsecure connection (http).&lt;/p&gt;
&lt;p&gt;Now we can move on and configure Nextcloud. If you go to the Nextcloud apps management and search for &amp;ldquo;openid&amp;rdquo; you will not only find the official app but also the community apps. Make sure to chose the app called &amp;ldquo;OpenID Connect user backend&amp;rdquo;. Just to avoid misunderstandings at this point, the Nextcloud community does an awesome job! I&amp;rsquo;m sure the community apps work great too, they may have even more features compared to the official app. But the goal of this article was to try out the officially supported OpenID-Connect app.&lt;/p&gt;
&lt;p&gt;After installing the app we go to the admin settings where we will find a new menu entry called &amp;ldquo;OpenID Connect&amp;rdquo; on the left sidebar and register a new provider:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/nextcloud-oidc.png&#34; /&gt;
&lt;p&gt;The app supports multiple OpenID Connect providers in parallel, so the first thing we do is to chose a &amp;ldquo;Identifier&amp;rdquo; which will be shown on the login page to let the user chose the right provider. For the other fields we enter the &amp;ldquo;Client ID&amp;rdquo;, &amp;ldquo;Client secret&amp;rdquo; and &amp;ldquo;Discovery endpoint&amp;rdquo; from Keycloak. The discovery endpoint looks like the following: &lt;code&gt;http://&amp;lt;your-keycloak-base-url&amp;gt;/realms/&amp;lt;REALM-NAME&amp;gt;/.well-known/openid-configuration&lt;/code&gt;. As you can see there are many more configuration parameters, for example a custom attribute mapping. But for the base installation we are complete.&lt;/p&gt;
&lt;p&gt;Now let&amp;rsquo;s try to login with OpenID Connect:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/nextcloud-login.png&#34; /&gt;
&lt;p&gt;As you can see, we have now an additional button called &amp;ldquo;Login with Keycloak&amp;rdquo;. Once clicked we get redirected to Keycloak:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/keycloak-login.png&#34; /&gt;
&lt;p&gt;After we successfully logged-in to Keycloak we get directly redirected back to Nextcloud and are logged-in. A look into our personal settings shows us that all our account detail like the full name and the email address where added correctly to our Nextcloud account:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc-2023/nextcloud.png&#34; /&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Nextcloud and OpenID-Connect</title>
      <link>https://schiessle.eu/en/articles/2020/07/26/nextcloud-and-openid-connect/</link>
      <pubDate>Sun, 26 Jul 2020 08:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2020/07/26/nextcloud-and-openid-connect/</guid>
      
      <image>https://schiessle.eu/img/nextcloud.png</image>
      
      
      
      <category>Nextcloud</category>
      
      <category>openid</category>
      
      
      
      <description>&lt;p&gt;&lt;strong&gt;NOTE:&lt;/strong&gt; There is a updated version of the article which works with the latest Nextcloud and Keycloak. &lt;a href=&#34;https://schiessle.eu/articles/2023/07/04/nextcloud-and-openid-connect/&#34;&gt;Please continue here!&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you looked at the &lt;a href=&#34;https://apps.nextcloud.com&#34;&gt;Nextcloud app store&lt;/a&gt; you could already find OpenID-Connect connectors before but since Nextcloud 19 it is an officially supported user back-end. So it was time for me to have a closer look at it and to try it out.&lt;/p&gt;
&lt;h2 id=&#34;get-a-openid-connect-provider&#34;&gt;Get a OpenID Connect provider&lt;/h2&gt;
&lt;p&gt;First step was to get an OpenID-Connect provider, sure I could have chosen one of the public services. But why not have a small nice provider running directly on my machine? &lt;a href=&#34;https://www.keycloak.org&#34;&gt;Keycloak&lt;/a&gt; makes this really simple. By following their &lt;a href=&#34;https://www.keycloak.org/guides#getting-started&#34;&gt;Getting Started Guide&lt;/a&gt; I could setup a OpenID-Connect provider in just a few minutes and run it directly on my local demo machine. I will show you how I configured Keycloak as an OpenID-Connect provider for Nextcloud but &lt;strong&gt;please keep in mind&lt;/strong&gt;, this is the first time I configured Keycloak and my main goal was to get it running quickly to test the Nextcloud connector. It is quite likely that I missed some important security setting which you would like to enable for a productive system.&lt;/p&gt;
&lt;p&gt;After installing Keycloak we go to &lt;code&gt;http://localhost:8080/admin&lt;/code&gt; which is the default URL in &amp;ldquo;standalone&amp;rdquo; mode and login as admin. The first thing we do is to configure a new Realm in the &amp;ldquo;Realm Settings&amp;rdquo;. Only &amp;ldquo;Name&amp;rdquo; and &amp;ldquo;Display name&amp;rdquo; need to be set, the rest can be kept as it is:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/realm-settings.png&#34; /&gt;
&lt;p&gt;Next we move on to the &amp;ldquo;Clients&amp;rdquo; tab, and created a new client:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/add-client.png&#34; /&gt;
&lt;p&gt;Set a random &amp;ldquo;Client ID&amp;rdquo;, I chose &amp;ldquo;nextcloud&amp;rdquo; in this example, and the root URL of your Nextcloud which is &lt;code&gt;http://localhost/stable&lt;/code&gt; in this case. After that we get redirected to the client configuration page. Most settings are already set correctly. We only need to adjusted two more settings.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/client.png&#34; /&gt;
&lt;p&gt;First we set the &amp;ldquo;Access Type&amp;rdquo; to &amp;ldquo;confidential&amp;rdquo;, this is needed in order to get a client secret which we need for the Nextcloud setup later on. While the &amp;ldquo;Valid Redirection URIs&amp;rdquo; work as it is with the wildcard, I used the one proposed by the Nextcloud OIDC app &lt;code&gt;http://localhost/stable/index.php/apps/user_oidc/code&lt;/code&gt;. This is the Nextcloud end-point to which Keycloak will redirect the user back after a successful login.&lt;/p&gt;
&lt;p&gt;Finally we create a user who should be able to login to Nextcloud later.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/user.png&#34; /&gt;
&lt;p&gt;While technically the &amp;ldquo;Username&amp;rdquo; is enough I directly set E-Mail address, first- and second name. Nextcloud will reuse this information later to pre-fill the users profile nicely. Don&amp;rsquo;t forget to go to the &amp;ldquo;Credentials&amp;rdquo; tab and set a password for your new user.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s it, now we just need to grab a few information to complete the Nextcloud configuration later on.&lt;/p&gt;
&lt;p&gt;First we go back to the &amp;ldquo;Realm Settings&amp;rdquo; of the &amp;ldquo;OIDCDemo&amp;rdquo;, under &amp;ldquo;OpenID Endpoint Configuration&amp;rdquo; we get a JSON document with all the parameter of our OpenID-Connect end-point. For Nextcloud we only need the &amp;ldquo;authorization_endpoint&amp;rdquo; which we find in the second line of the JSON file.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/authorization_endpoint.png&#34; /&gt;
&lt;p&gt;The second value is the client secret. We can find this in the credential tab of the &amp;ldquo;nextcloud&amp;rdquo; client settings:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/client-secret.png&#34; /&gt;
&lt;h2 id=&#34;nextcloud-setup&#34;&gt;Nextcloud setup&lt;/h2&gt;
&lt;p&gt;Before we continue, make sure to have this line in your config.php &lt;code&gt;&#39;allow_local_remote_servers&#39; =&amp;gt; true,&lt;/code&gt;, otherwise Nextcloud will refuse to connect to Keycloak on localhost.&lt;/p&gt;
&lt;p&gt;Now we can move on and configure Nextcloud. As mentioned before, the official OpenID-Connect app was released together with Nextcloud 19, so you need Nextcloud 19 or later. If you go to the Nextcloud apps management and search for &amp;ldquo;openid&amp;rdquo; you will not only find the official app but also the community apps. Make sure to chose the app called &amp;ldquo;OpenID Connect user backend&amp;rdquo;. Just to avoid misunderstandings at this point, the Nextcloud community does an awesome job! I&amp;rsquo;m sure the community apps work great too, they may even have more features compared to the new official app. But the goal of this article was to try out the officially supported OpenID-Connect app.&lt;/p&gt;
&lt;p&gt;After installing the app we go to the admin settings where we will find a new menu entry called &amp;ldquo;OpenID Connect&amp;rdquo; on the left sidebar. The setup is quite simple but contains everything needed:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/nextcloud-oidc.png&#34; /&gt;
&lt;p&gt;The app supports multiple OpenID Connect providers in parallel, so the first thing we do is to chose a &amp;ldquo;Identifier&amp;rdquo; which will be shown on the login page to let the user chose the right provider. For the other fields we enter the &amp;ldquo;Client ID&amp;rdquo;, &amp;ldquo;Client secret&amp;rdquo; and &amp;ldquo;Discovery endpoint&amp;rdquo; from Keycloak. After accepting the setting by clicking on &amp;ldquo;Register&amp;rdquo; we are done. Now let&amp;rsquo;s try to login with OpenID Connect:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/nextcloud-login.png&#34; /&gt;
&lt;p&gt;As you can see, we have now an additional button called &amp;ldquo;Login with Keycloak&amp;rdquo;. Once clicked we get re-directed to Keycloak:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/keycloak-login.png&#34; /&gt;
&lt;p&gt;After we successfully logged-in to Keycloak we get directly re-directed back to Nextcloud and are logged-in. A look into our personal settings shows us that all our account detail like the full name and the email address where added correctly to our Nextcloud account:&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-oidc/nextcloud.png&#34; /&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Real-time communication and collaboration in a file sync &amp; share environment - A introduction to Nextcloud Talk</title>
      <link>https://schiessle.eu/en/articles/2020/03/07/real-time-communication-and-collaboration-in-a-file-sync-share-environment-a-introduction-to-nextcloud-talk/</link>
      <pubDate>Sat, 07 Mar 2020 08:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2020/03/07/real-time-communication-and-collaboration-in-a-file-sync-share-environment-a-introduction-to-nextcloud-talk/</guid>
      
      <image>https://schiessle.eu/img/nextcloud.png</image>
      
      
      
      <category>Nextcloud</category>
      
      <category>fosdem</category>
      
      <category>cs3</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;At the beginning of this year I gave two times a presentation about Nextcloud Talk. First at the annual CS3 conference in Copenhagen and just one week later at FOSDEM in Brussels. Nextcloud Talk provides a full featured real-time communication platform. Completely Free Software, self-hosted and nicely integrated with all the other aspects of Nextcloud.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2020/03/07/real-time-communication-and-collaboration-in-a-file-sync-share-environment-a-introduction-to-nextcloud-talk/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>New challenges for Free Software business models</title>
      <link>https://schiessle.eu/en/articles/2019/11/17/new-challenges-for-free-software-business-models/</link>
      <pubDate>Sun, 17 Nov 2019 08:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2019/11/17/new-challenges-for-free-software-business-models/</guid>
      
      <image>https://schiessle.eu/img/fsfs.jpg</image>
      
      
      
      <category>fsfe</category>
      
      <category>sfscon</category>
      
      <category>freesoftware</category>
      
      <category>business</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;This year the FSFE community meeting was combined with the &amp;ldquo;South Tyrol Free Software Conference&amp;rdquo; (SFScon) in Bolzano. For me this was a special event because the first international FSFE community meeting ever happened as well at the SFScon in 2006. Back then I met many people from FSFE in person for the first time. For me this was the starting point for getting more and more involved in the Free Software Foundation Europe.&lt;/p&gt;
&lt;p&gt;At this years conference I gave a talk about the &amp;ldquo;New challenges for Free Software business models&amp;rdquo; at the FSFE track. A few weeks ago I published a article about this topic in the &lt;a href=&#34;https://www.linux-magazin.de/ausgaben/2019/10/fsfe-standpunkt/&#34;&gt;German Linux Magazine&lt;/a&gt;. As many of you may know, Free Software as such is not a business model but a license model which can be combined with many different business and development models.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/businessmodels.png&#34; alt=&#34;Distinction between business-, license- and development-model&#34; title=&#34;Distinction between business-, license- and development-model&#34;&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m convinced that working business models around Free Software are a important building block for Free Software to compete successfully with the proprietary software world. The questions how to make money with Free Software and how to build sustainable and strong companies around Free Software are important topics almost right from the beginning of the Free Software movement. Over time we come up with various business models which worked quite well. But the change in technology over the last few years start to put some of the more successful business models at risk. The talk summarized the current challenges and invited the audience to think about possible solutions.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2019/11/17/new-challenges-for-free-software-business-models/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
&lt;p&gt;The recording can be found &lt;a href=&#34;https://peertube.social/videos/watch/309583e7-60fc-4aa8-903b-6fdc1cb51f50&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;After the talk I had many interesting discussions. Most people agreed that this is a problem. One suggestion was to have a look at Mozilla for a successful business model. Another idea was that the big IaaS providers might buy some of the companies behind the software in the future and continue the development, which wouldn&amp;rsquo;t be a problem as long as they would stick to Free Software. Yet another interesting thought was that if you look at the software market as a whole you will realize that Free Software is still a small piece of the cake. As long as the cake as a whole and the Free Software part in particular grows fast we don&amp;rsquo;t have to worry that much how the Free Software part is split up, there will be enough space for everyone. The e.foundation was also mentioned as a possible example for a successful business model and many more ideas floated around.&lt;/p&gt;
&lt;p&gt;I don&amp;rsquo;t want to comment on the individual ideas here but it shows that we had a lively discussion with many interesting ideas and thoughts.&lt;/p&gt;
&lt;p&gt;Do you also have some thoughts around this topic? Feel free to share them in the comments!&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Cultural Techniques</title>
      <link>https://schiessle.eu/en/articles/2019/01/02/cultural-techniques/</link>
      <pubDate>Wed, 02 Jan 2019 00:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2019/01/02/cultural-techniques/</guid>
      
      <image>https://schiessle.eu/img/articles/culture.jpg</image>
      
      
      
      <category>culture</category>
      
      <category>technology</category>
      
      <category>software</category>
      
      <category>kulturtechnik</category>
      
      <category>FreeSoftware</category>
      
      
      
      <description>&lt;p&gt;These days I looked up the German word &amp;ldquo;Kulturtechnik&amp;rdquo; at &lt;a href=&#34;https://de.wikipedia.org/wiki/Kulturtechnik&#34;&gt;Wikipedia&lt;/a&gt; which translates to &amp;ldquo;cultural techniques&amp;rdquo; in English. Surprisingly there is no English Wipipedia article for it, so I have to quote the German one. This section attracted my attention the most:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[Für Kulturtechniken] sind ein oder mehrere Voraussetzungen nötig: das Beherrschen von Lesen, Schreiben und Rechnen, die Fähigkeit zur bildlichen Darstellung, analytische Fähigkeiten, die Anwendung von kulturhistorischem Wissen oder die Vernetzung verschiedener Methoden.&lt;/p&gt;
&lt;p&gt;Bei der Entwicklung von Kulturtechniken handelt es sich nicht um Leistungen von Einzelpersonen, sondern um Gruppenleistungen, die in einem soziokulturellen Kontext entstehen. Alle genannten Voraussetzungen benötigen daher immer die soziale Interaktion und gesellschaftliche Teilhabe (Partizipation).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;According to this description, cultural techniques are not capabilities of individuals but achievements of a collective, done in a socio-cultural context, it always requires social interaction and participation. This means that reading, writing or math are no culture techniques by itself, but collaborative writing would qualify as such, for example with a wiki or any other collaboration platforms.&lt;/p&gt;
&lt;h2 id=&#34;free-software-as-a-cultural-technique&#34;&gt;Free Software as a cultural technique&lt;/h2&gt;
&lt;p&gt;When talking about Free Software I argued already in the past that software is a new cultural technique. My arguments typically was along the line that software is everywhere and shapes our world. Software changed the way we live, learn, work, communicate, participate in society and share our culture. I think that&amp;rsquo;s still true, but this Wikipedia article added an important aspect to me. With the distinction between the tools and what we achieve collectively with it, I think we can argue that software alone is not a cultural technique, but Free Software is.&lt;/p&gt;
&lt;p&gt;By definition &lt;a href=&#34;https://fsfe.org/about/basics/freesoftware&#34;&gt;Free Software&lt;/a&gt; is a licensing model for software. A software license that gives the users the freedom to use, study, share and improve the software makes it Free Software. These days Free Software influence all areas of our live. Cars, airplanes, cash terminals, pay machines, the internet, televisions, smart phones, I could continue the list indefinitely, nothing would be possible without Free Software. The freedom given by the license and the influence it has on all areas of our live changed the way we develop software. A new development model was established and is used for most Free Software these days. The most successful Free Software is developed by open communities with a strong focus on collaboration and participation. This model is embraced by individuals and large organizations. According to the &lt;a href=&#34;https://www.linuxfoundation.org/blog/2017/10/2017-linux-kernel-report-highlights-developers-roles-accelerating-pace-change/&#34;&gt;2017 Linux Kernel Report&lt;/a&gt;, 4300 developers from over 500 companies have contributed to the kernel, with a impressive list of large companies. Everyone works at the same code, often in parallel. People discuss the changes proposed by each other and improve it together until it is ready to be released. The community is not limited to the code, in a similar collaborative way the corresponding design, documentation, artwork and translations are created. People exchange ideas in online forums, real time chats and meet at conferences. All this happens in a transparent and socio-cultural context, open for everyone to join.&lt;/p&gt;
&lt;p&gt;But not only the way Free Software is build, also the usage of the software fits the definition of cultural techniques. From a user perspective, Free Software fosters collaboration and participation in many ways. It can be shared freely so that it encourage collaboration in its area of use. For example pupils can exchange the software they use to do their homework or to prepare their presentation. This teaches a culture of collaboration and make sure that everyone has the same possibilities to participate. Different departments in organizations can exchange software and give it to as much employees as needed without worrying that the maximum number of users, allowed by the license is already exceeded.&lt;/p&gt;
&lt;p&gt;In a world defined by software, access to software decides who has access to our culture, to our communication tools, about our possibilities in education and at work. Free Software makes sure that everyone has the same possibilities to participate in today&amp;rsquo;s society. It fosters collaboration and participation in contrast to proprietary software which divides people and make sure that everyone is on his own.&lt;/p&gt;
&lt;p&gt;All this proves to me that Free Software is the latest cultural technique. As such it requires special attention by policy makers and society. I think it is in all our interest to protect and foster this new cultural technique.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>CS3 Workshop 2018 - Global Scale and the future of Federated Cloud Sharing</title>
      <link>https://schiessle.eu/en/articles/2018/02/01/cs3-workshop-2018-global-scale-and-the-future-of-federated-cloud-sharing/</link>
      <pubDate>Thu, 01 Feb 2018 19:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2018/02/01/cs3-workshop-2018-global-scale-and-the-future-of-federated-cloud-sharing/</guid>
      
      <image>https://schiessle.eu/img/globalscale.jpg</image>
      
      
      
      <category>Nextcloud</category>
      
      <category>cs3</category>
      
      <category>ocm</category>
      
      <category>cloud</category>
      
      <category>federation</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;At this years &lt;a href=&#34;http://cs3.cyfronet.pl/&#34;&gt;CS3 Workshop in Krakow&lt;/a&gt; I presented the current state of Nextcloud&amp;rsquo;s Global Scale architecture. Probably the most interesting part of the talk was the current development in the area of Federated Cloud Sharing, a central component of Global Scale. Originally, Federated Cloud Sharing was developed &lt;a href=&#34;https://www.schiessle.org/articles/2016/07/04/history-and-future-of-cloud-federation/&#34;&gt;by Frank Karlitschek and me in 2014&lt;/a&gt; at ownCloud. These day it enables cloud solutions from ownCloud, Pydio and Nextcloud to exchange files.&lt;/p&gt;
&lt;p&gt;As part of Global Scale we will add federated group sharing in the coming months. Further we want to enable apps to provide additional &amp;ldquo;federated share providers&amp;rdquo; in order to implement federated calendar sharing, federated contact sharing and more.&lt;/p&gt;
&lt;p&gt;The next iteration of Federated Cloud Sharing will be based on the &lt;a href=&#34;https://github.com/GEANT/OCM-API&#34;&gt;Open Cloud Mesh (OCM) specification&lt;/a&gt;. The &lt;a href=&#34;https://wiki.geant.org/display/OCM/Open&amp;#43;Cloud&amp;#43;Mesh&#34;&gt;Open Cloud Mesh initiative&lt;/a&gt; by GÉANT aims to turn our original idea of Federated Cloud Sharing into a vendor neutral standard. Something I explicitly support. In the process of implementing OCM we will propose some minor changes and additions to the existing specification to meet all our requirements. Directly after my talk I received a lot of positive feedback from different members of the Open Cloud Mesh initiative. I was especially happy to hear that PowerFolder already started to implement OCM as well and that our friends at Seafile also want to join us. I&amp;rsquo;m looking forward to work together with the OCM-Community in the following weeks and months in order to make our changes part of the official specification.&lt;/p&gt;
&lt;p&gt;I will write a more detailed article once we have a first prototype of our implementation. For now I want to share my presentation slides with you:&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2018/02/01/cs3-workshop-2018-global-scale-and-the-future-of-federated-cloud-sharing/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Software freedom in the Cloud</title>
      <link>https://schiessle.eu/en/articles/2017/11/14/software-freedom-in-the-cloud/</link>
      <pubDate>Tue, 14 Nov 2017 00:00:00 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2017/11/14/software-freedom-in-the-cloud/</guid>
      
      <image>https://schiessle.eu/img/articles/cloud-in-your-hand.jpg</image>
      
      
      
      <category>FreeSoftware</category>
      
      <category>cloud</category>
      
      <category>saas</category>
      
      <category>freedom</category>
      
      
      
      <description>&lt;p&gt;What does software freedom actually means, in a world where more and more software no longer runs on our own computer but in the cloud? I keep thinking about this topic for quite some time and from time to time I run into some discussions about this topic. For example a few days ago at &lt;a href=&#34;https://mastodon.social/@bjoern/98906420670923130&#34;&gt;Mastodon&lt;/a&gt;. Therefore I think it is time to write down my thoughts on this topic.&lt;/p&gt;
&lt;p&gt;Cloud is a huge marketing term which can actually mean a lot. In the context of this article cloud is meant as something quite similar to SaaS (software as a service). This article will use this terms interchangeable, because this are also the two terms the Free Software community uses to discuss this topic.&lt;/p&gt;
&lt;h2 id=&#34;the-original-idea-of-software-freedom&#34;&gt;The original idea of software freedom&lt;/h2&gt;
&lt;p&gt;At the beginning every software was free. In the 80s, when computer become widely used and people start to make software proprietary in order to maximise their profit, Richard Stallman come up with a incredible hack. He used copyright to reestablish software freedom by defining these four essential freedoms:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The freedom to run the software for every purpose&lt;/li&gt;
&lt;li&gt;The freedom study how the program works and adapt it to your needs&lt;/li&gt;
&lt;li&gt;The freedom to distribute copies&lt;/li&gt;
&lt;li&gt;The freedom to distribute modified versions of the program&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Every software licensed in a way that grants the user this four freedoms is called Free Software. This are the basic rules to establish software freedom in the world of traditional computing, where the software runs on our own devices.&lt;/p&gt;
&lt;p&gt;Today almost no company can exist without using at least some Free Software. This huge success was possible due to a pragmatic move by Richard Stallman, driven by a vision on how a freedom respecting software world should look like. His idea was the starting point for a movement which come up with a complete new set of software licenses and various Free Software operating systems. It enabled people to continue to use computers in freedom.&lt;/p&gt;
&lt;h2 id=&#34;saas-and-the-cloud&#34;&gt;SaaS and the cloud&lt;/h2&gt;
&lt;p&gt;Today we no longer have just one computer. Instead we have many devices such as smart phones, tablets, laptops, smartwatches, small home servers, IoT devices and maybe still a desktop computer at our office. We want to access our data from all this devices and switch during work between the devices seamlessly. That&amp;rsquo;s one of the main reasons why software as a service (SaaS) and the cloud became popular. Software which runs on a server and all the devices can connect to it. But of course this comes with a price, it means that we are relaying more and more on someones else computer instead of running the programs on our own computer. We lose control. This is not completely new, some of this solutions are quite old, others are rather new, some examples are mail servers, social networks, source code hosting platforms, file sharing services, platforms for collaborative work and many more. Many of this services are build with Free Software, but the software only runs on the server of the service provider and so the freedom never arrives at the user. The user stays helpless. We hand over the data to servers we don&amp;rsquo;t control. We have no idea what happens to our data and for many services we have no way to get our data again out of the service. Even if we can export the data we are often helpless because without the software which runs the original service, we can&amp;rsquo;t perform the same operations on our own servers.&lt;/p&gt;
&lt;h2 id=&#34;we-cant-turn-back-the-time&#34;&gt;We can&amp;rsquo;t turn back the time&lt;/h2&gt;
&lt;p&gt;We can&amp;rsquo;t stop the development of such services. History tells us that we can&amp;rsquo;t stop technological progress, whether we like it or not. Telling people not to use it will not have any notable impact. Quite the opposite, we the Free Software movement would lose the reputation we build over the last decades and with it any influence. We would no longer be able to change things for the better. Think again what Richard Stallman did about thirty years ago. He grew up in a world where software was free by default. When computers become a mass market product more and more manufactures turned software into a proprietary product. Instead of developing the powerful idea of Free Software, Richard Stallman could have decided to no longer use this modern computers and ask people to follow him. But would have many people joined him? Would it have stopped the development? I don&amp;rsquo;t think so. We would still have all the computers as we know them today, but without Free Software.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s why I strongly believe that, like thirty years ago, we need again a constructive and forward looking answer to the new challenges, brought to us by the cloud and SaaS. We, the Free Software community, need to be the driving force to lead this new way of computing into a way that respect the users freedom. Same as Richard Stallman did it back then by starting the Free Software movement. All this is done by people, so it&amp;rsquo;s people like us who can influence it.&lt;/p&gt;
&lt;p&gt;Finding answers to this questions requires us to think in new directions. The software license is still the corner stone. Without the software being Free Software everything else is void. But being Free Software is by no means enough to establish freedom in the world of the cloud.&lt;/p&gt;
&lt;h2 id=&#34;what-does-this-mean-to-software-freedom&#34;&gt;What does this mean to software freedom?&lt;/h2&gt;
&lt;p&gt;Having a close look at cloud solutions, we realise that it contains most of the time two categories of software. Software that runs on the server itself and software served by the server but executed on the users computer, so called JavaScript.&lt;/p&gt;
&lt;p&gt;Following the principle of the well established definition of software freedom, the software distributed to the user needs to be Free Software. I would call this the necessary precondition. But by just looking at the license of the JavaScript code we are trying to solve today&amp;rsquo;s problems with the tools of the past, completely ignoring that in the world of SaaS your computer is no longer the primary device. Getting the source code of the JavaScript under a Free Software license is nice but it is not enough to establish software freedom. The JavaScript is tightly connected to the software which runs of the server so users can&amp;rsquo;t change it a lot without breaking the functionality of the service. Further, with each page reload the user gets again the original version of the JavaScript. This means that, with respect to the users freedom, access to the JavaScript code alone is insufficient. Free JavaScript has mainly two benefits: First, the user can study the code and learn how it works and second, maybe reuse parts of it in their own projects. But to establish real software freedom a service needs to fulfil more criteria.&lt;/p&gt;
&lt;p&gt;The user needs access to the whole software stack, both the software which runs on the server and the software which runs the browser. Without the right to use, study, share and improve the whole software stack, freedom will not be possible. That&amp;rsquo;s why the &lt;a href=&#34;https://www.gnu.org/licenses/agpl-3.0&#34;&gt;GNU AGPLv3&lt;/a&gt; is incredible important. Without going into too much details, the big difference is how the license defines the meaning of &amp;ldquo;distribute&amp;rdquo;. This term is critical to the Free Software definition. It defines at which point the rights to use, study, share and improve the software gets transferred to a user. Typically that happens when the user gets a copy of the software. But in the world of SaaS you no longer get a real copy of the software, you just use it over a network connection. The GNU AGPLv3 makes sure that this kind of usage already entitles you to get the source code. Only if both, the software which runs on the server and the software which runs on the browser is Free Software, users can start to consider exercising their freedom. Therefore my minimal definition of freedom respecting services would be that the whole software stack is Free Software.&lt;/p&gt;
&lt;p&gt;But I don&amp;rsquo;t think we should stop here. We need more in order to drive innovation forward in a freedom respecting way. This is also important because various software projects already work on it. Telling them that these extra steps are only &amp;ldquo;nice to have&amp;rdquo; but not really important sends the wrong message.&lt;/p&gt;
&lt;p&gt;If the whole software stack is Free Software we achieved the minimum requirement to allow everyone to set up their own instance. But in order to avoid building many small islands we need to enable the instances to communicated with each other. A feature called federation. We see this already in the area of freedom respecting &lt;a href=&#34;https://en.wikipedia.org/wiki/Distributed_social_network&#34;&gt;social networks&lt;/a&gt; or in the area of &lt;a href=&#34;https://www.schiessle.org/articles/2016/07/04/history-and-future-of-cloud-federation/&#34;&gt;file sync and share&lt;/a&gt;. About a year ago I wrote an article, arguing that this is a feature needed for the &lt;a href=&#34;https://www.schiessle.org/articles/2016/02/12/the-next-generation-of-code-hosting-platforms/&#34;&gt;next generation code hosting platforms&lt;/a&gt; as well. I&amp;rsquo;m happy to see that GitLab started to look into exactly &lt;a href=&#34;https://gitlab.com/gitlab-org/gitlab-ce/issues/4013&#34;&gt;this&lt;/a&gt;. Only if many small instances can communicate with each other, completely transparent for the user so that it feels like one big service, exercising your freedom to run your own server becomes really interesting. Think for a moment about the World Wide Web. If you browse the Internet it feels like one gigantic universe, the web. It doesn&amp;rsquo;t matter if the page you navigate to is located at the same server or on a different ones, thousands of kilometres away from each other.&lt;/p&gt;
&lt;p&gt;If we reach the point where the technology is build and licensed in a way that people can decide freely where to run a particular service, there is one missing piece. We need a way to migrate from one server to another. Let&amp;rsquo;s say you start using a service provided by someone but at some point you want to move to a different provider or decide to run your own server. In this case you need a way to export your data from the first server and import it to the new one. Ideally in a way which allows you to keep the connection to your friends and colleagues, in case of a service which provides collaboration or social features. Initiatives like the &lt;a href=&#34;https://userdatamanifesto.org/&#34;&gt;User Data Manifesto&lt;/a&gt; thought already about it and gave some valuable answers.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;How do we achieve practical software freedom in the world of the cloud? In my opinion this are the corner stones:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Free Software&lt;/em&gt;, the whole software stack, this means software which runs on the server and on the users browser, needs to be free. Only then people can exercise their freedom.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Control&lt;/em&gt;, people need to stay in control of their data and need to be able to export/import them in order to move.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;em&gt;Federation&lt;/em&gt;, being able to exercise your freedom to run your own instance of a service without creating small islands and losing the connection to your friends and colleagues.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This is my current state of thinking, with respect to this subject. I&amp;rsquo;m happy to hear more opinions about this topic.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Nextcloud Conference 2017: Free Software licenses in a Nutshell</title>
      <link>https://schiessle.eu/en/articles/2017/09/25/nextcloud-conference-2017-free-software-licenses-in-a-nutshell/</link>
      <pubDate>Mon, 25 Sep 2017 15:44:52 +0200</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2017/09/25/nextcloud-conference-2017-free-software-licenses-in-a-nutshell/</guid>
      
      <image>https://schiessle.eu/img/nextcloud.png</image>
      
      
      
      <category>FreeSoftware</category>
      
      <category>licenses</category>
      
      <category>agplv3</category>
      
      <category>nextcloud</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;At this years Nextcloud conference I gave a lightening talk about Free Software licenses. Free Software developers often like to ignore the legal aspects of their project, still I think it is important to know at least some basics. The license you chose and other legal decisions you make are a important cornerstone to define the basic rules of the community around your code. Making good choices can enable a level playing field for a large, diverse and growing community.&lt;/p&gt;
&lt;p&gt;Explaining this huge topic in just five minutes was a tough challenge. The goal was to explain why we are doing things the way we are doing it. For example why we introduced the &lt;a href=&#34;https://github.com/nextcloud/server/blob/master/contribute/developer-certificate-of-origin&#34;&gt;Developer Certificate of Origin&lt;/a&gt;, a tool to create legal certainty, used by many large Free Software initiatives such as Linux, Docker or Eclipse these days. Further the goal was to transfer some knowledge about license compatibility and give some useful pointers for app developers how to decide whether a third party license is compatible or not. If the five minute lightening talk was to fast (and yes, I talked quite fast to match the time limit) or if you couldn&amp;rsquo;t attend, here are the slides to reread it:&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2017/09/25/nextcloud-conference-2017-free-software-licenses-in-a-nutshell/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>The most sincere form of flattery</title>
      <link>https://schiessle.eu/en/articles/2017/02/14/the-most-sincere-form-of-flattery/</link>
      <pubDate>Tue, 14 Feb 2017 10:51:31 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2017/02/14/the-most-sincere-form-of-flattery/</guid>
      
      <image>https://schiessle.eu/img/articles/looking-for-freedom.jpg</image>
      
      
      
      <category>agpl</category>
      
      <category>licenses</category>
      
      <category>nextcloud</category>
      
      
      
      <description>&lt;p&gt;&lt;a href=&#34;https://nextcloud.com&#34;&gt;Nextcloud&lt;/a&gt; now exists for almost exactly 8 months. During this time we put a lot of efforts in polishing existing features and developing new functionality which is crucial to the success of our users and customers.&lt;/p&gt;
&lt;p&gt;As promised, everything we do is &lt;a href=&#34;https://fsfe.org/about/basics/freesoftware.en.html&#34;&gt;Free Software&lt;/a&gt; (also called Open Source), licensed under the terms of the &lt;a href=&#34;https://www.gnu.org/licenses/agpl-3.0&#34;&gt;GNU APGLv3&lt;/a&gt;. This gives our users and customers the most possible flexibility and independence. The ability to use, study, share and improve the software also allows to integrate our software in other cloud solutions as long as you respect the license and we are happy to see that people make use of this rights actively.&lt;/p&gt;
&lt;h2 id=&#34;code-appearing-in-other-app-stores&#34;&gt;Code appearing in other app stores&lt;/h2&gt;
&lt;p&gt;We are proud to see that the quality of our software is not only acknowledged by our own users but also by users of other cloud solutions. Recently more and more of our applications show up at the ownCloud App Store. For example the community driven &lt;a href=&#34;https://apps.owncloud.com/content/show.php/News?content=174796&#34;&gt;News app&lt;/a&gt; or the &lt;a href=&#34;https://apps.owncloud.com/content/show.php/Server&amp;#43;info?content=174795&#34;&gt;Server Info app&lt;/a&gt;, developed by the Nextcloud GmbH. Additionally we have heard that our &lt;a href=&#34;https://github.com/nextcloud/user_saml&#34;&gt;SAML authentication application&lt;/a&gt; is widely considered far better quality than other, even proprietary alternatives, and used by customers of our competitors in especially the educational market. All this is completely fine as long as the combination of both, our application and the rest of the server, is licensed under the terms of the GNU AGPLv3.&lt;/p&gt;
&lt;h2 id=&#34;not-suitable-for-mixing-with-enterprise-versions&#34;&gt;Not suitable for mixing with enterprise versions&lt;/h2&gt;
&lt;p&gt;While we can’t actively work on keeping our applications compatible with other cloud solutions, we welcome every 3rd party efforts on it. The only draw-back, most of the other cloud solutions out there make a distinction between home users and enterprises on a license level. While home users get the software under a Free Software license, compatible with the license of our applications, Enterprise customers don’t get the same freedom and independence and are therefore not compatible with the license we have chosen. This means that all the users who uses propriety cloud solutions (often hidden by the term “Enterprise version”) are not able to legally use our applications. We feel sorry for them, but of course a solution exists – get support from the people who wrote your software rather than a different company. In general, we would recommend buying support for real Free Software and not just Open Source marketing.&lt;/p&gt;
&lt;p&gt;Of course we don’t want to sue people for copyright violation. But Frank choose the AGPL license 7 years ago on purpose and we want to make sure that the users of our software understand the license and it’s implications. In a nutshell, the GNU AGPLv3 gives you the right to do with the software whatever your want and most important all the entrepreneurial freedom and independence your business needs, as long as the combined work is again licensed under the GNU AGPLv3. By combining GNU AGPLv3 applications with a proprietary server, you violate this rule and thus the terms of the license. I hope that other cloud solutions are aware of this problem, created by their open-core business model, and take some extra steps to protect their customers from violating the license of other companies and individual contributors. For example by performing a license check before a application gets enabled.&lt;/p&gt;
&lt;h2 id=&#34;open-core-is-a-bad-model-for-software-development&#34;&gt;Open Core is a bad model for software development&lt;/h2&gt;
&lt;p&gt;This is one of many problems arising from the usage of open core business models. It puts users on risk if they combine the proprietary part with Free Software, more about it can be read &lt;a href=&#34;https://nextcloud.com/blog/8-ways-businesses-benefit-from-purchasing-open-source/&#34;&gt;here&lt;/a&gt;. That’s why we recommend all enterprise and home users to avoid a situation where proprietary and free licensed software is combined. This is a legal minefield. We at Nextcloud decided to take a clear stance on it. Everything is Free Software and there is only one version of the software for both home users and enterprises. Thus allows every home user, customer or partner to use all applications available as long as they respect the license.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Cloud Federation – Getting Social</title>
      <link>https://schiessle.eu/en/articles/2016/12/13/cloud-federation-getting-social/</link>
      <pubDate>Tue, 13 Dec 2016 10:45:48 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/12/13/cloud-federation-getting-social/</guid>
      
      <image>https://schiessle.eu/img/articles/nextcloud-user-profile.png</image>
      
      
      
      <category>federation</category>
      
      <category>nextcloud</category>
      
      <category>social</category>
      
      
      
      <description>&lt;p&gt;With &lt;a href=&#34;https://nextcloud.com/blog/nextloud-11-sets-new-standard-for-security-and-scalability/&#34;&gt;Nextcloud 11&lt;/a&gt; we continue to work on one of our hot topics: Cloud Federation. This time we focus on the social aspects. We want to make it as easy as possible for people to share their contact information. This enabled users to find each other and to start sharing. Therefore we extended the user profile in the personal settings. As the screenshot at the top shows, users can now add a wide range of information to their personal settings and define the visibility for each of them by clicking on the small icon next to it.&lt;/p&gt;
&lt;h2 id=&#34;privacy-first&#34;&gt;Privacy first&lt;/h2&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-user-profile-visibility.png&#34; alt=&#34;Change visibility of personal settings&#34; style=&#34;float: right&#34; /&gt;
&lt;p&gt;We take your privacy serious. That’s why we provide fine grained options to define the visibility of each personal setting. By default all new settings will be private and all settings which already exists before will have the same visibility as on Nextcloud 10 and earlier. This means that the users full name and avatar will only be visible to users on the same Nextcloud server, e.g. through the share dialog. If enabled by the administrator, this values, together with the users email address, will be synced with trusted servers to allow users from trusted servers to share with each other seamlessly.&lt;/p&gt;
&lt;p&gt;As shown at the screenshot at the right we provide three levels of visibility: “Private”, “Contacts” and “Public”. Private settings will be only visible to you, even users on the same server will not have access to it. The only exceptions are the avatar and the full name because this are central data used at Nextcloud for activities, internal shares, etc. Settings which are set to “Contacts” will be shared with users on the same server and trusted servers, defined by the administrator of the Nextcloud server. Public data will be synced to a global and public address book.&lt;/p&gt;
&lt;h2 id=&#34;introducing-the-global-address-book&#34;&gt;Introducing the global address book&lt;/h2&gt;
&lt;p&gt;The best real world equivalent to the global address book is a telephone directory. For a new phone number people can chose to publish their phone number together with their name and address to a public telephone directory to enable other people to find them. The global address book follows the same pattern. By default nothing gets published to the global address book. Only if the user sets at least one value in their personal settings to “Public”. In this case all the public data will be synced to the global address book together with the users Federated Cloud ID. Users can remove their data at any time again by simply setting their personal data back to “Contacts” or “Private”.&lt;/p&gt;
&lt;p&gt;In order to use the global address book as a source to find new people, this lookup needs to be enabled explicitly in the “Federated Cloud Sharing” settings by the administrator. For privacy reasons this is disabled by default. If enabled the share dialog of Nextcloud will query the global address book every time a user wants to share a file or folder, and suggest people found in the global address book. In the future there might be a dedicated button to access the global address book, both for performance reasons and to make the feature more discoverable.&lt;/p&gt;
&lt;h3 id=&#34;future-work&#34;&gt;Future work&lt;/h3&gt;
&lt;p&gt;The global address book can return many results for a given name. How do we know that we share with the right person? Therefore we want to add the possibility to verify the users email address, website and Twitter handle in Nextcloud 12. As soon as this feature is implemented the global address book will only return users where at least one personal setting is verified and also visualize the verified data so that the user can use this information to pick the right person.&lt;/p&gt;
&lt;p&gt;Further, I want to extend the meaning of “Contacts” in one of the next versions. The idea is that “Contacts” should not be limited to trusted servers but include the users personal contacts. For example the data set to “Contacts” could be shared with every person to which the user already established at least one federated share successfully, or to all contacts with a Federated Cloud ID in the users personal address book. This way we will move slowly in the direction of some kind of decentralized and federated social network based on the users address book. This will also enable users to easily push their new phone number or other personal data to all their friends and colleagues, things for which most people use centralized and proprietary services like so called “business networks” these days.&lt;/p&gt;
&lt;p&gt;Another interesting possibility, made possible by the global address book is to move complete user accounts from one server to another. Given that the user published at least some basic information on the global address book, they could use it to announce their move to another server. Other Nextcloud servers could find this information and make sure that existing federated shares continue to work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Keynote at Open16 - Restore the Internet</title>
      <link>https://schiessle.eu/en/articles/2016/09/29/keynote-at-open16-restore-the-internet/</link>
      <pubDate>Thu, 29 Sep 2016 08:02:32 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/09/29/keynote-at-open16-restore-the-internet/</guid>
      
      <image>https://schiessle.eu/img/nextcloud.png</image>
      
      
      
      <category>nextcloud</category>
      
      <category>federation</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;This year I was invented to the Open16 in Mechelen (Belgium) to give a keynote.
It was a really nice event with many interesting presentation and talks.&lt;/p&gt;
&lt;p&gt;I was asked by the organizer to started the keynote with the history of Nextcloud.
Why did we started Nextcloud and what do we want to do different. Then I moved on
with the main topic: &amp;ldquo;Restore the Internet - free, decentralized, open&amp;rdquo;. Why it is
important and what we are doing at Nextcloud to make it happen. This are the slides
to my talk:&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2016/09/29/keynote-at-open16-restore-the-internet/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Transfer Public Links to Federated Shares</title>
      <link>https://schiessle.eu/en/articles/2016/07/21/transfer-public-links-to-federated-shares/</link>
      <pubDate>Thu, 21 Jul 2016 09:56:48 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/07/21/transfer-public-links-to-federated-shares/</guid>
      
      <image>https://schiessle.eu/img/articles/nextcloud-transform-public-link.svg</image>
      
      
      
      <category>federation</category>
      
      <category>nextcloud</category>
      
      
      
      <description>&lt;p&gt;Creating public links and sending them to your friends is a widely used feature of &lt;a href=&#34;https://nextcloud.com/&#34;&gt;Nextcloud&lt;/a&gt;. If the recipient of a public link also has a Nextcloud or ownCloud account he can use the “Add to your Nextcloud” button to mount the content over WebDAV to his server. On a technical level all mounted public links use the same token, the one of the public link, to reference the shared file. This means that as soon as the owner removes the public link all mounts will disappear as well. Additionally, the permissions for public links are limited compared to normal shares, public links can only be shared read-only or read-write. This was the first generation of federated sharing which we introduced back in 2014.&lt;/p&gt;
&lt;p&gt;A year later we introduced the possibility to create federated shares directly from the share dialog. This way the owner can control all federated shares individually and use the same permission set as for internal shares. Both from a user perspective and from a technical point of view this lead to two different ways to create and to handle federated shares. With Nextcloud 10 we finally bring them together.&lt;/p&gt;
&lt;h2 id=&#34;improvements-for-the-owner&#34;&gt;Improvements for the owner&lt;/h2&gt;
&lt;div class=&#34;article-image&#34; style=&#34;float: right; width: 200px&#34;&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-convert-public-link-to-federated-share.png&#34;
alt=&#34;Public Link Converted to a Federated Share&#34; width=200px/&gt;
&lt;p class=&#34;image-description&#34;&gt;
    Public link converted to a federated share for bjoern@myNextcloud.net
  &lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;From Nextcloud 10 on every mounted link share will be converted to a federated share, as long as the recipient also runs Nextcloud 10 or newer. This means that the owner of the file will see all the users who mounted his public link. He can remove the share for individual users or adjust the permissions. For each share the whole set of permissions can be used like “edit”, “re-share” and in case of folder additionally “create” and “delete”. If the owner removes the original public link or if it expires all federated shares, created by the public link will still continue to work. For older installations of Nextcloud and for all ownCloud versions the server will fall-back to the old behavior.&lt;/p&gt;
&lt;h2 id=&#34;improvements-for-the-user-who-mounts-a-public-link&#34;&gt;Improvements for the user who mounts a public link&lt;/h2&gt;
&lt;div class=&#34;article-image&#34; style=&#34;float: left; width: 310px&#34;&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-mount-public-link.png&#34;
alt=&#34;After opening a public link the user can convert a public link to a federated share by adding his Federated Cloud ID or his Nextcloud URL&#34; width=310px/&gt;&lt;/a&gt;
&lt;p class=&#34;image-description&#34;&gt;
   After opening a public link the user can convert it to a federated share by
   adding his Federated Cloud ID or his Nextcloud URL
  &lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Users who receive a public link and want to mount it to their own Nextcloud have two options. They can use this feature as before and enter the URL to their Nextcloud to the “Add to your Nextcloud” field. In this case they will be re-directed to their Nextcloud, have to login and confirm the mount request. The owners Nextcloud will then send the user a federated share which he has to accept. It can happen that the user needs to refresh his browser window to see the notification.&lt;/p&gt;
&lt;p&gt;Additionally there is a new and faster way to add a public link to your Nextcloud. Instead of entering the URL to the “Add to your Nextcloud” field you can directly enter your federated cloud ID. This way the owners Nextcloud will send the federated share directly to you and redirect you to your server. You will see a notification about the new incoming share and can accept it. Now the user also benefit from the new possibilities of the owner. The owner can give him more fine grained permissions and from the users point of view even more important, he will not lose his mount if the public link gets removed or expires.&lt;/p&gt;
&lt;p&gt;Nextcloud 10 introduces another improvement in the federation area: If you re-share a federated share to a third server, a direct connection between the first and the third server will be created now so that the owner of the files can see and control the share. This also improves performance and the potential error rate significantly, avoiding having to go through multiple servers in between.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>History and Future of Cloud Federation</title>
      <link>https://schiessle.eu/en/articles/2016/07/04/history-and-future-of-cloud-federation/</link>
      <pubDate>Mon, 04 Jul 2016 11:22:33 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/07/04/history-and-future-of-cloud-federation/</guid>
      
      <image>https://schiessle.eu/img/articles/nextcloud-federated-cloud-sharing.jpg</image>
      
      
      
      <category>federation</category>
      
      <category>nextcloud</category>
      
      <category>owncloud</category>
      
      
      
      <description>&lt;p&gt;I’m now working for about two years on something called Federated Cloud Sharing. It started on June, 23er 2014 with the release of ownCloud 7.0. Back then it was simply called “Server to Server sharing”. During all this years I never wrote about the broader ideas behind this technology, why we do it, what we achieved and where we are going.&lt;/p&gt;
&lt;h2 id=&#34;motivation&#34;&gt;Motivation&lt;/h2&gt;
&lt;p&gt;The Internet started as a decentralized network, meant to be resilient to disruptions, both due to accidents or malicious activity. This was one of the key factors which made the Internet successful. From the &lt;a href=&#34;https://en.wikipedia.org/wiki/World_Wide_Web&#34;&gt;World Wide Web&lt;/a&gt;, over &lt;a href=&#34;https://en.wikipedia.org/wiki/Internet_Relay_Chat&#34;&gt;IRC&lt;/a&gt;, &lt;a href=&#34;https://en.wikipedia.org/wiki/Usenet_newsgroup&#34;&gt;news groups&lt;/a&gt;, &lt;a href=&#34;https://en.wikipedia.org/wiki/Email&#34;&gt;e-mail&lt;/a&gt; to &lt;a href=&#34;https://en.wikipedia.org/wiki/XMPP&#34;&gt;XMPP&lt;/a&gt;. Everything was designed as decentralized networks, which is why if you are on the Google servers you can email people at Yahoo. Everybody can set up his own web server, e-mail or chat server and communicate with everyone else. Individuals up to large organisations could easily join the network, participate and build business without barriers. People could experiment with new innovative ideas and nobody had the power to stop them or to slow them down. This was only possible because all underlying technology and protocols were build on both &lt;a href=&#34;https://fsfe.org/activities/os/os&#34;&gt;Open Standards&lt;/a&gt; and &lt;a href=&#34;https://fsfe.org/freesoftware/basics/summary&#34;&gt;Free Software&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This changed dramatically over the last ten years. Open and inclusive networks were replaced by large centralized services operated by large companies. In order to present yourself or your business in the public it was no longer enough to have your own website, you had to have a page on one or two key platforms. For communication it was no longer enough to have a e-mail address, or be on one of the many IRC or XMPP servers. Instead people expected that you have a account on one of the major communication platforms. This created huge centralized networks, with many problems for privacy, security and self-determination. To talk to everybody, you have to have an account on Facebook, at Google, Skype, Whatsapp, Signal and so on. The centralization also made it quite easy to censor people or manipulate their view by determining the content presented to them. The algorithms behind the Facebook news feed or the “what you missed” in Twitter are very clever — or so we assume, as we don’t know how they work or determine what is important.&lt;/p&gt;
&lt;p&gt;The last few years many initiatives started to solve this problem in various ways, for example by developing &lt;a href=&#34;https://en.wikipedia.org/wiki/Distributed_social_network&#34;&gt;distributed social networks&lt;/a&gt;. I work in the area of liberating people who share and sync all sort of data. We saw the rise of successfully projects such as &lt;a href=&#34;https://owncloud.org&#34;&gt;ownCloud&lt;/a&gt;, &lt;a href=&#34;https://pyd.io&#34;&gt;Pydio&lt;/a&gt; and now of course &lt;a href=&#34;https://nextcloud.com&#34;&gt;Nextcloud&lt;/a&gt;. They all have in common that they built Free Software platforms based to a large extend on Open Standards to allow people to host, edit and share their data without giving up control and privacy. This was a huge step in creating more competition and restoring decentralized structures. But it also had one big drawback. It created many small islands. You could only collaborate with people on the same server, but not with others who run their own server. This leads us to the concept of federated cloud sharing.&lt;/p&gt;
&lt;h2 id=&#34;server-to-server-sharing&#34;&gt;Server to Server Sharing&lt;/h2&gt;
&lt;p&gt;The first version of this ideas was implemented in ownCloud 7.0 as “Server to Server Sharing”. ownCloud already knew the concept of sharing anonymous links with people outside of the server. And, as ownCloud offered both a WebDAV interface and could mount external WebDAV shares, it was possible to manually hook a ownCloud into another ownCloud server. Therefore the first obvious step was to add a “Add to your ownCloud” button to this link shares, allowing people to connect such public links with their cloud by mounting it as a external WebDAV resource.&lt;/p&gt;
&lt;img class=&#34;article-image center&#34; src=&#34;https://schiessle.eu/img/articles/owncloud-mount-public-link-example.png&#34; /&gt;
&lt;h2 id=&#34;federated-cloud-sharing&#34;&gt;Federated Cloud Sharing&lt;/h2&gt;
&lt;p&gt;Server to server sharing already helped a lot to establish some bridges between many small islands created by the ability to self-host your cloud solution. But it was still not the kind of integration people where used to from the large centralized services and it only worked for ownCloud, not across various open source file sync and share solutions.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-personal-settings-personal-cloud-id.png&#34; alt=&#34;federated-cloud-id&#34; width=&#34;713&#34; /&gt;
&lt;p&gt;The next iteration of this concept introduced what we called a “federated cloud ID”, which looks similar to a e-mail address and, like email, refers to a user on a specific server. This ID could then be used in the normal share dialog to share files with people on a different server!&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-share-dialog-federated-sharing.jpg&#34; class=&#34;article-image center&#34; /&gt;
&lt;p&gt;The way servers communicate with each other in order to share a file with a user on a different server was &lt;a href=&#34;http://karlitschek.de/2015/08/announcing-the-draft-federated-cloud-sharing-api/&#34;&gt;publicly documented&lt;/a&gt; with the goal to create a standardized protocol. To further the protocol and to invite others to implement it we started the Open Cloud Mesh project together with GÉANT, an European research collaboration initiative. Today the protocol is already implemented by ownCloud, Pydio and &lt;a href=&#34;https://nextcloud.com/nextcloud-joins-open-cloud-mesh/&#34;&gt;now Nextcloud&lt;/a&gt;. This enables people to seamlessly share and collaborate, no matter if everyone is on the same server or if people run their own cloud server based on one of the three supporting servers.&lt;/p&gt;
&lt;h2 id=&#34;trusted-servers&#34;&gt;Trusted Servers&lt;/h2&gt;
&lt;p&gt;In order to make it easier to find people on other servers we introduced the concept of “trusted servers” as one of our last steps. This allows administrator to define other servers they trust. If two servers trust each other they will sync their user lists. This way the share dialogue can auto-complete not only local users but also users on other trusted servers. The administrator can decide to define the lists of trusted servers manually or allow the server to auto add every other server to which at least one federated share was successfully created. This way it is possible to let your cloud server learn about more and more other servers over time, connect with them and increase the network of trusted servers.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-trusted-servers.png&#34; class=&#34;article-image center&#34; /&gt;
&lt;h2 id=&#34;open-challenges-where-we8217re-taking-federated-cloud-sharing&#34;&gt;Open Challenges: where we’re taking Federated Cloud Sharing&lt;/h2&gt;
&lt;p&gt;Of course there are still many areas to improve. For example the way you can discover users on different server to share with them, for which we’re working on a global, shared address book solution. Another point is that at the moment this is limited to sharing files. A logical next step would be to extend this to many other areas like address books, calendars and to real-time text, voice and video communication and we are, of course, planning for that. I will write about this in greater detail in on of my next blogs but if you’re interested in getting involved, you are invited to &lt;a href=&#34;https://github.com/nextcloud&#34;&gt;check out what we’re up to on GitHub&lt;/a&gt; and of course, you can contact me any time.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Freedom for whom?</title>
      <link>https://schiessle.eu/en/articles/2016/06/15/freedom-for-whom/</link>
      <pubDate>Wed, 15 Jun 2016 20:34:22 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/06/15/freedom-for-whom/</guid>
      
      <image>https://schiessle.eu/img/articles/we-want-freedom.jpg</image>
      
      
      
      <category>business</category>
      
      <category>cla</category>
      
      <category>FreeSoftware</category>
      
      <category>nextcloud</category>
      
      
      
      <description>&lt;p&gt;This discussion is really old. Since the first days of the Free Software movement people like to debate to whom the freedom in Free Software is directed? The users? The code? The developers? Often this goes along with a discussion about &lt;a href=&#34;https://www.gnu.org/copyleft/&#34;&gt;copyleft&lt;/a&gt; vs non-protecting Free Software licenses like the BSD- and the MIT-License. I don’t want to repeat this discussion but look at the question from a complete different angle. I want to look at it from the position of a software company and its business model.&lt;/p&gt;
&lt;p&gt;If you talk to Free Software companies you realize, that very few have a business model completely based on Free Software. Most companies add proprietary extensions on top and use this as the main incentive for customers to buy their software. In 2008 Andrew Lampitt coined the term &lt;a href=&#34;https://en.wikipedia.org/wiki/Open_core&#34;&gt;open core&lt;/a&gt; to describe this kind of business models. There are many ways to argue in favor of open core. One argument I hear quite often is that the proprietary parts are only useful for large enterprises, so nothing is taken away from the community. This way the community gets reduced to the typical home user, which is a interesting way of looking at it. Why should we make such a distinction? And why does home users deserve software freedom more then large organizations?&lt;/p&gt;
&lt;p&gt;I understand that freedom in the context of software is a concept which can sound scary to some companies at the beginning. After all, that was the main reason why Open Source was invented, a &lt;a href=&#34;https://web.archive.org/web/20021217003716/http://www.opensource.org/advocacy/faq.html&#34;&gt;marketing campaign for Free Software&lt;/a&gt; to make business people feel more comfortable. Interestingly this changes quickly if you go into more details about what software freedom really means. More entrepreneurial freedom, control over the tools they use, software freedom as a precondition for privacy and security, independence, freedom to chose the supplier with the best offering and in case of software development the freedom to build on existing, well established technology instead of building everything from scratch. These are freedoms well understood and appreciated by entrepreneurs and they demand it in many other areas of their daily business. This lead me to the conclusion that software freedom is not only something for home users but it also important for large organizations.&lt;/p&gt;
&lt;p&gt;Open core often comes with a important side-effects. Most companies pick a strong copyleft license like the GNU GPL or the GNU AGPL, and then demand that every contributor signs a Contributor License Agreement (CLA). This CLA puts the company in a strong position. They are the only one who can distribute the software under a proprietary license and add proprietary extensions. This effectively removes one of the biggest strengths of copyleft licenses. If you set CLAs aside, copyleft licenses are a great tool to create an ecosystem of equal participants. Equality is really important to make individuals and organizations feel confident that joining the initiative is worthwhile in the long term. Everybody having the same rights and the same duties is the only way to develop a strong ecosystem with many participants. Therefore it is no wonder that projects using CLAs often get slowed down and have a less diverse community.&lt;/p&gt;
&lt;p&gt;RedHat was one of the first company which understood that all this, CLA’s and proprietary extensions, do more harm than good. It slows down the development. It keeps your community smaller as necessary and it adds the burden to develop all the proprietary extensions by your own instead of leveraging the power of a large community which can consists of employees, hobbyists, partners and customers. This goes so far that &lt;a href=&#34;http://readwrite.com/2013/08/13/red-hat-ceo-centos-open-source/&#34;&gt;RedHat even embrace competitors like CentOS&lt;/a&gt;, which basically gives RedHat Enterprise Linux away for free to people who don’t need the support. For a truly open organization this is not a problem but a great opportunity to spread the software and to become more popular. That’s a key factor to make sure, that RedHat is the de facto standard if it comes to enterprise GNU/Linux distributions.&lt;/p&gt;
&lt;p&gt;If a initiative is driven by a strong company it can be useful to move some parts out to a neutral entity. RedHat did this by founding the &lt;a href=&#34;https://getfedora.org/&#34;&gt;Fedora project&lt;/a&gt;. Another way to do this is by creating a foundation which makes sure that everyone has the same rights. Such a foundation should hold all rights necessary to make sure the project can continue no matter what happens to individual participants, including companies. For the governance of such a foundation it is important that it is not controlled by a single entity.&lt;/p&gt;
&lt;p&gt;This is exactly what makes me feel so excited about what we are doing at Nextcloud. We are building a complete free cloud solutions, not only for home users but for everyone. This solution will be much more than just file sync and share, from a company point of view stuff like calendar, contacts and video conferencing will become a first class citizen. All this will be Free Software, developed together with a great community. Home users, customers and partners are invited to be part of it, not just as a consumer but as part of a large and diverse community. Everybody should be empowered to change things to the better. In order to make all this independent from a single company we will set up a foundation. As described above the foundation will make sure that we have a intact and growing ecosystem with no single point of failure. This guarantees that Nextcloud can survive us and any other participant if needed.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Road Ahead</title>
      <link>https://schiessle.eu/en/articles/2016/05/26/road-ahead/</link>
      <pubDate>Thu, 26 May 2016 08:02:32 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/05/26/road-ahead/</guid>
      
      <image>https://schiessle.eu/img/articles/road-ahead.jpg</image>
      
      
      
      <category>community</category>
      
      <category>future</category>
      
      <category>owncloud</category>
      
      <category>personal</category>
      
      
      
      <description>&lt;p&gt;I just realized that at June, 1 it is exactly four years since I joined &lt;a href=&#34;https://owncloud.com/&#34;&gt;ownCloud Inc&lt;/a&gt;. That’s a perfect opportunity to look back and to tell you about some upcoming changes. I will never forget how all this get started. It was FOSDEM 2012 when I met &lt;a href=&#34;http://karlitschek.de&#34;&gt;Frank&lt;/a&gt;, we already knew each other from various Free Software activities. I told him that I was looking for new job opportunities and he told me about ownCloud Inc. The new company around the &lt;a href=&#34;https://owncloud.org/&#34;&gt;ownCloud&lt;/a&gt; initiative which he just started together with the help of others. I was directly sold to the idea of ownCloud and a few months later I was employee number six at ownCloud Inc.&lt;/p&gt;
&lt;p&gt;This was a huge step for me. Before joining ownCloud I worked as a researcher at the University of Stuttgart, so this was the first time I was working as a full-time software engineer on a real-world project. I also didn’t write any noteworthy PHP code before. But thanks to a awesome community I got really fast into all the new stuff and could speed up my contributions. During the following years I worked on many different aspects of ownCloud, from sharing, over files versions to the deleted files app up to a complete re-design of the server-side encryption. I’m especially happy that I could contribute substantial parts to a feature called &lt;a href=&#34;http://blog.schiessle.org/2016/03/14/federated-sharing-whats-new-in-owncloud-9-0/&#34;&gt;“Federated Cloud Sharing”&lt;/a&gt;, from my point of view one of the most important feature to move ownCloud to the next level. Today it is not only possible to share files across various ownCloud servers but also between other cloud solutions like Pydio.&lt;/p&gt;
&lt;p&gt;But the technical part is only a small subset of the great experience I had over the last four years. Working with a great community is just amazing. It is important to note that with community I mean everyone, from co-workers and students to people who contributed great stuff to ownCloud in their spare time. We are all ownCloud, there should be no distinction! We not only worked together in a virtual environment but meet regularly in person at Hackathons, various conferences and at the annual ownCloud conference. I met many great people during this time which I can truly call friends today. I think this explains why ownCloud was never just a random job to me and why I spend substantial parts of my spare time going to conferences, giving talks or helping at booths. ownCloud combined all the important parts for me: People, Free Software, Open Standards and Innovation.&lt;/p&gt;
&lt;p&gt;Today I have to announce that I will move on. May, 25 was my last working day at the ownCloud company. This is a goodbye and thank you to ownCloud Inc. for all the opportunities the company provided to me. But it is in no way a goodbye to all the people and to ownCloud as a project. I’m sure we will stay in contact! That’s one of many great aspects of Free Software. If it is done right a initiative is much more than any company which might be involved. Leaving a company doesn’t mean that you have to leave the people and the project behind.&lt;/p&gt;
&lt;p&gt;Of course I will continue to work on Free Software and with great communities, especially I have no plans to leave the ownCloud community. Actually I hope that I can even re-adjust my Free Software and community focus in the future… Stay tuned.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Guake Terminal Improvement for Multi-Monitor Setups</title>
      <link>https://schiessle.eu/en/articles/2016/03/26/guake-terminal-improvement-for-multi-monitor-setups/</link>
      <pubDate>Sat, 26 Mar 2016 19:03:59 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/03/26/guake-terminal-improvement-for-multi-monitor-setups/</guid>
      
      <image>https://schiessle.eu/img/articles/guake.png</image>
      
      
      
      <category>gtk</category>
      
      <category>guake</category>
      
      <category>hacking</category>
      
      <category>python</category>
      
      
      
      <description>&lt;p&gt;&lt;a href=&#34;http://guake.org/&#34;&gt;Guake&lt;/a&gt; is a top-down “Quake-style” terminal. I use it on a daily basis on the Xfce desktop. The only drawback, Guake doesn’t work the way I want it on a multi-monitor setup. On such a setup the terminal always starts on the main (left) monitor. But for many people, including myself, the left monitor is the small Laptop monitor. Therefor many people prefer to open the terminal on the secondary (right) monitor. If you search for “Guake multi-monitor” you can find many patches to achieve this behavior.&lt;/p&gt;
&lt;p&gt;For me it is not enough that the terminal always starts on the right monitor. I want the terminal to always start at the currently active monitor, the monitor which contain the mouse pointer. Luckily Guake is written in Python, this makes it quite easy to patch it without the need to re-compile and re-package it. Together with the patches already available on the Internet and a short look at the Gtk documentation I found a solution. To always show the terminal on the currently active monitor you have to edit &lt;code&gt;/usr/bin/guake&lt;/code&gt; and replace the method &lt;code&gt;get_final_window_rect(self)&lt;/code&gt; with following code:&lt;/p&gt;
&lt;pre lang=&#34;python&#34;&gt;def get_final_window_rect(self):
        &#34;&#34;&#34;Gets the final size of the main window of guake. The height
        is the window_height property, width is window_width and the
        horizontal alignment is given by window_alignment.
        &#34;&#34;&#34;
        screen = self.window.get_screen()
        height = self.client.get_int(KEY(&#39;/general/window_height&#39;))
        width = 100
        halignment = self.client.get_int(KEY(&#39;/general/window_halignment&#39;))

        # get the rectangle from the currently active monitor
        x, y, mods = screen.get_root_window().get_pointer()
        monitor = screen.get_monitor_at_point(x, y)
        window_rect = screen.get_monitor_geometry(monitor)
        total_width = window_rect.width
        window_rect.height = window_rect.height * height / 100
        window_rect.width = window_rect.width * width / 100

        if width &amp;lt; total_width:
            if halignment == ALIGN_CENTER:
                window_rect.x = (total_width - window_rect.width) / 2
                if monitor == 1:
                    right_window_rect = screen.get_monitor_geometry(0)
                    window_rect.x += right_window_rect.width
            elif halignment == ALIGN_LEFT:
                window_rect.x = 0
            elif halignment == ALIGN_RIGHT:
                window_rect.x = total_width - window_rect.width
        window_rect.y = 0
        return window_rect
&lt;/pre&gt;
&lt;p&gt;This patch is based on Guake 0.4.4. The current stable version is already at 0.8.4 and no longer contain the method shown above. Still version 0.4.4 is in use on the current Debian stable version (Jessie), therefore I thought that it might be useful for more people than just for me.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Federated Sharing  – What’s new in ownCloud 9.0</title>
      <link>https://schiessle.eu/en/articles/2016/03/14/federated-sharing-whats-new-in-owncloud-9-0/</link>
      <pubDate>Mon, 14 Mar 2016 16:03:24 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/03/14/federated-sharing-whats-new-in-owncloud-9-0/</guid>
      
      
      
      <category>federation</category>
      
      <category>owncloud</category>
      
      
      
      <description>&lt;p&gt;Privacy, control and freedom was always one of the main reasons to run your own cloud instead of storing your data on a proprietary and centralized service. Only if you run your own cloud service you know exactly where your data is stored and who can access it. You are in control of your data. But this also introduces a new challenge. If everyone runs his own cloud service it become inevitable harder to share pictures with your friends or to work together on a document. That’s the reason why we at ownCloud are working at a feature called &lt;a href=&#34;https://owncloud.org/federation/&#34;&gt;Federated Cloud Sharing&lt;/a&gt;. The aim of Federated Cloud Sharing is to close this gap by allowing people to connect their clouds and easily share data across different ownCloud installations. For the user it should make no difference whether the recipient is on the same server or not.&lt;/p&gt;
&lt;h2 id=&#34;what-we-already-had&#34;&gt;What we already had&lt;/h2&gt;
&lt;p&gt;The first implementation of Federated Cloud Sharing was introduced with ownCloud 8.0. Back then it was mainly a extension of the already existing feature to share a file or folder with a public link. People can create a link and share it with their friends or colleagues. Once they open the link in a browser they will see a button called “Add to your ownCloud” which enables them to mount the share as a WebDAV resource to their own cloud.&lt;/p&gt;
&lt;img class=&#34;article-image center&#34; src=&#34;https://schiessle.eu/img/articles/owncloud-mount-public-link-example.png&#34; /&gt;
&lt;p&gt;With ownCloud 8.1 we moved on and added the Federated Cloud ID as a additional way to initiate a remote share. The nice thing is that it basically works like a email address. Every ownCloud user automatically gets a ID which looks similiar to &lt;code&gt;john@myOwnCloud.org&lt;/code&gt;. Since ownCloud 8.2 the users Federated Cloud ID is shown in the personal settings.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-personal-settings-personal-cloud-id.png&#34; alt=&#34;federated-cloud-id&#34; width=&#34;713&#34; /&gt;
&lt;p&gt;To share a file with a user on a different ownCloud you just need to know his Federated Cloud ID and enter it to the ownCloud share dialog. The next time the recipient log-in to his ownCloud he will get a notification that he received a new share. The user can now decide if he wants to accept or decline the remote share. In order to make it easier to remember the users Federated Cloud ID the Contacts App allows you to add the ID to your contacts. The share dialog will automatically search the address books to auto-complete the Federated Cloud IDs.&lt;/p&gt;
&lt;h2 id=&#34;what8217s-new-in-owncloud-90&#34;&gt;What’s new in ownCloud 9.0&lt;/h2&gt;
&lt;p&gt;With ownCloud 9.0 we made it even easier to exchange the Federated Cloud IDs. Below you can see the administrator setting for the new Federation App, which will be enabled by default.&lt;/p&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/nextcloud-trusted-servers.png&#34; class=&#34;article-image center&#34; /&gt;
&lt;p&gt;The option “Add server automatically once a federated share was created successfully” is enabled by default. This means, that as soon as a user creates a federated share with another ownCloud, either as a recipient or as a sender, ownCloud will add the remote server to the list of trusted ownClouds. Additionally you can predefined a list of trusted ownClouds. While technically it is possible to use plain http I want to point out that I really recommend to use https for all federated share operations to secure your users and their data.&lt;/p&gt;
&lt;p&gt;What does it mean that two ownClouds trust each other? ownCloud 9.0 automatically creates a internal address book which contains all users accounts. If two ownClouds trust each other they will start to synchronize their system address books. In order to synchronize the system address books and to keep them up-to-date we use the well known and widespread CardDAV protocol. After the synchronization was successful ownCloud will know all users from the trusted remote servers, including their Federated Cloud ID and their display name. The share dialog will use this information for auto-completion. This allows you to share files across friendly ownClouds without knowing more than the users name. ownCloud will automatically find the corresponding Federated Cloud ID and will suggest the user as a recipient of your share.&lt;/p&gt;
&lt;p&gt;The screen-shot of the new Federation App shows a status indicator for each server with three different states: green, yellow and red. Green means that both servers are connected and the address book was synced at least once. In this state auto-completion should work. Yellow means that the initial synchronization is still in progress. Creating a secure connection between two ownCloud servers and syncing the users happens in the background. This can take same time, depending on the background job settings of your ownCloud and the settings of the remote server. If the indicator turns red something went wrong in a way that it can’t be fixed automatically. ownCloud will not try to reestablish a connection to the given server. To reconnect to the remote server you have to remove the server and add it again.&lt;/p&gt;
&lt;p&gt;If the auto-add option is enabled, the network of known and trusted ownClouds will expand every time a user on your server establish a new federated share. The boundaries between local users and remote users will blur. Each user will stay in control of his data, stored on his personal cloud but from a collaborative point of view everything will work as smooth as if all users would be on the same server.&lt;/p&gt;
&lt;p&gt;What will come next? Of course we don’t want to stop here. We will continue to make it as easy as possible to stay in control of your data and at the same time share your files with all the other users and clouds out there. Therefor we work hard to &lt;a href=&#34;http://karlitschek.de/2015/08/announcing-the-draft-federated-cloud-sharing-api/&#34;&gt;document and standardize our protocols&lt;/a&gt; and invite other cloud initiatives to join us to create a Federation of Clouds, not only across different ownCloud servers but also across otherwise complete different cloud solutions.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>The next Generation of Code Hosting Platforms</title>
      <link>https://schiessle.eu/en/articles/2016/02/12/the-next-generation-of-code-hosting-platforms/</link>
      <pubDate>Fri, 12 Feb 2016 19:30:55 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2016/02/12/the-next-generation-of-code-hosting-platforms/</guid>
      
      <image>https://schiessle.eu/img/articles/coding.jpg</image>
      
      
      
      <category>code</category>
      
      <category>federation</category>
      
      <category>git</category>
      
      <category>github</category>
      
      <category>hacking</category>
      
      <category>selfhosting</category>
      
      
      
      <description>&lt;p&gt;The last few weeks there has been a lot of rumors about GitHub. GitHub is a code hosting platform which tries to make it as easy as possible to develop software and collaborate with people. The main achievement from GitHub is probably to moved the social part of software development to a complete new level. As more and more Free Software initiatives started using GitHub it became really easy to contribute a bug fix or a new feature to the 3rd party library or application you use. With a few clicks you can create a fork, add your changes and send them back to the original project as a pull request. You don’t need to create a new account, don’t need to learn the tools used by the project, etc. Everybody is on the same platform and you can contribute immediately. In many cases this improves the collaboration between projects a lot. Also the ability to mention the developer of other projects easily in your pull request or issue improved the social interactions between developers and makes collaboration across different projects the default.&lt;/p&gt;
&lt;p&gt;That’s the good parts of GitHub, but there are also bad parts. GitHub is completely proprietary which makes it impossible to fix or improve stuff by yourself or run it by your own. Benjamin Mako Hill already argued 2010 why this is a problem and why &lt;a href=&#34;https://mako.cc/writing/hill-free_tools.html&#34;&gt;Free Software needs free tools&lt;/a&gt;. More and more people seems to realize that this can create serious problems and a large group of active and influential GitHub users sent a &lt;a href=&#34;https://github.com/dear-github/dear-github&#34;&gt;letter to GitHub&lt;/a&gt; which ends with:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Hopefully none of these are a surprise to you as we’ve told you them before. We’ve waited years now for progress on any of them. If GitHub were open source itself, we would be implementing these things ourselves as a community — we’re very good at that!”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I can’t stress this argument enough. The Free Software community is a community of people who are used to do stuff and don’t just consume it. If we use a third party library and find a bug or need a feature we don’t just complain, instead we look at the code, try to fix it and provide a patch to upstream. We could do the same for the tools we use. But we need to be able to do it. It has to be Free Software.&lt;/p&gt;
&lt;p&gt;Now a lot of rumors and discussion evolved around the news that &lt;a href=&#34;http://www.businessinsider.de/github-the-full-inside-story-2016-2?r=US&amp;amp;IR=T&#34;&gt;GitHub is undergoing a full-blown overhaul as execs and employees depart&lt;/a&gt;. Some people even predict that this will be the end of GitHub.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Wait for it. Three months from now, GitHub introduces &amp;ldquo;features&amp;rdquo; no-one wants or needs. 12 months from now, the exodus.&lt;/p&gt;
&lt;p&gt;— Pieter Hintjens (@hintjens) &lt;a href=&#34;https://twitter.com/hintjens/status/696269446386683904&#34;&gt;February 7, 2016&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It seems that many people underestimated the lock-in effect of the new hosting platforms such as GitHub for a long time. Now they start to realize that it might be easy to export the git repository but what about the issue tracker, the wiki, CI integration, all the social interaction and collaboration between the projects, all the useful scripts written for the GitHub-API? You can’t clone all this stuff easily and move on.&lt;/p&gt;
&lt;p&gt;I don’t want to go deeper into the discussion about what’s going on at GitHub and what will happen next. There are plenty of &lt;a href=&#34;http://hintjens.com/blog:111&#34;&gt;articles&lt;/a&gt; and discussions about it, you can read some of them if you follow the links in this blog. &lt;/p&gt;&lt;/p&gt;
&lt;p&gt;At the moment the ESLint initiative discusses the option to &lt;a href=&#34;https://github.com/eslint/eslint/issues/5205&#34;&gt;move away from GitHub&lt;/a&gt; and by reading the comments you can get a idea about the lock-in effect I’m talking about. With the growing dissatisfaction and with people realizing that they are sitting in a “golden cage” I have the feeling that we might have a opportunity to think about the next generation of code hosting platforms and how they should look like.&lt;/p&gt;
&lt;p&gt;Some of you may remember &lt;a href=&#34;https://en.wikipedia.org/wiki/Git_%28software%29#History&#34;&gt;how Git come into existence&lt;/a&gt;, the tool which is used as the underlying technology of GitHub. Ironically, Git was born because of quite similar reasons for which the next generation source code hosting platforms might arise. Before Git, the Linux-Kernel developer community used BitKeeper. BitKeeper is a proprietary source control management system. The developer decided to use it because from a technical point of view BitKeeper was so much better than what we had until then, mainly SVN and CVS. The developer enjoyed the tool and didn’t thought about the problems such a dependency could create. At some point the copyright holder of BitKeeper had withdrawn gratis use of the product after claiming that Andrew Tridgell had reverse-engineered the BitKeeper protocols. The Linux-Kernel community had to move on and Linus Torvalds wrote Git.&lt;/p&gt;
&lt;p&gt;Back to the next generation of source code hosting and collaboration platforms. It is easy to find Free Software to run your own git repository, a issue tracker and a wiki. But in 2016 I think that this is no longer enough. As described before, the crucial part is to connect software initiatives and developer to make the interaction between them as easy as possible. That’s why traditional code hosting platforms like for example &lt;a href=&#34;https://savannah.gnu.org/&#34;&gt;Savannah&lt;/a&gt; are no longer a real option for many projects. I think the next generation code hosting platform needs to work in a decentralized way. Every project should be able to either host its own platform or chose a provider freely without loosing the connection to other software initiatives and developers. This development, from proprietary and centralized solutions to centralized Free Software solutions to federated Free Software solutions is something we already saw in the area of &lt;a href=&#34;https://www.w3.org/Social/&#34;&gt;social networks&lt;/a&gt; and &lt;a href=&#34;http://karlitschek.de/2015/08/announcing-the-draft-federated-cloud-sharing-api/&#34;&gt;cloud services&lt;/a&gt;. Maybe it is worth looking at what they already achieved and how they did it.&lt;/p&gt;
&lt;p&gt;To make the same transition happen for code hosting platforms we need implementations based on Free Software, Open Standards and protocols which enabled this kind of federation. The good news is that we already have most of them. Git by itself is already a distributed revision control system and doesn’t need a central server for collaboration. What’s missing is a nice web interfaces to glue all this parts together: a issue tracker, a wiki, good integration in Free Software CI tools, good APIs and of course Git. This will enable us to fork projects across servers, send pull requests, interact with the other developers and comment on issues no matter if they are on the same server or not. Chances are high that we will already find a suitable protocol by looking at the large amount of &lt;a href=&#34;https://en.wikipedia.org/wiki/Comparison_of_software_and_protocols_for_distributed_social_networking&#34;&gt;federated social networks&lt;/a&gt;. By choosing a exiting protocol of a established federated social network we could even provide a tight integration in traditional social networks which could provide additional benefits beyond what we already have. The hard part will be to pull all this together. Will it happen? I don’t know. But I hope that after we have seen the raise and fall of SourceForge, Google Code and maybe at some point GitHub we will move on to create something more sustainable instead of building the next data silo and wait until it fails again.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Integrate ToDo.txt into Claws Mail</title>
      <link>https://schiessle.eu/en/articles/2014/06/10/combine-claws-mail-with-todo-txt/</link>
      <pubDate>Tue, 10 Jun 2014 19:22:56 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2014/06/10/combine-claws-mail-with-todo-txt/</guid>
      
      
      
      <category>claws</category>
      
      <category>hacking</category>
      
      <category>todo.txt</category>
      
      
      
      <description>&lt;p&gt;I use &lt;a href=&#34;http://claws-mail.org/&#34;&gt;Claws Mail&lt;/a&gt; for many years now. I like to call it “the mutt mail client for people who prefer a graphical user interface”. Like Mutt, Claws is really powerful and allows you to adjust it exactly to your needs. During the last year I began to enjoy managing my open tasks with &lt;a href=&#34;http://todotxt.com/&#34;&gt;ToDo.txt&lt;/a&gt;. A powerful but still simple way to manage your tasks based on text files. This allows me not only to manage my tasks on my computer but also to keep it in sync with my mobile devices. But there is one thing I always missed. Often a task starts with an email conversation and I always wanted to be able to transfer a mail easily to as task in a way, that the task links back to the original mail conversation. Finally I found some time to make it happen and this is the result:&lt;/p&gt;
&lt;p&gt;To integrate ToDo.txt into Claws-Mail I wrote the Python program &lt;a href=&#34;https://github.com/schiesbn/mail2todotxt&#34;&gt;mail2todotxt.py&lt;/a&gt;. You need to pass the path to the mail you want to add as parameter. By default the program will create a ToDo.txt task which looks like this:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&amp;lt;task_creation_date&amp;gt; &amp;lt;subject_of_the_mail&amp;gt; &amp;lt;link_to_the_mail&amp;gt;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Additionally you can call the program with the parameter &lt;em&gt;“-i”&lt;/em&gt; to switch to the interactive mode. Now the program will ask you for a task description and will use the provided description instead of the mail subject. If you don’t enter a subscription the program will fall back to the mail subject as task description. To use the interactive mode you need to install the Gtk3 Python bindings.&lt;/p&gt;
&lt;p&gt;To call this program directly from Claws Mail you need to go to Configuration-&amp;gt;Actions and create a action to execute following command:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;/path_to_mail2todotxt/mail2todotxt.py -i %f &amp;amp;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Just skip the &lt;em&gt;-i&lt;/em&gt; parameter if you always want to use the subject as task description. Now you can execute the program for the selected mail by calling Tools-&amp;gt;Actions-&amp;gt;&amp;ldquo;The-name-you-choose-for-the-action&amp;rdquo;. Additional you can add a short-cut if you wish, e.g. I use “Ctrl-t” to create a new task.&lt;/p&gt;
&lt;p&gt;Now that I’m able to transfer a mail to a ToDo.txt item I also want to go back to the mail while looking at my open tasks. Therefore I use the “open” action from Sebastian Heinlein which I extended with an handler to open claws mail links. After you added this action to your &lt;em&gt;~/.todo.action.d&lt;/em&gt; you can start Claws-Mail and jump directly to the referred mail by typing:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;t open &amp;lt;task_number_which_referes_to_a_mail&amp;gt;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;The original version of the “open” action can be found at &lt;a href=&#34;https://gitorious.org/todo-txt-glatzor&#34;&gt;Gitorious&lt;/a&gt;. The modified version you need to open the Claws-Mail links can be found &lt;a href=&#34;https://github.com/schiesbn/todotxt&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>The ownCloud Public Link Creator</title>
      <link>https://schiessle.eu/en/articles/2013/12/30/the-owncloud-public-link-creator/</link>
      <pubDate>Mon, 30 Dec 2013 09:28:03 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2013/12/30/the-owncloud-public-link-creator/</guid>
      
      
      
      <category>bash</category>
      
      <category>hacking</category>
      
      <category>owncloud</category>
      
      <category>thunar</category>
      
      
      
      <description>&lt;div class=&#34;article-image&#34; style=&#34;float: right; width: 300px&#34;&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/owncloud-public-link-creator-context-menu.png&#34; width=300px/&gt;
&lt;p class=&#34;image-description&#34;&gt;
    ownCloud Share Link Creator &amp;#8211; Context Menu
  &lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Holiday season is the perfect time to work on some stuff on your personal ToDo list. ownCloud 6 introduced a public REST-style &lt;a href=&#34;http://doc.owncloud.org/server/5.0/developer_manual/core/ocs-share-api.html&#34;&gt;Share-API&lt;/a&gt; which allows you to call various share operations from external applications. Since I started working on the Share-API I thought about having a simple shell script on my file manager to automatically upload a file and generate a public link for it… &lt;a href=&#34;https://github.com/schiesbn/shareLinkCreator&#34;&gt;Here it is!&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I wrote a script which can be integrated in the Thunar file manager as a “custom action”. It is possible that the program also works with other file managers which provide similar possibilities, e.g Nautilus. But until now I tested and used it with Thunar only. If you try the script with a different file manager I would be happy to hear about your experience.&lt;/p&gt;
&lt;div class=&#34;article-image&#34; style=&#34;float: left; width: 300px&#34;&gt;
&lt;img src=&#34;https://schiessle.eu/img/articles/owncloud-public-link-creator-upload.png&#34; width=300px/&gt;
&lt;p class=&#34;image-description&#34;&gt;
    ownCloud Share Link Creator &amp;#8211; File Upload
  &lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;If you configure the “custom action” in Thunar, make sure to pass the paths of all selected files to the program using the “%F” parameter. The program expects the absolute path to the files. In the “Appearance and Conditions” tab you can activate all file types and directories. Once the custom action is configured you can execute the program from the right-click context menu. The program works for all file types and also for directories. Once the script gets executed it will first upload the files/directories to your ownCloud and afterwards it will generate a public link to access them. The link will be copied directly to your clipboard, additionally a dialog will inform you about the URL. If you uploaded a single file or directory than the file/directory will be created directly below your default target folder as defined in the shell script. If you selected multiple files, than the program will group them together in a directory named with the current timestamp.&lt;/p&gt;
&lt;p&gt;This program does already almost everything I want. As already said, it can upload multiple files and even directories. One think I want to add in the future is the possibility to detect a ownCloud sync folder on the desktop. If the user selects a file in the sync folder than the script should skip the upload and create the share link directly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Edit:&lt;/strong&gt; In the meantime I got feedback that the script also works nicely with Dolphin, Nautilus and Nemo&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Introduction to the new ownCloud Encryption App</title>
      <link>https://schiessle.eu/en/articles/2013/05/28/introduction-to-the-new-owncloud-encryption-app/</link>
      <pubDate>Tue, 28 May 2013 15:08:13 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2013/05/28/introduction-to-the-new-owncloud-encryption-app/</guid>
      
      
      
      <category>owncloud</category>
      
      <category>encryption</category>
      
      
      
      <description>&lt;p&gt;Last weekend we &lt;a href=&#34;https://mail.kde.org/pipermail/owncloud/2013-May/009270.html&#34;&gt;released&lt;/a&gt; a first preview version of the new encryption app. This wouldn’t be possible without the work done by Sam Tuke and Florin Peter. Thanks a lot for all your work! Let me take the opportunity to tell you some details about the app, what it does and how it works.&lt;/p&gt;
&lt;p&gt;The encryption app for ownCloud 5 was a complete re-write. We moved from the relatively weak blowfish algorithm to the more secure AES algorithm. The complete encryption is built on top of OpenSSL a well-known and tested encryption library. Further, the encryption app is integrated into ownCloud seamlessly. This means that the encrypt and decrypt happens transparently so that you can still use all the other features from ownCloud like sharing, different viewer apps, WebDAV access etc.&lt;/p&gt;
&lt;p&gt;To make this possible, we decided to perform the encryption server-side. Still the architecture allows us to implement client-side encryption as an additional option later. Server-side encryption is especially interesting for users who also use the external storage app. Combining the external storage app with the encryption app allows you to use external storage without giving any 3rd-party provider access to your data.&lt;/p&gt;
&lt;p&gt;ownCloud uses the users log-in password for encryption. This means that you should choose a strong password in order to protect your data. It is important to know that by default a user will lose access to his data if he loses his log-in password. As an additional feature the administrator can generate a recovery key which allows him to recover user data. Once this feature is activated in the administrator settings every user can enable the recovery key in his personal settings. By default the recovery key is disabled. Every user can decide for himself whether he wants this additional protection against password loss or not. Since we are using server-side encryption this feature does not reduce the security. Keep in mind that your ownCloud administrator will always be able to intercept your data because everything gets encrypted and decrypted at the server. Since ownCloud is Free Software you can choose a trustworthy administrator freely or decide to be your own administrator if you wish.&lt;/p&gt;
&lt;p&gt;Let’s talk about some technical details and how the encryption works. The encryption is based on three different keys: every user has a private/public &lt;em&gt;key-pair&lt;/em&gt;, every file has a &lt;em&gt;file-key&lt;/em&gt; and to give multiple users access to a file we have &lt;em&gt;share-keys&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Every user has an asymmetric 4096-bit strong &lt;em&gt;key-pair&lt;/em&gt; which consists of a private and a public key. The private key is encrypted with the users log-in password, for the encryption AES-128 is used. Additionally there are up to two system-wide key-pairs: One for public link shares which allows ownCloud to decrypt files which are shared as public link and if enabled the recovery-key-pair.&lt;/p&gt;
&lt;p&gt;In order to not always have to encrypt and decrypt large files we have introduced the &lt;em&gt;file-keys&lt;/em&gt; which are 183 byte strong ASCII keys. The file-key is used to encrypt the users file symmetrically with AES-128. Than the file-key gets encrypted with the public keys from all users with access to the file. This means that if a user gets added or removed from a file we only have to re-encrypt the small file-key instead of the whole file.&lt;/p&gt;
&lt;p&gt;Every time a file-key gets encrypted to multiple users OpenSSL generates for each user an additional &lt;em&gt;share-key&lt;/em&gt;. Only the combination of the users private key with the corresponding share-key enables the user to decrypt the given file again.&lt;/p&gt;
&lt;p&gt;Everybody is welcome to test the new encryption app and report issues on our &lt;a href=&#34;https://mail.kde.org/mailman/listinfo/owncloud&#34;&gt;mailing list&lt;/a&gt; or preferable directly on &lt;a href=&#34;https://github.com/owncloud/core/&#34;&gt;GitHub&lt;/a&gt;. But keep in mind that this is a preview version, you should always have a backup of your unencrypted data!&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Free Software, Open Source, FOSS, FLOSS – Same same but different</title>
      <link>https://schiessle.eu/en/articles/2012/05/11/free-software-open-source-foss-floss-same-same-but-different/</link>
      <pubDate>Fri, 11 May 2012 21:24:50 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2012/05/11/free-software-open-source-foss-floss-same-same-but-different/</guid>
      
      
      
      <category>community</category>
      
      <category>floss</category>
      
      <category>foss</category>
      
      <category>FreeSoftware</category>
      
      <category>OpenSource</category>
      
      <category>terminology</category>
      
      <category>fsfe</category>
      
      
      
      <description>&lt;p&gt;There are two major terms connected to software you can freely use, study, share and improve: Free Software and Open Source. Based on them you can also find different combinations and translations like FOSS, Libre Software, FLOSS and so on. Reading articles about Free Software or listening to people involved in Free Software often raises the question: Why do they use one term or another and how they differ from each other?&lt;/p&gt;
&lt;h2 id=&#34;historical-background&#34;&gt;Historical background&lt;/h2&gt;
&lt;p&gt;Historically, Free Software was the first term, created somewhere around 1984 together with the &lt;a href=&#34;https://fsfe.org/about/basics/freesoftware&#34;&gt;Free Software definition&lt;/a&gt;. In 1997 Debian, a project aiming to create a completely free and community based GNU/Linux distribution, defined the &lt;a href=&#34;http://www.debian.org/social_contract#guidelines&#34;&gt;Debian Free Software Guidelines (DFSG)&lt;/a&gt; as a check-list to decide whether a program can be included in the distribution or not. In 1998 the Open Source Initiative was set up as a &lt;a href=&#34;http://web.archive.org/web/20021217003716/http://www.opensource.org/advocacy/faq.html&#34;&gt;marketing campaign&lt;/a&gt; for Free Software and introduced the &lt;a href=&#34;http://opensource.org/docs/osd&#34;&gt;Open Source definition&lt;/a&gt; by copying the DFSG and replacing “Free Software” with “Open Source”. According to a &lt;a href=&#34;http://lists.debian.org/debian-devel/1999/02/msg01641.html&#34;&gt;public statement&lt;/a&gt; by Bruce Perens, one of the founders of the OSI and author of the DFSG and Open Source Definition, the Open Source term was introduced as a synonym for Free Software. Perens eventually decided to return to the roots of the movement and to speak about Free Software again. This historical development shows that both Open Source and Free Software describe the complete set of software licenses granting the right to use, study, share and improve the software.&lt;/p&gt;
&lt;p&gt;In the course of time people came up with even more terms. Today, terms such as Libre Software, FOSS (Free and Open Source Software) or FLOSS (Free, Libre and Open Source Software) are often used to describe Free Software. In some cases people also use terms like “organic software” or “ethical software”. Often the motivation for these terms is to stay out of the terminology debate and to avoid confusion generated by words like “open” or “free”. At the end those terms create more confusion than they help because they virtually invite people to search for differences between the terms where actually no differences exist, regarding the software they describe.&lt;/p&gt;
&lt;p&gt;In short, these different terms share the same historical root and describe the same set of software, although the choice of one term over the others highlight different aspects of Free Software.&lt;/p&gt;
&lt;h2 id=&#34;usage-of-the-terms-by-different-people-and-organisations-within-the-movement&#34;&gt;Usage of the terms by different people and organisations within the movement&lt;/h2&gt;
&lt;p&gt;Today the Free Software movement is a large and diverse community. People have different interests in Free Software and different motivations to take part in this movement. But these differences are not necessarily related to the language they use. There are many people using the term Open Source and highlight the social and political dimensions of Free Software while on the other hand there are a people in our community who prefer the term Free Software but concentrate more on the practical benefits. This means that the terms Open Source and Free Software are not a good criterion to identify these different motivations.&lt;/p&gt;
&lt;p&gt;Beside individuals there are also many well known organisations in the Free Software ecosystem. Many of them play an important role and emphasize different aspects of Free Software. For example, some organisations focus on the technical direction of Free Software projects, some on legal aspects, some on political, social and ethical aspects and some focus on license evaluation. These organisations typically have decided to use one or another term and sticked to it. But this should not lead to the conclusion that the term they use is the critical factor regarding their motivations. The critical factor are the people driving the organisation and the goals of the organisation as such. The practical experience with different organisations and people in the community shows that the line can’t be drawn along the language they use.&lt;/p&gt;
&lt;p&gt;This diversity is good, as it reflects that Free Software provides many advantages in many different areas of our life. But we should not divide our community just by the term someone prefers. No matter what term someone uses and what his initial motivation is, at the end most of us work on the same set of software and on the enhancement of software freedom and any other aspect of Free Software.&lt;/p&gt;
&lt;h2 id=&#34;license-evaluation&#34;&gt;License evaluation&lt;/h2&gt;
&lt;p&gt;There are three entities in the Free Software movement which people look to for evaluations of Free Software licenses: The &lt;a href=&#34;http://www.debian.org&#34;&gt;Debian project&lt;/a&gt;, the &lt;a href=&#34;http://www.fsf.org&#34;&gt;Free Software Foundation (FSF)&lt;/a&gt; and the &lt;a href=&#34;http://www.opensource.org&#34;&gt;Open Source Initiative (OSI)&lt;/a&gt;. Most of the time they come to the same conclusion. In some corner cases they may disagree. In such cases the differences do not lie in different terms or different definitions, which as already shown have the same origin, but in the fact that it happens quite often that different people come to different conclusions for challenging legal questions. It would be a big mistake to use these cases to divide our community.&lt;/p&gt;
&lt;h2 id=&#34;protective-and-non-protective-licenses&#34;&gt;Protective and non-protective licenses&lt;/h2&gt;
&lt;p&gt;Looking at Free Software licenses there are two main categories, protective or &lt;a href=&#34;https://www.gnu.org/copyleft/&#34;&gt;Copyleft&lt;/a&gt; licenses and non-protective licenses. While Copyleft licenses are designed to protect the rights to use, study, share and improve the software non-protective licenses allow to distribute the software without those rights. Sometimes people think that the terms Free Software and Open Source are used to distinguish between protective and non-protective licenses. The lists of Free Software licenses by &lt;a href=&#34;http://www.debian.org/legal/licenses/&#34;&gt;Debian&lt;/a&gt;, the &lt;a href=&#34;https://www.gnu.org/licenses/license-list.html&#34;&gt;FSF&lt;/a&gt; and the &lt;a href=&#34;http://opensource.org/licenses/category&#34;&gt;OSI&lt;/a&gt; show that both protective and non-protective licenses comply with the Free Software definition and the Open Source definition. This means that neither the terms Open Source and Free Software nor the different definitions are suitable to distinguish between protective and non-protective licenses.&lt;/p&gt;
&lt;img class=&#34;article-image center&#34; src=&#34;https://schiessle.eu/img/articles/softwaremodels.png&#34; alt=&#34;This graphic should visualise the different software categories and their connection&#34; title=&#34;This graphic visualises the different software categories and their connection&#34; /&gt;
&lt;p&gt;Protective licenses and non-protective licenses are sub-classes of Free Software licenses recognized by the Open Source Initiative and the FSF. Copyleft or non-Copyleft is not a criteria suitable to distinguish between Open Source and Free Software, both terms describe the same set of software.&lt;/p&gt;
&lt;h2 id=&#34;development-model&#34;&gt;Development model&lt;/h2&gt;
&lt;p&gt;When looking at software we have to distinguish between the software model and the development model. While the software model describes the attributes of the software (e.g. free or proprietary) the development model describes different ways to develop software. As described at full length in &lt;a href=&#34;https://fsfe.org/freesoftware/enterprise/freesoftwarecompany&#34;&gt;“What makes a Free Software company?”&lt;/a&gt; the different development models are defined independently of the software models and work for both Free Software and proprietary software. Development models that leverage the advantage of an open and collaborative community can show their full strength in combination with the Free Software model. However this does not mean that an open, collaborative development process is a criterion for Free Software. There are Free Software projects developed by a single person or a company with little or no outside input. On the other hand developers of proprietary software have adapted collaborative development models to fit into their software model, e.g. SAP with its partnership program.&lt;/p&gt;
&lt;p&gt;While the development model can be a crucial factor for the success of a software project it is not suitable to distinguish between proprietary software and Free Software or one of its synonyms.&lt;/p&gt;
&lt;h2 id=&#34;why-do-i-still-insist-on-calling-it-free-software-if-it-is-all-the-same&#34;&gt;Why do I still insist on calling it Free Software if it is all the same?&lt;/h2&gt;
&lt;p&gt;If all these terms describe the same software people may wonder why I insist on using the term Free Software. The easiest answer is that I simply have to choose a term if I want to talk about Free Software. As explained in the article all the terms describe the same set of software, therefore I don’t see any value in combining them (e.g. FOSS or FLOSS). Quite the contrary, this combinations often create more confusion than clarity. So the remaining terms are Free Software and Open Source and I decided to stick with Free Software.&lt;/p&gt;
&lt;p&gt;Free Software is the oldest term. All other terms have their roots in the Free Software definition. It is a good tradition in science to use the first term and definition given by its author. Furthermore it is also advantageous if a term can be easily translated into different languages​​. This enables people to talk about Free Software in the most natural way, in their first language. In many cases Free Software even translates unambiguously into other languages, e.g. “logiciel libre” in French, “software libre” in Spanish, “software libero” in Italian or “Fri Software” in Danish which avoids the ambiguity between freedom and price of the English word “free”. I believe that it is important to use a clear terminology. I want to convey a strong message about freedom. Language is important because it frames how people think about a subject. Different terms focus on different aspects, even if they describe the same software and the language we use influences our thoughts about a subject. For me freedom is a core value of Free Software and I want that my language reflects this.&lt;/p&gt;
&lt;p&gt;Free Software, which is easy to translate in different languages and emphasises the aspect of freedom for individuals, business and public institutions, together with the clear &lt;a href=&#34;https://fsfe.org/about/basics/freesoftware&#34;&gt;definition&lt;/a&gt; provides these values. All this makes Free Software the right choice for me and I invite you to &lt;a href=&#34;https://fsfe.org/documents/whyfs&#34;&gt;follow me&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;For historical reasons there are different terms to describe software that is free to use, study, share and improve. All terms, Open Source, Free Software or one of the combinations have the same roots and describe the same set of software. When it comes to people and groups within the Free Software movement we see a large diversity of motivations, different people or groups focus on different aspects of Free Software. But whatever the motivation may be it is not the doing of the software, it is the people. Neither is it possible to distinguish the people according to the term they use nor is it the business of the Free Software movement or part of the Free Software definition to find and define groups within our community. The Free Software movement identifies Free Software and works on the enhancement and adoption of it with all its positive aspects. Regarding licenses, different groups agree in their evaluation of Free Software licenses except for some corner cases which shows the complexity of legal documents but not a division between people, movements or software along the terms they use. Protective (Copyleft) and non-protective licenses are sub-classes of Free Software licenses and are recognised as such by all groups in the Free Software movement. These two categories are not suitable to separate Open Source and Free Software.&lt;/p&gt;
&lt;p&gt;Even if all these terms describe the same set of software the terminology we use is still important because it frames how people think about a subject. Different terms focus on different aspects, even if they describe the same software. I want to put freedom first, for me freedom is a core value of Free Software and I want to respect the naming by the founder of the Free Software movement. These are the main reasons why I invite you to join me and &lt;a href=&#34;https://fsfe.org/documents/whyfs&#34;&gt;speak about Free Software&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;But no matter which term we use, we should not allow people to split our community just because of different terminology. At the end most of us work on the same set of software, improve it and foster software freedom no matter what our motivation or preferred term is. The community needs to stay together to have an impact on all levels of involvement and to improve Free Software in all aspects. Don’t let others use the strategy of “divide and conqueror” to harm our movement.&lt;/p&gt;
&lt;p&gt;In this context you should also read &lt;a href=&#34;https://fsfe.org/freesoftware/enterprise/chargeofitsbrand&#34;&gt;“It’s time for the community to take charge of its brand”&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>A successful year for the 1. RFC Stuttgart</title>
      <link>https://schiessle.eu/en/articles/2009/07/08/a-successful-year-for-the-1-rfc-stuttgart/</link>
      <pubDate>Wed, 08 Jul 2009 16:29:19 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/07/08/a-successful-year-for-the-1-rfc-stuttgart/</guid>
      
      
      
      <category>robocup</category>
      
      <category>stuttgart</category>
      
      <category>uni</category>
      
      
      
      <description>&lt;p&gt;This year it was the first time I participated at RoboCup tournaments. It was quite stressful but also really exiting and most important: successful!&lt;/p&gt;
&lt;p&gt;In April the year started with the German Open in Hanover. It was a hard week, we lived in a bus and worked every day far into the night. But it was worthwhile. After many years of struggle the &lt;a href=&#34;http://robocup.informatik.uni-stuttgart.de&#34;&gt;1. RFC Stuttgart&lt;/a&gt; finale made it and win the German Open!&lt;/p&gt;
&lt;p&gt;Here you can see a summary of the final game in Hanover against Osnabrück (Stuttgart = cyan; Osnabrück = magenta):&lt;/p&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/Su1ArYhltfc&#34; frameborder=&#34;0&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;p&gt;But this was not the end of our success in 2009. Last week we went to Graz, Austria for the RoboCup world championship. Like a few weeks ago in Hanover it was again a hard week. At the end we went home with two cups! First we won the free challenge with the presentation of our “Automatic Camera Man” and at Sunday we finally won the final and became world champion for the first time!&lt;/p&gt;
&lt;img class=&#34;article-image&#34; style=&#34;float: right; width: 220px; padding: 20px;&#34; src=&#34;https://schiessle.eu/img/articles/robocup09_result.png&#34; /&gt;
&lt;p&gt;The tournament started quite well with 6:0 wins in the first round robin. In the second round robin we had our only defeat and finished the round with 3:1 wins. The third round robin ended with 2:0 wins. In the semifinal we won against MRL (Iran) 4:1. Than in the final we met Tech United (Eindhoven, Netherlands) and beat them 4:1 for the world championship.&lt;/p&gt;
&lt;p&gt;This is the team which made all this happen:&lt;/p&gt;
&lt;img class=&#34;article-image center&#34; style=&#34;width: 420px; padding: 20px;&#34; src=&#34;https://schiessle.eu/img/articles/robocup09_team.png&#34; /&gt;
&lt;p&gt;Below you can see a video, recorded by Tech United, from the final (Stuttgart = magenta; Tech United = cyan).&lt;/p&gt;
&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/Pb6OB3OJbmI&#34; frameborder=&#34;0&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;p&gt;By the way, all robots are powered by Debian GNU/Linux and the software is developed with C++ and Qt (for graphical tools)…&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Free Software in Schools</title>
      <link>https://schiessle.eu/en/articles/2009/05/20/free-software-in-schools/</link>
      <pubDate>Wed, 20 May 2009 22:43:32 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/05/20/free-software-in-schools/</guid>
      
      
      
      <category>education</category>
      
      <category>FreeSoftware</category>
      
      
      
      <description>&lt;p&gt;At the moment Free Software in education is one of my main interests in the Free Software ecosystem. &lt;a href=&#34;http://wiki.fsfe.org/Education&#34;&gt;FSFE’s Fellowship wiki&lt;/a&gt; already provides some useful information on this topic. It’s quite interesting to see the development in this area. Further I think schools play an important role for the adoption of Free Software in many areas. What pupils learn and get used to during school is what they want to use and what they demand if they enter the business world. I also think that it is important to get as early as possible at least a basic idea about the role of software in the information society.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.linuxadvanced.at/grafiken/albumshaper/LinuxAdvanced/subalbum_1.html&#34;&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/linux-advances-distribution-for-education.jpg&#34; class=&#34;article-image center&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Today I read an interesting article about a school in Austria which uses &lt;a href=&#34;http://futurezone.orf.at/stories/1603209/&#34;&gt;GNU/Linux systems on USB sticks (German only)&lt;/a&gt;. With &lt;a href=&#34;http://www.linuxadvanced.at&#34;&gt;LinuxAdvanced&lt;/a&gt; the school created their own distribution based on Debian GNU/Linux 5.0 (aka Lenny) and the lightweight desktop environment Xfce.&lt;/p&gt;
&lt;p&gt;The Kremser Bundesgymnasium uses this system since two years on all computers in the computer science classrooms. Now they decided to switch from local installations to live systems on USB sticks. The advantage: The pupils can carry their system around with themselves. They can use it at school, at home or at any computer they want. About 50% of all pupils uses the system regularly at home. It seems like especially the young pupils using the system quite naturally and have no reservations. Further Rene Schwarzinger explains: “We don’t want to encourage our pupils to create illegal copies just to be able to work at home with the same programs as at school”. The obvious solution to avoid this is to use only &lt;a href=&#34;http://www.fsfe.org/documents/freesoftware&#34;&gt;Free Software&lt;/a&gt; at school and pass it down to the pupils.&lt;/p&gt;
&lt;p&gt;In autumn they want to introduce netbooks together with the GNU/Linux USB stick to the pupils.&lt;/p&gt;
&lt;p&gt;I really like the idea using USB sticks instead of normal installations on hard disks. Live systems are nothing new but I think it makes much sense in this scenario. With the USB sticks the pupils can work with their systems and their data wherever they want without having to convince their parents to install a new operating system at home which could be quite challenging, both technically and philosophically.&lt;/p&gt;
&lt;p&gt;I’m interested in more success stories about Free Software and GNU/Linux in schools. Please let me know if you know schools (especially in Germany or Europe) which already uses GNU/Linux or prepare the switch to Free Software.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Fedora and gpg-agent</title>
      <link>https://schiessle.eu/en/articles/2009/05/12/fedora-and-gpg-agent/</link>
      <pubDate>Tue, 12 May 2009 16:28:37 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/05/12/fedora-and-gpg-agent/</guid>
      
      
      
      <category>bash</category>
      
      <category>fedora</category>
      
      <category>gnupg</category>
      
      <category>smartcard</category>
      
      <category>ssh</category>
      
      
      
      <description>&lt;p&gt;While it was quite easy to set up my &lt;a href=&#34;http://fellowship.fsfe.org&#34;&gt;Fellowship&lt;/a&gt; smartcard for SSH logins on Debian GNU/Linux following this &lt;a href=&#34;http://blogs.fsfe.org/greve/?p=64&#34;&gt;instructions&lt;/a&gt; I never managed to get it working on Fedora GNU/Linux. At some point of time I just gave up. Today finally I found a solution in an on-line forum.&lt;/p&gt;
&lt;p&gt;The problem was that gpg-agent always stopped with the error message:&lt;/p&gt;
&lt;pre&gt;$ gpg-agent 
gpg-agent[2857]: can&#39;t connect to `/home/schiesbn/.gnupg/S.gpg-agent&#39;: No such file or directory
gpg-agent: no gpg-agent running in this session
&lt;/pre&gt;
&lt;p&gt;By default the gpg-agent on Fedora creates the socket in /tmp instead of in /home/schiesbn/.gnupg. So you have to move it manually over to your home directory once gpg-agent has started.&lt;/p&gt;
&lt;p&gt;To do this I use this script:&lt;/p&gt;
&lt;pre lang=&#34;bash&#34; line=&#34;0&#34;&gt;#!/bin/bash

# Decide whether to start gpg-agent daemon.
# Create necessary symbolic link in $HOME/.gnupg/S.gpg-agent

SOCKET=S.gpg-agent
PIDOF=`pidof gpg-agent`
RETVAL=$?

if [ &#34;$RETVAL&#34; -eq 1 ]; then
	echo &#34;Starting gpg-agent daemon.&#34;
	eval `gpg-agent --daemon `
else
	echo &#34;Daemon gpg-agent already running.&#34;
fi

# Nasty way to find gpg-agent&#39;s socket file...
GPG_SOCKET_FILE=`find /tmp/gpg-* -name $SOCKET`
echo &#34;Updating socket file link.&#34;
cp -fs $GPG_SOCKET_FILE $HOME/.gnupg/S.gpg-agent
&lt;/pre&gt;
&lt;p&gt;To execute this script during log-in I have added this to my ~/.bashrc:&lt;/p&gt;
&lt;pre lang=&#34;bash&#34; line=&#34;0&#34;&gt;# GPG-AGENT stuff
GET_TTY=`tty`
export $GET_TTY
$HOME/bin/gpg-agent-start.sh
&lt;/pre&gt;
&lt;p&gt;I still wonder why it works that easy on Debian and on Fedora i need all this scripting. But for the moment I’m just happy that I have found a solution to use my smartcard for SSH login on my Fedora systems.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Fellowship meeting Stuttgart</title>
      <link>https://schiessle.eu/en/articles/2009/03/29/fellowship-meeting-stuttgart/</link>
      <pubDate>Sun, 29 Mar 2009 20:36:47 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/03/29/fellowship-meeting-stuttgart/</guid>
      
      
      
      <category>education</category>
      
      <category>fsfe</category>
      
      <category>stuttgart</category>
      
      
      
      <description>&lt;p&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/fsfe-plussy.png&#34; class=&#34;article-image&#34; style=&#34;float: left; padding: 20px;&#34; /&gt;It’s time for the next &lt;a href=&#34;http://fellowship.fsfe.org&#34;&gt;Fellowship&lt;/a&gt; meeting in Stuttgart. It will take place at Thursday, 2 April at 19:00! We are going to meet in the “Unithekle”, Allmandring 17 , 70596 Stuttgart. Short term changes are announced in the &lt;a href=&#34;http://wiki.fsfe.org/groups/Stuttgart&#34;&gt;wiki&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This time we want to talk about &lt;a href=&#34;http://wiki.fsfe.org/Reasons_for_schools_to_use_Free_Software&#34;&gt;Free Software in education&lt;/a&gt;. I think this is an interesting and important topic. We live in the digital age. Therefore pupils should learn how to use and develop information technology in an social and sustainable way and all pupils should have equal opportunities. So if you know pupils, teachers or parents which are interested in &lt;a href=&#34;http://www.fsfeurope.org/documents/freesoftware.en.html&#34;&gt;Free Software&lt;/a&gt;, just take them with you to the Fellowship meeting.&lt;/p&gt;
&lt;p&gt;I’m sure we will also have enough time to talk about other interesting Free Software topics. So if you are interested in Free Software, the FSFE and/or Free Software in education come and meet us at Thursday, 2. April.&lt;/p&gt;
&lt;p&gt;For more information, also about previous events, look at our &lt;a href=&#34;http://wiki.fsfe.org/groups/Stuttgart&#34;&gt;wiki page&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>“Frühjahrsfestival zum Datenschutz” at Stuttgart</title>
      <link>https://schiessle.eu/en/articles/2009/03/25/fruhjahrsfestival-zum-datenschutz-at-stuttgart/</link>
      <pubDate>Wed, 25 Mar 2009 10:19:58 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/03/25/fruhjahrsfestival-zum-datenschutz-at-stuttgart/</guid>
      
      <image>https://schiessle.eu/img/fsfs.jpg</image>
      
      
      
      <category>cccs</category>
      
      <category>fsfe</category>
      
      <category>FreeSoftware</category>
      
      <category>privacy</category>
      
      <category>stuttgart</category>
      
      <category>slides</category>
      
      
      
      <description>&lt;p&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/fruehjahrsfestival-datenschutz-stuttgart-2009.jpg&#34; alt=&#34;Frühlingsfestival zum Datenschutz&#34; title=&#34;Frühlingsfestival zum Datenschutz&#34; style=&#34;float: left; width=300px&#34; class=&#34;article-image&#34; /&gt; Today the &lt;a href=&#34;http://www5.stuttgart.de/stadtbuecherei/MeineDaten/&#34;&gt;“Frühjahrsfestival zum Datenschutz”&lt;/a&gt; (engl. “spring festival of privacy”) starts at the public library of Stuttgart. This will be a 4 day event from 25. to 28. March 2009.&lt;/p&gt;
&lt;p&gt;Today the event will start at 19:30 with a speech by Padeluun, he is a member of the &lt;a href=&#34;http://www.bigbrotherawards.org/&#34;&gt;Big Brother Award&lt;/a&gt; panel in Germany and a chairman of the &lt;a href=&#34;http://www.foebud.org/&#34;&gt;FoeBuD e.V.&lt;/a&gt;, an association which works for civil rights and privacy. The title of his talk will be “Datenkraken. Die Kommunikationsgesellschaft und ihre Feinde” (engl: The communication-society and their enemies). Don’t miss it!&lt;/p&gt;
&lt;p&gt;The next days there will be a lot of workshops for pupils, parents and teenagers and other interesting talks.&lt;/p&gt;
&lt;p&gt;The last day (Saturday, 28. March) will be organised by the &lt;a href=&#34;http://www.cccs.de&#34;&gt;Chaos Computer Club Stuttgart (CCCS)&lt;/a&gt; with a lot of interesting &lt;a href=&#34;http://www.cccs.de/wiki/bin/view/Main/StadtBuecherei200903&#34;&gt;speeches&lt;/a&gt; and practical examples how to improve privacy. At 14:00 I will give a speech about “Freie Software und Datenschutz” (engl: Privacy and Free Software). This are the slides to my talk:&lt;/p&gt;
&lt;p&gt;&lt;br&gt;(&lt;i&gt;This blog contain some presentation slides, you can see them &lt;a href=&#34;https://schiessle.eu/en/articles/2009/03/25/fruhjahrsfestival-zum-datenschutz-at-stuttgart/&#34;&gt;here&lt;/a&gt;.&lt;/i&gt;)&lt;br&gt;&lt;/p&gt;
&lt;p&gt;Don’t miss the event! I’m sure it will be great!&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Happy Birthday FSFE!</title>
      <link>https://schiessle.eu/en/articles/2009/03/11/happy-birthday/</link>
      <pubDate>Wed, 11 Mar 2009 21:10:58 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/03/11/happy-birthday/</guid>
      
      
      
      <category>fsfe</category>
      
      
      
      <description>&lt;p&gt;Today the Free Software Foundation Europe (FSFE) &lt;a href=&#34;http://www.fsfeurope.org/news/2009/news-20090311-01.en.html&#34;&gt;celebrates&lt;/a&gt; his 2&lt;SUP&gt;3&lt;/SUP&gt; birthday! For 8 years now, the FSFE works for basic rights and freedom in the digital age, a world in which our life increasingly depends on software.&lt;/p&gt;
&lt;p&gt;In this eight years FSFE achieved a lot, from the local area to Europe and even up to the United Nations. It ranges from highly visible activities like the &lt;a href=&#34;http://www.documentfreedom.org&#34;&gt;Document Freedom Day&lt;/a&gt; and the recently launched &lt;a href=&#34;http://www.pdfreaders.org&#34;&gt;pdfreaders.org&lt;/a&gt; to a lot of behind-the-scenes activities like the work at the United Nations, promoting Free Software interests at the World Summit on the Information Society (WSIS), contributed to the Internet Governance Forum (IGF), taken part in discussions at the World Intellectual Property Organisation (WIPO), taught project managers of the World Bank about Free Software and many more.&lt;/p&gt;
&lt;p&gt;In honor of the day FSFE has released a special edition of the Fellowship Interview series, in which Georg Greve explains the history behind FSFE and how he came to found it. &lt;a href=&#34;http://fellowship.fsfe.org/interviews/greve/&#34;&gt;Here&lt;/a&gt; you can find the Interview.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Jabber Mail Notification</title>
      <link>https://schiessle.eu/en/articles/2009/02/20/jabber-mail-notification/</link>
      <pubDate>Fri, 20 Feb 2009 16:55:29 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/02/20/jabber-mail-notification/</guid>
      
      
      
      <category>hacking</category>
      
      <category>xmpp</category>
      
      
      
      <description>&lt;p&gt;I always struggled to find the right mail notification applet for my desktop. Furthermore I always stumble over the question: Why do I have to ask the mail server in a defined time interval “Do I have a new e-mail?”. Wouldn’t it be better if the mail server notifies me if a new e-mail arrives?&lt;/p&gt;
&lt;p&gt;This is probably somehow a new form of the good old question “mailing list vs bulletin board” or in general: Do i have to fetch the information or does the information come to me? Personally i always preferred to get the information and not to hunt around for them.&lt;/p&gt;
&lt;p&gt;Thinking about this question i realized that notification through &lt;a href=&#34;http://www.jabber.org&#34;&gt;Jabber&lt;/a&gt; would be perfect and the open &lt;a href=&#34;http://xmpp.org&#34;&gt;XMPP&lt;/a&gt; protocol virtually invites one to do such things.&lt;/p&gt;
&lt;p&gt;The idea was born. Now the first step was to find a easy to use XMPP implementation for a scripting language like Python, Ruby or PHP. At the end I found a quite nice and easy to use &lt;a href=&#34;http://code.google.com/p/xmpphp/&#34;&gt;PHP library&lt;/a&gt;. While searching such a library I also found this &lt;a href=&#34;http://garv.in/serendipity/archives/947-Jabber-E-Mail-Notify.html&#34;&gt;guidance (German only)&lt;/a&gt;, borrowed some code from it and my solution was born:&lt;/p&gt;
&lt;pre lang=&#34;PHP&#34; line=&#34;1&#34;&gt;&lt;?php
// The script gets the input either as an argument, from a REQUEST-variable or from stdin
// If you use it within procmail you will get the input through stdin 
if ($argv[1]) {
    $msg = $argv[1];
} elseif ($_REQUEST[&#39;msg&#39;]) {
    $msg = urldecode($_REQUEST[&#39;msg&#39;]);
} else {
    // open stdin. Only read the first 4096 character, this should be enough to match
    // the FROM- and  SUBJECT-header
    $stdin = fopen(&#39;php://stdin&#39;, &#39;r&#39;);
    $msg   = fread($stdin, 4096);

    if (empty($msg)) {
        $msg = &#34;empty&#34;;
    } else {
        // Get FROM und SUBJECT
        preg_match(&#39;@From:(.*)@i&#39;, $msg, $from);
	preg_match(&#39;@Subject:(.*)@i&#39;, $msg, $subject);
        $msg = &#34;\n&#34; . $from[0] . &#34;\n&#34; . $subject[0] . &#34;\n&#34;;
    }
}

// now init xmpp and get the notification out
include &#39;XMPPHP/XMPP.php&#39;;

$conn = new XMPPHP_XMPP(&#39;schiessle.org&#39;, 5222, &#39;user&#39;, &#39;password&#39;, &#39;xmpphp&#39;, &#39;schiessle.org&#39;, $printlog=false, $loglevel=XMPPHP_Log::LEVEL_INFO);

try {
    $conn-&gt;connect();
    $conn-&gt;processUntil(&#39;session_start&#39;);
    $conn-&gt;presence();
    $conn-&gt;message(&#39;me@jabber.server.org&#39;, $msg);
    $conn-&gt;disconnect();
} catch(XMPPHP_Exception $e) {
    die($e-&gt;getMessage());
}
?&gt;
&lt;/pre&gt;
&lt;p&gt;Now I just had to tell procmail to pipe the mails through the PHP script. If you want to get notified about all mails you can simply put this line at the top of your procmail rules (Or maybe at least behind the spam filter rules 😉 ):&lt;/p&gt;
&lt;pre lang=&#34;bash&#34; line=&#34;1&#34;&gt;:0c
|php /home/schiessle/bin/mailnotification.php
&lt;/pre&gt;
&lt;p&gt;I want to get notified only about some specific mails so I extended my procmail rules in this way:&lt;/p&gt;
&lt;pre lang=&#34;bash&#34; line=&#34;1&#34;&gt;:0
* ^(To:|Cc:).*foo@bar-mailinglist.org
{
 	:0c
        |php /home/schiessle/bin/mailnotification.php

        :0
        .bar-list/
}
&lt;/pre&gt;
&lt;p&gt;That’s it! All in all it was quite easy to get e-mail notification through Jabber. Now I don’t have to search for the right applet, configure it etc.. All I have to do is to start my Jabber client and I will get notified about new mails whatever desktop or computer i’m using.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>PDFreaders.org launched</title>
      <link>https://schiessle.eu/en/articles/2009/02/02/pdfreadersorg-launched/</link>
      <pubDate>Mon, 02 Feb 2009 22:18:10 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/02/02/pdfreadersorg-launched/</guid>
      
      
      
      <category>fsfe</category>
      
      <category>OpenStandards</category>
      
      
      
      <description>&lt;p&gt;Today the Free Software Foundation Europe (FSFE) &lt;a href=&#34;http://www.fsfeurope.org/news/2009/news-20090202-01.en.html&#34;&gt;announced&lt;/a&gt; their latest initiative: &lt;a href=&#34;http://www.pdfreaders.org&#34;&gt;PDFreaders.org&lt;/a&gt;. The initiative started in the Fellowship and is coordinated by the Fellows Hannes Hauswedell and Jan-Hendrik Peters. The Fellowship increases FSFE’s financial independence, FSFE’s political weight, FSFE’s workforce and is the source of many great projects, activites and campaigns. Read more about the &lt;a href=&#34;http://fellowship.fsfe.org&#34;&gt;Fellowship&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Many websites with PDF documents have a link to a proprietary PDF reader from one specific company. This initiative tries to change this and offers buttons to link to pdfreaders.org which leads people to a list of &lt;a href=&#34;http://www.fsfeurope.org/documents/freesoftware.en.html&#34;&gt;free as in freedom&lt;/a&gt; and vendor neutral PDF readers.&lt;/p&gt;
&lt;p&gt;FSFE president Georg Greve explains: “Interoperability, competition and choice are primary benefits of &lt;a href=&#34;http://www.fsfeurope.org/projects/os/&#34;&gt;Open Standards&lt;/a&gt; that translate into vendor-independence and better value for money for customers. Although many versions of PDF offer all these benefits for formatted text and documents, files in PDF formats typically come with information that users need to use a specific product. pdfreaders.org provides an alternative to highlight the strengths of PDF as an Open Standard.”&lt;/p&gt;
&lt;p&gt;Jan-Hendrik Peters, one of the coordinators of this initiative says: “Free Software gives us control over the software we use, and Open Standards give us control over our data and allow implementations by many different groups. We wanted to show that with the Portable Document Format people can have both.”&lt;/p&gt;
&lt;p&gt;Support Free Software and Open Standards! Put one of the &lt;a href=&#34;http://www.pdfreaders.org/graphics.html&#34;&gt;PDFreaders.org-Buttons&lt;/a&gt; next to PDF files on your websites!&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>An awesome event is over: KDE 4.2 Release Party and Fellowship Meeting at Stuttgart</title>
      <link>https://schiessle.eu/en/articles/2009/02/01/an-awesome-event-is-over-kde-42-release-party-and-fellowship-meeting-in-stuttgart/</link>
      <pubDate>Sun, 01 Feb 2009 16:30:33 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2009/02/01/an-awesome-event-is-over-kde-42-release-party-and-fellowship-meeting-in-stuttgart/</guid>
      
      
      
      <category>fsfe</category>
      
      <category>kde</category>
      
      <category>stuttgart</category>
      
      
      
      <description>&lt;p&gt;At Friday, 30.Jan.09 we had a joint event between &lt;a href=&#34;http://www.kde.org&#34;&gt;KDE&lt;/a&gt; and the &lt;a href=&#34;http://fellowship.fsfe.org&#34;&gt;Fellowship&lt;/a&gt; of the &lt;a href=&#34;http://www.fsfeurope.org&#34;&gt;Free Software Foundation Europe (FSFE)&lt;/a&gt; and it was simply awesome! Beside a lot of KDE and FSFE people we had a lot of visitors and at the end we were about 40 people! All interested in KDE 4.2 and &lt;a href=&#34;http://www.fsfeurope.org/documents/freesoftware.en.html&#34;&gt;Free Software&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://wiki.fsfe.org/FellowshipGroup/Stuttgart/KDE_4_2_Release_Party?action=AttachFile&amp;amp;do=view&amp;amp;target=img_0025.jpg&#34;&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/fsfe-meeting-stuttgart-2009-1.jpg&#34; class=&#34;article-image&#34; style=&#34;float: left; width: 300px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;At the beginning Frederik started with an introduction and showed all the new and cool things in KDE 4.2. After that i gave a talk about the work of FSFE, especially in 2008, explained the role of the Fellowship for FSFE and highlighted some cool activities from our Fellows. My slides can be found &lt;a href=&#34;http://www.schiessle.org/data/2009-01-30-fellowsip/fsfe&amp;#43;fellowship.pdf&#34;&gt;here&lt;/a&gt; (German). I think i could attract some people and would be really happy to see some new faces at our next Fellowship meeting (probably somewhen in March). If you don’t want to miss it, subscribe to our &lt;a href=&#34;https://lists.fsfe.org/mailman/listinfo/sueddeutschland&#34;&gt;mailing list for South Germany&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://wiki.fsfe.org/FellowshipGroup/Stuttgart/KDE_4_2_Release_Party?action=AttachFile&amp;amp;do=view&amp;amp;target=img_0033.jpg&#34;&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/fsfe-meeting-stuttgart-2009-2.jpg&#34; class=&#34;article-image&#34; style=&#34;float: right; width: 300px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;After my talk we made a small break and than Frank continued with a very interesting talk about the KDE community and how to get involved as a developer, writer, artist or user. Last but not least Sven talked about the new version of Amarok and what we can expect from the new release.&lt;/p&gt;
&lt;p&gt;This was the official part. Now the party started and we had a lot of fun and many interesting discussions between KDE developers and users, FSFE Fellows and all the other people who joined us at this evening. We also discussed some possible activities for the &lt;a href=&#34;https://wiki.fsfe.org/FellowshipGroup/Stuttgart/&#34;&gt;Fellowship Group Stuttgart&lt;/a&gt;. Some Fellows seems to be quite interested in the topic “Free Software in school and education”. I also think that this is a really important topic. Remember, the pupils from today are the decision makers from tomorrow.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://wiki.fsfe.org/FellowshipGroup/Stuttgart/KDE_4_2_Release_Party?action=AttachFile&amp;amp;do=view&amp;amp;target=img_0035.jpg&#34;&gt;&lt;img src=&#34;https://schiessle.eu/img/articles/fsfe-meeting-stuttgart-2009-3.jpg&#34; class=&#34;article-image&#34; style=&#34;float: left; width: 300px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As it becomes later a small group of people survived. One of them was Martin Konold, a KDE Developer from the very first days of KDE. He told us a lot of interesting and funny stories about the beginning of KDE and the development of the Free Software desktop.&lt;/p&gt;
&lt;p&gt;At 2:30 at night a great event was over. I really want to thank &lt;a href=&#34;http://www.kdedevelopers.org/blog/4326&#34;&gt;Frederik&lt;/a&gt; for his great help in organising this event and all the other KDE people who helped to make this event that awesome! It was a lot of fun and a great cooperation between KDE and FSFE people! Looking forward for the next opportunity to organise such a great event!&lt;/p&gt;
&lt;p&gt;More pictures can be found &lt;a href=&#34;https://wiki.fsfe.org/FellowshipGroup/Stuttgart/KDE_4_2_Release_Party&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Quick Guide to GPLv3</title>
      <link>https://schiessle.eu/en/articles/2007/11/08/quick-guide-to-gplv3/</link>
      <pubDate>Thu, 08 Nov 2007 21:30:24 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2007/11/08/quick-guide-to-gplv3/</guid>
      
      
      
      <category>FreeSoftware</category>
      
      <category>gpl</category>
      
      
      
      <description>&lt;p&gt;The FSF has released a &lt;a href=&#34;http://www.fsf.org/licensing/licenses/quick-guide-gplv3.html&#34;&gt;Quick Guide to GPLv3&lt;/a&gt;. This article explains all major changes in an easy-to-understand overview. So it is a good staring point for everyone who wants to understand GPLv3.&lt;/p&gt;
&lt;p&gt;It is also a good resource for developers who plan to release their software under the GPLv3.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>The Matrix Has You</title>
      <link>https://schiessle.eu/en/articles/2007/06/25/the-matrix-has-you/</link>
      <pubDate>Mon, 25 Jun 2007 10:05:03 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2007/06/25/the-matrix-has-you/</guid>
      
      
      
      <category>FreeSoftware</category>
      
      <category>fun</category>
      
      
      
      <description>&lt;p&gt;While browsing the Web i have found the video presentation &lt;a href=&#34;http://www.lsd.ic.unicamp.br/~oliva/fsfla/whatisthematrix/&#34;&gt;“Free Software and the Matrix”&lt;/a&gt; by Alexandre Oliva.&lt;/p&gt;
&lt;p&gt;Just take some time, watch this presentation and you will see how much the movie “The Matrix” discusses the issues of the Free Software movement.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Back from Chemnitz</title>
      <link>https://schiessle.eu/en/articles/2007/03/05/back-from-chemnitz/</link>
      <pubDate>Mon, 05 Mar 2007 20:51:07 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2007/03/05/back-from-chemnitz/</guid>
      
      
      
      <category>fsfe</category>
      
      
      
      <description>&lt;img src=&#34;https://schiessle.eu/img/articles/clt07_fsfe_booth.png&#34; class=&#34;article-image&#34; style=&#34;float: right;&#34; /&gt;
At this weekend Rainer and I were in Chemnitz at the [&amp;#8220;Chemnitzer Linux Tage&amp;#8221; (CLT)][1]. It was the first time that FSFE had a booth at this event and for me it was the first time going to a fair especially to work at the FSFE booth.
&lt;p&gt;The first day was really hard for us. Because of the late decision to go to Chemnitz we had a bad place for our booth and many visitors hadn’t seen us. But luckily we had found a much better place for the second day. This is a picture of our booth at the second day, it was in the central corridor in front of the entrance:&lt;/p&gt;
&lt;p&gt;I was surprised how many visitors come to our booth and asked who we are and what we are doing. After they had seen our GPLv3 stickers and pins the new version of the GPL and especially the DRM clause was a common topic, too. It was a lot of fun to talk about the FSFE, our work and other related topics to the visitors.&lt;/p&gt;
&lt;p&gt;Now that I’m back from Chemnitz and after almost four days without internet connection i have checked my emails and some news sites. I was surprised to read on pro-linux (a German GNU/Linux news site) a comment from a visitor of the CLT that he has talked to us and he thinks that FSFE has a “very intelligent position on DRM”. If others has become such a positive impression from FSFE too, i think it was a great success.I had a lot of fun and the CLT was a great event. I hope we will have a booth again next year.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Test your knowledge of the GPL and LGPL</title>
      <link>https://schiessle.eu/en/articles/2006/12/15/test-your-knowledge-of-the-gpl-and-lgpl/</link>
      <pubDate>Fri, 15 Dec 2006 18:17:14 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/12/15/test-your-knowledge-of-the-gpl-and-lgpl/</guid>
      
      
      
      <category>FreeSoftware</category>
      
      <category>gpl</category>
      
      
      
      <description>&lt;p&gt;While reading some &lt;a href=&#34;http://www.fsf.org/blogs&#34;&gt;FSF Blogs&lt;/a&gt; i found a link to a &lt;a href=&#34;http://www.gnu.org/cgi-bin/license-quiz.cgi&#34;&gt;license quiz&lt;/a&gt; where you can test your knowledge of the GPL and LGPL.. If you want to test your knowledge of the GPL and LGPL than try the license quiz.&lt;/p&gt;
&lt;p&gt;I remember that i had found this test already some years ago but forgot about it. So i tried it again to see if my licensing knowledge has improved. The last time i did the test i remember that i answered a few questions wrongly but this time everything was correct. Too bad that in a few months we will have a new &lt;a href=&#34;http://gplv3.fsf.org/&#34;&gt;GPL and LGPL.&lt;/a&gt; 😉&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>a lot of impressions and news</title>
      <link>https://schiessle.eu/en/articles/2006/11/13/a-lot-of-impressions-and-news/</link>
      <pubDate>Mon, 13 Nov 2006 18:57:37 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/11/13/a-lot-of-impressions-and-news/</guid>
      
      
      
      <category>fsfe</category>
      
      <category>java</category>
      
      <category>FreeSoftware</category>
      
      
      
      <description>&lt;p&gt;I’m back from the SFSCon and the first international FSFE Fellowship Meeting in Bolzano (Italy). For me i can say that it was a great event and it gaves me the opportunity to meet a lot of great people from the Free Software Foundation Europe and around Free Software in general.&lt;/p&gt;
&lt;p&gt;The Fellowship Meeting was also the place were a new project of the FSFE was launched, the &lt;a href=&#34;http://www.fsfeurope.org/projects/ftf/ftf.en.html&#34;&gt;Freedom Task Force (FTF)&lt;/a&gt;. A project which works in partnership with &lt;a href=&#34;http://www.gpl-violations.org&#34;&gt;gpl-violations.org&lt;/a&gt; and offers licensing education, fiduciary services and licence enforcement. For more information follow the link above.&lt;/p&gt;
&lt;p&gt;But that’s not enough something more happens. Sun &lt;a href=&#34;http://www.sun.com/aboutsun/media/presskits/2006-1113/&#34;&gt;announced&lt;/a&gt; to release Java as &lt;a href=&#34;http://fsfeurope.org/documents/freesoftware.en.html&#34;&gt;Free Software&lt;/a&gt; under the GPL. Already many people have written about it and so i just want to refer to &lt;a href=&#34;https://www.fsfe.org/en/fellows/greve/freedom_bits/free_software_ecosystem_changes_sun_announcing_java_under_gplv2_and_ftf&#34;&gt;Georg Greve’s good analysis&lt;/a&gt; of the situation. Also Richard Stallman has already reacted really positive:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;It will be very good that the &lt;a href=&#34;http://www.gnu.org/philosophy/java-trap.html&#34;&gt;Java trap&lt;/a&gt; won’t exist anymore, it will be a thing of the past. That kind of problem can still exist in other areas but it won’t exist for Java anymore. The GNU general public licence is the most popular and the most widely used software licence, used for some 70% of all free software packages. The special thing about this licence is that it’s a copyleft licence. That is to say, all versions of the program must carry this licence. So the freedoms that the GNU GPL gives to the users must reach all the users of the program, and that’s the purpose for which I wrote it. To ensure that all users of the software have the freedom that users should have.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;I think Sun has, well, with this contribution, have contributed more than any other company to the free software community in the form of software. And it shows leadership. It’s an example that I hope others will follow.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And this is the response of Eben Moglen&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;As Java became one of the most important languages for the expression of ideas about technology of programming in the last decade the question of Java’s freedom, wether it could be use freely and made part of free software projects, has been a crucial question. Sun’s policy of GPL’ing Java, which we are celebrating now, is an extraordinary achievement in returning programming technology to that state of freely available knowledge. Sun has now GPL’ed hardware designs, Sun is GPL’ing Java: that’s an extraordinary vote of confidence in this way of sharing information. And we, in the free software world, are very pleased and very flattered to see Sun taking its own very valuable and very important product and agreeing with us that they will be more advantageous to Sun as well as to the rest of the community if they are shared under these rules.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;So i just have to say thank you and congratulations to Sun for this step.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Login with GnuPG smartcard</title>
      <link>https://schiessle.eu/en/articles/2006/08/07/login-with-gnupg-smartcard/</link>
      <pubDate>Mon, 07 Aug 2006 16:09:36 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/08/07/login-with-gnupg-smartcard/</guid>
      
      
      
      <category>gnupg</category>
      
      <category>smartcard</category>
      
      
      
      <description>&lt;p&gt;Libpam-poldi allows you to use your Fellowship crypto card to log in your GNU/Linux system.&lt;/p&gt;
&lt;p&gt;First check if poldi detects your cardreader: ‘poldi-ctrl -d’. Unfortunately some cardreader doesn’t work with poldi and the existing free driver. For example the cardma4040 needs the non-free driver from Omnikey.&lt;/p&gt;
&lt;p&gt;If poldi successfully detected your cardreader you can start to configure poldi. Poldi has a pretty good documentation so i will keep my explanations rather short.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Root has to register the new card for poldi:
&lt;pre&gt;poldi-ctrl &amp;ndash;register-card &amp;ndash;account &amp;lt;your-user-account&amp;gt; &amp;ndash;serialno &amp;lt;serialno of your card&amp;gt;&lt;/pre&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;pre&gt;&lt;code&gt;You can also execute this command without &amp;amp;#8216;&amp;amp;#8211;account &amp;lt;your-user-account&amp;gt;&amp;amp;#8217; but than the user will not be able to install or update his card&amp;amp;#8217;s keys.

The serialno can be found by executing &amp;amp;#8216;gpg &amp;amp;#8211;card-status&amp;amp;#8217; and looking for &amp;amp;#8220;Application ID&amp;amp;#8221;.&amp;lt;/li&amp;gt; 

  * Now we have to establish a mapping between the user and the smartcard he owns: 
    &amp;lt;pre&amp;gt;poldi-ctrl --associate --account &amp;amp;lt;your-user-account&amp;amp;gt; --serialno &amp;amp;lt;serialno of your card&amp;amp;gt;&amp;lt;/pre&amp;gt;

  * Now you have to write your public key into the appropriate key file (you have to do this within your user account) 
    &amp;lt;pre&amp;gt;poldi-ctrl --set-key&amp;lt;/pre&amp;gt;

  * That&amp;amp;#8217;s it, now you can test it with &amp;amp;#8216;poldi-ctrl &amp;amp;#8211;test&amp;amp;#8217;
  * Now you have to tell pam, that you want to use poldi.

    Therefore you have to edit the files in /etc/pam.d. If, for example, you want to login to kdm with your card, edit the file /etc/pam.d/kdm. Replace the line &amp;amp;#8216;@include common-auth&amp;amp;#8217; with&amp;lt;/p&amp;gt; 
    &amp;lt;pre&amp;gt;auth    required   pam_poldi.so&amp;lt;/pre&amp;gt;
    
    If you want to login unattended, use
    
    &amp;lt;pre&amp;gt;auth    required   pam_poldi.so try-pin=123456 quiet&amp;lt;/pre&amp;gt;
    
    And if you want to fallback to regular unix passwords, use
    
    &amp;lt;pre&amp;gt;auth    sufficient pam_poldi.so try-pin=123456 quietauth    required   pam_unix.so nullok_secure&amp;lt;/pre&amp;gt;&amp;lt;/ol&amp;gt; 

Now you should be able to use your GnuPG smartcard to log in your GNU/Linux system.
&lt;/code&gt;&lt;/pre&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>French “iPod Law” violates Human Rights</title>
      <link>https://schiessle.eu/en/articles/2006/08/02/french-ipod-law-violates-human-rights/</link>
      <pubDate>Wed, 02 Aug 2006 21:26:51 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/08/02/french-ipod-law-violates-human-rights/</guid>
      
      
      
      <category>copyright</category>
      
      <category>drm</category>
      
      
      
      <description>&lt;p&gt;The so-called “iPod law” contains reduced fines for file sharing and forced companies to open their DRM specification to enable competition.&lt;/p&gt;
&lt;p&gt;The French Constitutional Council has declared this aspects unconstitutional. The justification: The “iPod law” violated the Human Right of constitutional protections of property.&lt;/p&gt;
&lt;p&gt;Mr. Menard, a partner at the Lovells law firm and a specialist in “intellectual property” said: “The Constitutional Council effectively highlighted the importance of intellectual property rights,” and added that Apple Computer and other companies could not be forced to share their copy-protection technology without being paid for it.&lt;/p&gt;
&lt;p&gt;Does it sound like a joke? But it’s true. For more information read:&lt;/p&gt;
&lt;p&gt;– &lt;a href=&#34;http://www.nytimes.com/2006/07/28/business/28cnd-music.html?ex=1311739200&amp;amp;en=a4590cf789d399fb&amp;amp;ei=5088&#34;&gt;New York Times: Parts of French ‘iPod Law’ Struck Down (English)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;– &lt;a href=&#34;http://www.golem.de/0608/46891.html&#34;&gt;Golem: iTunes-Gesetz verstößt gegen Menschenrechte (German)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;UPDATE: Jacques Chirac, president of France, has signed the law and so it become valid. I don’t know if the French Constitutional Council will stop the law but as long as nothing happens the law is legally valid. Great Britain, Sweden, Denmark, Norway and Poland could be the next countries with similar laws. Source (German): &lt;a href=&#34;http://de.theinquirer.net/2006/08/04/die_lex_itunes_tritt_in_kraft.html&#34;&gt;The Inquirer DE&lt;/a&gt;.&amp;lt;div class=&amp;ldquo;share-on-diaspora&amp;rdquo; data-url=&amp;ldquo;&lt;a href=&#34;http://blog.schiessle.org/2006/08/02/french-ipod-law-violates-human-rights/%22&#34;&gt;http://blog.schiessle.org/2006/08/02/french-ipod-law-violates-human-rights/&#34;&lt;/a&gt; data-title=&amp;ldquo;French &amp;ldquo;iPod Law&amp;rdquo; violates Human Rights&amp;rdquo;&amp;gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Interview with DefectiveByDesign</title>
      <link>https://schiessle.eu/en/articles/2006/08/02/interview-with-defectivebydesign/</link>
      <pubDate>Wed, 02 Aug 2006 15:53:01 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/08/02/interview-with-defectivebydesign/</guid>
      
      
      
      <category>drm</category>
      
      
      
      <description>&lt;p&gt;Thanks to Markus from &lt;a href=&#34;http://netzpolitik.org/2006/interview-mit-defectivebydesign-kampagne/&#34;&gt;netzpolitik.org&lt;/a&gt; i have found this interesting &lt;a href=&#34;http://digitalmusic.weblogsinc.com/2006/08/01/interview-with-defectivebydesign/&#34;&gt;interview&lt;/a&gt; with the &lt;a href=&#34;http://defectivebydesign.org/&#34;&gt;DefectiveByDesign&lt;/a&gt; campaign.&lt;/p&gt;
&lt;p&gt;The campaign has received quite a lot of attention in the media. For example the &lt;a href=&#34;http://defectivebydesign.org/petition/bonopetition&#34;&gt;“Bono petition”&lt;/a&gt; saw press coverage in more than 115 news papers and news sitest in the USA.&lt;/p&gt;
&lt;p&gt;Here a answer from DefectiveByDesign to a probably common question on this topic: &lt;em&gt;“Are those two goals (content protection and consumer protection) compatible with one another?”&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;DefectiveByDesign:&lt;/strong&gt; A better word than consumer, to describe me and you, is citizen. So is content protection and the rights of citizens compatible? When we live in a age where all digital works of art and all human knowledge can be transferred at (next to) zero cost, and where the cost of making one more copy is zero. Is it right to be building digital fences and digital handcuffs around this art and knowledge? If, as citizens of a society, we can see the advantages of allowing art and knowledge to flow without impediment, we as citizens will also have reason to find new ways to recompense the artists and knowledge purveyors. In fact, there are more artists working today than ever before, and more of their art is being enjoyed because of technology free from DRM and free of the Big Media gate keepers. The term “Content Protection” is a loaded term, framing the debate with their slant. I would say that this term really describes their attempt to hold back advancing society.&lt;/p&gt;
&lt;/blockquote&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Second draft of GPLv3</title>
      <link>https://schiessle.eu/en/articles/2006/07/27/second-draft-of-gplv3/</link>
      <pubDate>Thu, 27 Jul 2006 17:57:04 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/07/27/second-draft-of-gplv3/</guid>
      
      
      
      <category>FreeSoftware</category>
      
      <category>gpl</category>
      
      
      
      <description>&lt;p&gt;After about seven month of discussion and more than 1000 comments through &lt;a href=&#34;http://gplv3.fsf.org/comments/&#34;&gt;gplv3.fsf.org/comments/&lt;/a&gt; the &lt;a href=&#34;http://www.fsf.org&#34;&gt;FSF&lt;/a&gt; has published the second draft of the &lt;a href=&#34;http://gplv3.fsf.org/gpl-draft-2006-07-27.html&#34;&gt;GNU General Public License (GPL) Version 3&lt;/a&gt; and the first draft of the &lt;a href=&#34;http://gplv3.fsf.org/lgpl-draft-2006-07-27.html&#34;&gt;GNU Lesser General Public License (LGPL) Version 3&lt;/a&gt; which is now designed as a set of permissive exceptions to GPLv3 in accord with section 7. The main changes in the second draft of GPLv3 are clarifications of the DRM section, a reworked license compatibility section and provisions that specifically allow to distribute programs on certain file sharing networks such as BitTorrent. For more details look at &lt;a href=&#34;http://gplv3.fsf.org/gpl3-dd2-guide.html&#34;&gt;http://gplv3.fsf.org/gpl3-dd2-guide.html&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>Open letter to Bono (U2)  to take a stand against DRM</title>
      <link>https://schiessle.eu/en/articles/2006/06/30/open-letter-to-bono-u2-to-take-a-stand-against-drm/</link>
      <pubDate>Fri, 30 Jun 2006 09:12:03 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/06/30/open-letter-to-bono-u2-to-take-a-stand-against-drm/</guid>
      
      
      
      <category>copyright</category>
      
      <category>drm</category>
      
      
      
      <description>&lt;p&gt;&lt;a href=&#34;http://defectivebydesign.org&#34;&gt;DefectiveByDesign&lt;/a&gt;, a &lt;a href=&#34;http://www.fsf.org&#34;&gt;FSF&lt;/a&gt; campaign to eliminate DRM, has written an open letter to &lt;a href=&#34;http://en.wikipedia.org/wiki/Bono&#34;&gt;Bono&lt;/a&gt; the lead singer of the Irish rock band &lt;a href=&#34;http://en.wikipedia.org/wiki/U2&#34;&gt;U2&lt;/a&gt; to take a stand against Digital Restrictions Management (DRM). The group has focused on Bono because of his social activism and leadership in the music industry. The aim is to collect 10.000 signatures, at which point they will seek an audience with Bono, discuss with him the threats posed by DRM and request that he be the final signer.&lt;/p&gt;
&lt;p&gt;Some time ago i have already &lt;a href=&#34;https://www.fsfe.org/en/fellows/schiessle/blog/world_intellectual_property_day_canadian_musicians_say_not_in_our_names&#34;&gt;blogged&lt;/a&gt; about a initiative of Canadian musicians against DRM (&lt;a href=&#34;http://www.musiccreators.ca/&#34;&gt;http://www.musiccreators.ca/&lt;/a&gt;). The open letter to Bono could be the first step to achieve something similar in Europe or even worldwide.&lt;/p&gt;
&lt;p&gt;You can sign the letter at: &lt;a href=&#34;http://defectivebydesign.org/petition/bonopetition&#34;&gt;http://defectivebydesign.org/petition/bonopetition&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>License fee for PDF export?</title>
      <link>https://schiessle.eu/en/articles/2006/06/04/license-fee-for-pdf-export/</link>
      <pubDate>Sun, 04 Jun 2006 22:19:02 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/06/04/license-fee-for-pdf-export/</guid>
      
      
      
      <category>FreeSoftware</category>
      
      <category>open standards</category>
      
      <category>pdf</category>
      
      
      
      <description>&lt;p&gt;As a GNU/Linux user i’m used to have PDF export in almost every program. With Office 2007 Microsoft finally wants to offer this common feature to their users too. But it seems like Adobe doesn’t like this idea. As cnet &lt;a href=&#34;http://news.com.com/Report&amp;#43;Microsoft&amp;#43;expects&amp;#43;Adobe&amp;#43;to&amp;#43;file&amp;#43;antitrust&amp;#43;suit/2100-1012_3-6079320.html?tag=nefd.top&#34;&gt;reported&lt;/a&gt; Adobe asked Microsoft to remove the PDF export feature or pay a fee for it.&lt;/p&gt;
&lt;p&gt;Brian Jones from Microsoft has published some &lt;a href=&#34;http://blogs.msdn.com/brian_jones/archive/2006/06/03/616022.aspx&#34;&gt;information&lt;/a&gt;, too.&lt;/p&gt;
&lt;p&gt;Adobe promotes PDF as an &lt;a href=&#34;http://en.wikipedia.org/wiki/Open_standard&#34;&gt;open standard&lt;/a&gt;. But if Adobe now starts to sue competitors they can no longer claim that PDF is an open standard.&lt;/p&gt;
&lt;p&gt;What does this mean for all the Free Software applications with PDF export and for the exchange of documents in general? If Adobe starts to sue Microsoft, who will be the next victim? It would be a big loss for everyone if we can no loger rely on PDF as an open standard.&lt;/p&gt;
</description>
    </item>
    
    <item>
      
      
      
	<category>English</category>
        
      
      
      	
      <title>“World Intellectual Property Day” – Canadian musicians say “Not in Our Names”</title>
      <link>https://schiessle.eu/en/articles/2006/04/27/world-intellectual-property-day-canadian-musicians-say-not-in-our-names/</link>
      <pubDate>Thu, 27 Apr 2006 22:16:34 +0000</pubDate>
      <author>Björn Schießle (bjoern@schiessle.org)</author>
      <guid>https://schiessle.eu/en/articles/2006/04/27/world-intellectual-property-day-canadian-musicians-say-not-in-our-names/</guid>
      
      
      
      <category>copyright</category>
      
      <category>drm</category>
      
      
      
      <description>&lt;p&gt;April 26th was the &lt;a href=&#34;http://www.heise.de/newsticker/meldung/72409&#34;&gt;“World Intellectual Property Day” (German)&lt;/a&gt;. Brigitte Zypries, minister of justice of Germany, said “We need a better sense of right and wrong for ‘intellectual property&amp;rsquo;” and announced that the protection of ‘intellectual property’ will be the main focus when Germany will held the Presidency of the Council of the European Union in 2007.&lt;/p&gt;
&lt;p&gt;At the same time Canadian musicians like Avril Lavigne, Sarah McLachlan or Sloan say &lt;a href=&#34;http://www.musiccreators.ca/docs/A_New_Voice-Policy_Paper.pdf&#34;&gt;“Not in Our Names”&lt;/a&gt;. The “Canadian Music Creators Coalition” (&lt;a href=&#34;http://www.musiccreators.ca/&#34;&gt;CMCC&lt;/a&gt;) will ensure that lobbyists for major record labels and music publishers are not the only voices heard in debates about Canada’s copyright laws and other key cultural policy issues (&lt;a href=&#34;http://www.musiccreators.ca/docs/Press_Release-April_26.pdf&#34;&gt;press release&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;The CMCC is united under three key principles:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Suing Our Fans is Destructive and Hypocritical&lt;/li&gt;
&lt;li&gt;Digital Locks are Risky and Counterproductive&lt;/li&gt;
&lt;li&gt;Cultural Policy Should Support Actual Canadian Artists&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I think this is a great campaign and i hope musicians from other countries will recognize it and follow the Canadian musicians with similar campaigns.&amp;lt;div class=&amp;ldquo;share-on-diaspora&amp;rdquo; data-url=&amp;ldquo;&lt;a href=&#34;http://blog.schiessle.org/2006/04/27/world-intellectual-property-day-canadian-musicians-say-not-in-our-names/%22&#34;&gt;http://blog.schiessle.org/2006/04/27/world-intellectual-property-day-canadian-musicians-say-not-in-our-names/&#34;&lt;/a&gt; data-title=&amp;ldquo;&amp;ldquo;World Intellectual Property Day&amp;rdquo; - Canadian musicians say &amp;ldquo;Not in Our Names&amp;rdquo;&amp;quot;&amp;gt;&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
