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 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โฆ
Poliverso - notizie dal Fediverso โ
in reply to Poliverso - notizie dal Fediverso โ • •Fediverse reshared this.
Ruud
in reply to Poliverso - notizie dal Fediverso โ • • •like this
Poliverso - notizie dal Fediverso โ likes this.
Poliverso - notizie dal Fediverso โ
in reply to Ruud • •like this
๐ป๐๐๐๐ ๐ฆ๐ง๐ป๐ป๐ likes this.
Fediverse reshared this.
Snot Flickerman
in reply to Poliverso - notizie dal Fediverso โ • • •like this
๐ป๐๐๐๐ ๐ฆ๐ง๐ป๐ป๐ likes this.
Poliverso - notizie dal Fediverso โ
in reply to Snot Flickerman • •Fediverse reshared this.
jordanlund
in reply to Poliverso - notizie dal Fediverso โ • • •like this
Poliverso - notizie dal Fediverso โ likes this.
Poliverso - notizie dal Fediverso โ
in reply to jordanlund • •Fediverse reshared this.
jelloeater85
in reply to jordanlund • • •lambalicious
in reply to Poliverso - notizie dal Fediverso โ • • •like this
Poliverso - notizie dal Fediverso โ likes this.
yessikg
in reply to Poliverso - notizie dal Fediverso โ • • •Poliverso - notizie dal Fediverso โ
in reply to yessikg • •@yessikg I understand that this bug might seem like a deliberately hostile action against the threadverse, but the reality is that ActivityPub is objectively a shithole ๐คฃ and with every good step forward, there is the risk of stepping on a shit!
These problems could simply arise from the fact that Mastodon is starting to really work on the management of Activitypub groups. It is therefore appropriate to report any incompatibilities to the Mastodon staff, so that they can correct their roadmap
Fediverse reshared this.
kopper [they/them]
in reply to Poliverso - notizie dal Fediverso โ • • •from what i can tell (from the work in progress pull request) mastodons group implementation explicitly does not aim for compatibility with lemmy
other than that, i agree on activitypub being crap in terms of making interoperability easy
like this
Poliverso - notizie dal Fediverso โ likes this.
reshared this
Poliverso - notizie dal Fediverso โ e ๐ป๐๐๐๐ ๐ฆ๐ง๐ป๐ป๐ reshared this.
Poliverso - notizie dal Fediverso โ
in reply to kopper [they/them] • •@kopper [they/them] rightly mastodon cannot and should not aim for full compatibility with Lemmy and Piefed.
In fact, Lemmy has some unique features (such as the intentionally limited management of crossposting) that cannot be managed.
However, it would be appropriate and above all ethical, for Mastodon groups to be compatible with Friendica groups, Gup groups and Mbin magazines.
This would allow mastodon users to continue using the Activity pub groups of other platforms, including Lemmy.
I remember in fact that even WordPress (which at the moment, represents the most important novelty of the Fediverse) is perfectly able to publish on the Lemmy communities and on the Friendica groups!
like this
๐ป๐๐๐๐ ๐ฆ๐ง๐ป๐ป๐ likes this.
reshared this
Fediverse, ๐ป๐๐๐๐ ๐ฆ๐ง๐ป๐ป๐ e Nelfaneor reshared this.
kopper [they/them]
in reply to Poliverso - notizie dal Fediverso โ • • •like this
Poliverso - notizie dal Fediverso โ likes this.
reshared this
Poliverso - notizie dal Fediverso โ reshared this.
Jupiter Rowland
in reply to Poliverso - notizie dal Fediverso โ • • •And re-invent the wheel once more, preferably in a proprietary way that's as incompatible with the rest of the Fediverse as possible but sold to the Mastodon users as the Fediverse gold standard.
FTFY
Poliverso - notizie dal Fediverso โ likes this.
Poliverso - notizie dal Fediverso โ
in reply to Jupiter Rowland • •@Jupiter Rowland Unfortunately your acid comments don't seem too far from reality... ๐ ๐ ๐คฃ
But for now, I'll pretend I didn't hear them ๐
Poliverso - notizie dal Fediverso โ
Unknown parent • •Fediverse reshared this.