The fediverse has been buzzing with talk about end-to-end encryption. In this (quite long) article, I’ll try to explain what E2EE is, what some common approaches to it are in the instant messaging space, and what I think would be the best way to use it on the fediverse.

(Note: Pictures are just there to break up the boredom. A hotel bar.)

After long months of doing only bugfix and security releases, we are finally releasing the long-awaited 1.0 release. No more nines!

(Hey! Don’t know what Pleroma is? Check out this page!)

The first commit in Pleroma happened 2016, on October 26th. Now it’s a few years and months later, and we are doing our first stable release!

Are you still running develop? That’s so 2018.

In my last few posts I talked a bit about Pleroma. Since then, we had a lot of questions about what Pleroma is, how it is different from GNU Social and Mastodon, why you should use it and so on. This post will be an introduction to Pleroma, so read on if you are interested.

After some work, ActivityPub support will be merged into the develop branch of Pleroma in the next days.

This change will add the following user facing features:

• Support for Mastodon’s visibility suggestion settings, like private posts and direct messages.
• Slightly faster federation

Not too much for a few weeks of work. Anyway, here are my thoughts about the whole process.

In my free time, I develop a free software social network server called Pleroma (code). It is compatible with GNU Social, Mastodon, Friendica, and any other server that implements the OStatus protocol. Recently, there has been some buzz about a new protocol for federated social networking: ActivityPub. This protocol is now a W3C Recommendation, which means that it’s a kind of ‘standard’, if you care about that sort of thing. Here’s my opinion on it, and how it came to be where it is now.