Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

nl-201406.en.xhtml 10KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html newsdate="2014-06-04" type="newsletter">
  3. <head>
  4. <title>FSFE Newsletter - June 2014</title>
  5. </head>
  6. <body class="newsletter article" microformats="h-entry" id="nl-201406">
  7. <h1 class="p-name">FSFE Newsletter – June 2014</h1>
  8. <h2>Security is interdependent: We are all Gmail users now</h2>
  9. <p newsteaser="yes">You care about privacy and you are either paying an e-mail provider, or even
  10. run your own mail server to keep autonomy, control, and privacy over your
  11. email. You do this because you want to make sure that no big company has copies
  12. of all of your personal email. Still, this does not prevent other companies
  13. from getting their hands on your data. It is not enough to merely take care of
  14. your own security, if you seek to increase your security. You have to convince
  15. your peers to increase their security, too: like Jacob Appelbaum says, <a
  16. href="http://www.roussos.cc/2014/05/14/our-privacy-is-interdependent/">security
  17. is interdependent</a>.</p>
  18. <p>FSF board member Benjamin Mako Hill wondered how much of his email has ended
  19. up in the hands of companies such as Google. So he wrote a small program to go
  20. through all his email since April 2004 (when Gmail was introduced) and analyse
  21. it. <a
  22. href="http://mako.cc/copyrighteous/google-has-most-of-my-email-because-it-has-all-of-yours">Read
  23. what Benjamin found out</a>, what <a
  24. href="https://blogs.fsfe.org/gerloff/2014/05/27/were-all-gmail-users-now-pt-2">results
  25. FSFE's Karsten Gerloff</a> and <a
  26. href="http://hroy.eu/posts/gmail-most-email/">Hugo Roy</a> got when they
  27. reproduced it, and why not try those scripts out for yourself?</p>
  28. <h2>Is it a torch light or a spy in your pocket?</h2>
  29. <p>A lot of programs that people install on their Android devices violate their
  30. security. It is common that those programs ask users to accept non-readable
  31. terms and conditions, once installed they might reveal where the device (and
  32. therefore the user) currently is, and access personal data like user's address
  33. books or text messages. A seemingly innocent app such as a torch light can thus
  34. violate the user's privacy.</p>
  35. <p>For owners of mobile devices it is important to have an app store that
  36. exclusively provides Free Software. Since this means that the source code can
  37. be checked by external parties other than the vendor, they can check what an
  38. app really does, and highlight or directly remove anti-features. The result is
  39. a repository providing software with licenses that respect the user's rights
  40. instead of violating them.</p>
  41. <p>In the last months we experienced that more and more people care about the
  42. software on their mobile devices. <a
  43. href="https://blogs.fsfe.org/mk/consumer-protection-for-mobiles-is-it-a-torch-light-or-a-spy-in-your-pocket/">Your
  44. editor summarised what is currently happening with Free Your Android</a>,
  45. including promotion in Greece, updating and translation status of our F-Droid
  46. leaflets, an interview with the F-Droid developer, and your editor
  47. participating in an event about consumer protection in the mobile phone sphere
  48. in the German Parliament.</p>
  49. <h2>Another security nightmare: DRM</h2>
  50. <p>After a <a href="http://lwn.net/Articles/584167/">possible setback for DRM
  51. in Europe</a> it is important to raise more awareness about this issue. We
  52. cannot stay quiet while some companies use Digital Restriction Management to
  53. write their own copyright laws, restrict us, and decrease our IT security. Many
  54. organisations including <a
  55. href="https://www.eff.org/deeplinks/2014/05/how-drm-harms-our-computer-security">EFF</a>,
  56. April, and us participated in the <a
  57. href="http://www.defectivebydesign.org/thanks-for-a-great-international-day-against-drm">Day
  58. Against DRM</a>, organised by FSF to highlight the dangers of DRM. The FSFE
  59. used the occasion to <a href="/news/2014/news-20140506-01.html">contact the
  60. European Commission with an Open Letter about DRM in HTML5</a>. We explained
  61. that DRM is directly contrary to the interests of the vast majority of Internet
  62. users everywhere.</p>
  63. <p>Just a few days later the Free Software community received the bad news from
  64. Mozilla: DRM will be implemented in Firefox (the part is called EME). The
  65. reactions ranged from the <a
  66. href="https://www.fsf.org/news/fsf-condemns-partnership-between-mozilla-and-adobe-to-support-digital-restrictions-management">FSF
  67. condemning the partnership between Mozilla and Adobe</a>, <a
  68. href="https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/">Mozilla
  69. justifying its decision</a>, <a
  70. href="https://leomca.github.io/2014/05/15/Mozilla-and-DRM.html">others
  71. supporting it</a>, and <a
  72. href="http://blogs.computerworlduk.com/open-enterprise/2014/05/whither-mozilla/index.htm">Glyn
  73. Moody criticising them by comparing Mozilla's mission with its current
  74. action</a>. As always we are interested in your opinion. What do you think
  75. about Mozilla's decision and its reasoning? What can the Free Software
  76. community do to counterbalance this move? Let us know on our <a
  77. href="https://mail.fsfeurope.org/mailman/listinfo/discussion">public discussion
  78. list</a>.</p>
  79. <h2>Something completely different</h2>
  80. <ul>
  81. <li>FSFE's country team Netherlands <a
  82. href="https://blogs.fsfe.org/flx/2014/05/07/the-importance-of-free-software/">wrote
  83. a short text &quot;The Importance of Free Software&quot;</a> (also <a href="https://blogs.fsfe.org/flx/2014/05/07/het-belang-van-vrije-software/">available in Dutch</a>) about the
  84. relevance of Free Software and its conclusions for policy makers. The text
  85. highlights the crucial question for our society about &quot;who controls the
  86. software?&quot;. &quot;Because if we don't control the software we use, it
  87. controls us. And whoever controls the software therefore controls us.&quot; The
  88. text then was used to convince candidates to sign the <a
  89. href="http://freesoftwarepact.eu">Free Software Pact</a> - a project run by
  90. <a href="http://www.april.org/">April</a> and supported by many organisations, including
  91. the FSFE.</li>
  92. <li>Fellowship Groups: After two years as a Fellowship representative in FSFE's
  93. GA, <a
  94. href="http://www.roussos.cc/2014/04/30/athens-free-software-monthly-meetups/">Nikos
  95. Roussos now started local FSFE meetings in Athens</a>. Furthermore we had a
  96. <a
  97. href="https://blogs.fsfe.org/guido/2014/05/report-from-the-first-fellowship-meeting-in-wiesbaden/">first
  98. Fellowship meeting in Wiesbaden</a>. In addition, new groups are establishing
  99. regular meetings since a while now in Zurich and Cologne.</li>
  100. <li>Our sister organisation, the FSF, awarded the <a
  101. href="https://www.fsf.org/news/tehnoetic-wireless-usb-adapter-now-fsf-certified-to-respect-your-freedom">Respects
  102. Your Freedom (RYF) certification to the Tehnoetic TET-N150 wireless USB
  103. adapter</a>. The RYF certification mark is awarded to products that meet the
  104. FSF's standards in regard to users' freedom, control over the product, and
  105. privacy. Visitors of FSFE's booth at FOSDEM might already know those adapters,
  106. as Tiberiu C. Turbureanu sold them at our booth.</li>
  107. <li>From the <a href="http://planet.fsfe.org">planet aggregation</a>:
  108. <ul>
  109. <li>Carsten Agger explains what the result of the <a href="https://blogs.fsfe.org/agger/2014/05/26/elections-14-not-much-to-celebrate/">Danish referendum on the European patent court and the unitary patent means for software patents</a>.</li>
  110. <li>Leena Simon published an essay about the importance of attributions and the flow of information named <a href="http://leena.de/standing-on-the-shoulders-of-free-culture/">&quot;Standing on the Shoulders of Free Culture&quot;</a>.</li>
  111. <li>Your editor wrote about the <a href="https://blogs.fsfe.org/mk/support-hardware-computing-platform-for-hackers-and-free-software-drivers-now/">Novena hardware computing platform for hackers and Free Software drivers</a> and documented <a href="https://blogs.fsfe.org/mk/how-to-generate-a-new-wifi-password-the-mobile-friendly-way/">how to generate a new wifi password the mobile friendly way</a>.</li>
  112. <li>Henri Bergius spent three days at the GNOME Developer Experience hackfest
  113. <a href="http://bergie.iki.fi/blog/flowhub-gnome-dx/">working on the NoFlo
  114. runtime for GNOME</a>.</li>
  115. <li>Mario Fux wrote that <a href="https://blogs.fsfe.org/mario/?p=231">Debian's
  116. KDE community needs help</a>.</li>
  117. <li>Our new intern <a
  118. href="https://blogs.fsfe.org/seeger/2014/05/23/linuxtag-2014/">Bela
  119. Seeger</a> as well as long term Fellow <a
  120. href="https://blogs.fsfe.org/padams/?p=303">Paul Adams</a> report from Linuxtag
  121. in Berlin.</li>
  122. <li>While Konstantinos Boukouvalas wrote about LPI affiliates, <a
  123. href="http://blogs.fsfe.org/boukouvalas/?p=556">openLabs and OSCAL, as well
  124. as the Albanian Free Software Community</a>.</li>
  125. </ul></li>
  126. </ul>
  127. <h2>Get active: Your experiences with programming resources for children</h2>
  128. <p>Beside <a
  129. href="https://blogs.fsfe.org/guido/2014/05/free-software-in-education-news-april/">publishing
  130. the monthly Free Software in education news</a> our education team answers a
  131. lot of question by people who want to use more Free Software in education.</p>
  132. <p>As the edu-team was asked for good resources to teach kids to program, Guido
  133. Arnold thought the answer (or more a summary of the answers) might be
  134. interesting to others as well. So he published <a
  135. href="https://blogs.fsfe.org/guido/2014/05/teach-programming-with-free-software/">the
  136. summary</a>. To improve our education website we ask you to give us feedback on
  137. those resources. How do you like them, did you already have experience with
  138. some of them, what was good, where did you have problems, and which resources
  139. did we miss?</p>
  140. <p>Thanks to all the <a href="/contribute/contribute.html">volunteers</a>, <a href="http://fellowship.fsfe.org/join">Fellows</a> and
  141. <a href="/donate/thankgnus.html">corporate donors</a> who enable our work,<br/>
  142. <a href="/about/kirschner">Matthias Kirschner </a> - <a href="http://www.fsfe.org">FSFE</a></p>
  143. <!--/e-content-->
  144. </body>
  145. <sidebar promo="about-fsfe"><!--
  146. <h3>FSFE News</h3>
  147. <ul>
  148. <li><a href="/news/">Press Releases</a></li>
  149. <li><a href="/news/newsletter.html">Newsletters Archive</a></li>
  150. <li><a href="/events/">Upcoming Events</a></li>
  151. <li><a href="http://planet.fsfe.org/">Planet Blogs</a></li>
  152. <li><a href="/contact/community.html">Free Software Discussions</a></li>
  153. </ul>
  154. --></sidebar>
  155. <author id="kirschner" />
  156. <date>
  157. <original content="2014-06-04" />
  158. </date>
  159. <followup>donate</followup>
  160. <tags>
  161. <tag>newsletter</tag>
  162. <tag>ayc</tag>
  163. <tag>DRM</tag>
  164. </tags>
  165. </html>
  166. <!--
  167. Local Variables: ***
  168. mode: xml ***
  169. End: ***
  170. -->