Show Navigation

Public
- Public
- Network
- Groups
- Popular
- People

Notices by Friendica News (news@forum.friendi.ca)

Friendica News (news@forum.friendi.ca)'s status on Tuesday, 08-Sep-2020 14:11:11 EDT Friendica News

Hotfix Release of Friendica 2020.07-1

Thanks to Roger Meyer who reported a flaw in the administration module of Friendica, we could fix a security vulnerability that could leak sensitive information from the server environment. The hotfix release 2020.07-1 includes the patch for the stable release branch of Friendica. The development and RC branches have been updated as well.
Affected versions of Friendica
All versions of Friendica since April 2019 (develop branch) and June 2019 (stable) are affected.

Through the admin module environment variables of the server system can be read by anyone on the internet. Among other things this may include database passwords for Docker installs and the memcached SASL password. Therefore we recommend all node admins to change their potentially affected passwords after the upgrade to 2020.07-1. Furthermore this fix also prevents anonymous users to update node-wide addon settings.
How to Upgrade.
This information only applies to the stable release 2020.07 of Friendica. The patch has separately been added to the develop and 2020.09-rc branch of the repository.
Using Git
Important: We are removing the master branch and are using the stable branch instead.

Updating from the git repositories of Friendica will be a bit more complicated as you might be used to as we decided to rename the branch for the stable releases to stable. Hence you need to switch the branch you want to use, after pulling the current version of the code from the repositories. As usual, please remember to update the dependencies with composer as well.
cd friendica
git fetch
git checkout stable
git pull
Pulling in the dependencies with composer is not necessary for this hotfix 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 (https://files.friendi.ca/friendica-full-2020.07-1.tar.gz) file and unpack it on your local computer. Compared to the 2020.07 release only a few files were updated and none of the config files are affected. So you can just upload the changed files onto your server.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks again Roger Meyer to make us aware of this problem!
friendi.ca/2020/09/08/hotfix-r…
In conversation Tuesday, 08-Sep-2020 14:11:11 EDT from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
4. The friendica translation project on Transifex
  
  Translate friendica into your own language.
Friendica News (news@forum.friendi.ca)'s status on Sunday, 06-Sep-2020 04:36:28 EDT Friendica News

Friendica 2020.09 Release Candidate available

We are wrapping up the summer contributions to Friendica for the upcoming release and are very happy to announce the availability of the release candidate in the git repositories.

If you want to help to find some bugs and rough edges in the 2020.09 release, now is the perfect moment to switch from the stable or development branch to the freshly created 2020.09-rc branch. To do so please run
git fetch
git checkout 2020.09-rc
git pull
bin/composer.phar install --no-dev
in the root directory of your Friendica and the addon directory. The command to update the dependencies (composer) is only necessary in the Friendica root directory.

Thanks for testing the new release! If you find any problems, please report them either at the issue tracker https://github.com/friendica/friendica/issues on github or in the support forum https://forum.friendi.ca/profile/helpers.
Known Problems
Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread https://forum.friendi.ca/display/3e3ce0df-865f-0d6e-992d-679374230100 for a workaround.
Should the DB update process 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.
friendi.ca/2020/09/06/friendic…
In conversation Sunday, 06-Sep-2020 04:36:28 EDT from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. File without filename could not get a thumbnail source.
  
  Fabio
  
  !Friendica Developers Friendica 2020.07 (and develop) doesn't work on php 7.0. Looks like it's because of this https://github.com/Level-2/Dice/issues/189 I ...
Friendica News (news@forum.friendi.ca)'s status on Sunday, 12-Jul-2020 15:20:54 EDT Friendica News
Friendica “Red Hot Poker” 2020.07 released

We are pleased to announce the slightly delayed release of Friendica 2020.07.

Thanks to everyone who contributed to make this release! The 2020.07 release is composed from 280 tickets, closing 66 numbered issues and enhanced several aspects of Friendica and the communication with other projects within the Fediverse and the Federation. For a full reference, please have a look at the https://github.com/friendica/friendica/blob/stable/CHANGELOG file, some important things are worth highlighting them here:
- Friendica is now using table views for the database which can cause errors from the MySQL database (Prepared statement needs to be re-prepared). If you encounter such, please have a look at this issue in the Friendica tracker https://github.com/friendica/friendica/issues/8550 and this article at stackoverflow https://stackoverflow.com/questions/4380813/how-to-get-rid-of-mysql-error-prepared-statement-needs-to-be-re-prepared if you are encountering problems in that aspect,
- In the frio theme we introduced a more… menu at the bottom of postings which contains the not so often used actions (editing, pinning, etc.), Additionally it is now save to hit the ESC key while composing a new posting.
- You will now find allow lists, deny lists and block lists instead of their old labels.
- We found some places where we could enhance the performance of Friendica.
Not directly linked to this release but worth mentioning is the https://github.com/ingoj/cleanup-friendica script by ingoj to assist Friendica node admins and help with forgotten or dead accounts.
How to Update

Updating from old Friendica versions
If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version https://friendi.ca/2020/03/30/friendica-red-hot-poker-2020-03-released/.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2020.03 to the 2020.06 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.
Using Git
Updating from the git repositories of Friendica will be a bit more complicated as you might be used to as we decided to rename the branch for the stable releases to stable. Hence you need to switch the branch you want to use, after pulling the current version of the code from the repositories. As usual, please remember to update the dependencies with composer as well.
cd friendica
git fetch
git checkout BRANCH
bin/composer.phar install
cd addon
git fetch
git checkout BRANCH
Where BRANCH is either the new stable branch or the develop branch, depending which version of Friendica you want to use. The old master branch will not receive any updates and will be removed soon.

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 (https://github.com/friendica/friendica/releases/download/2020.07/friendica-full-2020.07.tar.gz and friendica-addons 2020.07.tar.gz https://github.com/friendica/friendica-addons/archive/2020.07.tar.gz, Note both are located at github) 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-2020.03 archive), so you don’t have to worry about them.
Post Update Tasks
The database update should be applied automatically, but maybe 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 (days)) to be applied, depending on the size of your Friendica database.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!
friendi.ca/2020/07/12/friendic…
In conversation Sunday, 12-Jul-2020 15:20:54 EDT from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
4. The friendica translation project on Transifex
  
  Translate friendica into your own language.
5. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
6. Error "Prepared statement needs to be re-prepared" on owner-view table breaks proxified images · Issue #8550 · friendica/friendica
  
  from GitHub
  
  After the view update, all the subsequent proxified image I've received are triggering 500 errors. Sample URLs: https://friendica.mrpetovan.com/proxy/3d/aHR0cHM6Ly9pLmNoemJnci5jb20vb3JpZ2luYWwv...
7. How to get rid of MySQL error 'Prepared statement needs to be re-prepared'
  
  from Stack Overflow
  
  I've rewritten my site php-code and added MySQL Stored Procedures. In my local version everything works fine but after I uploaded my site to hosting server I'm constatly getting fatal error 'Prep...
8. ingoj/cleanup-friendica
  
  from GitHub
  
  Cleanup script for Friendica node admins. Contribute to ingoj/cleanup-friendica development by creating an account on GitHub.
Friendica News (news@forum.friendi.ca)'s status on Thursday, 02-Jul-2020 02:50:47 EDT Friendica News

Happy 10th Birthday Friendica!

Ten years ago the 1st commit https://git.friendi.ca/friendica/friendica/commit/6348e70daa113e8b3203de8fbc919d08c90d972e to the git repository of Mistpark was made by Mike Macgirvin, a project that since has become Friendica accumulating some 27.000 commits contributing the work of more then 250 people from all around the world.
Mistpark and Friendica themes from 2010 to 2020
Together we have build a social media platform that had many faces over the years. It has grown from a decentralized communication platform into an integral part of the https://en.wikipedia.org/wiki/Fediverse and Federation. Allowing its users to interact with their friends and family across the borders of nodes, projects and physical distance outside the world of data-harvesting corporations.

Thank you Mike and everybody else who has contributed their time to the project over the years! And while we are preparing the 2020.06 release https://forum.friendi.ca/display/f3ad7b1c-745e-e63a-ca7a-80a162175644 of Friendica, lets have a big party to celebrate ten years of this wonderful part of the free social web.
friendi.ca/2020/07/02/happy-10…
In conversation Thursday, 02-Jul-2020 02:50:47 EDT from pirati.ca permalink
Attachments
1. File without filename could not get a thumbnail source.
  
  friendica
  
  from Friendica git
  
  Friendica Communications Platform (please note that this is a clone of the repository at github, issues are handled there)
2. File without filename could not get a thumbnail source.
  
  Friendica 2020.06-rc created
  
  I've just created a 2020.06-rc branch in the core and addon repositories and pushed the version 2020.06-rc. We thus have a release candidate for the 2020.06 ...
Friendica News (news@forum.friendi.ca)'s status on Sunday, 08-Mar-2020 14:15:08 EDT Friendica News
Friendica 2020.03 Release Candidate (RC) available for testing

Today we have branched of the release candidate https://github.com/friendica/friendica/tree/2020.03-rc (RC) of the upcoming Friendica 2020.03 https://github.com/friendica/friendica/milestone/19 version. We’d like to invite you to test the code so that some last rough edges can be smoothed out prior to the release.

The release contains many bug fixes (about 40% of the pull request were aimed to this goal) but also some new features. Some highlights from the upcoming release:
- The multiple profile feature was removed and replaced by free form profile fields that you can present different audiences (unverified visitors of your profile and selected Friendica contact/-groups). The old (additional) profiles are converted automatically for the new format.
- The hide-wall profile option was replaced by a hopefully more clear option to have your public postings unlisted on the community page of your node.
- The creation of delegated accounts was made more easy.
- The accessibility of the web-interface was improved.
- Admins can now manage the users of their node from the command line.
- An addon to use Markdown instead of BBCode while composing new postings and comments was added.
Important
Please remember that Friendica now needs at least PHP version 7.0 and MySQL 5.6 (or equivalent) installed on the server to function properly.
How to help testing the release candidate?
Assuming that you are running the 2019.12 version of Friendica and that you have installed via git: Please pull the current sources for the core of Friendica and the addons from github. You should see a notification about a new branch called 2020.03-rc during the pull. in both repositories. You just need to checkout this branch with a

git checkout 2020.03-rc

and remember to follow the usual steps after updating using git. Please report any issues you encounter using either the issue tracker https://github.com/friendica/friendica/issues at github or the Friendica support https://forum.friendi.ca/~helpers or https://forum.friendi.ca/~admins forums.

Thanks for testing the new code with us!
Should the DB update process 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.
friendi.ca/2020/03/08/friendic…
In conversation Sunday, 08-Mar-2020 14:15:08 EDT from friendica.mrpetovan.com permalink
Friendica News (news@forum.friendi.ca)'s status on Monday, 20-May-2019 06:39:24 EDT Friendica News
Friendica release candidate 2019.06-rc available

Today we have branched off the release https://github.com/friendica/friendica/tree/2019.03-RC candidate https://github.com/friendica/friendica/tree/2019.06-rc (RC) for the upcoming 2019.06 release of Friendica. Since end of March, we fixed some bugs and added some interesting new features. These include:
- Two factor authorisation (Google authenticator compatible) was added to the login process for user accounts.
- Handling of re-shares was improved and the number of re-shares of a posting is now displayed.
- The look of the error pages was improved.
Important
Please note that with this version Friendica will not be running anymore with PHP 5.6. Minimal required version of PHP is now 7.0.
How to help testing the release candidate?
Please pull the current sources for the core of Friendica and the addons from github. You should see a notification about a new branch called 2019.06-rc during the pull. in both repositories. You just need to checkout this branch with a
git checkout 2019.06-rc
and remember to follow the usual steps after updating using git https://github.com/friendica/friendica/blob/develop/doc/Update.md#using-git. Please report any issues you encounter using either the issue tracker https://github.com/friendica/friendica/issues at github or the Friendica support https://forum.friendi.ca/profile/helpers or https://forum.friendi.ca/profile/admins forums.

We have changed the internal mechanism how requests are routed to the endpoints in the code to be processed. If you find any action, that is missing a response, please notify us about this potential missing route.
Should the DB update process 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.
friendi.ca/2019/05/20/friendic…
In conversation Monday, 20-May-2019 06:39:24 EDT from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
4. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
Friendica News (news@forum.friendi.ca)'s status on Sunday, 28-Apr-2019 05:56:24 EDT Friendica News

Friendica 2019.04 released

This release fixes a bug allowing unauthorised access to private postings under certain circumstances.
How to update
For this release notes we assume, that you are running Friendica 2019.03 https://friendi.ca/2019/03/22/friendica-2019-03-dalmatian-bellflower-released/ if not, please update to that release before proceeding.
Using git
If you have used git for installation, update your system simply by doing a git pull in the core repository of Friendica. The fix is applied to the master and the devel branch of the repository.

An update of the addons repository is not needed.
Using the archive files
Before uploading the extracted files from the archive please make sure that you have a backup copy of your configuration file (config/local.config.php).

Please download the archive file frintica-full-2019.04.tar.gz https://friendi.ca/wp-content/uploads/2019/04/friendica-full-2019.04.tar.gz which contains the needed 3rd party dependencies.

Compared to the 2019.03 release only four files have changed: CHANGELOG, VERSION, boot.php and mod/display.php.

Extract the archive and upload the contained files (all or only the four mentioned above) to your server.
Post upgrade procedure
There should be no action necessary after the files are exchanged if you were updating from the 2019.03 release of Friendica.
friendi.ca/2019/04/28/friendic…
In conversation Sunday, 28-Apr-2019 05:56:24 EDT from friendica.mrpetovan.com permalink
Attachments
1. File without filename could not get a thumbnail source.
  
  Friendica 2019.03 "Dalmatian Bellflower" Released
  
  By Tobias from friendica
  
  Friendica 2019.03 “Dalmatian Bellflower” Released
Friendica News (news@forum.friendi.ca)'s status on Friday, 22-Mar-2019 16:48:38 EDT Friendica News
Friendica 2019.03 “Dalmatian Bellflower” Released
A year of Friendica with The Tazmans Flax-lily https://friendi.ca/2018/03/23/friendica-3-6-the-tazmans-flax-lily-released/. Thanks everyone who contributed, be it directly by commiting patches or new features, doing translations or reporting issues.

And now, we happily announce the availability of Friendica 2019.03 “Dalmatian Bellflower”. It contains many bug fixes, enhancements of existing functionality and some new features. The most noteworthy changes since the last release in January are:
- The storage backend for photos and attachments was made plug-able and an experimental file system backend was added.
- ActivityPub support was added to the forum functionality, and got some general improvements to smooth out quirks discovered since the initial implementation.
- The performance of the background process was enhanced.
You can find a complete overview of the changes in the https://raw.githubusercontent.com/friendica/friendica/master/CHANGELOG file.
How to Update

Updating from old Friendica versions
If you are updating from an older version then the 2018.09 release, please first update your Friendica instance to that version https://friendi.ca/2018/09/23/friendica-2018-09-released/ as there were several important changes in that version.

Please further note, that since Friendica 3.6 we use composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better save than sorry.

With this release we raised the requirements to PHP and MySQL to PHP 7.1+, MySQL 5.6+ (or compatible alternatives e.g. MariaDB 10.0.5+). If you are still using PHP 5.6.1 we don’t expect problems, but encourage you to upgrade your PHP installation. Please make sure, that your systems meets this new requirement.
Known Problems
The performance of the background process (workers) was improved by removing a bottleneck, As a consequence the worker will consume more system resources. On the plus side, you will most likely not need aas many workers as you needed before to perform the pending jobs.

During the RC phase several admin reported high system LOADs. As a rule of thumb, you should set the Maximum number of parallel workers (plus an additional fastlane worker) and set the Maximum Load Average to the number of threads your servers CPU cores can perform. These values are not carved into stone, you can most likely further adjust the settings to increase the performance of the system.
Using GIT
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica
git pull
bin/composer.phar install
cd addons
git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using git checkout master (or develop).

Be aware that the .htaccess file was removed from the git repository in the last version. You might have to restore yours from a backup (if you have done local changes) or from the .htaccess-dist if you had not done it before.
Using the Archive Files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive (https://friendi.ca/wp-content/uploads/2019/03/friendica-full-2019.03.tar.gz and friendica-addons-2019.02.tar.gz https://github.com/friendica/friendica-addons/archive/2019.03.tar.gz) 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 .htconfig.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-2019.03 archive), so you don’t have to worry about them.

Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Post Update Tasks
The database update should be applied automatically, but maybe 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.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!
friendi.ca/2019/03/22/friendic…
In conversation Friday, 22-Mar-2019 16:48:38 EDT from friendica.mrpetovan.com permalink
Friendica News (news@forum.friendi.ca)'s status on Sunday, 03-Mar-2019 05:38:30 EST Friendica News
Friendica 2019.03 RC available

Today we have branched off the release candidate https://github.com/friendica/friendica/tree/2019.03-RC (RC) for the upcoming 2019.03 release of Friendica. Since end of January, we fixed some bugs and added some interesting new features. These include:
- The used storage backend for uploaded media files is now plug-able. By default Friendica currently support the file system and the database as storage devices. But this list can be expanded via addons.
- The postings and comments of the logged in user now have a delivery indication included in the displayed header of the posting.
- The frio theme has got a live preview of new attachments, and
- visitors can now override the language settings by appending a lang=CODE parameter to the URL in the browser address bar.
If you are updating from an older version then the 2018.09 release, please first update your Friendica instance to that version https://friendi.ca/2018/09/23/friendica-2018-09-released/ as there were several important changes in that version. Afterwards you can continue to update to the RC branch.
How to help testing the release candidate?
Please pull the current sources for the core of Friendica and the addons from github. You should see a notification about a new branch called 2019.03-RC during the pull. in both repositories. You just need to checkout this branch with a
git checkout 2019.03-RC
and remember to follow the usual steps after updating using git https://github.com/friendica/friendica/blob/develop/doc/Update.md#using-git. Please report any issues you encounter using either the issue tracker https://github.com/friendica/friendica/issues at github or the Friendica support https://forum.friendi.ca/profile/helpers or https://forum.friendi.ca/profile/admins forums.
Should the DB update process 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.
friendi.ca/2019/02/20/friendic…
In conversation Sunday, 03-Mar-2019 05:38:30 EST from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. File without filename could not get a thumbnail source.
  
  Friendica 2018.09 released
  
  By Tobias from friendica
  
  Friendica 2018.09 released
4. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
Friendica News (news@forum.friendi.ca)'s status on Monday, 21-Jan-2019 04:26:30 EST Friendica News
Friendica 2019.01 released

We are pleased to announce the availability of Friendica The Tazmans Flax-lily 2019.01, which bundles up our work since September 2018. This includes over 130 fixed issues and some exciting new features. If you are interested in all of them, please have a look at the https://raw.githubusercontent.com/friendica/friendica/master/CHANGELOG file.

Most noteworthy of these changes are:
- Friendica does now natively support ActivityPub https://friendi.ca/2018/11/18/activitypub-support-in-friendica/ (AP https://en.wikipedia.org/wiki/ActivityPub) in addition to the DFRN, diaspora* and OStatus protocols. The AP functionality was tested with Hubzilla, Mastodon, Nextcloud Social, Osada, PeerTube, Pixelfed and Pleroma.
- The configuration structure has changed again! Your old .htconfig.php and config/local.ini.php file will still work, but you will get a notification in the admin panel with some hopefully explaining text on how to convert your settings to the new config/local.config.php config file.
- The manual and automatic installation process was enhanced.
Thanks everyone https://raw.githubusercontent.com/friendica/friendica/master/CREDITS.txt who has made this release possible. Your work is much appreciated!

Please note, that this will be the last version of Friendica supporting PHP 5.6.
How to Update
If you are updating from an older version then the 2018.09 release, please first update your Friendica instance to that version https://friendi.ca/2018/09/23/friendica-2018-09-released/ as there were several important changes in that version.

Please further note, that since Friendica 3.6 we use composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better save than sorry.
Using the Archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (https://github.com/friendica/friendica/releases/download/2019.01/friendica-full-2019.01.tar.bz2 and friendica-addons-2019.01.tar.gz https://github.com/friendica/friendica-addons/archive/2019.01.tar.gz 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 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-2019.01 archive), so you don’t have to worry about them.

Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Using git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica
git pull
bin/composer.phar install
cd addon
git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using git checkout.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks again everyone who helped making this release possible and have fun!
friendi.ca/2019/01/21/friendic…
In conversation Monday, 21-Jan-2019 04:26:30 EST from pirati.ca permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
4. The friendica translation project on Transifex
  
  Translate friendica into your own language.
5. File without filename could not get a thumbnail source.
  
  ActivityPub support in Friendica
  
  By Tobias from friendica
  
  ActivityPub support in Friendica
6. File without filename could not get a thumbnail source.
  
  Friendica 2018.09 released
  
  By Tobias from friendica
  
  Friendica 2018.09 released
Friendica News (news@forum.friendi.ca)'s status on Tuesday, 11-Dec-2018 09:30:32 EST Friendica News

Friendica 2018.12 RC available

Today we have branched off the release candidate https://github.com/friendica/friendica/tree/2018.12-rc (RC) for the upcoming 2018.12 release of Friendica The Tazmans Flax-lily. Over the last quarter of the year many issues were resolved, alongside with some enhancements and new features. Most noteworthy the initial support of ActivityPub https://friendi.ca/2018/11/18/activitypub-support-in-friendica/ as communication protocol between nodes in the Fediverse.

For all these changes we now feel it is time for them to get released. Before this will happen, we’d like to invite you, to test them and report back some rough edges and problems you encountered. We are especially interested in the experiences of people who are currently running the 2018.09 release of Friendica.

If you are updating from an older version then the 2018.09 release, please first update your Friendica instance to that version https://friendi.ca/2018/09/23/friendica-2018-09-released/ as there were several important changes in that version. Afterwards you can continue to update to the RC branch.
How to help testing the release candidate?
Please pull the current sources for the core of Friendica and the addons from github. You should see a notification about a new branch called 2018.12-RC during the pull. in both repositories. You just need to checkout this branch with a
git checkout 2018.12-rc
and remember to follow the usual steps after updating using git https://github.com/friendica/friendica/blob/develop/doc/Update.md#using-git. Please report any issues you encounter using either the issue tracker https://github.com/friendica/friendica/issues at github or the Friendica support https://forum.friendi.ca/profile/helpers or https://forum.friendi.ca/profile/admins forums.
Should the DB update process 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.
friendi.ca/2018/12/11/friendic…
In conversation Tuesday, 11-Dec-2018 09:30:32 EST from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
4. File without filename could not get a thumbnail source.
  
  ActivityPub support in Friendica
  
  By Tobias from friendica
  
  ActivityPub support in Friendica
5. File without filename could not get a thumbnail source.
  
  Friendica 2018.09 released
  
  By Tobias from friendica
  
  Friendica 2018.09 released
Friendica News (news@forum.friendi.ca)'s status on Sunday, 18-Nov-2018 10:30:20 EST Friendica News
ActivityPub support in Friendica

What is ActivityPub?

In the last couple of weeks support for https://activitypub.rocks/ (AP) has landed in Friendica. For those who do not know AP–it is the attempt to provide a common protocol different projects can use to let their users and server communicate among each other. It was developed by the W3C Social Working Group https://www.w3.org/wiki/Socialwg and is adopted in the realm of the Fediverse/Federation by other projects like Funkwhale, Hubzilla, Mastodon, Pleroma or Osada.
Current state of implementation

At this point AP implementation is still a work in progress. Although many parts already charmingly work.

So what can you already use?
- You can follow and un-follow accounts that support the AP protocol. We mainly test with Mastodon and Pleroma, so other AP supporting projects might not work at the moment. If you encounter such a case, please report it in the Support Forum or open a new issue at https://github.com/friendica/friendica/issues.
- The public and non-public communication works. You can write new postings and comments; like, unlike and delete them.
- The distribution of comments for public postings is done both ways; thread based like e.g. in Friendica and diaspora* by the creator of a thread, and per posting as known from OStatus based systems.
- The thread completion works the same, as Friendica already does the completion for threads from GNUsocial, so conversations are not torn apart.
- When the initial distribution of your posting was not successful for some contacts, the posting will be re-queued for a later delivery retry.
Some things currently do not work, of have rough edges at the borders of the Friendica network to the (or some) other parts of the Fediverse. Among these, the most prominent are
- AP does not support direct messages. There is only the workaround to make an non-public posting, restricted to one recipient and mention the recipient.
- Resettling of your account to another node, does not work over AP.
And of course, you may find other quirks along the way. For the things that are currently not possible with AP we use the old ways, if they existed, so you wont loose functionality.
When can I use it?

You already can. That is, if your Friendica node is running the current development version of the code from the development branch https://github.com/friendica/friendica/tree/develop. If you are running the current stable 2018.09 release (or an older version) you will get AP support with the December release of Friendica.

So stay tuned
friendi.ca/2018/11/18/activity…
In conversation Sunday, 18-Nov-2018 10:30:20 EST from forum.friendi.ca permalink
Friendica News (news@forum.friendi.ca)'s status on Tuesday, 13-Nov-2018 04:30:21 EST Friendica News

Friendica Hackathon 2018

Three times we’ll wake up, be hot then it’s Friendica hackathon weekend.

We are grateful that we can use the youth-club E-LOK http://zope2.in-berlin.de:8100/wsb/elok, Laskerstraße 6-8 near Ostkreuz https://www.openstreetmap.de/karte.html?zoom=16&lat=52.5014&lon=13.46153&layers=B000TT station in Berlin, again as venue for the Friendica hackathon in Berlin this year. Some of us will gather at Friday afternoon at the venue for set-up and already doing some work. Hacking will most likely really happen at Saturday and Sunday; focusing the work on the open issues of the upcoming 2018.12 release https://github.com/friendica/friendica/milestone/14. If you are interested in the progress, you can follow it with the https://github.com/friendica/friendica/labels/Berlin2018 label for closed issues . If you want to join from abroad, we will be online at the Friendica IRC channel (#friendica at freenode.net) most of the time.

https://friendi.ca/wp-content/uploads/2018/11/elok800.jpg
Entrance area of the youth-club E-LOK in Berlin

If you want to join us at the hackathon. Please contact https://social.diekershoff.de/~tobias and let him know, so that the snacks wont run out at Saturday evening But don’t hesitate, spontaneous visitors are welcome as well!

Happy hacking!
friendi.ca/2018/11/13/friendic…

In conversation Tuesday, 13-Nov-2018 04:30:21 EST from pirati.ca permalink
Friendica News (news@forum.friendi.ca)'s status on Sunday, 23-Sep-2018 17:00:22 EDT Friendica News
Friendica 2018.09 released

Dear everybody in the Federation, the Fediverse and anywhere else, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.09.

This release brings the long awaited restructuring of the item table in the database, alongside some 100 closed issues from the tracker. Please see the https://raw.githubusercontent.com/friendica/friendica/master/CHANGELOG file for the complete overview of the changes. Here just a short list of the noteworthy changes since the 2018.05 https://friendi.ca/2018/06/01/friendica-2018-05-released/ release of Friendica.
- The long awaited restructuring of the item table of the database will finally be included in this release. The needed changes and alterations of the database structure and content will take some time. Depending on the resources available on your system this can take hours or even days. The maintenance mode will inform you about the progress.
- The configuration structure is changed. Your old `.htconfig.php` file will still work, but you will get a notification in the admin panel with some hopefully explaining text on how to convert your settings to the config file. In some cases the encoding https://forum.friendi.ca/display/1860bc0e435b504c796e187715802340 of the displayed text got mangled up, if you are suffering from such garbage you need to switch to the new config style and set the correct encoding for the database.
- The `.htaccess` file is no part of the git repository anymore. Instead we now ship the `.htaccess-dist` file that you have to copy to the `.htaccess` location. This has the advantage that you can now customise the `.htaccess` file to meet your requirements. Please make a copy of your old `.htaccess` file should you have made any changes and restore the file after the update from the backup or the distributed file. Without a working `.htaccess` file your node will probably not work!
- We removed the old syntax highlighting mechanism from `[code]` blocks due to problems federating the highlighted syntax to other platforms. There will be an https://github.com/friendica/friendica-addons/pull/737 for this in the next release.
- The libravatar service will be continued, so contrary to the note with the last release, you can keep using the libravatar addon to automatically generate avatar pictures for your users.
Thanks everyone https://raw.githubusercontent.com/friendica/friendica/develop/util/credits.txt who has made this release possible. Your work is much appreciated!
How to Update
Updating from old Friendica versions
If you are updating from a version older then Friendica 3.5.4 https://friendi.ca/2017/10/16/friendica-3-5-4-release/) you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.

Please further note, that since Friendica 3.6 https://friendi.ca/2018/03/23/friendica-3-6-the-tazmans-flax-lily-released/ we use composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems (except those listed below), but better save than sorry.

This is especially true during this update for your `.htaccess` file which we removed from the repository so you can make local adjustments to the files without further conflicts. Please make a copy of the file before you start the update and restore it afterwards. If you have not made any changes to the file, you can use the new `.htaccess-dist` file and copy that to the `.htaccess` file.
Using the Archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (https://github.com/friendica/friendica/files/2409065/friendica-full-2018.09.tar.gz and friendica-addons-2018.09.tar.gz https://github.com/friendica/friendica-addons/archive/2018.09.tar.gz 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 `.htconfig.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-2018.09 archive), so you don’t have to worry about them.

Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Using git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica
git pull
bin/composer.phar install
cd addons
git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using `git checkout`.

Be aware that the `.htaccess` file was removed from the git repository. You have to restore yours from a backup (if you have done local changes) or from the `.htaccess-dist` file (copy the file to `.htaccess` if you had not done any changes to the old `.htaccess` file).
Post-Update Procedures
The conversion process of the items stored in the database can take a long time. Reports indicate some hours to days or even weeks depending on the number of stored items and the available resources on the server.

If you can start the process directly from the command line interface, this will speed up the process significantly. To do so run the following command (use screen or a similar tool so you can detach from the session while the process is running):
bin/console postupdate
from the base of your Friendica installation.

The conversation of the stored items to the new structure of the database will cause some load on the server. It will not interfere with the daily usage of your Friendica node. Once it is finished the needed storage for the database should be lowered significantly, especially on large nodes.
Known Problems
Should the DB update process 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 below.
Problem with InnoDB on MySQL 5.7
One user [reported problems](github.com/friendica/friendica…) during the update of the database using MySQL 5.7 getting the error message `Creating index ‘PRIMARY’ required more than ‘innodb_online_alter_log_max_size’ bytes of modification log. Please try again.` from MySQL. If you encounter this problem, please [try the following:](github.com/friendica/friendica…)
- increase the config value mentioned in the error message above,
- execute this command in your mysql console: `update config set v=1278 where k=”post_update_version”;`
- after this execute the command `bin/console postupdate`.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks again everyone who helped making this release possible and have fun!
friendi.ca/2018/09/23/friendic…
In conversation Sunday, 23-Sep-2018 17:00:22 EDT from friendica.mrpetovan.com permalink
Attachments
1. File without filename could not get a thumbnail source.
  
  Friendica 3.5.4 released
  
  By Tobias from friendica
  
  Friendica 3.5.4 released
2. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
3. File without filename could not get a thumbnail source.
  
  Friendica 3.6 released
  
  By Tobias from friendica
  
  Friendica 3.6 released
4. File without filename could not get a thumbnail source.
  
  Friendica 2018.05 released
  
  By Tobias from friendica
  
  Friendica 2018.05 released
5. Rebeka Catalina
  
  !Friendica Support Since yesterday I have several unicode encoding issues on develop branch. Can anybody confirm this?
6. [highlightjs] Add new addon by MrPetovan · Pull Request #737 · friendica/friendica-addons
  
  from GitHub
  
  Related to friendica/friendica#5765 Since we aren't doing syntax highlighting in the core, I'd figured people would like a replacement, and this is the one. Depends on friendica/friendica#5773
7. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
8. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
9. The friendica translation project on Transifex
  
  Translate friendica into your own language.
Friendica News (news@forum.friendi.ca)'s status on Tuesday, 28-Aug-2018 05:50:18 EDT Friendica News
Friendica 2018.08 RC available

Today we have branched off the release candidate https://github.com/friendica/friendica/tree/2018.08-rc (RC) for the upcoming 2018.08 release of Friendica The Tazmans Flax-lily. Over the last 3 month many issues were resolved, alongside with some enhancements and new features. For all these changes we now feel it is time for them to get released. Before this will happen, we’d like to invite you, to test them and report back some rough edges and problems you encountered. We are especially interested in the experiences of people who are currently running the 2018.05 release of Friendica.

Some things you should be aware of before testing:
- The long awaited restructuring of the item table of the database will finally be included in this release. The needed changes and alterations of the database structure and content will take some time. Depending on the resources available on your system this can take hours or even days. The maintenance mode will inform you about the progress.
- The configuration structure is changed. Your old .htconfig.php file will still work, but you will get a notification in the admin panel with some hopefully explaining text on how to convert your settings to the config file. In some cases the encoding https://forum.friendi.ca/display/1860bc0e435b504c796e187715802340 of the displayed text got mangled up, if you are suffering from such garbage you need to switch to the new config stile and set the correct encoding for the database.
- The .htaccess file is no part of the git repository anymore. Instead we now ship the .htaccess-dist file that you have to copy to the .htaccess location. This has the advantage that you can now customize the .htaccess file to meet your requirements. Please make a copy of your old .htaccess file should you have made any changes and restore the file after the switch to the RC branch from the backup or the distributed file. Without a working .htaccess file your node will probably not work!
How to help testing the release candidate?
Please pull the current sources for the core of Friendica and the addons from github. You should see a notification about a new branch called 2018.08-RC during the pull. in both repositories You just need to checkout this branch with a
git checkout 2018.08-rc
and remember to follow the usual steps after updating using git https://github.com/friendica/friendica/blob/develop/doc/Update.md#using-git. Please report any issues you encounter using either the issue tracker https://github.com/friendica/friendica/issues at github or the Friendica support https://forum.friendi.ca/profile/helpers or https://forum.friendi.ca/profile/admins forums.

For a complete list of changes, please have a look at the file listing of this pull request https://github.com/friendica/friendica/pull/5685/files at github.
Should the DB update process get stuck
If you encounter this, please initiate the DB update manually from the command line by running the script
scripts/dbstructure.php update
from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.
friendi.ca/2018/08/28/friendic…
In conversation Tuesday, 28-Aug-2018 05:50:18 EDT from friendica.mrpetovan.com permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
3. Rebeka Catalina
  
  !Friendica Support Since yesterday I have several unicode encoding issues on develop branch. Can anybody confirm this?
4. friendica/friendica
  
  from GitHub
  
  Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
5. Changelog 2018.08 by tobiasd · Pull Request #5685 · friendica/friendica
  
  from GitHub
  
  The CHANGELOG for the 2018.08 release. This should be the last PR merged before the release happens.
Friendica News (news@forum.friendi.ca)'s status on Friday, 01-Jun-2018 04:55:20 EDT Friendica News
Friendica 2018.05 released

Dear Federation, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.05.

Back on track with scheduled releases, after 3.6 took such a long time. In this release we have packed some bug fixes and enhancements. After an incompatibility glitch with the last release, Friendica 2018.05 is now again compatible with PHP 5.6. However we recommend using a more recent PHP version to further enhance the performance gain from the ongoing overhaul of the Friendica code and processes. Obviously GDPR was one thing we concentrated on for this release. Identifying problems in existing features (e.g. account and node mobility), adding new features (see below) and making things more transparent. To make a long story short, here a list of the noteworthy changes since the last release:
- Finnish translation was added to the repository from Transifex. With it, Friendica now has 20 localizations from which 11 have more then 80% of the core plattform translated (DE, EN, EN-GB, EN-US, ES, FI, FR, IT, PL, RU, ZH-CN).
- New module for Terms of Services for your node that can be activated from the admin panel. If the module is activated links from the general information page and the user registration will be added. Additionally a basic privacy statement can be shown in both, the TOS page and the registration page.
- Many utility scripts are now bundled in a console that can be found in the bin directory. Please see bin/console –help for all available commands.
- When entering a new password, the choosen one will be checked locally against a database of exposed passwords https://github.com/friendica/friendica/issues/4604.
- As libravatar is closing their service https://blog.libravatar.org/posts/Libravatar.org_is_shutting_down_on_2018-09-01/ we have added a new alternative to the gravatar service based on David Revoy’s http://www.davidrevoy.com/ https://framagit.org/Deevad/cat-avatar-generator: the catavatar.
- The long deprecated themes frost( and frost-mobile have been removed from the Friendica repository. If you need them, you can find them in the https://github.com/friendica/deprecated-themes repository.
For a list of further changes, please have a look at the https://raw.githubusercontent.com/friendica/friendica/master/CHANGELOG file.

https://friendi.ca/wp-content/uploads/2018/05/friendica2018.05_cloud.png
wordcloud from the commit messages

Thanks to everyone who made this release possible, by writing code, translating the user interface and reporting issues!
How to update?
Pre-Update procedures
Ensure that the last backup of your Friendica database was done recently. While testing, we did not encounter problems, but better save than sorry.
From the archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (https://github.com/friendica/friendica/files/2061623/friendica-full-2018.05.tar.gz and friendica-addons-2018.05.tar.gz https://github.com/friendica/friendica-addons/archive/2018.05.tar.gz) 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 .htconfig.php file. 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-2018.05 archive), so you don’t have to worry about them.
From git
Regardless of the branch you are on (master, develop or 2018.05-rc) all you have to do to get the new code is to run
git pull
on your server in the base and the addon directory. Remember to update the dependencies as well.

Due merging conflicts the development branch will receive the update later. The release notes will be updated then.

If you helped testing the release candidate, you should also switch to either the master or the develop branch. Thanks for testing!

If you are updating from an older version then the 3.6 release, please be aware that Friendica is now using composer to manage the dependencies. After you pulled the latest code, you have to check the dependencies for updates as well. To do so run
bin/composer.phar install
from the base directory of your Friendica installation. To be able to extract the downloaded archives, you need to have the php-zip module installed on your server. If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs https://github.com/friendica/friendica/blob/master/doc/Developers-Intro.md#composer for further information about this.

If you are updating from a version older then 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
Post-Update procedures
If you are updating from the 3.6 release (or older versions) of Friendica please remember to change the path to the worker in the cron job to adopt the changed location.

It should now be something along these lines:
/usr/bin/php bin/worker.php
Among other things the worker will detect changes to the database structure. The changes will be applied automatically and may, depending on the size of your table (especially the item table) and the available resources on the server, take some time. On larger systems this can be hours.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://forum.friendi.ca/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/dashboard/ 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 https://forum.friendi.ca/profile/helpers with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!
friendi.ca/2018/06/01/friendic…
In conversation Friday, 01-Jun-2018 04:55:20 EDT from pirati.ca permalink
Friendica News (news@forum.friendi.ca)'s status on Saturday, 03-Mar-2018 04:00:22 EST Friendica News

3.6 RC available

Hey everyone, we have just branched off a release candidate branch for the next stable release of Friendica to focus on testing the code and fixing the final problem. For this to succeed, we’d like to ask you to test the https://github.com/friendica/friendica/tree/3.6-rc code on your node if you like.

This branch is for the final bug fixes and translation updates before the release. We don’t expect to heavy changes to it till the release. New features wont be included there. Instead pull requests for those should be done against the development branch as usual.
How to switch to the RC branch?
If you are currently running the develop branch, then all you have to do is to checkout the 3.6-rc branch after a pull from the repositories.
git pull
git checkout 3.6-r
cd addons
git pull
git checkout 3.6-rc
Assuming that you already have the composer call in your updating routing. In the last couple days there were no changes to the dependencies.

If you are currently using the last stable release code installed from git, the procedure is almost identical. There is one thing you should be aware of before doing the switch—we switched to composer https://friendi.ca/2018/01/18/important-changes-for-the-development-branch-of-friendica/ for dependency management. If you don’t take this into account, your Friendica node will not work after the pull of the new code.

You can either add a call to
util/composer.phar install --no-dev
after the git pull in your update routines for the core repository, or you can add a small script to the “post-merge” git-hook https://github.com/friendica/friendica/blob/develop/doc/Developers-Intro.md#composer. The script will then automatically be executed by git if there were changes to the dependencies.

Please be aware, that there were some heavy work on the database structure since the last stable release of Friendica. This means that depending on the size of your database, your node might need some time to apply all the changes. The maintenance mode will inform you about the progress.

After you performed the update, you need to touch your cron job for the background process. The script handling the worker has been moved to scripts directory. So your cron job must now contain: something like
/usr/bin/php scripts/worker.php
instead of the old location in the include directory.

If you are updating from a very old version of Friendica, you have to first update to version 3.5.4 before you can update to the 3.6-rc branch.

Should you encounter any problems while testing the RC code, please let us know about in the Friendica support forum https://forum.friendi.ca/~helpers, at https://github.com/friendica/friendica/issues or over any other of the support channels https://github.com/friendica/friendica/blob/3.6-rc/doc/FAQ.md#where-i-can-find-help.

Thanks for testing and helping!
https://friendi.ca/2018/03/03/3-6-rc-available/
In conversation Saturday, 03-Mar-2018 04:00:22 EST from pirati.ca permalink
Attachments
1. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
2. File without filename could not get a thumbnail source.
  
  Important changes for the development branch of Friendica
  
  By heluecht from friendica
  
  Important changes for the development branch of Friendica
3. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
4. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
5. friendica/friendica
  
  from GitHub
  
  friendica - Friendica Communications Platform
Friendica News (news@forum.friendi.ca)'s status on Tuesday, 28-Nov-2017 08:24:14 EST Friendica News
Hackathon Berlin 2017

Thanks to the nice people of the e-lok http://zope2.in-berlin.de:8100/wsb/elok we had our Hackathon over the last weekend near Ostkreuz station in Berlin. Seven people coming together to work on the themes, code and the documentation. Altogether we had many discussion rounds, a small workshop, produced 26 pull requests https://github.com/friendica/friendica/pulls?q=is%3Apr+is%3Aclosed+label%3ABerlin2017 and had a lot of fun. Thanks to everybody who could attend!

On Friday evening we started with a small workshop about creating an https://github.com/friendica/friendica-addons for https://github.com/friendica/friendica. The resulting https://en.wikipedia.org/wiki/Rot13 thingy is nothing that should be used, not in this form and not for any serious purpose. But the step-by-step discussion about the code brought up enough questions to clarify the process of writing addons for Friendica. Even though it is not as good as the live workshop, you can find the code and documentation on https://github.com/tobiasd/rot13_hackathon2017.,

After the warm-up phase on Friday evening, Saturday and Sunday were busy with coding and documentation work. Some highlights are:
- The !-mentions for forums, introduced before the Hackathon got some love. The difference between the @-mentioning and the !-mentioning of a forum is, that the ! is exclusive for one forum. Forum postings will not be send to other networks or your contacts [1],. If you select a forum in the ACL, it will make sure, that you only select one forum.
- The documentation was updated, and in some parts new German translations were added.
- The vier theme got a new style called Plus Minus. It is work in progress at the moment with the goal to have a minimalistic version concentrating more on the information of the postings, and not so much on the meta stuff.
  
  http://friendi.ca/wp-content/uploads/2017/11/vier-plusminus.jpg
  Screenshot of the plusminux style from the vier theme.
- We set up a second http://directory.friendica.belug.de/ directory server that you can use. The two directory servers to sync their content, so you can put any one of them into your nodes configuration. Many thanks to the Berlin Linux User Group https://belug.de/home.html for providing the server alongside with your node in the network!
- We have build some preliminary version of a Debian package for Friendica. Not finished, but at least install able for now. We’ll investigate ways to publish the upcoming version 3.6 packages.
- We wrote two new utility scripts for the admins to run from the CLI of their servers. These can be used to silence accounts from the nodes global community page or block them completely from the node.
Thanks everybody involved making this event possible! And happy coding
[1]Please note: At the moment previously selected groups, e.g. via the default postings permissions, are not overwritten. If you have a non-public default set of recipient-permissions, please the the ACL permission to public / “visible to all” before selecting the target forum.
In conversation Tuesday, 28-Nov-2017 08:24:14 EST from friendica.mrpetovan.com permalink
Friendica News (news@forum.friendi.ca)'s status on Monday, 20-Nov-2017 03:24:13 EST Friendica News

Changes in the background process

As part of reworking the code base there today changes in the development branch landed, that require some manual configuration changes. If you are using the development branch, and have pulled the latest code from github (everything after the PR The poller is now the worker and we have a “scripts” folder https://github.com/friendica/friendica/pull/3920 #3920) you need to do the following adjustment to your cron job.

Change the old process from
*/10 * * * * cd /home/myname/mywebsite; /usr/bin/php include/poller.php
to
*/10 * * * * cd /home/myname/mywebsite; /usr/bin/php scripts/worker.php

but remember to adopt your actual path and interval settings.

If you are running the stable 3.5.4 release (or before) you don’t need to change anything at the moment!
In conversation Monday, 20-Nov-2017 03:24:13 EST from friendica.mrpetovan.com permalink
Attachments
1. The poller is now the worker and we have a "scripts" folder by annando · Pull Request #3920 · friendica/friendica
  
  from GitHub
  
  Hopefully this will not affect the ongoing changes from @MrPetovan All executable scripts are now moved out of the include folder. Additionally all occurrences of "poller.php" are renamed to "worke...
Friendica News (news@forum.friendi.ca)'s status on Monday, 16-Oct-2017 05:36:14 EDT Friendica News

Friendica 3.5.4 released

Dear Federation, the Friendica team is pleased to announce the release of Friendica *Asparagus* 3.5.4.

This release is a hotfix release for a bug that was overlooked in the 3.5.3rc phase during saving searches to the users side menu. It also includes fixes to smaller issues we had with relocating accounts from one node of the network to another. As well as the support for the new Diaspora* relocation signal, that was planned for the upcoming 3.6 release of Friendica. Which means if you move to another node, now your Diaspora contacts will receive the signal as well and vice versa.

Additionally we fixed numerous bugs that the community had found and we polished some quirks. For the complete list of changes, please see the https://raw.githubusercontent.com/friendica/friendica/develop/CHANGELOG file.
How to Update?
If you used `git` to install your copy of Friendica and use the master or develop branch, a git pull is enough to upgrade.

If you have helped to iron out quirks for this release and used the 3.5.4rc branch of the repository you just need to pull from the repository and switch to either the master or develop branch.

If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-3.5.3.zip https://github.com/friendica/friendica/archive/3.5.4.zip and friendica-addons-3.5.3.zip https://github.com/friendica/friendica-addons/archive/3.5.4.zip) and unpack it on your local computer.
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 https://github.com/friendica/friendica/issues?q=is%3Aopen+is%3Aissue+label%3A%22Junior+Jobs%22” 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 https://github.com/friendica/friendica or let us know in the development forum https://helpers.pyxis.uberspace.de/profile/developers.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation https://github.com/friendica/friendica/tree/develop/doc, the translation https://www.transifex.com/Friendica/friendica/ 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 https://helpers.pyxis.uberspace.de/profile/helpers with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun

In conversation Monday, 16-Oct-2017 05:36:14 EDT from pirati.ca permalink

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.