Friendica is a decentralised communications platform that integrates social communication

Overview

Friendica Social Communications Server

Welcome to the free social web.

Friendica is a decentralised communications platform that integrates social communication. Our platform links to independent social projects and corporate services.

Our mission is to free friends, family and colleagues from data-harvesting corporations; we aim for social communication to be free and open, while flowing between any provider as easily as email does.

Friendica connects you effortlessly to a federated communications network of several thousand servers, with more than half a million user registrations. You can directly connect to anyone on Friendica, Mastodon, Diaspora, GnuSocial, Pleroma, or Hubzilla, regardless where each user profile is hosted.

With Friendica, you can also fully interact with anyone on Twitter, post on Facebook and receive any content on Tumblr, Wordpress or RSS. Friendica allows you to integrate most things on the web via a range of addons such as ITTT, Buffer; you will be able to easily control your own data as you decide.

Join today and get your Friendica profile!

Have a look at the installation documentation for further information about installing and using Friendica.

Friendica Screenshots

Frio theme in mobile browser Frio theme in mobile browser
Frio theme, mobile browser. Timeline and composer view.
Frio theme in desktop browser
Frio theme, desktop browser. Timeline view, contact info popped up, control menu open.
Frio theme in desktop browser
Frio theme, desktop browser. Menu open for controlling individual posts.
Frio theme in desktop browser
Frio theme, desktop browser. Profile view, notification menu open.
Frio theme in desktop browser
Number of new posts, in total and by group.
Frio theme in desktop browser
Calender with popup of event.
Frio theme default colour in standard browser on tablet
Notifications menu and private messages counter, standard browser on tablet.
Frio theme in desktop browser
Number of visible contacts, standard browser.
Frio theme in desktop browser
Network posts chronologically ordered, standard browser.
Vier theme in desktop browser
Vier theme, desktop browser. Public timeline view.
Vier theme in desktop browser
Vier theme, desktop browser. Community post displayed.

Endorsements

Comments
  • Move global functions from include/ to class methods in src/

    Move global functions from include/ to class methods in src/

    We already are having some files in /include that are containing classes that we could move without a problem to /src.

    This includes diaspora.php, dfrn.php and ostatus.php and possibly some more.

    Tracking document: https://ethercalc.org/friendica_classes

    Please update it with your planned changes.

    Per @MrPetovan

    So that everything is clear: in Model should only be static classes that interact with the DB with the same name as a database table. In Object should be all the support classes that don't interact with any database table and shouldn't have the same name as a database table.

    Remaining files:

    • [x] api.php (needs proper router first)
    • [x] conversation.php
    • [x] dba.php (covered by #5410)
    • [x] enotify.php
    • [x] items.php (#8880)
    • [x] security.php (#5946)
    • [x] text.php (#6042)
    Junior Jobs Enhancement 
    opened by annando 116
  • No accounts after DB update

    No accounts after DB update

    Hello,

    Since the last update, my - it seems - existing database problems have worsened.

    I have received feedback that the virtual table "category-view" is causing a problem. However, "bin/console dbstructure update -f" did not generate an error message.

    Since the update to version: 2021.04 / database: 1413/1369 I cannot log in anymore. The accounts seem to be untraceable.

    However, I still get no error message after entering "bin/console dbstructure update -f".

    Currently it should be about the following tables:

    post-user-view post-thread-user-view

    How can I solve this problem? Or rather, can I update the tables?

    opened by gravity-deleted 111
  • PHP Notices in PHP error log

    PHP Notices in PHP error log

    Friendica version you encountered the problem

    2018.08-dev

    Friendica source (git, zip)

    git

    PHP version

    PHP 7.0.30

    SQL version

    10.0.34-MariaDB

    I tried to filter my PHP log to get sorted and unique lines. Unfortunately I pulled today from develop. So maybe some entries are duplicates because the line numbers have changed.

    Here it comes: :-)

    Undefined index: account-type in .../src/Protocol/OStatus.php on line 1411
    Undefined index: addr in .../mod/message.php on line 491
    Undefined index: addr in .../src/Protocol/DFRN.php on line 745
    Undefined index: adjust in .../src/Model/Event.php on line 38
    Undefined index: adjust in .../src/Model/Event.php on line 43
    Undefined index: adjust in .../src/Model/Event.php on line 70
    Undefined index: adjust in .../src/Model/Event.php on line 76
    Undefined index: album in .../mod/videos.php on line 375
    Undefined index: album in .../mod/videos.php on line 385
    Undefined index: allow_api in .../addon/xmpp/xmpp.php on line 97
    Undefined index: attach in .../src/Protocol/OStatus.php on line 1375
    Undefined index: author-avatar in .../src/Protocol/Diaspora.php on line 3540
    Undefined index: author-name in .../src/Protocol/Diaspora.php on line 3540
    Undefined index: body in .../src/Protocol/OStatus.php on line 1166
    Undefined index: contact_allow in .../mod/events.php on line 136
    Undefined index: contact_deny in .../mod/events.php on line 138
    Undefined index: desc in .../src/Model/Event.php on line 81
    Undefined index: description in .../mod/parse_url.php on line 37
    Undefined index: finish in .../src/Model/Event.php on line 44
    Undefined index: frio_background_color in .../view/theme/frio/config.php on line 22
    Undefined index: frio_background_image in .../view/theme/frio/config.php on line 24
    Undefined index: frio_bg_image_option in .../view/theme/frio/config.php on line 25
    Undefined index: frio_contentbg_transp in .../view/theme/frio/config.php on line 23
    Undefined index: frio_link_color in .../view/theme/frio/config.php on line 21
    Undefined index: frio_nav_bg in .../view/theme/frio/config.php on line 19
    Undefined index: frio_nav_icon_color in .../view/theme/frio/config.php on line 20
    Undefined index: group_allow in .../mod/events.php on line 135
    Undefined index: group_deny in .../mod/events.php on line 137
    Undefined index: guid in .../src/Protocol/OStatus.php on line 1929
    Undefined index: hashtags in .../src/Object/Post.php on line 345
    Undefined index: host in .../src/Protocol/Diaspora.php on line 1271
    Undefined index: HTTP_IF_NONE_MATCH in .../mod/proxy.php on line 38
    Undefined index: language in .../include/enotify.php on line 31
    Undefined index: mentions in .../src/Object/Post.php on line 346
    Undefined index: name in .../src/Model/Profile.php on line 137
    Undefined index: name in .../src/Protocol/DFRN.php on line 743
    Undefined index: notify_flags in .../include/enotify.php on line 531
    Undefined index: page_flags in .../src/Content/Nav.php on line 189
    Undefined index: page-flags in .../src/Protocol/DFRN.php on line 2147
    Undefined index: page-flags in .../src/Protocol/DFRN.php on line 2154
    Undefined index: photo in .../src/Protocol/DFRN.php on line 755
    Undefined index: photo in .../src/Protocol/DFRN.php on line 763
    Undefined index: plink in .../src/Protocol/Diaspora.php on line 3541
    Undefined index: post-type in .../mod/editpost.php on line 114
    Undefined index: profile_uid in .../mod/display.php on line 301
    Undefined index: resource-id in .../mod/videos.php on line 379
    Undefined index: scheme in .../src/Protocol/Diaspora.php on line 1271
    Undefined index: source_link in .../include/enotify.php on line 580
    Undefined index: source_name in .../include/enotify.php on line 579
    Undefined index: source_photo in .../include/enotify.php on line 581
    Undefined index: superblock in .../addon/superblock/superblock.php on line 142
    Undefined index: tag in .../src/Model/Item.php on line 2787
    Undefined index: tag in .../src/Model/Item.php on line 2796
    Undefined index: tags in .../mod/parse_url.php on line 41
    Undefined index: tags in .../src/Object/Post.php on line 344
    Undefined index: title in .../mod/parse_url.php on line 33
    Undefined index: title in .../src/Protocol/OStatus.php on line 1920
    Undefined index: to_name in .../include/enotify.php on line 583
    Undefined index: uid in .../include/conversation.php on line 487
    Undefined index: uid in .../include/enotify.php on line 582
    Undefined index: uid in .../include/enotify.php on line 647
    Undefined index: uid in .../mod/display.php on line 297
    Undefined index: uid in .../mod/display.php on line 324
    Undefined index: uid in .../mod/display.php on line 326
    Undefined index: uid in .../mod/ping.php on line 111
    Undefined index: uid in .../src/Model/Profile.php on line 156
    Undefined index: uid in .../src/Object/Thread.php on line 66
    Undefined index: url in .../mod/proxy.php on line 360
    Undefined index: url in .../src/Model/User.php on line 733
    Undefined index: url in .../src/Protocol/DFRN.php on line 744
    Undefined index: url in .../src/Protocol/Diaspora.php on line 1391
    Undefined index: user in .../mod/events.php on line 38
    Undefined index: verb in .../src/Core/NotificationsManager.php on line 276
    Undefined index: wall in .../mod/editpost.php on line 113
    
    Bug 
    opened by AlfredSK 107
  • Red Circle Slash Image Everywhere

    Red Circle Slash Image Everywhere

    Randomly, but particularly after emptying browser cache, if I go to my network feed, or even someone's profile status page, any images they posted with friends-only permissions is replaced by a red circle. When I go to their Photos page, it doesn't show any of their friends-only photos to me. The problem goes away just as randomly, but is sometimes persistent. Frustrating problem overall.

    Bug UX 
    opened by miqrogroove 97
  • Extremely slow loading

    Extremely slow loading

    Im running the latest 2020.12-rc and updated one hour ago. Apart the login and first display of the first page of my timeline everything is completely slow.

    • When I try to open a notification, the post will be displayed after 5-10 Minutes
    • When I try to switch accounts it is nearly the same veeeeeeeery slow

    Everything seems to be very slow and the browser is loading "forever" after I logged in.

    The server itself is idling and other applications on that server are functioning completely normal an fast.

    • Server has no load
    • Network is ok

    Do you experience the same? My Friendica server is at the moment not usable with wait times between 3-10 minutes after each click.

    Bug Performance 
    opened by hoergen 88
  • Move configuration to config/

    Move configuration to config/

    Closes #4889

    I'm at it again with a massive PR to move Friendica's confiiguration out of the .htconfig.php file and into the 20th century.

    This PR is in line with my previous efforts to centralize initialization into the \Friendica\App class.

    Instead of including .htconfig.php every time a script needs to access the DB, the configuration and database loading is done when creating a new App instance.

    I finally opted for the INI format that PHP natively supports but I'm planning on using the current plain PHP structure when I move the DBStructure definition out of the DBStructure class into the same config/ folder.

    Enhancement 
    opened by MrPetovan 82
  • Photos uploaded in comments get no permissions

    Photos uploaded in comments get no permissions

    Expected behavior

    • I make a public comment to a public post.
    • I attach a photo.
    • The photo is public.

    Actual behavior

    • The photo has no permissions.

    If I go to the photo and click Permissions, it says it is public, and if I submit at that point, it becomes actually public.

    Looks like the image does not get any permission set - not even the public one. It looks like 'public' but in fact it is somehow set to 'none'.

    https://libranet.de/display/0b6b25a8-125e-5f4d-0f94-670912314070

    Friendica version you encountered the problem

    Friendica, version 2020.03-dev that is running at the web location https://libranet.de. The database version is 1335, the post update version is 1329.

    Bug 
    opened by clacke 76
  • Explicit mentions: Make the Friendica display user-controlled

    Explicit mentions: Make the Friendica display user-controlled

    Follow-up to #6541

    We need to explicitly display the mentions in the post body to networks that are used to it to avoid confusions, but we don't need to systematically display them in the comment boxes.

    We should add an additional feature setting to allow admins to enabled/disable/lock displaying mentions in comment boxes, and for users to be able to enable/disable it for finer mentioning control.

    Thanks @rebeka-catalina for the report, see https://forum.friendi.ca/display/fd59d1fe-175c-50a9-e97b-66c395538401

    Steps:

    • [x] Add implicit mentions to outgoing Diaspora post body. (#6614)
    • [x] Add implicit mentions to outgoing ActivityPub post body. (#6614)
    • [x] Remove implicit mentions from incoming ActivityPub post body. (#6614)
    • [x] Remove implicit mentions from incoming ActivityPub post tags. (#6614)
    • [x] Add user config to enable explicit mentions in the comment box. (#6614)
    • [x] Improve the top-level comment box behavior when there already are replies in the thread. (#6660)
    UX Enhancement 
    opened by MrPetovan 71
  • Add ActivityPub support to connect with Mastodon

    Add ActivityPub support to connect with Mastodon

    Mastodon has announced that they will drop OStatus in the future to foxus solely on ActivityPub that they were among the first projects to implement.

    This makes the Mastodon implementation the de facto reference ActivityPub implementation for microblogging.

    While this task is related to #4592, there's a significant chance that implementation to connect with both services will heavily diverge, hence this new separate issue.

    Thanks to @Lionirdeadman for the reminder.

    New Feature Federation 
    opened by MrPetovan 69
  • Queue filling up

    Queue filling up

    Expected behavior

    The "Message queues" should be processed and at least the open tasks number should be close to 0.

    Actual behavior

    The "Message queues" are filling up, currently this are the Numbers: Message queues: 8267 - 3628

    The first number ist constantly increasing, the second is going up and down but not below 2000.

    Steps to reproduce the problem

    Maybe enable "direct relay" function (might be one reason for this to happen, function enabled yesterday).

    Friendica version you encountered the problem

    2018-05-dev

    (I thought I did a pull before, but unfortunately I didn't, so this is the latest "git pull" output) remote: Counting objects: 11, done. remote: Compressing objects: 100% (2/2), done. remote: Total 11 (delta 6), reused 7 (delta 6), pack-reused 3 Unpacking objects: 100% (11/11), done. From https://github.com/friendica/friendica 48f849205..7f0bd63b7 develop -> origin/develop Updating 48f849205..7f0bd63b7 Fast-forward Vagrantfile | 2 +- {util => bin/dev}/friendica-to-smarty-tpl.py | 0 {util => bin/dev}/make_credits.py | 0 {util => bin/dev}/minifyjs.sh | 0 {util => bin/dev}/updatetpl.py | 0 {util => bin/dev}/vagrant_provision.sh | 2 +- {util => bin/dev}/vagrant_vhost.sh | 0 7 files changed, 2 insertions(+), 2 deletions(-) rename {util => bin/dev}/friendica-to-smarty-tpl.py (100%) rename {util => bin/dev}/make_credits.py (100%) rename {util => bin/dev}/minifyjs.sh (100%) rename {util => bin/dev}/updatetpl.py (100%) rename {util => bin/dev}/vagrant_provision.sh (98%) rename {util => bin/dev}/vagrant_vhost.sh (100%) Loading composer repositories with package information Installing dependencies (including require-dev) from lock file Nothing to install or update Generating optimized autoload files Already up to date.

    Friendica source (git, zip)

    git

    PHP version

    PHP Version => 7.2.4

    SQL version

    mysql Ver 15.1 Distrib 10.1.31-MariaDB, for Linux (x86_64) using readline 5.1

    Edit

    1. The worker is running fine, there is almost no load on the system, ps aux returns 30 processes of the worker, I increased this from 20 in the hope to have the queue decreasing faster.
    Sup­port Request 
    opened by utzer 67
  • Community page: initial loading super slow - DB query running for 1.5 minutes

    Community page: initial loading super slow - DB query running for 1.5 minutes

    • [X] I have searched open and closed issues for duplicates

    Bug Description

    The current DB stucture in develop is producing some very slow queries. The one that is extremely slow is the query for loading the content of the community pages. It takes approx. 1.5 - 2 minutes until the page is completely loaded.

    Subsequent pages (content) loaded via infinite scroll are pretty fast. When I scroll down the next items are loaded in approx. 1 second.

    The query:

    # Thread_id: 613292  Schema: friendica  QC_hit: No
    # Query_time: 85.822263  Lock_time: 0.000050  Rows_sent: 25  Rows_examined: 10194724
    # Rows_affected: 0  Bytes_sent: 1815
    # Tmp_tables: 8  Tmp_disk_tables: 0  Tmp_table_sizes: 1269880
    # Full_scan: Yes  Full_join: No  Tmp_table: Yes  Tmp_table_on_disk: No
    # Filesort: No  Filesort_on_disk: No  Merge_passes: 0  Priority_queue: No
    SET timestamp=1612607182;
    SELECT `uri-id`, `commented`, `author-link` FROM `post-thread-view` WHERE (`uid` = 0 AND `private` = 0 AND `visible` AND NOT `deleted` AND NOT `moderated` AND NOT `author-blocked` AND NOT `owner-blocked` AND (NOT `causer-blocked` OR `causer-id` = 0) AND NOT `contact-blocked` AND ((NOT `contact-readonly` AND NOT `contact-pending` AND (`contact-rel` IN (2, 3))) OR `self` OR `gravity` != 0 OR `contact-uid` = 0) AND NOT EXISTS (SELECT `uri-id` FROM `post-user` WHERE `hidden` AND `uri-id` = `post-thread-view`.`uri-id` AND `uid` = 0) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `author-id` AND `blocked`) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `owner-id` AND `blocked`) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `author-id` AND `ignored` AND `gravity` = 0) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `owner-id` AND `ignored` AND `gravity` = 0)) ORDER BY `commented` DESC LIMIT 25;
    

    Explain the query:

    MariaDB [friendica]> explain SELECT `uri-id`, `commented`, `author-link` FROM `post-thread-view` WHERE (`uid` = 0 AND `private` = 0 AND `visible` AND NOT `deleted` AND NOT `moderated` AND NOT `author-blocked` AND NOT `owner-blocked` AND (NOT `causer-blocked` OR `causer-id` = 0) AND NOT `contact-blocked` AND ((NOT `contact-readonly` AND NOT `contact-pending` AND (`contact-rel` IN (2, 3))) OR `self` OR `gravity` != 0 OR `contact-uid` = 0) AND NOT EXISTS (SELECT `uri-id` FROM `post-user` WHERE `hidden` AND `uri-id` = `post-thread-view`.`uri-id` AND `uid` = 0) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `author-id` AND `blocked`) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `owner-id` AND `blocked`) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `author-id` AND `ignored` AND `gravity` = 0) AND NOT EXISTS (SELECT `cid` FROM `user-contact` WHERE `uid` = 0 AND `cid` = `owner-id` AND `ignored` AND `gravity` = 0)) ORDER BY `commented` DESC LIMIT 25;
    +------+--------------------+--------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+---------+---------------------------------------+----------+-------------+
    | id   | select_type        | table              | type   | possible_keys                                                                                                                                                                                                                                                      | key        | key_len | ref                                   | rows     | Extra       |
    +------+--------------------+--------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+---------+---------------------------------------+----------+-------------+
    |    1 | PRIMARY            | post-thread        | index  | PRIMARY,owner-id,author-id,causer-id                                                                                                                                                                                                                               | commented  | 5       | NULL                                  |       25 | Using where |
    |    1 | PRIMARY            | post-thread-user   | eq_ref | PRIMARY,uid_wall,uid_pinned,uri-id                                                                                                                                                                                                                                 | PRIMARY    | 7       | const,friendica.post-thread.uri-id    |        1 | Using index |
    |    1 | PRIMARY            | post-user          | ref    | uri-id,contact-id                                                                                                                                                                                                                                                  | uri-id     | 4       | friendica.post-thread.uri-id          |        1 |             |
    |    1 | PRIMARY            | item               | ref    | parent,uid_id,deleted_changed,uid_wall_changed,uid_eventid,uid_unseen_contactid,uid_contactid_id,uid_network_received,uid_network_commented,uid_commented,uid_thrparent,uid_parenturi,uid_uri,uid_received,uid_contactid_received,uri-id,uid_unseen_wall,causer-id | uri-id     | 5       | friendica.post-thread.uri-id          |        1 | Using where |
    |    1 | PRIMARY            | contact            | eq_ref | PRIMARY,self_uid,pending_uid,blocked_uid,uid_rel_network_poll,uid_network_batch,uid_name,uid_lastitem,uid_network_self_lastupdate                                                                                                                                  | PRIMARY    | 4       | friendica.post-user.contact-id        |        1 | Using where |
    |    1 | PRIMARY            | author             | eq_ref | PRIMARY,blocked_uid                                                                                                                                                                                                                                                | PRIMARY    | 4       | friendica.post-thread.author-id       |        1 | Using where |
    |    1 | PRIMARY            | owner              | eq_ref | PRIMARY,blocked_uid                                                                                                                                                                                                                                                | PRIMARY    | 4       | friendica.post-thread.owner-id        |        1 | Using where |
    |    1 | PRIMARY            | causer             | eq_ref | PRIMARY,blocked_uid                                                                                                                                                                                                                                                | PRIMARY    | 4       | friendica.post-thread.causer-id       |        1 | Using where |
    |    1 | PRIMARY            | parent-item        | eq_ref | PRIMARY,authorid_received                                                                                                                                                                                                                                          | PRIMARY    | 4       | friendica.item.parent                 |        1 |             |
    |    1 | PRIMARY            | parent-item-author | eq_ref | PRIMARY                                                                                                                                                                                                                                                            | PRIMARY    | 4       | friendica.parent-item.author-id       |        1 | Using index |
    |    6 | DEPENDENT SUBQUERY | user-contact       | eq_ref | PRIMARY,cid                                                                                                                                                                                                                                                        | PRIMARY    | 7       | const,friendica.post-thread.owner-id  |        1 | Using where |
    |    5 | DEPENDENT SUBQUERY | user-contact       | eq_ref | PRIMARY,cid                                                                                                                                                                                                                                                        | PRIMARY    | 7       | const,friendica.post-thread.author-id |        1 | Using where |
    |    4 | MATERIALIZED       | user-contact       | ref    | PRIMARY,cid                                                                                                                                                                                                                                                        | PRIMARY    | 3       | const                                 |        1 | Using where |
    |    3 | MATERIALIZED       | user-contact       | ref    | PRIMARY,cid                                                                                                                                                                                                                                                        | PRIMARY    | 3       | const                                 |        1 | Using where |
    |    2 | MATERIALIZED       | post-user          | ref    | uid_uri-id,uri-id                                                                                                                                                                                                                                                  | uid_uri-id | 3       | const                                 | 13342874 | Using where |
    +------+--------------------+--------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+---------+---------------------------------------+----------+-------------+
    

    Steps to Reproduce

    1. try to go to the (global) community page
    2. experience the extreme slowness
    3. have a look at you slow queries log file

    Actual Result: Initial page loading takes 1.5 - 2 minutes

    Expected Result: Page should be loaded in 1.5 - 2 seconds :-)

    Platform Info

    Friendica Version: 2021.03-dev - dbstructure 1398/1398 - postupdate 1384/1384

    Friendica Source: git

    PHP version: 7.4

    SQL version: 10.3 MariaDB

    Bug 
    opened by AlfredSK 66
  • How to reduce database size

    How to reduce database size

    I have been running my single user Friendica instance for a few months on a shared hoster without any major performance issues.

    My hoster contacted me and informed me that the database size is exceeding the allocated quota. I am at 12GB currently. Now I am looking for ways to reduce the database size but have not been able to find any useful how-tos online.

    My storage has been set to file system from the beginning. Under Administration>Page>Performance I reduced all lifetimes to 15 days. As I understood my cronjob would then optimize the data in the database accordingly but this did not help yet

    Here is my cronjob: */5 * * * * cd /var/www/virtual/$USER/html && php bin/worker.php > /dev/null 2>&1

    Please help me find a way to reduce the database size. Thank you Rick

    Sup­port Request 
    opened by rickgardner077 4
  • Add /about alias for /friendica page

    Add /about alias for /friendica page

    It is well-known that Mastodon servers have "about server" page /about with server rules, admin contacts and list of blocked servers and users go there to check this information.

    Friendica has similar /friendica page but it is not intuitive for someone unfamiliar with Friendica to find it, especially if they just try to do it the usual way by adding /about to the server name. So it would be minor enhancement to make this same page also accessible with /about path. Even better if now obsolete but still well-remembered /about/more path also leads there (on Mastodon /about/more redirects to /about).

    New Feature Junior Jobs 
    opened by SpcCw 1
  • Double notifications when

    Double notifications when "watched" contact re-shares posts

    Not sure if this is a bug but it feels like undesired behaviour: Friendica 2022-10, loma.ml. Setup: I do have some users for which I have set up to be notified if they post anything new. Outcome, right now: If any of these users re-shares a post by someone else, I receive two notifications (both in Mastodon-compatible apps and in the web user interface), one about the user that re-shared the post (which is a person I am following) and one for the user that originally posted this. This is a bit surprising, and it would suffice to only have the "reshare" notification.

    Bug 
    opened by kr428 2
  • [Mastodon API] Header image not applied by clients

    [Mastodon API] Header image not applied by clients

    Followup to https://github.com/friendica/friendica/issues/12233 (thanks for addressing that issue and can confirm: Fedilab is no longer crashing when trying to set header image).

    Now when trying to set header image in Fedilab or Tusky, the apps allow image selection, applying the change results in confirmation message, but the image is never set.

    Not sure how to provide more details or debug further - no error message is shown.

    Bug API 
    opened by foss- 0
  • 404 error when making a search

    404 error when making a search

    Hello,

    I'm a new Friendica user and I set up my own Friendica instance. However, after setup, I'm encountering an issue when I'm trying to find an user (i.e., my old profile on Mastodon). Whatever I type in the search box, when submitting I get a 404 error page with this error:

    Exception produite dans /var/www/html/src/Module/HTTPException/PageNotFound.php:49
    Stack trace:
    #0 /var/www/html/src/BaseModule.php(244): Friendica\Module\HTTPException\PageNotFound->content()
    #1 /var/www/html/src/Module/HTTPException/PageNotFound.php(80): Friendica\BaseModule->run()
    #2 /var/www/html/src/App.php(719): Friendica\Module\HTTPException\PageNotFound->run()
    #3 /var/www/html/index.php(44): Friendica\App->runFrontend()
    #4 {main}
    

    And the URL of the search page is (redacted host): /search?q=%40cvillisek89%40noc.social

    I'm not sure whether it is a bug or an issue related to my set-up... I'm using Nginx on Debian, with the rewrite rules provided in the config example on Github. I also disabled cgi fixpath in the PHP FPM config. I don't know where it comes from, as I'm not seeing this error in neither nginx nor php-fpm logs.

    Is it a bug?

    Sup­port Request 
    opened by villisek 1
Releases(2022.10)
  • 2022.10(Oct 14, 2022)

    It took a bit longer then expected, but we are very happy to announce the availability of the new stable version of Friendica the "Giant Rhubarb" 2022.10.

    Kudos to everyone who made this release possible by their contributions!

    In addition to fixing bugs and improving the performance of Friendica, the highlights of the changes since the 2022.06 release are

    • the Gàidhlig translation was added to the repository, thanks to the work of @gunchleoc,
    • node admins using relays can now configure languages of postings arriving over the relay that should be discarded automatically,
    • the 2FA login has been reworked, and
    • it was discovered that using the Blowfish algorithm is implying a password length limit of 72 characters. Should you use a longer password, this will be transparently dealt with upon your next login.

    For details, please the CHANGELOG file in the repository.

    Since version 2022.06 the lowest required PHP version Friendica needs on the server was raised to PHP 7.3 and PHP 8.0 is supported.

    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 Twitter.

    How to Update

    Updating from old Friendica versions

    If you are updating from an older version than the 2022.06 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 2022.10 release would be

    cd friendica
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git pull
    

    If you want to use a different branch than the stable one, you need to fetch and checkout the branch before your perform the git pull.

    Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

    Using the Archive Files

    If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2022.10.tar.gz (sha256) and friendica-addons 2022.10.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-2022.10 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

    Regarding the update process none as of writing.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2022.06(Jun 11, 2022)

    We are very happy to announce the avail-ability of the new stable version of Friendica. With this release the "Siberian Iris" cycle is closed and we start a new one, the "Giant Rhubarb". 20 people have contributed directly to the code of Friendica "Giant Rhubarb" over the last year, committing over 2500 pull requests fixing nearly 200 numbered issues and adding new features.

    Kudos to everyone who made this release possible by their contributions!

    In addition to fixing bugs and improving the performance of Friendica, the highlights of the changes of the last year since the first release of the "Siberian Iris" are

    • The UI translations for Arabic and Dansk was added and Friendica supports now left-to-right languages generally better then before.
    • We have two new addons (S3 and WebDAV) to use additional storage back-ends for storing the media files.
    • The Mastodon compatible API was improved, you now should be able to use most Mastodon clients with your Friendica account.
    • The federation with Diaspora*, Mastodon, PeerTube, Pleroma and Lemmy was enhanced.
    • The themes (Frio and vier) got some touch ups, and the screen-reader support of Frio was improved.

    For details, please the CHANGELOG file in the repository.

    The lowest required PHP version Friendica needs on the server was raised to PHP 7.3 and PHP 8.0 is supported.

    Breaking Change If you are running a custom addon, please note that the 2022.06 release does a breaking change removing the hooks settings_form and settings_post. Your addon should use the addon_settings hook instead.

    What is Friendica

    Friendica is a decentralised communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.

    How to Update

    Updating from old Friendica versions

    If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.

    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 2022.06 release would be

    cd friendica
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git pull
    

    If you want to use a different branch then 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-2022.06.tar.gz (sha256) and friendica-addons 2022.06.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-2022.06 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

    Regarding the update process none as of writing.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2022.03(Mar 7, 2022)

    We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2022.03. This release is mainly a bug fixing release with breaking changes. Notably these are:

    • The closing of a bug in the recipient selector for private messages. The bug could result in direct messages being send to the wrong person from the contact list of the user.
    • The rework of how messages in private forums are delivered. Those are now as well distributed using the ActivityPub protocol. After a node is updated, communication in private forums is not longer possible with older versions of Friendica.
    • The StatusNet compatible API now uses the same ID as the Mastodon compatible API. Users of clients using the StatusNet compatible API (such as Friendiqa) need to remove the account from the client and re-register it.

    For a detailed overview of the changes, please have a look at the CHANGELOG.

    How to Update

    Updating from old Friendica versions

    If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.

    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 2022.03 release would be

    cd friendica
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git pull
    

    If you want to use a different branch then the stable one, you need to 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-2022.03.tar.gz (sha256) and friendica-addons 2022.03.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-2022.03 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

    Regarding the update process none as of writing.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2022.02(Feb 6, 2022)

    We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2022.02. This is the first release containing the work of the Arabic translation team - thanks a lot for your work! Other highlights of the release are

    • The video tab was removed from the profile, in exchange Friendica profiles now have a media tab, showing postings that contain more then just text.
    • An addon to allow usage of WebDAV for the storage back-end has been added.

    For a detailed overview of the changes, please have a look at the CHANGELOG.

    How to Update

    Please note: With this release the minimal PHP version that Friendica requires is PHP 7.3 and later. Known issues with PHP 8 are collected in the issue tracker at github, though Friendica seems to work fine with PHP 8 now.

    Deprecation Warning: Some old and unmaintained addons have been removed from the core addon repository. These addons are: blogger, buffer, jappixmini, notimeline, xmpp.

    Updating from old Friendica versions

    If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.

    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 2021.09 to the 2021.12 release candidate, so hopefully you will have a smooth transition.

    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 2022.02 release would be

    cd friendica
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git pull
    

    If you want to use a different branch then the stable one, you need to 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-2022.02.tar.gz (sha256) and friendica-addons 2022.02.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-2022.02 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

    • After the update please make sure that the directory vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer is write-able by your web 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” 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!

    Source code(tar.gz)
    Source code(zip)
  • 2021.09(Sep 25, 2021)

    The summer sprint is over and we are happy to announce the availability of the new stable release of Friendica "Siberian Iris" 2021.09. It contains more then 160 pull requests from seven contributors and updates to several language packages from the translation teams.

    For a detailed overview of the changes, please have a look at the CHANGELOG. The highlights of the release are

    How to Update

    Please note: With the release of 2021.09 Friendica does require at least PHP version 7.2 or above. Known issues with PHP 8 are collected in the issue tracker at github.

    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.

    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 2021.07 to the 2021.09 release candidate, so hopefully you will have a smooth transition.

    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 2021.09 release would be

    cd friendica
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git pull
    

    If you want to use a different branch then the stable one, you need to 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-2021.09.tar.gz (sha256) and friendica-addons 2021.09.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-2021.09 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

    None at the time of writing.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2021.07(Jul 4, 2021)

    We are very happy to announce the availability of the new stable release of Friendica "Siberian Iris" 2021.07. This release contains 219 pull requests from ten contributors and the work of the translation teams. While fixing some problems identified, we have added some nice features

    • support for right-to-left languages was added,
    • the API was expanded to have Mastodon compatible endpoints and
    • an addon was added to support SAML services like keycloak for login.

    For a detailed overview of the changes, please have a look at the CHANGELOG.

    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.

    In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

    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 2021.04 to the 2021.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 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.

    cd friendica
    git fetch
    git checkout BRANCH
    git fetch
    bin/composer.phar install --no-dev
    cd addon
    git fetch
    git checkout BRANCH
    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 (friendica-full-2021.07.tar.gz and friendica-addons 2021.07.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-2021.07 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

    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 for a workaround.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2021.04(Apr 26, 2021)

    with a slight delay, we are happy to announce the availability of the new stable version of the Friendica communications server: Friendica Siberian Iris 2021.04.

    This is mostly a bug fixing release, stabilizing the new features we introduced over the Red Hot Poker cycle, but also finishing some long time restructuring work on the database structure, which results in a greatly improved performance of Friendica. This release bundles 196 pull requests fixing 53 filed issues. For a detailed overview of the changes, please have a look at the CHANGELOG, some of the highlights

    • The reworking of how items are stored in the database was finished, which results in a great improvement of Friendicas performance. Please note that the needed upgrade might take hours depending of your database size.
    • Admins can now block tags from the trending tag widget.
    • We removed the Flash based addons from the addon repository.

    And a heads up for developers, we moved some endpoints in the API to normalize the endpoints.

    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.

    In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be necessary.

    Pre-Update Procedures

    Ensure that the last backup of your Friendica installation was done recently. Despite the long duration of the database upgrade we had no reports of unaddressed problems during the RC phase.

    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

    Important: We removed the master branch and are using the stable branch instead.

    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.

    cd friendica
    git fetch
    git checkout stable
    git pull
    bin/composer.phar install --no-dev
    cd addon
    git fetch
    git checkout stable
    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 (friendica-full-2021.04.tar.gz and friendica-addons 2021.04.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-2021.01 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

    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 for a workaround.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2021.01(Jan 4, 2021)

    and a happy new year dear reader. Not quiet in time for the holidays, but we are very happy to announce the availability of the latest stable version of the Friendica communications server which bundles up some 270 pull requests closing 86 numbered issues. For a detailed overview of the changes, please have a look at the CHANGELOG, some of the highlights

    • Thanks to Balázs Úr Friendica is now available in Hungarian. The German, Italian and Russian translation was updated as well.
    • hansw-nlo made us aware of some places where user input was not properly escaped. For security reasons we urge you to upgrade to the new release. See Issue 9538 for details.
    • The performance of the background process was further improved. For nodes running on very limited hardware, this might cause some problems. If you are running Friendica on such hardware please be aware that you might need to adjust settings like the worker_cooldown in your configuration file.
    • Friendica is now able to directly re-share a posting in addition to the manual cite and re-share we are used to. Additionally the native re-sharing mechanisms of the different protocols supported by Friendica got improved and re-shared postings are now displayed on the users profile page.

    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.

    In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

    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.09 to the 2020.12 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

    Important: We removed the master branch and are using the stable branch instead.

    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.

    cd friendica
    git fetch
    git checkout BRANCH
    bin/composer.phar install --no-dev
    cd addon
    git fetch
    git checkout BRANCH
    

    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 (friendica-full-2021.01.tar.gz and friendica-addons 2021.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 (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-2021.01 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

    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 for a workaround.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2020.09-1(Sep 24, 2020)

    During the RC phase of the 2020.09 release of Friendica a problem during sending out notification mails was not observed by the testers, but only reported after the release. Therefore we release now the 2020.09-1 hotfix release which will re-enable those mails.

    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.

    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.07 to the 2020.09 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

    Important: We are removing the master branch and are using the stable branch instead.

    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.

    cd friendica
    git fetch
    git checkout BRANCH
    bin/composer.phar install --no-dev
    cd addon
    git fetch
    git checkout BRANCH
    

    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 (friendica-full-2020.09-1.tar.gz and friendica-addons 2020.09-1.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-2020.09 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

    If you are using lighttpd to serve your Friendica node the boolean AND operator for the full text search seems not to be working at the moment.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2020.09(Sep 20, 2020)

    We are happy to announce the availability of Friendica 2020.09, wrapping up the work over the summer. It bundles some exciting new features and enhancements with numerous fixes along the way.

    This release is composed of 230 pull requests to the development branch, that closed 65 numbered tickets and enhanced several aspects of Friendica and the communication with other projects within the Fediverse. For a full reference, please have a look at the CHANGELOG file, some important things are worth highlighting here:

    • The speed of the full text search was enhanced significantly. If you had disabled it before, please check it out now and let us know if it works for you as we are considering to remove the option to disable it in a future release.
    • The themes got some updates. Among other things the way how a re-share is displayed. If you like the old display style better you'll find an option in the user settings to switch back.
    • Some time ago we did a user voting about which additional features should be handled in a unified way on all Friendica instances. The last of these items are now reworked. One of these is that all public calendar entries are now available as iCAL file from your profile.
    • Friendica is now supporting Activity Pub relay server. For more information please have a look at this forum thread

    Additionally this release contains a fix for a problem that Roger Meyer discovered in the processing of Activity Pub messages. We encourage all Friendica admins to update their nodes to the 2020.09 release to prevent problems arising from this. Thanks to Roger to report the issue!

    If you are using PHP version 7.0 there is currently a problem with one of the dependencies of Friendica. Please see this forum thread for more information.

    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.

    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.07 to the 2020.09 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

    Important: We are removing the master branch and are using the stable branch instead.

    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 fetch
    git checkout BRANCH
    bin/composer.phar install --no-dev
    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 (friendica-full-2020.09.tar.gz and friendica-addons 2020.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 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.09 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

    If you are using lighttpd to serve your Friendica node the boolean AND operator for the full text search seems not to be working at the moment.

    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!

    Source code(tar.gz)
    Source code(zip)
  • 2020.07-1(Sep 8, 2020)

    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 (friendica-full-2020.07-1) 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” 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 again Roger Meyer to make us aware of this problem!

    Source code(tar.gz)
    Source code(zip)
  • 2020.07(Jul 12, 2020)

    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 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 and this article at stackoverflow 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 cleanup-friendica script by ingoj to assist Friendica node admins and help with forgotten or dead accounts.

    If you are using PHP version 7.0 there is currently a problem with one of the dependencies of Friendica. Please see this forum thread for more information.

    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.

    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

    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 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 (friendica-full-2020.07.tar.gz and friendica-addons 2020.07.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-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.

    Known Issues

    After the release it was reported, that one of the dependencies of Friendica is currently not compatible to PHP 7.0, although claiming otherwise. If you are using this version of PHP and want to install Friendica 2020.07 you have to edit the source code slight.y. For more information, see the forum thread about the problem.

    If you are using MySQL there is an issue under investigation you should be aware of. This issue affects only users of MySQL, users of MariaDB have not reported this issue.

    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!

    Source code(tar.gz)
    Source code(zip)
    friendica-full-2020.07.tar.gz(30.38 MB)
  • 2020.03(Mar 30, 2020)

    We are happy to announce the avail-ability of Friendica "Red Hot Poker" 2020.03!

    Thanks to all the helpers during the RC phase to polish some corners of the release. Almost 400 tickets went into this release according to the milestone, closing something around 90 numbered issues and some unnumbered as well. But along all these fixes we also introduced some new features and revamped some aspects of your daily life with Friendica. For a complete list of changes, please have a look into the CHANGELOG, here are some of the highlights:

    • We adopted the "audio" type for ActivityPub postings and are now federating with Funkwhale.
    • 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.

    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 had some reports about problems with the profile field migration. All of these should be fixed, but better safe than sorry.

    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.

    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-2020.03.tar.gz and friendica-addons-2020.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 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.

    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.

    Please note, that some of the changes to the database structure will take some time (hours)) 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” 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!

    Source code(tar.gz)
    Source code(zip)
  • 2019.12(Dec 23, 2019)

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

    Source code(tar.gz)
    Source code(zip)
  • 2019.09(Sep 29, 2019)

    Friendica 2019.09 released

    We are proud to release the new version of Friendica 'Dalmatian Bellflower' 2019.09. As usual this release contains many bug fixes (we closed some 60 issues from the list) and code enhancements alongside of some new features. Some highlights are:

    • A Japanese translation was added to the Friendica core and some addons.
    • The two factor authorisation got improved. If you are using client apps, those now need a separate password set in the user configuration.
    • One can now search for the URL of any public ActivityPub posting to interact with the posting. You need to copy the postings address and paste it into the search field.
    • Users of the frio theme can now choose to use a separate compose page instead of the modal dialog.
    • Admins can now block servers based on URL patterns and enable a trending tags widget for the community page.

    for a complete overview please see the CANGELOG file.

    Many thanks to everyone who made this release possible. <3

    Known Issues

    One of the bug fixes that was applied in this release will cause old contact requests that were discarded initially to reappear. Users will have to reevaluate the request. We are sorry for the inconvenience this may cause to you and your users.

    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 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 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.09.tar.gz and friendica-addons-2019.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 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.09 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!

    Source code(tar.gz)
    Source code(zip)
  • 2019.06(Jun 23, 2019)

    Friendica 2019.06 Released

    Thanks everyone who contributed, be it directly by committing patches or new features, doing translations or reporting issues.

    The Tazmans Flax-lily in a word cloud from the titles of the commit messages

    And now, we happily announce the availability of Friendica 2019.06. It contains many bug fixes, enhancements of existing functionality and some new features. The most noteworthy changes since the last release in March are:

    • Added native two-factor authentication
    • Added reshare counts
    • Added mascot to error pages (thanks to @lostinlight)
    • Moved Friendica private message and contact request to ActivityPub

    You can find a complete overview of the changes in the CHANGELOG file.

    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 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 safe than sorry.

    With this release we raised the hard requirements to PHP 7. If you are still using PHP 5.6+, this version won't work anymore on your system and we urge you to upgrade to PHP 7.1 at least.

    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 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 (zip or tar.gz) please download the current version of the archive (friendica-full-2019.06.zip and friendica-addons-2019.06.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.06 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!

    Source code(tar.gz)
    Source code(zip)
  • 2019.04(Apr 28, 2019)

    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 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 frientica-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.

    Source code(tar.gz)
    Source code(zip)
  • 2019.03(Mar 22, 2019)

    Friendica 2019.03 "Dalmatian Bellflower" Released

    A year of Friendica with The Tazmans Flax-lily. Thanks everyone who contributed, be it directly by commiting patches or new features, doing translations or reporting issues.

    The Tazmans Flax-lily in a word cloud from the titles of the commit messages

    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 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 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 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 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 (friendica-full-2019.03.tar.gz and friendica-addons-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 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.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” 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!

    Source code(tar.gz)
    Source code(zip)
  • 2019.01(Jan 21, 2019)

    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 CHANGELOG file.

    Most noteworthy of these changes are:

    • Friendica does now natively support ActivityPub (AP) 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 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 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.

    Please note that Friendica now requires MySQL version 5.6+ or compatible (e.g. MariaDB 10.0.5). Please make sure, that your systems meets this new requirement.

    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 (friendica-full-2019.01.tar.bz2 [or tar.gz] and friendica-addons-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.

    Known Problems

    Update 2019-01-22: Some of the early adopters have discovered the following issues, that went unnoticed during the RC phase.

    • Sometimes the update process of the database seems to get stuck. If you notice high LOAD on your system and MySQL active processes in the process list that seem to cause the LOAD, please issue the following command from the base of your Friendica installation on the CLI.

        bin/console.php dbstructure update
      
    • The config update guide seems not to be shown in the admin panel. As mentioned above, both old config formats are still supported, so no need to hurry. But if you are looking for the guide to migrate your config file format to the new one, please see here: help/Config.

    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 again everyone who helped making this release possible and have fun!

    Source code(tar.gz)
    Source code(zip)
    friendica-full-2019.01.tar.bz2(20.63 MB)
  • 2018.09(Oct 4, 2018)

    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 CHANGELOG file for the complete overview of the changes. Here just a short list of the noteworthy changes since the 2018.05 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 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 addon 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 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) 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 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 (friendica-full-2018.09.tar.gz and friendica-addons-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 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:

    • 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” 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!

    Source code(tar.gz)
    Source code(zip)
  • 2018.05(Jun 1, 2018)

    If you don't want to clone the repository but use an archive file to download Friendica, please use the friendica-full-2018.05.tar.gz file and not the automatically generated archives. The full archive does also include the dependencies. If you downloaded one of the other archives, either download the full archive or run bin/composer.phar install --no-dev at the CLI from the base of your Friendica directory.


    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.
    • As libravatar is closing their service we have added a new alternative to the gravatar service based on David Revoy's 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 deprecated-themes repository.

    For a list of further changes, please have a look at the CHANGELOG file.

    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 (friendica-full-2018.05.tar.gz and friendica-addons-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 via composer as well.

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

    Source code(tar.gz)
    Source code(zip)
  • 3.6(Mar 23, 2018)

    The year started with sad news that Tony Baldwin passed away January 6th. Tony was an early member of the Friendica/RedMatrix/Hubzilla community who contributed ideas, addons, themes and utility tools. He was a great spirit among the FLOSS people, an artist, a translator, an interpreter and a great friend who is deeply missed.

    This release is dedicated to the memory of Tony "tazman" Baldwin.

    With no further ado, we'd like to present to you Friendica 3.6 The Tazmans Flax-​lily.

    Noteworthy Changes

    It took a long while this time for the developers find the opportunity to say now is the right time. Initially we wanted to have the release after last years hackathon, but then the big adventure of reorganising the code was started and that took some time. But the long wait was worth it, the code got cleaner and faster.

    Some things we want to highlight are:

    • You can now interact with postings on the community page, even if you are not connected with the author.
    • Forums can now be addressed with an !, e.g. !helpers. The ACL dialog does this automatically when you select a forum as recipient and has the forums listed separately from user groups and regular contacts. Addressing a forum with an ! will make the posting exclusively for the subscribers to the forum (public or private depends on the forum settings).
    • Dependency management is now done using composer (see below).
    • The API was improved, letting the native clients provide a nicer mobile user experience.

    Additionally we fixed numerous bugs that the community had found and we polished some quirks and added some more features. For the complete list of changes, please see the CHANGELOG file.

    How to Update?

    We started to use composer for dependency management. This means, that if you are using git to manage the Friendica sources on your server, there is now an additional step in the update process. If you used the archives provided, you don't need to care about it, as the archives contain the dependencies as well.

    Should you encounter any problems while testing the RC code, please let us know about in the Friendica support forum, at github or over any other of the support channels.

    Independent of the update path you are choosing, please be aware that there are some changes to the database structure to enhance the performance of Friendica that will be applied automatically to your database. Depending on the size of your database, especially the item table, these changes can take several hours.

    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 release.

    Updating with git from the stable (master) branch

    As mentioned above, Friendica is now using composer for dependency management. This means that you have to do one further step when updating your git repository. This can be either an additional command every time you update, or adding a shell script to a git hook.

    Composer needs to be able to unpack the downloaded archives, hence you need to have the PHP zip module available on your server.

    If you want to do it all manually, then use the following sequence of commands: starting in the base directory of your Friendica installation.

    git pull
    php util/composer.phar install
    cd addon
    git pull
    

    This will download the updated sources from github, call composer to get the dependencies and then change into the addon repository to fetch the new code there as well.

    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 for further information about this.

    Updating with git from the RC or the development branches

    As the changes regarding the dependency management are likely already in place on your system, a git pull in your Friendica core repository and the addon repository should bring you on the latest code as usual.

    If you helped testing the release candidate--thanks a lot for helping!--you need to decide either to checkout the master or develop branch after the pull.

    If you are using the develop branch, please be reminded about the recent path changes for many scripts.

    Updating using the source archives

    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-full-3.6.zip or tar.gz and friendica-addons-3.6.zip or 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-3.6 archives), so you don't have to worry about them.

    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.

    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!

    Source code(tar.gz)
    Source code(zip)
    friendica-full-3.6.tar.gz(21.41 MB)
    friendica-full-3.6.zip(23.42 MB)
  • 3.5.4(Mar 23, 2018)

    This is a hotfix release for a bug we introduced with 3.5.3 for saving searches. It also contains some minor fixes for moving your account to another node and support for the Diaspora account moving.

    Source code(tar.gz)
    Source code(zip)
  • 3.5.3(Oct 5, 2017)

    Dear Federation, the Friendica DevTeam is pleased to announce the release of Friendica Asparagus 3.5.3.

    Aside of the ongoing performance enhancements and code refractoring, some note worthy changes in this release:

    • We ironed out some problems with the federation towards Mastodon and enhanced Diaspora and OStatus federation, as well as the bridges to other systems.
    • We marked several old addons as unsupported. This includes the retrieveraddon due to unwanted side effects, as well as old "frontend" cron addons as their functionality is in core for some time now.

    Additionally we fixed numerous bugs that the community had found and we polished some quirks. For the complete list of changes, please see the CHANGELOG file.

    How to Update?

    Make sure to have MySQL 5.5.3+ or a compatible version (e.g. MariaDB) installed on your server.

    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.3rc 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 and friendica-addons-3.5.3.zip) 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.

    Please note that there are some changes to the database structure that will take some time to be applied.

    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 :-)

    Source code(tar.gz)
    Source code(zip)
  • 3.5.2(Jun 6, 2017)

    Dear Federation, we are pleased to announce the immedeate availability of Friendica "Asparagus" 3.5.2.

    The main focus of the last few months' work was spent on internal code restructuring and performance enhancements. For a full list of changes, please refer to the CHANGELOG file. The highlights are:

    • Enhanced compatibility with MySQL 5.7+.
    • New support for 4 bytes unicode characters (mostly used for emojis). MySQL version 5.5.3 is now a hard minimum requirement.
    • Enhanced federation with Mastodon and preparation for upcoming changes in the Diaspora protocol.
    • The switch to the worker process introduced in the 3.5.1 version as the background process mechanism as it has a better performance. If you are using poorman's cron, external cron or proc runner for the background process, you have to adopt to the frontend worker (see docs) as it makes these addons obsolete.
    • The most visible change is the long time project lead by Rabuzarus, the "frio" theme, which finally removed the "experimental" flag. It still is not 100 percent complete, but it is ready for daily usage.

    Addtionally we fixed numerous bugs that the community had found and we polished some quirks.

    How to Update?

    Make sure to have MySQL 5.5.3+ or a compatible version (e.g. MariaDB) installed on your server.

    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.2rc branch of the repository, please switch to either the master or develop branch after the git pull.

    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.2.zip and friendica-addons-3.5.2.zip) 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.

    Please note theat there are some changes to the database structure that will take some time to be applied.

    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.

    Have fun 🙂

    Source code(tar.gz)
    Source code(zip)
  • 3.5.1(Mar 12, 2017)

    This release is mainly a bug fix release for the Asparagus release of Friendica. It closes some 50 issues from the github tracker and various others the com­mu­nity has found. It also includes some work on the performance of the system, thanks to the bad performance of one of the developers hosting providers. Among other things, these changes also include some work on the database structure. These changes will be applied automatically, but may take some time depending on your system resources and database size.

    Many thanks to everybody who reported a bug, fixed an issue or implemented a new feature!

    You can find the complete list of changes in the CHANGELOG.

    Notable changes

    • The new worker background progress can now also be called from external cron jobs. If you are using one of the extcron, procrunner or poormancron addons you can now replace this now with the worker process. (Disable the addon when switching to the worker process.)
    • The TinyMCE rich text editor was removed If you start typing a BBCode tag, a list of fitting BBCode elements will popup you can choose from.
    • Initial native federation with Mastodon nodes is working. More work for the federation with OStatus using projects is planned for the upcoming 3.5.2 release.
    • We deprecated the frost themes, as the default theme (vier) supports mobile devices with small screens since version 3.5. We have also deleted the files of themes deprecated with the 3.5 release last year.

    How to update?

    If you are using git to keep track of the Friendica code, you can use

    git pull
    

    and it will fetch the current code. Don't forget to also fetch the new code from the addon repository.

    If you have installed Friendica and the addons from the zip file, you can download the corresponding files friendica-3.5.1.zip and friendica-addons.zip. Just download these files to your computer, unzip them and transfer the files with an FTP client to your server into a new directory. Copy the .htconfig.php file into the new directory. Rename the old direcoty and afterwards change the name of the new directory to the initial name of your friendica directory.

    How to contribute?

    If you want to contribute to the project you do not need to have coding experience. There are a number of tasks listed in the issue traker 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.

    Have fun :-)

    Source code(tar.gz)
    Source code(zip)
  • 3.5(Sep 13, 2016)

  • 3.4.3(Dec 22, 2015)

  • 3.4.2(Sep 29, 2015)

  • 3.4.1(Jul 6, 2015)

    This version fixes a security issue in RINO. If you have $a->config['system']['rino_encrypt'] = true; in your .htconfig.php, please install this update, go to /admin/site and under "Advanced", "RINO Encryption" select "RINO 2". RINO 1 will be removed in next version.

    see the CHANGELOG for more info about this release

    Source code(tar.gz)
    Source code(zip)
PHP Secure Communications Library

phpseclib - PHP Secure Communications Library Supporting phpseclib Become a backer or sponsor on Patreon One-time donation via PayPal or crypto-curren

null 4.9k Dec 4, 2022
PHP Secure Communications Library

phpseclib - PHP Secure Communications Library Supporting phpseclib Become a backer or sponsor on Patreon One-time donation via PayPal or crypto-curren

null 4.9k Dec 1, 2022
Open source social sign on PHP Library. HybridAuth goal is to act as an abstract api between your application and various social apis and identities providers such as Facebook, Twitter and Google.

Hybridauth 3.7.1 Hybridauth enables developers to easily build social applications and tools to engage websites visitors and customers on a social lev

hybridauth 3.3k Nov 28, 2022
Ebansos (Electronic Social Assistance) is a web application that provides citizen data management who will receive social assistance to avoid misdirection assistance from public service/government.

E Bansos Ebansos (Electronic Social Assistance) is a web application that provides citizen data management who will receive social assistance to avoid

Azvya Erstevan I 12 Oct 12, 2022
Open Source Social Network (OSSN) is a social networking software written in PHP.

Open Source Social Network (OSSN) is a social networking software written in PHP. It allows you to make a social networking website and helps your members build social relationships, with people who share similar professional or personal interests. It is available in 17 international languages.

Open Source Social Network 915 Dec 4, 2022
Arc social share - A Social Bookmarking Plugin for Textpattern

arc_social_share A Social Bookmarking Plugin for Textpattern; easily add links for sharing content with numerous social networks. arc_social_share 1.4

Andy Carter 5 Nov 15, 2022
Social Network - Social Media App

Social Network Social Network - Social Media App. Demo Features Auth System (Login, Register, Forgot Password, Password Reset & Email Verification) Us

Noval 2 Jan 18, 2022
Talkino allows you to integrate multi social messengers and contact into your website and enable your users to contact you using multi social messengers' accounts.

Talkino Welcome to our GitHub Repository Talkino is a click to chat plugin to show your agents’ multiple social messengers, phone and emails on the ch

Traxconn 2 Sep 21, 2022
A component-centric backend communication layer for Alpine.js

A component-centric backend communication layer for Alpine.js. Installation Install using the following command: composer require radio/radio Install

Radio.js 75 Dec 20, 2021
Pimcore Bundle that enbable pimcore to expose webook for communication to third parties

WebHookBundle Plugin This extention provide an easy way to send dataobjects to an external sites via json, whenever a pimcore event occurs on a specif

Sintra  - Digital Business 22 Aug 9, 2022
Pretty Good Privacy (PGP) is an encryption program that provides cryptographic privacy and authentication for data communication.

Pretty Good Privacy (PGP) is an encryption program that provides cryptographic privacy and authentication for data communication. PGP is used for signing, encrypting, and decrypting texts, e-mails, files, directories, and whole disk partitions and to increase the security of e-mail communications. Phil Zimmermann developed PGP in 1991.

[sCRiPTz-TEAM] 3 Dec 31, 2021
A WordPress plugin for managing user permission, education, and communication.

A WordPress plugin for managing user permission, education, and communication. Texas A&M University System

Texas A&M University, College of Liberal Arts 1 Oct 22, 2021
An online communication application that provides a real-time or live transmission of text messages from sender to receiver.

Realtime-chat-application An online communication application that provides a real-time or live transmission of text messages from sender to receiver.

isha 2 Aug 15, 2022
API abstracting communication with SQL providers (eg: MySQL) on top of PDO inspired by Java JDBC

SQL Data Access API Table of contents: About Configuration Execution Installation Unit Tests Examples Reference Guide About This API is a ultra light

Lucian Gabriel Popescu 0 Jan 9, 2022
Known: a social group platform

Known: a social group platform Installation One-click Known sites If you want to install on your own web space, we recommend Reclaim Hosting, which in

Known 966 Dec 3, 2022
Fresns core library: Cross-platform general-purpose multiple content forms social network service software

About Fresns Fresns is a free and open source social network service software, a general-purpose community product designed for cross-platform, and su

Fresns 45 Nov 28, 2022
BraincraftedBootstrapBundle integrates Bootstrap into Symfony2 by providing templates, Twig extensions, services and commands.

BraincraftedBootstrapBundle BraincraftedBootstrapBundle helps you integrate Bootstrap in your Symfony2 project. BootstrapBundle also supports the offi

Braincrafted 403 Aug 13, 2022
Laravel Debugbar (Integrates PHP Debug Bar)

Laravel Debugbar This is a package to integrate PHP Debug Bar with Laravel. It includes a ServiceProvider to register the debugbar and attach it to th

Barry vd. Heuvel 14.7k Dec 5, 2022