Skip to main content


!Friendica Support
Is there a facility to report posts/accounts that violate rules? I can't find any option to do this on a post or an account. I looked in the official Wiki and found no clues either.
in reply to David - Forking Mad

I do not have that option. Screen shot below shows what I see for your post. If I try other random posts, I do get the top part...Add tag, etc. But never and ignore ... server or Report Post option at the bottom
in reply to David - Forking Mad

I checked your instance and it's running Friendica 2023.05. Moderation was added in latest release.

https://friendi.ca/2023/12/24/friendica-2023-12-released/


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!

https://friendi.ca/2023/12/24/friendica-2023-12-released/



(Nitter addon enabled: Twitter links via https://nitter.poast.org)

reshared this

in reply to David - Forking Mad

Interesting. I'm surprised moderation is new.
We did try to install 2023.12 from new but after repeated failures we gave up. We then used Yunohost, which I would have preferred not to. Its latest install build is 2023.05. i m not sure if we can now do an upgrade outwith the Yunohost environment
in reply to David - Forking Mad

@David - Forking Mad I'm running an instance here on develop branch. Do you still have the error messages from 2023.12 release? If you like you can share them here people here can look over it. And did you run the all-famous ./bin/composer.phar install --no-dev command? Or do you have a bundle with fully populated vendor directory? I'm just guessing here at that maybe that directory isn't populated.

Friendica Support reshared this.

in reply to David - Forking Mad

It might be worth us giving a new install an attempt again. I'd rather not be on Yunohost for this version reason. We got to a point where visiting the website wanted to go to the install folder but there was no folder or redirect working.
in reply to David - Forking Mad

@David - Forking Mad Ah, that might (remote, distant diagnose is always a bad idea) mean, that mod_rewrite isn't active? I might have to try it myself here. And 2024.03 is on it's way.

Friendica Support reshared this.

in reply to David - Forking Mad

Hi @Roland Häder, I did check that mod_rewrite was active and that .htaccess was a copy of the sample.

Friendica Support reshared this.

in reply to David - Forking Mad

If I reinstall, using the same domain name, will this screw up anything on the fediverse as I assume the new install will have a new key/ID.
Happy to drop all the user data as we're only testing at the moment

Friendica Support reshared this.

in reply to David - Forking Mad

@David - Forking Mad Yes, a new install always comes with new cryptographic keys. But of course you an upgrade an existing installation. But make backup of both files and database.

Friendica Support reshared this.

in reply to David - Forking Mad

@Roland Häder I'm not sure I can upgrade as the current was built using a Yunohost build, and they are on 2023.05. I doubt it allows the standard upgrade feature.

So I think I have two options:

Install a new 2023.05 (using the git repository) and restore my database. And then upgrade to 2023.12.
OR
install a brand new 2023.12 and NOT restore my data as I would assume the DB has a slightly different structure.

Friendica Support reshared this.

in reply to David - Forking Mad

@David - Forking Mad Then I would go with first option. The 2nd one will require you to give up your domain (you need an other host name). Or some tricky copy-paste of the keys but that might not work. So best is to backup your 2023.05 database, uninstall yunohost, install 2023.12 including updated addons, restore database dump and run the usual update steps.

From my script at https://f.haeder.net/deploy.sh these are the database upgrade steps to run:

echo "$0: db update ..."
./bin/console dbstructure update || exit 255
echo "$0: post-update ..."
./bin/console postupdate || exit 255
echo "$0: db drop ..."
./bin/console dbstructure drop -e || exit 255

Friendica Support reshared this.

in reply to Roland Häder

@David - Forking Mad
You might consider to create a subdomain and a new friendica instalation.
That way you can leave the old one as is and use it and start with the new one from scratch.

Friendica Support reshared this.

in reply to utopiArte

@utopiArte @David - Forking Mad Yes, that is always an option. The downside here is that a sub-domain is now in front of your domain. But if that's fine with you, no objection. :-)

Friendica Support reshared this.

in reply to utopiArte

I did think of that @utopiArte but i'd like to use the main domain ultimately. I might do a sub-domain test as I really struggled to get 2023.12 installed. If I can get it up on the sub I will have figured out the issues and can install on the top domain

Friendica Support reshared this.

in reply to David - Forking Mad

@David - Forking Mad @utopiArte Try beta.talkbox.social with closed registration where you can try newer versions out before installing them on your main domain.

Friendica Support reshared this.

in reply to David - Forking Mad

I guess you already have all the info you need at hand, this is an install instruction for VPS in progress (lot's of spoilers).

Friendica Support reshared this.

in reply to David - Forking Mad

Thanks @Roland Häder I will attempt a new install of 2023.12 in the morning and see how I get on.

Friendica Support reshared this.

in reply to David - Forking Mad

I know you are all sitting on the edge of your seat waiting for an update on my move/upgrade. 😆

I can report that it appears to have been a success. I built a brand new 2023.12, which I managed to get fully installed. I then cleared the DB and recovered my DB from 2023.05 and ran the DB update scripts mentioned by @Roland Häder

I'm up, and live, on 2023.12. I really appreciate everyone's help on this.

My Worker queue is very busy. 999 apparently. Full of "Add Contact" commands. I will just leave it to run.🤷‍♂️

I did setup a cron job for worker.php. I do however notice when I look at the running processes that worker.php has a --no_cron at the end, is that normal?

in reply to David - Forking Mad

> when I look at the running processes

How do you do that?
some SSH command at hand?

Friendica Support reshared this.

in reply to David - Forking Mad

👍

https://www.geeksforgeeks.org/htop-command-in-linux-with-examples/

@Remind Me 2 days

Friendica Support reshared this.

in reply to David - Forking Mad

@David - Forking Mad
Just tested htop it, it comes preinstalled on the ubuntu VPS the guide in evolution mentioned above.
Adding it right now to that friendica installation DIY!

Friendica Support reshared this.