Der US-Milliardär hatte bereits Bundeskanzler Scholz verhöhnt. Nun war das deutsche Staatsoberhaupt dran: Steinmeier sei ein antidemokratischer Tyrann, postete Musk.

Der US-Milliardär Elon Musk hat Bundespräsidenten Frank-Walter Steinmeier als "Tyrannen" beschimpft. Auf dem X-Account des Tesla-Chefs, der als enger Berater des designierten US-Präsidenten Donald Trump gilt, heißt es: "Steinmeier ist ein antidemokratischer Tyrann. Schande über ihn." Das Bundespräsidialamt sagte auf Nachfrage, man habe den Kommentar zur Kenntnis genommen, äußere sich aber nicht dazu.

Musk nimmt mit seinem Kommentar Bezug auf das Posting der AfD-nahen Influencerin Naomi Seibt, die Steinmeier attackierte, nachdem der Bundespräsident sich bei seiner Rede zur Auflösung des Bundestages gegen Einflussnahme von außen gewandt hatte. Dabei hatte das Staatsoberhaupt explizit auch die Plattform X genannt. Seibt unterstellte Steinmeier, er wolle das Ergebnis einer Wahl annullieren, wie es soeben in Rumänien geschehen sei.

[...]

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 see 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 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.12.tar.gz (sha256) and friendica-addons 2024.12.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.12 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.

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 know 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!

friendica-exporter

A prometheus exporter for getting some metrics of a Friendica server instance.

^Friendica

Tobias

2023-12-24 15:14:03

wordpress

We are very happy to announce the availability of the new stable release of Friendica “Yellow Archangel” 2023.12. Finally wrapping up the changes since May – the highlights of this release are

• the bluesky connector has been made bi-directional,
• moderation reports can now be send by users and reviewed by the node admins,
• user defined groups are now called Circles and forum accounts are now Group accounts, and last but not least
• users now have a better control over their network streams with the new Channels feature.

Note that the minimal PHP version for Friendica was raised to PHP 7.4 with this release. In addition please be aware that the IntlChar module of PHP is now required for installing Friendica.

For details, please the CHANGELOG file in the repository.

What is Friendica

Friendica is a decentralized 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.

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 2023.12 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-2023.12.tar.gz (sha256) and friendica-addons 2023.12.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-2023.12 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

Following the release of Friendica 2023.12 the following issues were reported:

• S3 addon unusable [13760]

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/2023/12/24/friendic…

GitHub - friendica/friendica: Friendica Communications Platform

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

^GitHub

I want to draw attention to an administrative process at the W3C Social Web Community Group (SocialCG), the standards group that manages ActivityPub and Activity Streams 2.0 and a number of other open social networking standards. The group is considering a new charter to define how decisions are made and how the members work together. This might seem like a minor process, but it’s actually part of a bigger deal for the Fediverse. To see why, you need to understand the structure of the W3C.

The W3C (World Wide Web Consortium) is the standards organization that specifies the Web platform, like HTML (kind of), CSS, and RDF. It also is the organization that standardized ActivityPub and AS2 in 2019. The W3C process requires a special kind of group, called a Working Group, to create official recommendations on the part of the organization. Working Groups can have members nominated by the W3C member organizations, as well as some Invited Experts.

The W3C has another structure, called a Community Group, that’s much looser. Anyone can join a community group, as long as they sign the Contributor License Agreement, which grants a copyright and patent license to the work they do with the group. Community Groups don’t produce formal recommendations in the W3C; they can produce Community Group Reports, which can be documents, software, or really anything.

So, the Social Web Working Group created and edited ActivityPub and AS2 back in the mid-2010s. The group had a charter that extended into 2018; it was extended to early 2019 so the work on ActivityPub could be finished. The working group was then disbanded. A new Community Group, the SocialCG, had been started in 2017. It took over the process of supporting new extensions to AP and AS2, as well as maintaining the errata for the two main documents. Importantly, it can’t make major changes to the documents themselves — that requires a working group.

The experience of developers and users over the last decade in using ActivityPub has pointed out some real needs for updates to the documents. The W3C staff have asked the SocialCG to draft a charter for a new working group that could make backwards-compatible changes to these documents — adding clarifications, and possibly including new features. This would be great for the specifications, great for the Social Web, and great for the Internet at large.

The problem is that there isn’t a clear relationship between the boundaries of the new working group and the boundaries of the community group. What input would members of the community group have in the editing of the updated ActivityPub documents? Especially given that W3C members tend to be more commercial and institutional than the mostly Open Source developers who work in the SocialCG, there is a concern that a new Social Web Working Group would prioritize the needs of corporate developers with lots of resources, at the expense of Open Source devs making code for small communities.

The answer we’ve landed on is to implement a stage process, in which new ideas are initiated and documented as Community Group Reports before the Working Group takes them up for possible inclusion the main recommendation documents — or becoming new recommendations on their own. This process has worked well in other Community Groups at W3C, and the W3C staff is really supportive of it.

One problem with this process for the SocialCG is that we never adopted rules for how we make decisions when we started the group. We agreed casually to use the same consensus-based mechanisms we’d used in the Social Web Working Group, but never put together an official charter for the group. This casual structure has worked well for a long time, but in order to set up this more formal staging process, we need to have a more formal decision-making process.

The good news is that the norm in the W3C, as in most Internet standards organization, is to use consensus-based decision-making. So, the new SocialCG proposed charter has a lot of casual consensus, too, as well as pretty open participation on a very peer-oriented basis. It’s about the minimum structure you need to have a long-running organization.

So, let me recap: we want updated, backwards-compatible versions of ActivityPub and Activity Streams 2.0 with more clarity and maybe even new features. In order to get those, we need a Working Group. In order to get that, we need to establish a stage process. And in order to adopt the stage process, we need to have a new CG charter. So: CG charter leads to stage process leads to WG leads to new specs leads to new features.

The Community Group intends to consider approving the new CG charter at its January 2025 meeting. So, people interested in ActivityPub, standardization, and group dynamics in general are invited to review the documents and submit GitHub issues or comment on existing issues. If you’re not already a member of the SocialCG, you can join in a just a few minutes. It’s also reasonable for non-members to comment or make suggestions.

This work is complicated, but it’s also fascinating, and it is an exciting part of putting ActivityPub on a solid footing for the future.

I'm writing this from my Piefed server because my Friendica server, my-place.social, can no longer view helpers@forum.friendi.ca. I get a 500 error. As far as I can tell, viewing all other groups and contacts works fine.

This problem may be related to the Wasabi outage from yesterday. I use Wasabi S3 for image storage, and they had a partial outage yesterday that caused obvious issues on the server, like blurred images. I say this because the exception may be image related.

This is the error in the friendica log:

2024-11-30T13:23:16Z app [ERROR]: ** Uncaught Exception TypeError: "Friendica\Object\Image::__construct(): Argument #1 ($data) must be of type string, null given, ** called in /var/www/html/src/Object/Image.php on line 781" at /var/www/html/src/Object/Image.php line 62 {"exception":"TypeError: Friendica\Object\Image::__construct(): Argument #1 ($data) must be of type string, null given, called in /var/www/html/src/Object/Image.php on line 781 and defined in /var/www/html/src/Object/Image.php:62\nStack trace:\n#0 /var/www/html/src/Object/Image.php(781): Friendica\Object\Image->__construct()\n#1 /var/www/html/src/Model/Post/Link.php(152): Friendica\Object\Image->getBlurHash()\n#2 /var/www/html/src/Model/Post/Link.php(79): Friendica\Model\Post\Link::fetchMimeType()\n#3 /var/www/html/src/Content/Text/BBCode.php(321): Friendica\Model\Post\Link::getByLink()\n#4 /var/www/html/src/Content/Text/BBCode.php(861): Friendica\Content\Text\BBCode::proxyUrl()\n#5 [internal function]: Friendica\Content\Text\BBCode::Friendica\Content\Text\{closure}()\n#6 /var/www/html/src/Content/Text/BBCode.php(851): preg_replace_callback()\n#7 /var/www/html/src/Content/Text/BBCode.php(1883): Friendica\Content\Text\BBCode::convertImages()\n#8 /var/www/html/src/Content/Text/BBCode.php(1389): Friendica\Content\Text\BBCode::convertImagesToHtml()\n#9 /var/www/html/src/Util/Strings.php(517): Friendica\Content\Text\BBCode::Friendica\Content\Text\{closure}()\n#10 /var/www/html/src/Content/Text/BBCode.php(2517): Friendica\Util\Strings::performWithEscapedBlocks()\n#11 /var/www/html/src/Content/Text/BBCode.php(1324): Friendica\Content\Text\BBCode::performWithEscapedTags()\n#12 /var/www/html/src/Util/Strings.php(517): Friendica\Content\Text\BBCode::Friendica\Content\Text\{closure}()\n#13 /var/www/html/src/Content/Text/BBCode.php(2517): Friendica\Util\Strings::performWithEscapedBlocks()\n#14 /var/www/html/src/Content/Text/BBCode.php(1323): Friendica\Content\Text\BBCode::performWithEscapedTags()\n#15 /var/www/html/src/Content/Text/BBCode.php(1283): Friendica\Content\Text\BBCode::convert()\n#16 /var/www/html/src/Model/Item.php(3340): Friendica\Content\Text\BBCode::convertForUriId()\n#17 /var/www/html/src/Model/Item.php(3471): Friendica\Model\Item::putInCache()\n#18 /var/www/html/src/Object/Post.php(464): Friendica\Model\Item::prepareBody()\n#19 /var/www/html/src/Object/Post.php(655): Friendica\Object\Post->getTemplateData()\n#20 /var/www/html/src/Object/Post.php(655): Friendica\Object\Post->getTemplateData()\n#21 /var/www/html/src/Object/Post.php(655): Friendica\Object\Post->getTemplateData()\n#22 /var/www/html/src/Object/Thread.php(204): Friendica\Object\Post->getTemplateData()\n#23 /var/www/html/src/Content/Conversation.php(680): Friendica\Object\Thread->getTemplateData()\n#24 /var/www/html/src/Content/Conversation.php(583): Friendica\Content\Conversation->getThreadList()\n#25 /var/www/html/src/Model/Contact.php(1725): Friendica\Content\Conversation->render()\n#26 /var/www/html/src/Module/Contact/Conversations.php(123): Friendica\Model\Contact::getThreadsFromId()\n#27 /var/www/html/src/BaseModule.php(250): Friendica\Module\Contact\Conversations->content()\n#28 /var/www/html/src/App.php(682): Friendica\BaseModule->run()\n#29 /var/www/html/index.php(46): Friendica\App->runFrontend()\n#30 {main}"} - {"file":null,"line":null,"function":null,"request-id":"674b11c1ce218","stack":"ErrorHandler::handleException (128), ErrorHandler::Friendica\Core\Logger\Handler\{closure}","uid":"caec99","process_id":9285}

I tried updating the contact information, unfollowing/following. I can't view it from any other account on the server. I assume the contact record in the database is corrupted.

I thought of playing with the .console archive function to archive the contact and see if I can follow it again to have the server build a new record, but stuff like this could have unintended consequences. So, I'm reaching out first.

Does anyone have advice on how to fix this?

The Social Web Foundation is pleased to announce the Social Web Devroom at FOSDEM 2025, and invite participants to submit proposals for talks for the event.

FOSDEM is an exciting free and open source software event in Brussels, Belgium that brings together thousands of enthusiasts from around the world. The event spans the weekend of February 1-2, 2025 and features discussion tracks (“devrooms”) for scores of different technology topics.

The Social Web Devroom will take place in the afternoon of Saturday, February 1.

Format

There will be two available talk formats:

• 25 minutes – for bigger projects, followed by 5 minutes of questions.
• 8 minutes – lightning talks on smaller or newer projects, in groups of 3, followed by 6 minutes of combined questions for the group.

Topics

The Social Web Devroom is open to talks all about the Social Web AKA the Fediverse, including:

• Implementations of the ActivityPub protocol or ActivityPub API
• Clients for ActivityPub-enabled software like Mastodon
• Supporting services for the Fediverse, like search or onboarding
• ActivityPub-related libraries, toolkits, and frameworks
• Tools, bots, platforms, and related topics

Important dates

• Submission open: 1 Nov 2024
• Submission deadline: 1 Dec 2024
• Acceptance notifications: 10 Dec 2024
• Final schedule announcement: 15 Dec 2024
• Devroom: 1 Feb 2025

Submissions

Submit talk proposals to pretalx.fosdem.org/fosdem-2025… . Select “Social Web” from the “Track” dropdown, and include the length of your talk (8/25) in the submission notes.

Code of Conduct

All attendees and speakers must be familiar with and agree to the FOSDEM Code of Conduct fosdem.org/2025/practical/cond….

Contact

Questions about topics, formats, or the Social Web in general should go to contact@socialwebfoundation.org.

The development cycle for the 2024.09 release enters the last stage before the stable release – today we have branched off the 2024.09 release candid branch. 2024.09-rc contains all the features of the stable release and is meant to test the new features, find some last rough edges and smooth out the path to the final stable release at the end of October. 2024.09 will be mostly a maintenance release fixing issues in various parts of Friendica. If you want to help out in testing, please checkout the new 2024.09-rc branch and report problems that you encounter.

The most notable changes in this release are:

• we now support HLS and further improved the compatibility with Bluesky,
• 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,
• Friendica is now REUSE compliant and supports FEP-67ff

What is Friendica

Friendica is a decentralized 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 use the 2024.09 RC Version of Friendica

If you want to help in the release process, you can checkout the 2024.09-rc branch from the git repositories.
git fetchgit checkout 2024.09-rcgit pullbin/composer.phar install --no-dev
Note that you only need to pull the composer dependencies in the core repository.

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 2024.09-rc phase is meant to identify and preferable resolve quirks and bugs that should not be in the 2024.09 release, but have slipped through so far. So if you switch your node to the 2024.09-rc version of Friendica, please let us know about rough edges you find, either at the issue tracker (github account required), in the support group or in the developers group.

Thanks a lot for helping with the release 🙂