Ok so recently I ran into a hiccup with an issue that effects how my jetstream and daemons run on my #friendica instance, as I am still working on the what I created a workaround that makes sure that they run as they should, I made one more semi useful script for a resource control hack, that helps throttle lsphp to reduce server loads on limited resources without compromising flow of feeds, then I have made some cron adjustments that may or may not help your #friendica instance; I am sharing my little scripts and hacks for those who may have resource issues where their daemon and jetstream keep getting killed, or where they are on a limited server environment, I offer no promise nor support, but for me it is working nicely;
Again I make no claims of actual usability or benefit, as of posting this it seems to be working well on my #friendica instance;


Crons

# --- Friendica Automation Suite ---
MAILTO="your-email@domain.com"
SHELL="/bin/bash"

# Core background tasks
0 */1 * * * /home/USER/friendica_cron.sh >/dev/null 2>&1
*/15 * * * * /usr/bin/flock -n /tmp/fc_worker.lock -c cd /home/USER/public_html && bin/console worker >/dev/null 2>&1

# Maintenance: Monthly Smarty purge (1st of the month)
0 0 1 * * /usr/bin/rm -rf /home/USER/public_html/view/smarty/compile/* >/dev/null 2>&1

# Maintenance: Weekly Storage & Cache clearing (Sundays)
0 1 * * 0 cd /home/USER/public_html; bin/console storage clear >/dev/null 2>&1
30 1 * * 0 cd /home/USER/public_html; bin/console cache clear >/dev/null 2>&1

# Watchdogs: StayAlive & Bouncer
@reboot /bin/bash /home/USER/scripts/StayAlive.sh > /dev/null 2>&1 &
0 * * * * pgrep -f StayAlive.sh > /dev/null || /bin/bash /home/USER/scripts/StayAlive.sh > /dev/null 2>&1 &

@reboot /bin/bash /home/USER/scripts/bouncer.sh > /dev/null 2>&1 &
* * * * * pgrep -f bouncer.sh > /dev/null || /bin/bash /home/USER/scripts/bouncer.sh > /dev/null 2>&1 &

README

⚙️ The Friendica Automation Suite (Crontab)
Scheduled Maintenance & Self-Healing Guards
This configuration file acts as the "Brain" of your Friendica instance. It manages the scheduling for background tasks, periodic cache cleaning, and—most importantly—ensures your custom stability scripts (Bouncer and StayAlive) never stop running.

⚠️ Implementation Note: Replace YOUR_HOME, YOUR_USER, and YOUR_INSTANCE_ROOT with your actual server paths.

These Crons are provided "as-is" for educational and personal use.

They will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk..

🛠 What This Schedule Manages
1. Core Background Tasks
Hourly Maintenance: Runs friendica_cron.sh to handle general background cleanup.

Frequent Worker: Executes the Friendica worker every 15 minutes to keep the federation queue moving.

2. Housekeeping & Performance
To prevent disk bloat and keep the interface snappy, the following cleanup tasks are automated:

Monthly Smarty Purge: Clears compiled template files on the 1st of every month to refresh the UI engine.

Weekly Storage Cleanup: Clears the avatar and storage cache every Sunday at 1:00 AM.

Weekly Node Cache: Flushes the node cache every Sunday at 1:30 AM to keep remote directory info fresh.

3. The "Immortal" Guard System
The most critical part of this setup is the Watchdog for the Watchdogs.

Boot Persistence: Both the StayAlive.sh (Service Guard) and bouncer.sh (Resource Throttle) are set to trigger immediately upon a server reboot (@reboot).

The Safety Check: Every hour (for StayAlive) and every minute (for the Bouncer), the system checks if the scripts are still running. If they’ve been killed by the system, it automatically restarts them.

📋 Installation
To apply these rules to your server:

Open your crontab editor:

Bash
crontab -e
Paste the configuration, ensuring your paths are correct.

Save and exit.

🔍 Pro-Tip: Monitoring
You have MAILTO set at the top. If your server is configured for mail, any errors from these tasks will be sent directly to your inbox. If you prefer to log to a file instead, you can change the >/dev/null 2>&1 at the end of the lines to >> ~/cron_log.txt 2>&1.


Bouncer

#!/bin/bash

# These are the Bouncer's Rules
MAX_KIDS=3        # Only 3 people in the kitchen at once
MAX_HEAT=2        # Only 2% energy allowed
CHECK_TIME=5      # Wait 5 seconds before checking again

while true
do
  # 1. Count how many 'lsphp' workers are busy with your site
  CURRENT_KIDS=$(pgrep -f "lsphp.*YOUR_INSTANCE_ROOT" | wc -l)

 # Lower priority for all lsphp processes to keep the server cool
    pgrep -u *YOUR_USER lsphp | xargs -r renice -n 15 > /dev/null 2>&1

  # 2. If there are more than 3...
  if [ "$CURRENT_KIDS" -gt "$MAX_KIDS" ]; then
    echo "Bouncer: Too many kids! Making the extras wait in the hallway."
    
    # This finds the newest workers and tells them to 'STOP' (Pause)
    # They stay in line, but they don't use any CPU while paused.
    pgrep -f "lsphp.*YOUR_INSTANCE_ROOT" | tail -n +$((MAX_KIDS+1)) | xargs kill -STOP
    
    # Wait for things to cool down
    sleep $CHECK_TIME
    
    # Tell them they can 'CONT' (Continue) ONE BY ONE
        echo "$EXTRAS" | while read -r kid_pid; do
            if [ ! -z "$kid_pid" ]; then
                kill -CONT "$kid_pid"
                echo "Bouncer: Letting kid $kid_pid back in."
                sleep 1 
            fi
        done
  fi

  # Take a small breath so the Bouncer doesn't get tired
  sleep 1
done

README

🚪 The LSPHP Bouncer
Resource Throttle & Process Queue for Shared Hosting
The LSPHP Bouncer is a lightweight Bash watchdog designed for users on LiteSpeed-based hosting. It prevents your account from hitting "Resource Limit Reached" errors (508 errors) by pausing excess PHP processes (lsphp) instead of letting them crash the site or trigger a provider-level kill.

⚠️ Maintenance Notice
This project is provided "as-is" for educational and personal use.

It will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk..

🧐 How It Works
LiteSpeed servers often spawn many lsphp workers to handle incoming traffic. If too many start at once, your host might lock your account for exceeding CPU or process limits.

The Headcount: Every second, the Bouncer counts how many PHP workers are active for your specific site.

The Velvet Rope: If the count exceeds your MAX_KIDS limit, the Bouncer sends a SIGSTOP signal to the extra processes. This pauses them—they stay in the queue but stop consuming CPU cycles.

The Entry: After a short cooldown (CHECK_TIME), the Bouncer sends a SIGCONT signal, letting those processes finish their work one by one.

🛠 Configuration
Open the script and adjust these "House Rules" to match your hosting plan:

MAX_KIDS: The maximum number of PHP processes you are allowed (e.g., 3).

CHECK_TIME: How many seconds to pause the "extras" before letting them work again.

Process Filter: The script looks for "lsphp.*your.domain". Ensure the string matches what shows up in your process monitor (usually top or htop).

🚀 Setup & Execution
1. Make it Executable
Bash
chmod +x bouncer.sh
2. Run the Bouncer
To keep the Bouncer running even after you log out of SSH:

Bash
nohup ./bouncer.sh > /dev/null 2>&1 &
📈 Why use this?
Avoids 508 Errors: Instead of the server showing a "Limit Reached" page, the site just feels a tiny bit slower while the Bouncer staggers the load.

CPU Friendly: Paused processes (kill -STOP) consume zero CPU, helping you stay under the "Energy" or "Heat" limits of your host.

Specific Targeting: Using pgrep -f, it only targets your specific site's workers, leaving other processes alone.


Persistent Service Guard

#!/bin/bash

# --- CONFIGURATION (Users change these) ---
# The absolute path to your application root
SITE_ROOT="/path/to/your/app"

# The path to the PHP binary (usually 'php' or a specific version)
PHP_CLI="/usr/bin/php"

# Name of the console executable
CONSOLE_APP="bin/console.php"

# Where to save the logs
LOG_FILE="./guard_log.txt"

# List of services to monitor
SERVICES=("daemon" "jetstream")

# --- CORE LOGIC (Do not edit below) ---
CONSOLE_PHP="$SITE_ROOT/$CONSOLE_APP"

echo "$(date): Persistent Guard started for services: ${SERVICES[*]}" >> "$LOG_FILE"

while true; do
    for SERVICE in "${SERVICES[@]}"; do
        # Check status
        STATUS=$($PHP_CLI $CONSOLE_PHP $SERVICE status 2>&1)

        if [[ "$STATUS" != *"is running"* ]]; then
            echo "$(date): $SERVICE is DOWN. Attempting start..." >> "$LOG_FILE"
            $PHP_CLI $CONSOLE_PHP $SERVICE start >> "$LOG_FILE" 2>&1
        fi
    done
    sleep 60
done

README

Persistent Service Guard
A robust, lightweight Bash-based watchdog script designed to monitor and automatically restart background services (such as Friendica daemons or Jetstream workers) for PHP-based applications.

⚠️ Maintenance Notice
This project is provided "as-is" for educational and personal use.

It will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk.

🚀 What It Does
The Service Guard addresses the common issue where background processes or daemons on shared or private hosting may crash or be killed by the system.

Active Monitoring: It loops indefinitely, checking the status of defined services every 60 seconds.

Automatic Recovery: If a service is reported as "not running," the script immediately attempts to restart it.

Logging: Every check, failure, and restart attempt is timestamped and recorded for auditing.

🛠 Setup & Usage
1. Configuration
Before running, ensure the following variables in guard.sh match your environment:

SITE_ROOT: The absolute path to your application root.

PHP_CLI: The path to the PHP binary (e.g., /usr/bin/php).

SERVICES: The names of the services to monitor (e.g., "daemon" "jetstream").

2. Permissions
Grant execution rights to the script:

Bash
chmod +x guard.sh
3. Execution
Run the script in the background to ensure it persists after your session ends:

Bash
nohup ./guard.sh > /dev/null 2>&1 &
📊 Managing Logs
The script appends data to guard_log.txt. To prevent this file from consuming excessive disk space, use one of the following methods:

Manual Truncation
Clear the log without stopping the script:

Bash
> guard_log.txt
Automatic Log Rotation (Improvement Example)
To automate log management, add this logic inside the while loop of the script:

Bash
# Improvement: Simple Log Rotation
MAX_SIZE=1048576 # 1MB in bytes
FILE_SIZE=$(stat -c%s "$LOG_FILE")

if [ "$FILE_SIZE" -gt "$MAX_SIZE" ]; then
echo "$(date): Log rotated (size limit reached)" > "$LOG_FILE"
fi
📈 Potential Improvements
Users wishing to extend the script's functionality can implement the following:

1. Auto-Discovery
Replace the hardcoded PHP_CLI path with dynamic discovery:

Bash
PHP_CLI=$(which php)
2. Failure Notifications
Integrate curl to send alerts to Discord or Telegram when a service fails:

Bash
# Discord Notification Example
curl -H "Content-Type: application/json" -X POST -d "{\"content\": \"⚠️ Alert: $SERVICE has crashed. Restarting...\"}" YOUR_WEBHOOK_URL
3. Dependency Validation
Add a check to verify the application exists before the loop starts:

Bash
if [ ! -f "$CONSOLE_PHP" ]; then
echo "Error: Console application not found at $CONSOLE_PHP"
exit 1
fi


⚖️ License (MIT)
Copyright (c) 2026 pasjrwoctx👽 (Philip A. Swiderski Jr.)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE

@Friendica Support @Friendica Developers @Friendica Admins

You can encourage my continued useless ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at https://www.paypal.com/donate?campaign_id=5BN5MB5BVQL22

Just some cron adjustments that may or may not help your #friendica instance;

# --- Friendica Automation Suite ---
MAILTO="your-email@domain.com"
SHELL="/bin/bash"

# Core background tasks
0 */1 * * * /home/USER/friendica_cron.sh >/dev/null 2>&1
*/15 * * * * cd /home/USER/public_html; bin/console worker >/dev/null 2>&1

# Maintenance: Monthly Smarty purge (1st of the month)
0 0 1 * * /usr/bin/rm -rf /home/USER/public_html/view/smarty/compile/* >/dev/null 2>&1

# Maintenance: Weekly Storage & Cache clearing (Sundays)
0 1 * * 0 cd /home/USER/public_html; bin/console storage clear >/dev/null 2>&1
30 1 * * 0 cd /home/USER/public_html; bin/console cache clear >/dev/null 2>&1

# Watchdogs: StayAlive & Bouncer
@reboot /bin/bash /home/USER/scripts/StayAlive.sh > /dev/null 2>&1 &
0 * * * * pgrep -f StayAlive.sh > /dev/null || /bin/bash /home/USER/scripts/StayAlive.sh > /dev/null 2>&1 &

@reboot /bin/bash /home/USER/scripts/bouncer.sh > /dev/null 2>&1 &
* * * * * pgrep -f bouncer.sh > /dev/null || /bin/bash /home/USER/scripts/bouncer.sh > /dev/null 2>&1 &

README

⚙️ The Friendica Automation Suite (Crontab)
Scheduled Maintenance & Self-Healing Guards
This configuration file acts as the "Brain" of your Friendica instance. It manages the scheduling for background tasks, periodic cache cleaning, and—most importantly—ensures your custom stability scripts (Bouncer and StayAlive) never stop running.

⚠️ Implementation Note: Replace YOUR_HOME, YOUR_USER, and YOUR_INSTANCE_ROOT with your actual server paths.

These Crons are provided "as-is" for educational and personal use.

They will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk..

🛠 What This Schedule Manages
1. Core Background Tasks
Hourly Maintenance: Runs friendica_cron.sh to handle general background cleanup.

Frequent Worker: Executes the Friendica worker every 15 minutes to keep the federation queue moving.

2. Housekeeping & Performance
To prevent disk bloat and keep the interface snappy, the following cleanup tasks are automated:

Monthly Smarty Purge: Clears compiled template files on the 1st of every month to refresh the UI engine.

Weekly Storage Cleanup: Clears the avatar and storage cache every Sunday at 1:00 AM.

Weekly Node Cache: Flushes the node cache every Sunday at 1:30 AM to keep remote directory info fresh.

3. The "Immortal" Guard System
The most critical part of this setup is the Watchdog for the Watchdogs.

Boot Persistence: Both the StayAlive.sh (Service Guard) and bouncer.sh (Resource Throttle) are set to trigger immediately upon a server reboot (@reboot).

The Safety Check: Every hour (for StayAlive) and every minute (for the Bouncer), the system checks if the scripts are still running. If they’ve been killed by the system, it automatically restarts them.

📋 Installation
To apply these rules to your server:

Open your crontab editor:

Bash
crontab -e
Paste the configuration, ensuring your paths are correct.

Save and exit.

🔍 Pro-Tip: Monitoring
You have MAILTO set at the top. If your server is configured for mail, any errors from these tasks will be sent directly to your inbox. If you prefer to log to a file instead, you can change the >/dev/null 2>&1 at the end of the lines to >> ~/cron_log.txt 2>&1.

⚖️ License (MIT)
Copyright (c) 2026 pasjrwoctx👽 (Philip A. Swiderski Jr.)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE

@Friendica Support @Friendica Developers @Friendica Admins

You can encourage my continued useless ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at https://www.paypal.com/donate?campaign_id=5BN5MB5BVQL22

Ok so I made one more semi useful script for a resource control hack, again I make no claims of actual usability or benefit, as of posting this it seems to be working well on my #friendica instance;

#!/bin/bash

# These are the Bouncer's Rules
MAX_KIDS=3 # Only 3 people in the kitchen at once
MAX_HEAT=2 # Only 2% energy allowed
CHECK_TIME=5 # Wait 5 seconds before checking again

while true
do
# 1. Count how many 'lsphp' workers are busy with your site
CURRENT_KIDS=$(pgrep -f "lsphp.*YOUR_INSTANCE_ROOT" | wc -l)

# 2. If there are more than 3...
if [ "$CURRENT_KIDS" -gt "$MAX_KIDS" ]; then
echo "Bouncer: Too many kids! Making the extras wait in the hallway."

# This finds the newest workers and tells them to 'STOP' (Pause)
# They stay in line, but they don't use any CPU while paused.
pgrep -f "lsphp.*YOUR_INSTANCE_ROOT" | tail -n +$((MAX_KIDS+1)) | xargs kill -STOP

# Wait for things to cool down
sleep $CHECK_TIME

# Tell them they can 'CONT' (Continue) one by one
pgrep -f "lsphp.*YOUR_INSTANCE_ROOT" | xargs kill -CONT
fi

# Take a small breath so the Bouncer doesn't get tired
sleep 1
done


README
🚪 The LSPHP Bouncer
Resource Throttle & Process Queue for Shared Hosting
The LSPHP Bouncer is a lightweight Bash watchdog designed for users on LiteSpeed-based hosting. It prevents your account from hitting "Resource Limit Reached" errors (508 errors) by pausing excess PHP processes (lsphp) instead of letting them crash the site or trigger a provider-level kill.

⚠️ Maintenance Notice
This project is provided "as-is" for educational and personal use.

It will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk..

🧐 How It Works
LiteSpeed servers often spawn many lsphp workers to handle incoming traffic. If too many start at once, your host might lock your account for exceeding CPU or process limits.

The Headcount: Every second, the Bouncer counts how many PHP workers are active for your specific site.

The Velvet Rope: If the count exceeds your MAX_KIDS limit, the Bouncer sends a SIGSTOP signal to the extra processes. This pauses them—they stay in the queue but stop consuming CPU cycles.

The Entry: After a short cooldown (CHECK_TIME), the Bouncer sends a SIGCONT signal, letting those processes finish their work one by one.

🛠 Configuration
Open the script and adjust these "House Rules" to match your hosting plan:

MAX_KIDS: The maximum number of PHP processes you are allowed (e.g., 3).

CHECK_TIME: How many seconds to pause the "extras" before letting them work again.

Process Filter: The script looks for "lsphp.*your.domain". Ensure the string matches what shows up in your process monitor (usually top or htop).

🚀 Setup & Execution
1. Make it Executable
Bash
chmod +x bouncer.sh
2. Run the Bouncer
To keep the Bouncer running even after you log out of SSH:

Bash
nohup ./bouncer.sh > /dev/null 2>&1 &
📈 Why use this?
Avoids 508 Errors: Instead of the server showing a "Limit Reached" page, the site just feels a tiny bit slower while the Bouncer staggers the load.

CPU Friendly: Paused processes (kill -STOP) consume zero CPU, helping you stay under the "Energy" or "Heat" limits of your host.

Specific Targeting: Using pgrep -f, it only targets your specific site's workers, leaving other processes alone.

⚖️ License (MIT)
Copyright (c) 2026 pasjrwoctx👽 (Philip A. Swiderski Jr.)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

@Friendica Support @Friendica Developers @Friendica Admins

You can encourage my continued useless ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at https://www.paypal.com/donate?campaign_id=5BN5MB5BVQL22

Ok so recently I ran into a hiccup with an issue that effects how my jetstream and daemons run on my #friendica instance, as I am still working on the what I created a workaround that makes sure that they run as they should, I am sharing my little script for those who may have issues where their daemon and jetstream keep getting killed, I offer no promise nor support, but for me it is working nicely;

#!/bin/bash

# --- CONFIGURATION (Users change these) ---
# The absolute path to your application root
SITE_ROOT="/path/to/your/app"

# The path to the PHP binary (usually 'php' or a specific version)
PHP_CLI="/usr/bin/php"

# Name of the console executable
CONSOLE_APP="bin/console.php"

# Where to save the logs
LOG_FILE="./guard_log.txt"

# List of services to monitor
SERVICES=("daemon" "jetstream")

# --- CORE LOGIC (Do not edit below) ---
CONSOLE_PHP="$SITE_ROOT/$CONSOLE_APP"

echo "$(date): Persistent Guard started for services: ${SERVICES}" >> "$LOG_FILE"

while true; do
for SERVICE in "${SERVICES[@]}"; do
# Check status
STATUS=$($PHP_CLI $CONSOLE_PHP $SERVICE status 2>&1)

if [[ "$STATUS" != *"is running"* ]]; then
echo "$(date): $SERVICE is DOWN. Attempting start..." >> "$LOG_FILE"
$PHP_CLI $CONSOLE_PHP $SERVICE start >> "$LOG_FILE" 2>&1
fi
done
sleep 60
done

README
Persistent Service Guard
A robust, lightweight Bash-based watchdog script designed to monitor and automatically restart background services (such as Friendica daemons or Jetstream workers) for PHP-based applications.

⚠️ Maintenance Notice
This project is provided "as-is" for educational and personal use.

It will not be maintained or updated.

No support or bug fixes will be provided.

Use at your own risk.

🚀 What It Does
The Service Guard addresses the common issue where background processes or daemons on shared or private hosting may crash or be killed by the system.

Active Monitoring: It loops indefinitely, checking the status of defined services every 60 seconds.

Automatic Recovery: If a service is reported as "not running," the script immediately attempts to restart it.

Logging: Every check, failure, and restart attempt is timestamped and recorded for auditing.

🛠 Setup & Usage
1. Configuration
Before running, ensure the following variables in guard.sh match your environment:

SITE_ROOT: The absolute path to your application root.

PHP_CLI: The path to the PHP binary (e.g., /usr/bin/php).

SERVICES: The names of the services to monitor (e.g., "daemon" "jetstream").

2. Permissions
Grant execution rights to the script:

Bash
chmod +x guard.sh
3. Execution
Run the script in the background to ensure it persists after your session ends:

Bash
nohup ./guard.sh > /dev/null 2>&1 &
📊 Managing Logs
The script appends data to guard_log.txt. To prevent this file from consuming excessive disk space, use one of the following methods:

Manual Truncation
Clear the log without stopping the script:

Bash
> guard_log.txt
Automatic Log Rotation (Improvement Example)
To automate log management, add this logic inside the while loop of the script:

Bash
# Improvement: Simple Log Rotation
MAX_SIZE=1048576 # 1MB in bytes
FILE_SIZE=$(stat -c%s "$LOG_FILE")

if [ "$FILE_SIZE" -gt "$MAX_SIZE" ]; then
echo "$(date): Log rotated (size limit reached)" > "$LOG_FILE"
fi
📈 Potential Improvements
Users wishing to extend the script's functionality can implement the following:

1. Auto-Discovery
Replace the hardcoded PHP_CLI path with dynamic discovery:

Bash
PHP_CLI=$(which php)
2. Failure Notifications
Integrate curl to send alerts to Discord or Telegram when a service fails:

Bash
# Discord Notification Example
curl -H "Content-Type: application/json" -X POST -d "{\"content\": \"⚠️ Alert: $SERVICE has crashed. Restarting...\"}" YOUR_WEBHOOK_URL
3. Dependency Validation
Add a check to verify the application exists before the loop starts:

Bash
if [ ! -f "$CONSOLE_PHP" ]; then
echo "Error: Console application not found at $CONSOLE_PHP"
exit 1
fi
⚖️ License (MIT)
Copyright (c) 2026 pasjrwoctx👽 (Philip A. Swiderski Jr.)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

@Friendica Support @Friendica Developers @Friendica Admins

You can encourage my continued useless ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at https://www.paypal.com/donate?campaign_id=5BN5MB5BVQL22

@Melanie Wehowski ich bin #neuhier auf deinem Server und war bisher ein #mastodon user. - #scham

Erst einmal vielen Dank für deine Arbeit und das ich hier sein darf.

Ich habe ein paar Fragen zu Friendica, die mir das Web nicht so einfach beantworten konnte.

#theme - kann man das Theme im Webbrowser irgendwo umstellen? Türkise Schrift auf hellem Hintergrund ist nichts mehr für meine alten Augen.
Ich bin zu doof es zu finden.

Aus Sicherheitsgründen habe ich #2FA aktiviert. Damit funktioniert die Anmeldung über #Relatica nicht mehr.
Gibt es so was wie #API-Schlüssel oder App-#Passphrases?

Durch den Systemwechsel von #Mastodon zu #friendica konnte ich keine Account-Umleitung und keinen Follower Ex- & Import nutzen. Die meisten habe ich einfach händisch neu angelegt.
Ich würde aber gerne #Hashtags folgen. Ich verstehe noch nicht, wo ich diese eintrage.

Ich komme mir mit meinen Fragen mal wieder vor, wie ein Anfänger.
Oder bin ich nur der, der sich traut, diese öffentlich zu stellen?

Auf jeden Fall vielen Dank für die Arbeit, die du hier rein steckst und einen schönen Sonntag aus dem #BergischLand.

@Friendly Koala @Marek 🇦🇺🇩🇪 @Matthias @Michael 🇺🇦 fwiw

i did more testing yesterday. the file import fails silently on all four of my #friendica instances. three are

Friendica, version 2026.01 that is running at the web location https://friendica.au. The database version is 1586/1586, the post update version is 1550/1550.

and the fourth is

Friendica, version 2026.04-dev that is running at the web location https://friendica.opensocial.space. The database version is 1592/1592, the post update version is 1550/1550.

given my initial fedi place ~4 years ago was a Masto instance, & all my numerous #fedihops since then have involved exporting the then-current following-list from the then-latest instance [of any software] & importing it into my new/latest fedi instance, that same process occurred when i began including various friendica instances in my fedihopping. so, the fact that my three older friendica instances successfully did accept the import, back when i did them in prior years, together with the fact that this present, new, instance on the latest stable F version, does not, AND that those three older instances since updating to their latest versions also no longer accept the import, leads me to tentatively conclude this latest version's file import code is broken, when it did still work in the previous versions.

so, in absence of the bulk import tool working, yesterday i spent many hours manually following each of my desired accounts one by one, ie, manually building up my Contacts in this my newest friendica account. such a boring inefficient task, & one which few noobs would be willing to perform, i suspect... ie, in the interests of not driving potential new friendica users away, this apparent bug should be fixed asap imo.

thank you.

Hallo zusammen,
ich hab festgestellt dass RSS-Feeds die ich über Friendica abonniert hab (z.B. RND) in Mastodon-Apps immer eingeklappt angezeigt werden. Der Artikel-Titel landet offenbar als Content Warning.

Das gleiche passiert auch bei meinen eigenen Posts wenn ich einen Titel vergebe.

Im Mastodon Netzwerk: Alles okay
Im 2. Mastodon-Konto Friendica: Posts mit Titel sind alle eingeklappt

Ist das bekannt? Gibt es da was geplantes oder einen Workaround?
Danke!


@Friendica Support
#Mastodon #Friendica #ContentWarning

Content warning: FollowBackBot in Friendica ? Click to open/close

@Friendica Support

TL;DR

Is it possible to use FollowBackBot - _followback@tags.pub on Friendica instances?

BACKGROUND

hello

i have accounts on two small Friendica instances, this one & also @Droppie [farcebk] 🐨♀🌈🐧​🦘

being small, they both have, to be blunt, really lousy hashtag-fetching behaviour from the wider fediverse. given i follow a lot of tags [these are as important or maybe even more so, than simply following only personal accounts, for me], this ongoing lousiness poses a real threat for my two accounts having any prospect of being serious daily fediverse "homes" for me, given both instances miss out on a large proportion of posts / tags that i routinely see each day in my Masto & Sharkey accounts.

I have tried using relay.fedi.buzz follows, eg tag-firefoxnightly@relay.fedi.buzz on another of my friendica accounts, but tbh it's a PITA coz i cannot simply do it myself, but instead must explicitly request the instance owner to manually add them at the server level via terminal. that kills all spontaneity for me.

recently i became aware of FollowBackBot - _followback@tags.pub [read the whole thread if you want all the background; https://friendica.au/display/7c8d90bc-252d65d8d081ff63-cb0df0a1], but in none of my friendica accounts am i able to actually [strong][em]follow[/em][/strong] it. eg, in this current account, the pic below shows the failure:



can anyone pls help me solve this?

cc: @Marek 🇦🇺🇩🇪 @Friendly Koala @Droppie [infosec] 🐨 ​

#Friendica #FriendicaAU #farcebookspace #HashtagFetching #dropbearpooterising

hi @Marek 🇦🇺🇩🇪 @Friendly Koala @Friendica Support

after much prevarication, due to the unsolved issue of the instance not fetching most of my followed hashtags [latest post: https://friendica.au/display/f3535bde-5769-d73a-ae22-15e898311506], i decided this arvo to press ahead anyway & import my Masto contacts here, via the corresponding Masto following_accounts.csv file. it did not work; nothing happened, despite a brief popup msg telling me the import had finished.

wondering if the #friendica contacts tool possibly didn't like the other account info after each account name [various combos of true, false], i edited the text file to remove them all, & retried. it still didn't work.

i feel a bit silly, in that there must be some obvious error i'm making, but atm i can't see it.

this is a sample from the edited file i've tried to import:

1earthmedia@universeodon.com
wansti@friendica.au
thisweekinkde@social.opendesktop.org
newd_bot@chinwag.org
lowqualityfacts@mstdn.social

is there something wrong with that format pls?

there are 289 entries in the file, fwiw.

@Friendly Koala @Marek 🇦🇺🇩🇪 @AJ Sadauskas @FollowBackBot today i have mucked about some more with this, & now have formed a tentative conclusion that this service is not compatible with friendica.

the essential first step is to

FollowBackBot

Follow me and I will follow you back. Your public posts will then be boosted through tags.pub. Unfollow me, and the boosts will stop

but afaict the #friendica GUI simply provides no facility to DO that initial Follow of this service. i tested in #FirefoxNightly, #Floorp, & Vivaldi.

in Masto, per pic below, searching for that tag does generate the standard Masto Follow Hashtag button.



otoh by contrast, in friendica a completely different page ensues, per next pic, which has NO button or any other way obvious to me, to actually DO the Follow.



alas, it seems i still have no good way so far to expand the reach of hashtag-fetching across fedi, in a small friendica instance.

@Friendica Support

For if you missed it, @Tobias hidding in plain sight at #FOSSDEM2026 giving a talk about #friendica.

friendica - hidden in plain sight since 2025

An die vielen neuen #Friendica Nutzenden hier im Fediverse.
Diese drei Adressen solltest du dir unbedingt merken und ggf. folgen solltest:

• !helpers !Friendica Support - Hier bekommst du schnellen Hilfe, wenn du allgemeine Fragen zu Friendica hast.
  
• admins@forum.friendi.ca !Friendica Admins - richtet sich an alle (Neu-)Admin:e, die sich zum Betrieb eines Friendica Servers austauschen wollen.
  
• developers@forum.friendi.ca !Friendica Developers - Hier tauschen sich Entwickler:innen und Interessierte aus, die zu Friendica-Projekt beitragen wollen.

Kopiert die jeweilig passende Adressen in die Suche und folgt den Gruppen, um Fragen stellen zu können oder um selbst zu helfen.

An die vielen neuen #Friendica Nutzenden hier im Fediverse.
Diese drei Adressen solltest du dir unbedingt merken und ggf. folgen:

• !helpers !Friendica Support - Hier bekommst du schnellen Hilfe, wenn du allgemeine Fragen zu Friendica hast.
  
• admins@forum.friendi.ca !Friendica Admins - richtet sich an alle (Neu-)Admin:e, die sich zum Betrieb eines Friendica Servers austauschen wollen.
  
• developers@forum.friendi.ca !Friendica Developers - Hier tauschen sich Entwickler:innen und Interessierte aus, die zu Friendica-Projekt beitragen wollen.

Kopiert die jeweilig passende Adressen in die Suche und folgt den Gruppen, um Fragen stellen zu können oder um selbst zu helfen.

Ich habe eine Einladung zu eurosky.social bekommen, einem aus den Niederlanden betriebenen europäischen AT-Protocol-Netz, das wie ich verstehe auch mit Bluesky förderiert ist. Ist bekannt ob das Bluesky-Plugin von Friendica inzwischen problemlos mit AT-Servern arbeitet, die nicht von Bluesky sind? Ich meine in einem Readme was gelesen zu haben dass die Funktionalität da sei, aber noch nicht freigeschaltet sei. Ich würde gerne meine Bluesky-Account nach Eurosky migrieren, möchte aber sicher sein dass ich dann auch weiterhin komfortable mit Freindica beide Netze, Fediversum/Activitypub und *sky/AT, bespielen kann. #Bluesky #Addon #Friendica
!Friendica Support

!free open source investigation around #friendica circles, how to implement them best and what are the results and outcomes for contacts of other platforms.

A quest for best practice and eventual #bugResearch

contact groups surrounding the project scriptedTalesClub

@Anomaly i have a hard time leaving a dangling thread sometimes, it usually results in a lot of aggravation, but it keeps me busy so I don't feel so much of the pain im in, anyways stable is what I preach as I dangle off a cliff, have to accept the risk of failure and loss before jumping into chaos, sometimes I win and learn sometimes I lose and learn; actually at the moment its all working well, I am trying to figure out now how to disable comments, I have it working locally on my single user instance which is useless, the war is getting to to work across the fediverse without breaking everything else, #friendica is robust yet fragile, every little change seems to throw it into a panik or crash, I may figure it out by the next release, maybe;

@Raroun @Friendica Support within the past fortnight i discovered a new theme has been added, gnome, which is a much nicer alternative to the existing dark & black themes. despite me being a kde plasma fangirl, heehee. thanks for it.

one minor quibble with it is that unlike all the other themes, this one does not readily highlight the new items in the Notifications menu dropdown, instead subtly using just the theme's accent colour at the extremities. that works, but IMO it would still be desired to assign an obvious contrast background colour to the new items, like the other themes.

given clearly i am wishlist-dreaming atm, one other desirable enhancement would be to let users pick their own custom accent colour, for this & other themes.

#friendica #opensocialspace

Alright, it worked to switch the branch to stable for those two images (or whatever this is called in Docker) and there was no outstanding DB update before or after I switched the branch.

Anyone else did update the #Docker based setup of #Friendica to the 2026 version yet?

@Friendica Support @Raroun overnight [it's now my saturday 10am, midnight germany] there's been a subtle change in the timestamping of all posts in all my timelines. previously they displayed their posting time as "x hours ago", & i could only see the actual posting time by hovering on that item. now, they directly display the posting time... & i like this a lot. has there been a software update that did this, or was an administrative config change made?

this is not a complaint, not a problem -- i like this change -- it's just a surprise, so i am curious. thank you.

#Friendica #OpensocialSpace

omg, it only took me a month and a half with 50 or so failures wipes restores wipes and finally a fresh install after losing 3 database backups and imports, lost a few days of posts over all, but I finally got my #friendica instance upgraded to Friendica 'Blutwurz' 2026.04-dev - 1589 with php 8.5.2, and so far it appears to actually be working this time, i love friendica, I just wish the @Friendica Admins @Friendica Developers @Friendica Support had made it a bit more flexible every little change breaks everything, and it becomes a nearly never ending chase to customize and keep current, anyways for now I think my quite little instance is upgraded and running;

You can encourage my continued useless #poetry, creativity and expression of self, #commentary, random thoughts, #philosophy and ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at https://www.paypal.com/donate?campaign_id=5BN5MB5BVQL22

Hello !Friendica Support
can I switch the docker branch now?

I have right now:

app:
    image: friendica:2025.07-rc-fpm

and

cron:
    image: friendica:2025.07-rc-fpm

Can I switch this to:

app:
    image: friendica:stable-fpm

and

cron:
    image: friendica:stable-fpm

And just do a docker pull?

#Friendica #Docker

Which setting of GD and ImageMagick in #Friendica is causing that big JPEG are not processed and hence uploada fail after the Upload finished?

Upload limits are all high enough, but the 40...40 MB file uploads and then nothing more happens.

I might have asked that question already some years ago.

@Friendica Support

[strong]Frage | Friendica: Verschwindende Kommentarbenachrichtigungen[/strong]

Ich hatte drei Kommentare zu einen Kommentar von mir. Da ich jedoch die letzten drei paar Tage keine Zeit hatte, wollte ich sie heute beantworten. Wollte, weil auf einmal die Kommentarbenachrichtigungen weg sind und ich die Kommentare nicht mehr finde. Wie finde ich sie wieder bzw. habe ich überhaupt eine Chance sie zu finden?

#Frage #Friendica #Benachrichtigungen # Kommentarbenachrichtigungegen !Friendica Support

Hello !Friendica Support,

I just noticed that there is a bug in the current developer version of Friendica when commenting on Diaspora posts. Instead of the comment, this link appears:

• https://www.w3.org/ns/activitystreams#View

Here you can see it on Diaspora:

• https://despora.de/posts/18bd4f00e9fb013e4025466de73a75e5

#Friendica #Diaspora #Bug

Weil ich es gerade erst kennengelernt habe; weiß wer, wie #Friendica mit #Trails umgehen kann?
Habe eben die Instanz auf dem Server von @Milan
https://trails.tchncs.de/trails?page=1 entdeckt und schaffte ich es bisher weder einzelne Routenposts innerhalb meiner Friendicinastanz darzustellen, noch Trails-Accounts zu folgen. !Friendica Support
Finde das Konzept, Wander- und #Radrouten im Fedi zu teilen genial. Das passt so gut ins Fediverse, dass ich denke dasss das ein großer Erfolg werden könnte. Leider scheint es bei mir nioch nicht richtig zu klappen.

Wo finde ich eine Anleitung zu Friendica-Nachrichten-Relais?

Relaisserver sind großartig, um Inhalte in deinem Server zu verbreiten, besonders für kleine Server - stimmt! Entsprechend würde ich nach dem Tod von gup.pe gerne ein Nachrichten-Relais aufsetzen, welches Beiträge mit #​Brettspiele auf kleinen Instanzen sichtbar macht.
Nur: Wo finde ich eine Anleitung, was nach Festsetzung des Kontotyps zu tun ist? Und wieso kann ein Relais-Konto keinem anderen Relais-Konto folgen? Hier erscheint neuerdings die Fehlermeldung

Dies scheint ein Relais-Konto zu sein. Diese können nicht von Nutzern gefolgt werden.

Vor ein paar Versionen ging das noch.

#Friendica #FriendicaHelp #FriendicaRelays @Friendica Support

[strong]Frage | Friendica: Wie stelle ich bei mir das 'Titelbild' ein?[/strong]

Mir ist aufgefallen das ich inzwischen bei immer mehr Kontakten ein 'Titelbild' angezeigt bekomme und zwar nicht nur bei den üblichen Verdächtigen wie z. B. Mastodon, sondern auch bei Friendica Accounts. Wie bzw. wo stelle ich das ein?



Danke für Eure Tipps und Hilfe im Voraus.

#Frage #Friendica #Hintergrundbild #Titelbild !Friendica Support

Content warning: Gefilterter Begriff: 🇺🇦 Click to open/close

@Friendica Support
Habe gestern meine #Friendica Stable auf "Blutwurz" geupdated (ich musste diesen schönen Namen jetzt einfach mal schreiben)

Ich nutzte das #bookface scheme unter Frio.
https://github.com/randompenguin1/bookface
Dabei ist mir aufgefallen, dass das ich in Desktopgröße einen kleinen Darstellungsschönheitsfehler habe.
Da steht oben jetzt einmal in english "compose" und daneben noch mal in Deutsch, "neuer Beitrag" (siehe Screenshot!). Wie kann ich das vielleicht fixen?

[strong]Frage | Friendica: Werden nicht alle Bilder eines Beitrags nach Lemmy federiert?[/strong]

Mir ist eben aufgefallen das in einen Beitrag der zu Feddit.org (Lemmy) federiert wurde dort ein Bild fehlt. Ich weiß dabei nicht ob es nicht vielleicht an Lemmy liegt. Hier die URLs zu den Beitrag.

https://loma.ml/display/373ebf56-1969-793e-5cac-95f106440550

https://feddit.org/post/24960034

Habt Ihr auch schon solche Erfahrungen gemacht. Bisher hatte ich damit keine Probleme, habe aber auch nie darauf geachtet.

#Frage #Friendica #Lemmy #Federation #Bilder #2026-01-28 !Friendica Support

Hi guys,

I just experienced a wierd issue with image federation to #Mastodon.

This post contains 50Mpix image that never federates from #Friendica to Mastodon. Snac and Pleroma does not try to cache the image, so #federation to them works.

Shouldn't be thumbnail federated instead of full size image? Is this bug of Friendica or Mastodon?

I'm on 2024.12 so far, Yuno did not updated packages yet.

Thank you for help
!Friendica Support

Just noticed the new friendica version has been released . See https://github.com/friendica/friendica/releases/tag/2026.01

For u3a.social I'll be doing an upgrade on a test instance as soon as I can and then plan for the live upgrade (I'll also want to switch to native rather than docker database).

The nice thing about test upgrades is you get to test your backups !

@U3ACommunities Computing #friendica @Friendica Support #fediverse

@Michael 🇺🇦 oh wow, that's great news, thx. 🤗 [albeit also somewhat inconvenient in that any time i wish to add any new relay.fedi.buzz accounts i have to involve my instance-admin, rather than simply do it myself like in my sharkey & masto accounts]

i have three remaining #friendica accounts, so here's a question to each of
- @Melissa BearTrix #farcebookspace
- @Raroun #opensocialspace
- @Tuxi ⁂ #anonsysnet

pls would you each be kind enough to apply Michael's advice, which if i understand correctly, means:

bin/console relay add tag-aur@relay.fedi.buzz
bin/console relay add tag-arch@relay.fedi.buzz
bin/console relay add tag-archlinux@relay.fedi.buzz
bin/console relay add tag-distrobox@relay.fedi.buzz
bin/console relay add tag-firefoxnightly@relay.fedi.buzz
bin/console relay add tag-friendicahelp@relay.fedi.buzz
bin/console relay add tag-gnucash@relay.fedi.buzz
bin/console relay add tag-kmymoney@relay.fedi.buzz
bin/console relay add tag-lesbian@relay.fedi.buzz
bin/console relay add tag-linuxwomen@relay.fedi.buzz
bin/console relay add tag-montypython@relay.fedi.buzz 

thank you all very much.

cc:
@Droppie [opensoc]
@Droppie [anonsys] 🐨♀🌈🐧​🦘

#friendica #fedibuzz

@Friendica Support

hello. in my mastodon & sharkey instances, i can extend the range of hashtagged posts available from other servers by also following several @relay.fedi.buzz tags, eg

@tag-aur@relay.fedi.buzz
@tag-arch@relay.fedi.buzz
@tag-archlinux@relay.fedi.buzz
@tag-distrobox@relay.fedi.buzz
@tag-firefoxnightly@relay.fedi.buzz
@tag-friendicahelp@relay.fedi.buzz
@tag-gnucash@relay.fedi.buzz
@tag-kmymoney@relay.fedi.buzz
@tag-lesbian@relay.fedi.buzz
@tag-linuxwomen@relay.fedi.buzz
@tag-montypython@relay.fedi.buzz 

unfortunately, these seem non-functional in all my #friendica accounts.

am i doing something wrong? is there a way to make them work pls? 🤔🤷‍♀️

!Friendica Support Hi guys. Is there any way to integrate #XMPP with #Friendica? For example: authenticating with XMPP using Friendica credentials or some other integration? Thanks.

Hello !Friendica Support can someone share with me the activity pub troll domains, those bad actors I should put in the server block list?

would I add *.example.org oder *example.org or which is the correct way?

#Friendica

Hey all, in two week this years #FOSDEM will happen in #Brussels - there will be a Social Web Dev room on Saturday and a brief update about Friendica.

I heard whispers that @Michael 🇺🇦 and @Fabio will be there. Question who else? And would you mind to grab some fries and call it a #Friendica community meetup?

!Friendica Support

v.01
(Text in Edition zur spaeteren Weiterleitung an @Friendica Developers und @howTo @Tutorial )

Katharina Debus wrote:

Hallo allerseits, ich finde die Funktion nicht, wie ich Alternativtext für Bilder (in Posts) in friendica [Server loma.nl] eingeben kann.

In der Galerie geht das ueber das entsprechende Eingabefeld (wie bereits erwaehnt).
Leider ist das noch nicht direkt beim hochladen wahrend dem Erstellen eines Beitrags als Optionfeld beim hochladen der Fall. Das bedeutet unter anderem das wenn ein ALTtext bei der Textbearbeitung, wie weiter unten beschrieben, eingefuegt wird dieser Text gleichzeitig auch in die Galerie auftaucht.


Allgemein ist anzumerken das im Gegensatz zu #mastodon #friendica eine wesentlich bessere Bildergalerie besitzt. Ebenso das diese eigentlich noch nie wirklich ueberarbeitet wurde, das bedeutet unter anderem das die ALTtext Initiative fuer #barriereFreiheit auch nicht eingearbeitet wurde.

Angesichts dieser Umstaende ergibt sich folgende best practice zum erstellen von Beitraegen und Antworten:
(Bearbeitung vom Desktop aus)

• [li] Oeffne zwei Fenster, eines mit dem zu bearbeitenden Text, ein weiteres fuer die Bildergalerie.
  [li] Waehrend der Text bearbeitet wird werden im zweiten Fenster (Reiter) ueber die Fotogalerie die Bilder direkt in die entsprechenden Bilderkategorien hochgeladen.
  [li] In einem zweiten Schritt wird ein drittes Fenster geoffnet in dem die Fotogalerie zu sehen ist.
  * nach hochladen eines Bildes muss dieses Fenster aktualisiert werden um die neuen Bilder anzuzeigen.
  [li] Oeffnen des neuen Bildes in einem neuen Fenster.
  [li] Auswahl der Editierfunktion des neuen Bildes in dem Bildfenster.
  [li] Einfuegen des ALTtextes in dem Bildbeschreibungsfenster.
  [li] Einfuegen der hashtags fuer das betreffende Bild.
  [li] (Sicherheits)Ueberpruefung der Zugriffsberechtigungen fuer das betreffende Bild
  [li] Einfuegen des neuen Bildes in dem Themen- oder Antworttext ueber die

Bildereinfuegen aus Bildergalerie Option
* aktuell werden Bilder am Endes des Textfeldes eingefuegt. Bei mehreren Bildern erscheint es praktisch erste den gesamten Text zu erstellen und alle entsprechende Bilder zu bearbeiten, dann alle Bilder auf ein mal nach einander einzufuegen und dann die Bilder in den Text einzuordnen.
[li] Die Textfelder der Bildergalerie sind in der Ansicht sehr begrenzt. Bei laengeren Bildbeschreibungen empfiehlt es sich die Texte extern zu erstellen.
* Eine weitere Option ist den Text noch einmal im Textbearbeitungsfeld des Artikels mit einem Rechtschreibkorrektor zu ueberpruefen. Der bbCode macht dies allerdings sehr unuebersichtlich.

Hier eine recht neue ziemlich elaborierte und organisierte Bildergalerie eines Projektes und ein Link zu einem Thema inklusive Antworten das u.a. mit jener Bildergalerie erstellt wurde:
Bildergalerie bitpickup
Wochenbericht tierraNietos

Bildergaleriekatogorie der hier eingestellten howTo Bilder und weiterer screens die beim erstellen dieser Antwort gleich miterstellt und hochgeladen wurden:
https://tupambae.org/photos/utopiarte/album/667269656e646963615475746f
Diese zeigen die oben beschrieben Vorgehensweise, es fehlen jedoch noch die entsprechenden ALTtexte, deshalb wurden sie hier und jetzt noch nicht verwendet:


Allgemeine bbCode Optionen

Ansicht des bbCodes wenn ein Bild ueber das normale Textbearbeitungsfenster eingefuegt wurde:
[img][url=https://tupambae.org/photos/utopiarte/image/17782667726967b82ab6676886807720][img=https://washington.communitynetwork.us/photo/preview/1024/30975][/img][/url][/img]

Position in der der #ALTtext direkt im Textfenster eingefuegt werden kann:
[img][url=https://tupambae.org/photos/utopiarte/image/17782667726967b82ab6676886807720][img=https://washington.communitynetwork.us/photo/preview/1024/30975]DIES IST DER ORT AN DEM DER "ALTtext" IM TEXTBEARBEITUNGSFENSTER EINGEFUEGT WERDEN MUSS[/img][/url][/img]
(wie bereits erwaehnt, ein so erstellter ALTtext wird nicht in der Bildergalerie gespeichert!)

Detail:
..720-1.jpeg => -1 definiert die Aufloesung\Groesse des angezeigten Bildes. Originalgroesse waere ..720-0.jpeg




Bildercode der eingefuegt wird wenn ein Bild das zunaechst komplett ueber die Bildergalerie hochgeladen wurde, daraufhin in der Bildergalerie bearbeitet wurde und letzten Endes im Text ueber die aus der Bildergalerie einfuegen Option in den Text eingefuegt wurde:
[url=https://tupambae.org/photos/utopiarte/image/13167083826967ab673c232297153138][img=https://washington.communitynetwork.us/photo/preview/1024/30977]Bildbeschreibung die direkt in der Fotogalerie eingegeben wurde. Ein Bildschirmausschnitt zeigt den Antworttext der gerade eingestellt wurde. Ein Pfeil der mit der Nummer eins Identifiziert wurde zeigt eine der beiden Optionen wie direkt ein Bild in einen Text der in friendica erstellt wird hochgeladen werden kann.[/img][/url]

bugReport Bilder einfuegen und Bildergalerie

(friendica 2024.03)
* Bilder die in einer Untergalerie ueber das Textfeld eingefuegt wurden werden nicht direkt nach erneutem laden der Untergalerie angezeigt
* Kommentarefunktion in der Bildegalerie ist "broken". Die Texteditierung wird nicht uebernommen

Wunschliste Bilder einfuegen und Bildergalerie

[li] Bilder einfuegen ueber Textfeld:
* ALTtext Feld Option
* hashtagFeld Option
* Bildergaleriekategorie Option
* Spracheinstellungsoption fuer den ALTtext (und das Bild selber?)
Bildergalerie
* variable Textfeldergroesse in der Bildbearbeitungsseite der Bildergalerie
(Bulk-)Bilderohochladenseite
* ALTtext Option fuer alle gleichzeitig hochgeladenen Bilder
* hashTag Option fuer alle gleichzeitig hochgeladenen Bilder
* Spracheinstellungsoption fuer den ALTtext (und das Bild selber?)
* spezifisches ALTtext Feld fuer jedes hochgeladene Bild
* spezifische hashTag Option fuer jedes hochgeladene Bild
* temproraere Option fuer Bilder die noch nicht veroeffentlicht werden sollen oder noch bearbeitet werden muessen
* Veroeffentlichung zu einem speateren Zeitpunkt
* Vorprogramierbare Aenderung der Zugriffsberechtigung zu einem spaeteren Zeitpunkt

@Katharina Debus @VegOS @Thomas @Raroun

@Wilhelm thanks... somehow I kept missing things on Pleroma. The reason I switched to Pleroma originally was to play around, but then when my Friendica @utzer@social.yl.ms burned I was stuck on #Pleroma... also looked at Mastodon, but it just isn't checking all requirements I have. So I am back to Friendica and now Docker. I need to improve the setup, but I think it works quite fine like it is for now.

I love the "stay local" function, don't know why that is not a thing on Pleroma and the really reliable search for post URLs is such an underrated feature. Pleroma has this as well, but often it just doesn't work. Same is the search for users by handle, love #Friendica there too.