CINXE.COM

<?xml version="1.0"?> <!DOCTYPE html> <html xmlns:xi="http://www.w3.org/2001/XInclude" xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <meta charset="utf-8"/><meta http-equiv="x-ua-compatible" content="ie=edge"/><meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no, maximum-scale=5.0"/><meta content="website" property="og:type"/><meta content="summary" property="twitter:card"/><meta content="/images/ogp.png" property="og:image"/><meta content="724" property="og:image:width"/><meta content="724" property="og:image:height"/><link rel="stylesheet" href="/stylesheets/normalize.css"/><link rel="stylesheet" href="/stylesheets/default.css"/><link rel="apple-touch-icon" sizes="180x180" href="/images/apple-touch-icon.png"/><link rel="icon" type="image/png" sizes="32x32" href="/images/pleroma_logo_vector_bg_32.png"/> <title>Pleroma Blog</title> <link rel="stylesheet" href="/stylesheets/blog.css"/> </head> <body> <div xmlns:xi="http://www.w3.org/2001/XInclude" class="navbar-header-container"> <div class="navbar-header"> <div class="navbar-brand"> <a href="/"> <div class="navbar-brand-logo"> </div> </a> </div> <div class="desktop-menu"> <a href="https://docs-develop.pleroma.social/"><div class="navbar-link"><i class="icon-book"> </i>Documentation</div></a><a href="https://git.pleroma.social/"><div class="navbar-link"><i class="icon-code"> </i>Source</div></a><a href="https://api.pleroma.social/"><div class="navbar-link"><i class="icon-plug"> </i>API</div></a><a href="/blog/"><div class="navbar-link"><i class="icon-newspaper"> </i>Blog</div></a><a href="/announcements/"><div class="navbar-link"><i class="icon-megaphone"> </i>News</div></a><a href="https://liberapay.com/Pleroma-euro/"><div class="navbar-link"><i class="navbar-liberapay-logo"> </i>Donation</div></a> </div> <button id="menu-button" class="hamburger-menu nojs-menu" type="button"> <i class="icon-menu"> </i> <div id="menu-content" class="hamburger-content"> <a href="https://docs-develop.pleroma.social/"><div class="navbar-link"><i class="icon-book"> </i>Documentation</div></a><a href="https://git.pleroma.social/"><div class="navbar-link"><i class="icon-code"> </i>Source</div></a><a href="https://api.pleroma.social/"><div class="navbar-link"><i class="icon-plug"> </i>API</div></a><a href="/blog/"><div class="navbar-link"><i class="icon-newspaper"> </i>Blog</div></a><a href="/announcements/"><div class="navbar-link"><i class="icon-megaphone"> </i>News</div></a><a href="https://liberapay.com/Pleroma-euro/"><div class="navbar-link"><i class="navbar-liberapay-logo"> </i>Donation</div></a> </div> </button> </div> <script src="/scripts/navbar.js"> </script> </div> <article class="article-list"> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2023/10/16/nlnet-grant"><time>2023-10-16 15:27 UTC+2</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2023/10/16/nlnet-grant"><h2>We got a grant from NLNet!</h2></a> <div class="article-short-summary-content"> <p>Hi, HJ here. After spring’s disaster and previous years of mismanagement and never-ending drama some folks in pleroma-dev have been pretty demotivated and burned out. Having pleroma as a side “weekend warrior” kind of deal doesn’t help it either, as most of us have jobs/schools and other stuff to do and people would rather spend weekend relaxing. not to mention, I personally would really love working on Pleroma fulltime, but alas it doesn’t pay bills. After seeing a whole bunch of fediverse projects on NLnet I thought “why the heck not” and with the rest of dev community’s blessing, send the application. Several months and bunch of paperwork later we got approved.</p> <p>And here it is: <a href="https://nlnet.nl/project/Pleroma/">https://nlnet.nl/project/Pleroma/</a></p> <p>Since we have somewhat a history of being not-entirely-transparent about being financed by someone let’s rectify this right now, in a bit of a QnA format.</p> <p><strong>Q:</strong> Is this another (hostile) takeover?<br/> <strong>A:</strong> No. At least I hope it doesn’t come as such. I just want people to be able to spend more time working on project. I don’t intend on telling people what to do and project direction is really up to community’s decision. </p> <p><strong>Q:</strong> How much?<br/> <strong>A:</strong> Around 30k€ for a year. </p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2021/01/13/the-big-pleroma-and-fediverse-faq"><time>2021-01-13 19:35 UTC</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2021/01/13/the-big-pleroma-and-fediverse-faq"><h2>The Big Pleroma and Fediverse FAQ Part 1 - Beginner Questions</h2></a> <div class="article-short-summary-content"> <p>Recent events surrounding social media have made many people think about leaving the currently dominant platforms. If you are looking for alternatives, you’ll inevitably come across the term ‘Fediverse’. But what is the Fediverse and why should you use it?</p> <p>In this first in a series of FAQs, I’ll try to answer questions that a total beginner might have. In later installments, I’ll answer more questions about the technical details and about Pleroma specifics.</p> <p>I hope this will help you along on your way to the Fediverse!</p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2020/08/28/releasing-pleroma-2-1-0"><time>2020-08-28 1:00 UTC</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2020/08/28/releasing-pleroma-2-1-0"><h2>Releasing Pleroma 2.1.0</h2></a> <div class="article-short-summary-content"> <p><img src="/images/pleroma_tan_2.1_cofe.png" alt=""/> </p> <p>Half a year after Pleroma 2.0, today we are releasing our next big version, Pleroma 2.1. Doesn’t sound like that much more, but it’s full of new features and fixes! Keep reading on to find out what we baked for you.</p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2020/03/08/releasing-pleroma-2-0-0"><time>2020-03-08 10:52 UTC</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2020/03/08/releasing-pleroma-2-0-0"><h2>Releasing Pleroma 2.0.0</h2></a> <div class="article-short-summary-content"> <p><img src="/images/pleroma_tan_2.0_nac.jpg" alt=""/> </p> <p>Long-awaited and finally ready, just in time for <del>FOSDEM</del> International Women’s Day, Pleroma 2.0.0 is here! There have been a lot of changes, including breaking ones, so let me give you a quick tour of this release. </p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2019/06/28/pleroma-1.0.0"><time>2019-06-28T14:37:36+02:00</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2019/06/28/pleroma-1.0.0"><h2>Pleroma 1.0.0</h2></a> <div class="article-short-summary-content"> <p><em>Note: this has originally been posted at <a href="https://blog.soykaf.com/post/pleroma-1.0/">https://blog.soykaf.com/post/pleroma-1.0/</a></em> </p> <p>After long months of doing only bugfix and security releases, we are finally releasing the long-awaited 1.0 release. No more nines!</p> <p><img src="/images/pleroma_1.png" alt=""/></p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2019/04/01/bbs-support"><time>2019-04-01T04:01:00+02:00</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2019/04/01/bbs-support"><h2>Fighting the Bloat! SSH Support in Pleroma</h2></a> <div class="article-short-summary-content"> <p>Pretty much one year ago, we started fighting the typical Web 4.0 Javascript bloat by adding <a href="/blog/2018/04/01/gopher/">Gopher support</a>. After a wildly successful <a href="/blog/2019/02/22/pleroma-0-9-9/">0.999 release</a>, we heard your calls for more debloating. The biggest complaint with the gopher support was the inability to post. So today, we’re taking it a step further: Making Pleroma a BBS.</p> <p><img src="/images/pleroma-ssh-help.png" alt=""/></p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2019/02/22/pleroma-0.9.9"><time>2019-02-22T13:58:34+01:00</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2019/02/22/pleroma-0.9.9"><h2>Pleroma's First Release! 0.9.9</h2></a> <div class="article-short-summary-content"> <p>The <a href="https://git.pleroma.social/pleroma/pleroma-fe/tree/191c02af1ebfc7e6c53dc88d97c4e3ca23fbea8b">first commit</a> in Pleroma happened 2016, on October 26th. Now it’s a few years and months later, and we are doing our first stable release!</p> <p>Are you still running <code>develop</code>? That’s so 2018.</p> <p><img src="/images/0.9.9.screenshot.png" alt=""/></p> </div> </div> </div> <div class="article-short"> <div class="article-meta article-short-date"> <a href="/blog/2018/04/01/gopher"><time>2018-04-01T04:01:00+02:00</time></a> </div> <div class="article-short-summary"> <a class="article-short-title" href="/blog/2018/04/01/gopher"><h2>Gopher Support in Pleroma</h2></a> <div class="article-short-summary-content"> <p><em>Note: this has originally been posted at <a href="https://blog.soykaf.com/post/gopher-support-in-pleroma/">https://blog.soykaf.com/post/gopher-support-in-pleroma/</a></em> </p> <p>As you may already know, <a href="/">Pleroma</a> is high-performance and low-resource fediverse server mean to run even on small devices like a Raspberry Pi.</p> <p>Still, there is one part of Pleroma that is wasteful to the extreme…</p> <p><img src="/images/no-js.png" alt=""/></p> <p>It’s true! Pleroma’s mother allowed it to have TWO frontends, but both are resource-hogging Javascript monstrosities. If you don’t have a ‘modern’ browser that turns your PC into a heater, you won’t be able to see any posts!</p> <p>So where did we go wrong? I think the problem goes way back. We made a deal with the Devil when we accepted free-form HTML into our systems. The best solution is to not make this mistake anymore, and go back to the future to a better alternative.</p> <p>And that’s why, today, I’m announcing <a href="https://en.wikipedia.org/wiki/Gopher_(protocol)">Gopher</a> support for Pleroma!</p> </div> </div> </div> </article> <footer> <div class="footer"> <div class="footer-legal"> <a rel="license" href="https://creativecommons.org/licenses/by/4.0/">CC-BY 4.0</a> </div> <div class="footer-social-icons"> <a class="footer-rss-link" rel="alternate" type="application/rss+xml" href="/blog/feed.xml"> <i class="icon-rss"> </i> All Posts </a> </div> </div> </footer> </body> </html>