We are very happy to announce the availability of the new stable release of Friendica “Yellow Archangel” 2024.08. In addition to several improvements and new features, this release contains several fixes for security issues reported by apexrabbit, Devilx86 and ponlayookm – Thank you for the reports! We strongly recommend all Friendica admins to update their installations to this stable release.

The highlights of Friendica 2024.08 are

• the usage of system resources and performance has been improved in various parts of Friendica,
• added monitoring endpoints for e.g. Zabbix and Grafana,
• added shortened display of links (default 30 characters, admins can define the length in the config file via the display_link_length)

Note that the minimal PHP version for Friendica was raised to PHP 7.4 with this release.

For details, please the CHANGELOG file in the repository.

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 Tumbler and BlueSky.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2022.12 release, please first update your Friendica instance to that version as it contained some breaking changes.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently.

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 2024.08 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 than the stable one, you need to fetch and 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

Due to problems with the build pipeline we cannot provide archive files at the moment that contain all dependencies as usual. We will update this documents as soon as possible.

Do not use the archive files provided by github as they do not contain the dependencies.

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 this update might run for days.

Known Issues

At the time of writing this, none

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 especially to all the new contributors to Friendica, and have fun!

friendi.ca/2024/08/17/friendic…

Tobias

2024-08-17 17:19:12

Friendica 2024.08 released

We are very happy to announce the availability of the new stable release of Friendica “Yellow Archangel” 2024.08. In addition to several improvements and new features, this release contains several fixes for security issues reported by apexrabbit, Devilx86 and ponlayookm – Thank you for the reports! We strongly recommend all Friendica admins to update their installations to this stable release.

The highlights of Friendica 2024.08 are

• the usage of system resources and performance has been improved in various parts of Friendica,
• added monitoring endpoints for e.g. Zabbix and Grafana,
• added shortened display of links (default 30 characters, admins can define the length in the config file via the display_link_length)

Note that the minimal PHP version for Friendica was raised to PHP 7.4 with this release.

For details, please the CHANGELOG file in the repository.

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 Tumbler and BlueSky.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2022.12 release, please first update your Friendica instance to that version as it contained some breaking changes.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently.

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 2024.08 release would be
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch than the stable one, you need to fetch and 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-2024.08.tar.gz (sha256) and friendica-addons 2024.08.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-2024.08 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 this update might run for days during which the site might not be accessible.

Known Issues

At the time of writing this, none

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 especially to all the new contributors to Friendica, and have fun!

GitHub - friendica/friendica: Friendica Communications Platform

Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.

^GitHub

Heute müssen wir Euch darüber informieren, dass wir uns von einigen unserer Services verabschieden.

Wir verabschieden uns von unseren Invidous und Piped Instanzen. Da Youtube sich immer wieder neue Möglichkeiten einfallen lässt alternative Frontends wie Invidious und Piped auszusperren ist uns der Aufwand jedes Mal das zu beheben einfach zu groß.
Hier findet ihr Alternative Invidious und Piped Instanzen.
Für unsere Friendica Instanzen werden wir auch weiterhin (solange es möglich ist) serverseitig funktionierende Invidious und Piped Instanzen in den jeweiligen Addons einstellen.

Als Zweites verabschieden wir uns von unserem Threads Relay/Feed.
Wir mussten leider zu viel Zeit aufwenden mit den Beschwerden bezüglich des Accounts aufbringen. Bedauerlicherweise sind einige User des Fediverse nicht in der Lage, die Beschreibung des Relay lesen und waren immer wieder der Meinung, das Relay wäre nur dafür da die Daten an Threads zu liefern. Es ist auf die Dauer einfach zu anstrengend den Usern jedes Mal zu erklären wie das Fediverse überhaupt funktioniert und das sie doch bitte erstmal sich die Beschreibung durchlesen sollen, statt sofort sich zu beschweren.

Leider mussten wir in den letzten Wochen die Blockliste für Server und Person erweitern. Zu den Personen/Accounts gehen wir hier nicht weiter ein, es sein nur so viel gesagt das wir damit evtl. rechtliche Konsequenzen für unsere Instanz vorbeugen.

Zu den blockierten Servern können wir sagen, dass es sich hier bei in letzter Zeit vor allem um Datensammler handelt.
Da wäre als Erstes zu nennen maven.ly / *.heymaven.com, die mit den Post und Daten aus dem Fediverse sammelten und sie in ihre eigene Social-Networking-App einfügen ohne das dabei auf die Quellen der Beiträge verlinkt wird. Zusätzlich wurde mit den Daten auch noch die Maven eigene KI trainiert . Nach einigen Protesten aus dem Fediverse hat Maven angeblich alle gesammelten Daten wieder gelöscht. Wir werden aber weiterhin ihre Server blockieren.

Als Zweites wäre da awakari.com die ebenfalls die Daten aus dem Fedivers sammeln, um damit ihr Suchmaschine zu betreiben. Sie geben zwar vor Kostenlos zu sein was aber nicht stimmt, der Zugang zu ihrer API nur 30 Tage kostenlos ist. Nach dem sich auch hier einige User aus dem Fediverse beschwert haben wurde der Service, der die Daten sammelt activitypub.awakari.com vom Netz genommen.
Wir mussten heute aber feststellen, dass der Service wieder aktiv ist, nur unter einer anderen Domain activitypub.awakari.app also haben wir diese auch gesperrt.

Die anderen Sperren betreffen nur Server, die das AP Protokoll noch nicht richtig implementiert habe und zu häufig in den Logs auftauchten oder zu hohe Last auf unseren Server verursachten.