We are very happy to announce the availability of the new stable release of Friendica “Interrupted Fern” 2024.12. In addition to several improvements and new features, this release contains the fix for the broken installation wizard.

The highlights of Friendica 2024.12 are

• added exporter for prometheus,
• we dropped the support of OStatus (the predecessor of ActivityPub) after evaluating the amount of active servers/contacts that are still only using this protocol, and deprecated the fancybox addon
• Friendica is now REUSE compliant and supports FEP-67ff

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

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2023.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.12 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 unforseen changes in the CI not possible at the moment.

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 with 2024.12

But the development branch is currently rather unstable and should be used with caution as the development diverged far (for Friendica terms) from the now stable branch. We will let our very valued ALPHA testers when the dev team things that the development branch is stable enough again.

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/2025/01/01/friendic…

@jrossstocholm ​hi 😊 not...bonfire community is in the roadmap but we are not yet working on federated group as of now

Is there a public test instance for Bonfire Community?

#bonfire #bonfirecommunity

Is this Activity #trending?

Of the many A/C units in the world, mine is perfectly functional. :functional_ac:

"Whereof one cannot speak, thereof one must be silent."
Tractatus Logico-Philosophicus (1922)

Books by udwig Wittgenstein at PG:
https://www.gutenberg.org/ebooks/author/1861

~Ludwig Wittgenstein (26 April 1889 – 29 April 1951)

#books #literature #philosophy

@jrossstocholm @coyote @Ianp5a @gilles @ivan Sort of yeah! If you're familiar with Linux you could also compare bonfire flavours to Linux distributions. They may share a lot of the same software but make different choices about what's included, the default configs, etc. Also some flavours are created/maintained by us and some will be governed autonomously by other groups...​

@coyote @Ianp5a @mayel @gilles @ivan I am trying really hard to understand bonfire 😊.

When you say that "Bonfire community" will have groups - does that mean that it will be a different version of Bonfire - and different from "Bonfire social"?

So, for comparisons to #bigtech:

Bonfire Social --> Twitter (micro-blogging)
Bonfire Community --> Facebook​

I am in no way saying that it is a bad thing, but just to compare, pixelfed is the brand name of the platform where users can chose where to sign up. But it's the same app. But bonfire will more likely be a "powered by bonfire" where whatever brand name will be on top and bonfire will be the underlying infrastructure/core?

A bit like PPBoard was back in the day 😊

https://sourceforge.net/projects/pbboard/

Hi all, I'm interested in enabling Drupal websites to be able to post to bonfire social instances. I have already done this for Mastodon, and I found this issue about compatibility with the Mastodon API: github.com/bonfire-networks/...

I see that there is already a checkmark next to posts in there. I am looking to test if my mastodon Drupal module already works for posting to bonfire via the API. Mastodon provides an interface for administering api access for your applications, and generates client secrets, keys, and access tokens. I am curious about whether this is intended to be core functionality or dependent on an extension, and looking for comments about when this might be possible or how to do it if it already is. Thanks! Looking forward to playing around more with bonfire and following its growth.

Test?