mediagoblin-0.8.0-gallery-of-fine-creatures.html 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168
  1. <html>
  2. <head>
  3. <title>
  4. MediaGoblin 0.8.0: A Gallery of Fine Creatures
  5. </title>
  6. <meta name="date" contents="2015-06-04 09:15" />
  7. <meta name="author" contents="Deb Nicholson" />
  8. <meta name="tags" contents="release" />
  9. </head>
  10. <body>
  11. <p class="centered">
  12. <img src="/blog_images/0.8.0/gallery_of_fine_creatures_banner-scaled.png"
  13. alt="MediaGoblin 0.8.0: A Gallery of Fine Creatures banner" />
  14. </p>
  15. <p>
  16. We're excited to announce that MediaGoblin 0.8.0, "A Gallery of Fine
  17. Creatures", has been released! The biggest news is that the client to
  18. server API (making use of the future federation API) is much improved!
  19. That means that users no longer have to depend on a browser to access
  20. MediaGoblin. You can access and post to your MediaGoblin instance via
  21. any of several Pump.io compatible clients, like
  22. <a href="https://pumpa.branchable.com/">Pumpa</a> and
  23. <a href="https://jancoding.wordpress.com/dianara/">Dianara</a> (or
  24. write your own using
  25. <a href="http://pypump.org/en/latest/">PyPump</a>)! The grand goal is
  26. a generic (and ubiquitous) client protocol that will work with lots of
  27. different served applications that use the pump standard. Eventually,
  28. any Pump API compatible client will essentially be a MediaGoblin
  29. client and a Pump.IO client. We expect more client types to be added
  30. very soon!
  31. </p>
  32. <p>
  33. Part of the process of world domination via federation means that
  34. we're now able to support serving content to multiple client types
  35. through a single protocol.
  36. </p>
  37. <p>
  38. For example, here's a user uploading an image using the Pump.IO
  39. client, Pumpa:
  40. </p>
  41. <p class="blog_image">
  42. <a href="/blog_images/0.8.0/pumpa_upload-from_pumpa2.png"
  43. ><img src="/blog_images/0.8.0/pumpa_upload-from_pumpa2.png"
  44. alt="Pumpa uploading image to MediaGoblin" /></a>
  45. </p>
  46. <p>
  47. And here's that same image, now uploaded to MediaGoblin!
  48. </p>
  49. <p class="blog_image">
  50. <a href="/blog_images/0.8.0/pumpa_upload-on_mediagoblin.png"
  51. ><img src="/blog_images/0.8.0/pumpa_upload-on_mediagoblin-scaled.png"
  52. alt="Image from Pumpa now on MediaGoblin!" /></a>
  53. </p>
  54. <p>
  55. In a nutshell, the client to server part of the API/federation
  56. equation is working. We are still working on server to server
  57. federation that will enable us to share comments, tagging and all the
  58. other things that can happen to your shared content on someone else's
  59. server that you may (or may not) want hear about.
  60. </p>
  61. <p>
  62. By the way, if you're using MediaGoblin with Apache (rather than Nginx
  63. or some other setup), you'll need to add "WSGIPassAuthorization On" to
  64. your config or the API won't work. You can look at
  65. <a href="https://wiki.mediagoblin.org/Deployment#Apache_2_Config_With_mod_wsgi">this
  66. wiki page</a>
  67. for reference.
  68. </p>
  69. <p>
  70. Speaking of updating and getting with the times, we are officially
  71. offering preliminary support for Python 3. Most of our features work
  72. without Python 2 installed, so welcome aboard futurists! As always, if
  73. you spot something we missed, we'd
  74. <a href="http://mediagoblin.org/pages/join.html">love to hear from you</a>
  75. via our bugtracker, mailing list or IRC channel.
  76. </p>
  77. <p>
  78. Also on the upgrade list for this release, GStreamer! We're now using
  79. version 1.0 which adds a nice new thumbnailer and includes much improved
  80. video transcoding support. If you didn't get thumbnails before, it wasn't
  81. you. We encourage you to try again and see if it works for you now!
  82. </p>
  83. <p class="blog_image">
  84. <a href="/blog_images/0.8.0/video_thumbs.png"
  85. ><img src="/blog_images/0.8.0/video_thumbs-scaled.png"
  86. alt="Video thumbs, rendering nicely" /></a>
  87. <br />
  88. <i>
  89. Thumbnails from <a href="http://venomslab.com/">Venom's Lab</a>,
  90. licensed under
  91. <a href="http://creativecommons.org/licenses/by/3.0/">CC
  92. BY-SA 3.0</a>
  93. </i>
  94. </p>
  95. <p>
  96. Obviously, the future demands cleaner packaging. Configure and make
  97. support is now the default... welcome to fewer steps for installing
  98. your MediaGoblin instance, which will be critical as we build packages
  99. for Fedora, Debian and any other distro that wants to help its users
  100. host the federated future of the web.
  101. </p>
  102. <p>
  103. We've also switched away from Transifex, which had become proprietary
  104. (boo!) to
  105. <a href="https://chapters.gnu.org/projects/mediagoblin/">an instance of</a>
  106. <a href="http://pootle.translatehouse.org/">Pootle</a> that
  107. many of our fellow GNU projects are now using for translations. If you've
  108. been looking for a fully free translation tool, Pootle may be just the
  109. thing you've been looking for!
  110. </p>
  111. <p>
  112. And finally, we fixed the footer. It is now forced to the bottom of page,
  113. instead of floating in the middle of short pages which everyone agrees was
  114. sub-optimal.
  115. </p>
  116. <p>
  117. Next up is server to server federation. This is what Jessica Tallon has
  118. been working on full-tilt -- thanks to everyone who pitched in on the
  119. <a href="http://mediagoblin.org/pages/campaign.html">MediaGoblin campaign</a>.
  120. (Though the campaign is over, you can still donate!)
  121. Both Chris and Jessica have been participating in the
  122. <a href="https://www.w3.org/wiki/Socialwg">W3C Social Working Group</a> on
  123. a federation standard. (As well as a general purpose client to server
  124. API... you better believe the increased client support coming out of
  125. this release is related!) The design is very closely related to the
  126. existing Pump API spec we've been using. You can read the
  127. <a href="https://w3c-social.github.io/activitypump/">current draft</a> of
  128. the standard here. We've got more news on the way, including on that
  129. federation front. Expect more news soon!</p>
  130. <p>
  131. Thanks to everyone who is helping us make the future of the web happen
  132. everywhere! This release wouldn't have happened without the help of
  133. these people: Alon Levy, Asheesh Laroia, Andrew Browning, Berker
  134. Peksag, Boris Bobrov, Christopher Allan Webber, Deb Nicholson, Ineiev,
  135. Jaakko Luttinen, Jakob Kramer, Jeremy Pope, Jessica Tallon, Jim
  136. Campbell, Laura Arjona, Meg Ford, Rodrigo Rodrigues da Silva, and
  137. Ben Sturmfels. You all rock!
  138. </p>
  139. <p>
  140. Want to put in your own help towards the future of federated, awesome
  141. media publishing? <a href="http://mediagoblin.org/pages/join.html">Join us!</a>
  142. Visit us in IRC (#mediagoblin on freenode.net) or sign up for regular
  143. updates on our
  144. <a href="http://lists.mediagoblin.org/listinfo/devel">mailing list</a>
  145. Got ideas or questions about our work? Email us at press AT
  146. mediagoblin DOT org -- we look forward to hearing from you!
  147. </p>
  148. </body>
  149. </html>