Friendica 2022.05 Release Candidate Available

We are happy to announce the availability of the release candidate for the upcoming Friendica 2022.05 release, to focus on fixing existing bugs and smoothing out of rough edges..

Since the release in March

  • a regression was fixed that could lead to mentioning all accounts that received a non-public posting;
  • the Dansk (da_DK) translation was added to the repository;
  • the API was enhanced;
  • there is an experimental setting to allow postings in the past (#11411);
  • an addon was added which allows the usage of S3 services for the file storage back-end.

If you are running a custom addon, please note that the 2022.05 release does a breaking change removing the hooks settings_form and settings_post. Your addon should use the addon_settings hook instead.

What is Friendica

Friendica is a decentralised communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.

How to use the 2022.05 RC Version of Friendica

If you want to help in the relase process, you can checkout the 2022.05-rc branch from the git repositories (core and addons).

git fetch
git checkout 2022.05-rc
git pull
bin/composer.phar install --no-dev

Note that you only need to pull the composer dependencies in the core repository. Alternatively you may download the tar archives from files.friendi.ca.

Wordcloud generated from the commit messages of the 2022.05-rc
This cloud show the words mostly used in the commit messages for the 2022.05 release of Friendica.

Should the upgrade process of the database get stuck

If you encounter this, please initiate the DB update manually from the command line by running the script

./bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.

What to do with Quirks

The 2022.05-rc phase is meant to identify and preferable resolve quirks and bugs that should not be in the 2022.05 release. So if you switch your node to the 2022.05-rc version of Friendica, please let us know about rough edges you find, either at the issue tracker (github account required), in the support forum or in the development forum.

Thanks a lot for helping with the release 🙂


Friendica 2022.02 released

We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2022.02. This is the first release containing the work of the Arabic translation team – thanks a lot for your work! Other highlights of the release are

  • The video tab was removed from the profile, in exchange Friendica profiles now have a media tab, showing postings that contain more then just text.
  • An addon to allow usage of WebDAV for the storage back-end has been added.

For a detailed overview of the changes, please have a look at the CHANGELOG.

How to Update

Please note: With this release the minimal PHP version that Friendica requires is PHP 7.3 and later. Known issues with PHP 8 are collected in the issue tracker at github, though Friendica seems to work fine with PHP 8 now.

Deprecation Warning: Some old and unmaintained addons have been removed from the core addon repository. These addons are: blogger, buffer, jappixmini, notimeline, xmpp.

Updating from old Friendica versions

If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2021.09 to the 2021.12 release candidate, so hopefully you will have a smooth transition.

Using Git

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well. So, assuming that you are on the stable branch, the commands to update your installation to the 2022.02 release would be

cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull

If you want to use a different branch then the stable one, you need to checkout the branch before your perform the git pull.

Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2022.02.tar.gz (sha256) and friendica-addons 2022.02.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2022.02 archive), so you don’t have to worry about them.

Post Update Tasks

The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script

bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues

  • After the update please make sure that the directory vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer is write-able by your web server.

How to Contribute

If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!


Friendica 2021.12 Release Candidate available

We are happy to announce the availability of the release candidate branch of Friendica 2021.12, which was just branched off the current development branch, to focus on fixing existing bugs and smoothing out of rough edges. If you want to help in this process, you can checkout the 2021.21-rc branch from the git repositories (core and addons).

git fetch
git checkout 2021.12-rc
git pull
bin/composer.phar install --no-dev

Note that you only need to pull the composer dependencies in the core repository. Alternatively you may download the tar archives from files.friendi.ca

Most work has been spend to the internal code of Friendica, so there may be problems lurking underneath the surface. We have deprecated a number of unsupported addons, added Arabic translation and a new WebDAV storage backend. For a full list of changes, please have a look into the CHANGELOG for this release.

Thanks for testing the new release! If you find any problems, please report them either at the issue tracker on github or in the support forum.

Should the upgrade process of the database get stuck

If you encounter this, please initiate the DB update manually from the command line by running the script

./bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.


Friendica 2021.09 released

The summer sprint is over and we are happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2021.09. It contains more then 160 pull requests from seven contributors and updates to several language packages from the translation teams.

For a detailed overview of the changes, please have a look at the CHANGELOG. The highlights of the release are

How to Update

Please note: With the release of 2021.09 Friendica does require at least PHP version 7.2 or above. Known issues with PHP 8 are collected in the issue tracker at github.

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2021.07 to the 2021.09 release candidate, so hopefully you will have a smooth transition.

Using Git

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well. So, assuming that you are on the stable branch, the commands to update your installation to the 2021.09 release would be

cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull

If you want to use a different branch then the stable one, you need to checkout the branch before your perform the git pull.

Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2021.09.tar.gz (sha256) and friendica-addons 2021.09.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.09 archive), so you don’t have to worry about them.

Post Update Tasks

The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script

bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues

Update Mon Sept 27th: If you are using MySQL (not MariaDB) the automatic DB structure updates may fail see issue 10768.

Update Mon Oct 4th / 7th: Solved for the full archive downloadable from files.friendi.ca. A node-specific config/local.config.php file has been inadvertently included in the full archive. Please make sure you either remove it or overwrite it with your own when you perform the update as described above.

How to Contribute

If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!


Friendica Hackathon 2021

Following our tradition of annual Hackathons we will gather together at the first weekend in October (Friday 1st to Sunday 3rd). As it was the case last year, the 2021 Hackathon will be online again. Further information on how to join will be posted in this conversation in the developers Forum.

If you want to join the Hackathon, please do so! No programming skills required for discussions and feedback is welcome.


Friendica 2021.09 Release Candidate available

We are pleased to announce that we branched off the 2021.09 release candidate from the current development branch in preparation to the upcoming release. Over the summer scheduled postings were implemented and the admin panels look into the log file got some refurbishment. For a more detailed list of changes, please see pull request 10621.

If you want to help to hunt down rough edges and bugs ahead of the release in June, now is the perfect moment to switch from the stable or development branch to the freshly created 2021.09-rc branch. To do so please run

git fetch
git checkout 2021.09-rc
git pull
bin/composer.phar install --no-dev

in the root directory of your Friendica and the addon directory. The command to update the dependencies (composer) is only necessary in the Friendica root directory.

Thanks for testing the new release! If you find any problems, please report them either at the issue tracker on github or in the support forum.

Please note that the minimal PHP version that Friendica is requiring with this release will be PHP 7.2.

Should the DB update process get stuck

If you encounter this, please initiate the DB update manually from the command line by running the script

./bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.


Friendica 2021.07 released

We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2021.07. This release contains 219 pull requests from ten contributors and the work of the translation teams. While fixing some problems identified, we have added some nice features

  • support for right-to-left languages was added,
  • the API was expanded to have Mastodon compatible endpoints and
  • an addon was added to support SAML services like keycloak for login.

For a detailed overview of the changes, please have a look at the CHANGELOG.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version.

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2021.04 to the 2021.06 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well.

cd friendica
git fetch
git checkout BRANCH
git pull
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH
git pull

Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.07.tar.gz and friendica-addons 2021.07.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.07 archive), so you don’t have to worry about them.

Post Update Tasks

The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script

bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

How to Contribute

If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!


Friendica 2021.06 first Release Candidate available

Back to the schedule, we are glad to announce the availability of the initial release candidate of the Friendica 2021.06 release. During the past month. the focus of the work was on enhancing the Mastodon compatible API and adding support for RTL languages to the web interface as well as new addons to use SAML services like Keycloak for login.

If you want to help to hunt down rough edges and bugs ahead of the release in June, now is the perfect moment to switch from the stable or development branch to the freshly created 2021.06-rc branch. To do so please run

git fetch
git checkout 2021.06-rc
git pull
bin/composer.phar install --no-dev

in the root directory of your Friendica and the addon directory. The command to update the dependencies (composer) is only necessary in the Friendica root directory.

Thanks for testing the new release! If you find any problems, please report them either at the issue tracker on github or in the support forum.

Please be aware the since the last stable release the database structure was changed, after the switch to the RC branch your server will need some time to perform these changes.

Known Problems

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

Should the DB update process get stuck

If you encounter this, please initiate the DB update manually from the command line by running the script

./bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.


Friendica 2021.04 Released

With a slight delay, we are happy to announce the availability of the new stable version of the Friendica communications server: Friendica Siberian Iris 2021.04.

Photo of a Siberian Iris by Kristine Tanne
Photo of a Siberian Iris by Kristine Tanne

This is mostly a bug fixing release, stabilizing the new features we introduced over the Red Hot Poker cycle, but also finishing some long time restructuring work on the database structure, which results in a greatly improved performance of Friendica. This release bundles 196 pull requests fixing 53 filed issues. For a detailed overview of the changes, please have a look at the CHANGELOG, some of the highlights

  • The reworking of how items are stored in the database was finished, which results in a great improvement of Friendicas performance. Please note that the needed upgrade might take hours depending of your database size.
  • Admins can now block tags from the trending tag widget.
  • We removed the Flash based addons from the addon repository.

And a heads up for developers, we moved some endpoints in the API to normalize the endpoints.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version.

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be necessary.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. Despite the long duration of the database upgrade we had no reports of unaddressed problems during the RC phase.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Important: We removed the master branch and are using the stable branch instead.

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well.

cd friendica
git fetch
git checkout stable
git pull
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout stable
git pull

Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.04.tar.gz and friendica-addons 2021.04.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.01 archive), so you don’t have to worry about them.

Post Update Tasks

The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script

bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

How to Contribute

If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!