Show Navigation
Notices by Friendica News (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…
-
Wrapping up for the end-of-the-year? We too; and therefore we are happy to announce the release of Friendica “Dalmatian Bellflower” 2019.12.
This release bundles up some bug fixes, but mostly enhancements to existing features and adds some new ones as well. For a full list of changes, please have a look at the CHANGELOG file in the repository. For a short summery, the highlights are:
The titles of all the pull requests of the 2019.12 release summarized as word cloud. - The ACL dialogue introduced in the 2019.09 release on the new compose page for the frio theme was now adopted to all themes.
- The handling of reshares was made more native for the federated platforms and federation with Diaspora*, Mastodon, Pixelfed and Peertube was improved.
- The API was improved and got some new endpoints to improve the experience of using Friendica with mobile apps like Fedilab.
- Postings can now be pinned to your profile wall and
- if you like, you can connect to Discourse forums via email.
Thanks to all the people who have made this release possible!
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2018.09 release, please first update your Friendica instance to that version as there were several important changes in that version.
Please note, that we moved the shipped .htaccess
file to .htaccess-dist
in the 2019.01 version. Make sure that you have saved a copy of the file if you made any changes to it, so that you can copy the file from the backup after the upgrade.
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.
Furthermore, we raised the minimal requirements with the 2019.06 version to PHP 7. Before updating please ensure that you are using a supported PHP version on your server. We suggest PHP 7.2 or later.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better safe than sorry.
Using Git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to update the dependencies with composer as well.
cd friendica
git pull
bin/composer.phar install
cd addon
git pull
If you want to switch the branch (e.g. if you helped to test the release candidate) 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 2019.01 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 (tar.gz) please download the current version of the archive (friendica-full-2019.12.tar.gz and friendica-addons-2019.12.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 (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-2019.12
archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format in the 2019.03 version. 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” 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 have fun!
https://friendi.ca/2019/12/23/friendica-2019-12-released/
-
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…
-
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