Friendica Admins (admins) group

!Friendica Admins Hi admins! If you are hunted by database errors like Cannot delete or update a parent row: a foreign key constraint fails (`friendica`.`#sql-alter-463-2034e1`, CONSTRAINT `#sql-alter-463-2034e1_ibfk_4` where the table name and the constraint name contains #sql-alter, then have got a look at that page: mariadb.com/kb/en/innodb-data-…
These #sql-alter tables are leftovers from failed alter commands.

Attention: Before you apply any changes, please perform a backup.

📢 ensure legacy proxy is disabled

In the current development branch the legacy proxy functionality has been removed github.com/friendica/friendica… as bad actors might misuse it.

If you are using any other version of Friendica, please ensure that the proxify_content config variable is set to false. For this you can either use the admin panel (Site configuration -> Proxify external content) or set it to false on the command line using the console tool bin/console config system proxify_content 0.

!Friendica Admins

Friendica config optimization for limited resources

Hey everyone, and especially @Michael Vogel

I'd like to compile a list of settings for Friendica to work on limited resources. Based on settings I'm using on my Raspi 4 but with the knowledge of all of you, as I'm almost certain that I missed some optimization possibilities.

Personal user settings

• Account settings -> Social Media -> General Social Media Settings -> Followed content scope: select "only conversations my follows started". This is obviously a personal choice, but only follow (and importing) the postings from the accounts I follow and not also the content they interact with reduces the amount of postings that are imported into the system. If they think a posting is important enough to share it, then you'll see it.

Settings in the admin panel

Activate the "fast lane" worker. This will keep one worker process dealing only with the delivery of content. Afterall we want to share postings with contacts in a social network, so this should not suffer from other tasks the worker has to perform.

Limit public access

If non-logged in users have less access to potentially resource hungry parts of Friendica. This includes "Community pages for visitors" (None), "Disallow public access to addons listed in the apps menu.", "Only local search".

Discovery

Discovering potential contacts is great, but will use resources. So

• set "Discover followers/followings from contacts" to None and just to be sure deactivate "Discover contacts from other servers".
• Also "Only update contacts/servers with local data" should limit the data-waste filling up the database.

Remote content

Delete it automatically, as long as it is not protected by the users of the node. The settings for this are

• "Lifespan of remote items" and also
• limit the "Maximum age of items in the search table".
• The "Lifespan of raw conversation data" is kept for 90 days by default, but the description claims it is save to delete it after 14 days so, take the minimum save value.

Don't forget to select "Clean database" and "Periodically optimize tables". The optimization will actually free the space the table is reserving on the storage (else the database will fill up the reserved space before claiming more).

Relays

Relay server are great to get content into your node, especially on small nodes (likely those with limited resources). Fill the global community page and have nice channel content based on them. But those postings will also eat the resources of the server quickly. So...

• set the "Relay scope" to tags and define some tags your server should import. Also "Allow user tags" so that the user can set tags to follow from the relay. However
• set the "Lifespan of unclaimed items" to 1 (or another low value) so that these posting will get deleted quickly again

Display of content

Limit the amount of postings and comments that are shown on one page.

Settings in the config file

• system -> fetch_perents = false this will prevent Friendica to fetch missing parent posts
• system -> optimize_all_tables = true this will optimizes all tables instead of only tables like workerqueue or the cache, so when things in the database are deleted, more space is freed.

What have I missed? I mean apart from optimizing the database settings and how the web server serves PHP content.

!Friendica Admins

Not sure if we are speaking about the same thing here. The search index is a completely new table and the search text only includes the content that should be searched for. Means: no links, no BBCode tags, only the text.

Concerning attachments: They are stored in the post-media table anyway.

Limited communication with *THAT* server

Heya dear Friendica admins,

since the 2023.12 https://friendi.ca/2023/12/24/friendica-2023-12-released/ release of Friendica you can limit the communication with nodes of the Fediverse before blocking communication completely. Then communication, the exchange of postings, will still be possible -- but the data exchanged with the other node are limited as much as possible.

This might be a way to deal with communication to a good friends on evil corporate server without providing too much information about users of your node. The settings to configure this limited communication have to be put into the config/local.config.php (see defaults https://git.friendi.ca/friendica/friendica/src/branch/develop/static/defaults.config.php#L328) file at the moment, it is planned to get the settings into the admin panel, but for now it is only the config file. There, in the system section add the following:

"limited_servers" => "social.evil-corp.com, other-evil.com";

and from then on communication with the two servers social.evil-corp.com and other-evil.com is limited to the technical necessary information. This includes

• The posting and its content
• From the user profile the nickname and the profile key.

@Michael Vogel please correct me if I'm missing something, and thanks for implementing this solution!

!Friendica Admins #Friendica #Fediverse

!Friendica Support !Friendica Admins If your system is on the "develop" branch and recently updated their code, then you will be able posting to Twitter again. The Twitter addon now is only a posting connector, since for everything else you have to pay. Also, since there are now low posting limits, each user has to register their own app.

Head over to the Developer Portal https://developer.twitter.com/en/portal/projects-and-apps for that purpose. If you already have got an app registered, make sure that it belongs to a "project" and is no "Standalone App". In the section "Keys and Tokens" you will then find all the needed data, means "API Key and Secret" and "Access Token and Secret". These values have to be added in the Twitter settings in their respective fields.

When you submitted the values, have a look at the field " Last Status Summary". This should show some "200 - ..." value. If the number is in the 400 or 500 range, then something is wrong with your keys.

Later that field will contain the result after each post, so expect to see "201 - Created" in that field after the first post is done. Again: If the value is not in the 200 range, then something is wrong. Then have a look at " Last Status Content" to see the details.

Have fun!