To begin with @Hypolite Petovan, the original idea is to offer for example to projects like @YunoHost :neopossum_box: or @Castopod 😛odcasting2: a profile on forum.friendi.ca, the same way our very @Friendica Support works.
Most #fediVerse platforms have profiles on their own platform and/or a #mastodon profile, because that's the kinda standard thought and behavior. But actually to me it looks like the #friendica #communityForum page capabilities exceed by far what mastodon or others have to offer. Well, I haven't digged into the fedi clone of reddit to see if that would be an even better option. What is true tho is that forum.friendi.ca is already long standing and our community has gone a long way, so there is in general terms "no single point of failure" like in other projects that depend on one main figure and that's it.

I consider our helpers community experience here, with all the followers of our helpers page getting resend the help requests posted to the forum, chiming in to help out and solve issues, very positive. So this is a proven setup and could help lot's of other projects out here too. Actually I do think that if implemented and adopted, it even could have a positive feed back loop for friendica itself, but that's like something on another page.

So having forum.friendi.ca already up and running, why not support the fediVerse community opening our doors to those who fulfill certain basic community standards?

This server here (tupambae.org) as well is only mend to be a forum server, and of course it's doors are open for any #fediPlatform that likes to have an own forum page over here, yet somehow to me it look's like forum.friendi.ca is the first natural and ideal candidate for something like that.

Of course same goes for a #fediAdmin, #activityPub or #APIdeveloppers community support forum, if that is desired or useful.

Right now in general terms the fedi lives on using some tags or maybe some a.gup.pe addresses, but it's actually us who hold and develop that option for more than a decade now inside the federation itself.

Was that more clarifying @hypolite?

!Friendica Developers !Friendica Support As of right now I am not sure if my #Friendica instance is working across the #fediverse as I am not seeing much engagement at all, and more than half of who I am following, I am not receiving their #feeds at all, and at this point I am clueless as to what is going on or how to deal with, because I dont know what is wrong, or if anything is wrong.

VersionFriendica 'Interrupted Fern' 2025.02-dev - 1576
Server Settings
PHP
version 8.1.31
php.ini /opt/alt/php81/etc/php.ini
upload_max_filesize 256M
post_max_size 256M
memory_limit 512M
MySQL / MariaDB
max_allowed_packet 268435456

I am not seeing much engagement, more so I am not seeing posts of those I follow across the fediveres, and I know several post a few times a day, but I am not seeing much activity at all, any ideas on what may be going on would be great, and please any directions please make very simple to understand, brain issues, sometimes I struggle grasping things that should be easy. If it matters, I am in cPanel on shared hosting, so not root access to anything.

https://social.2ndshot.photos/profile/pasjrwoctx pasjrwoctx@social.2ndshot.photos

Friendica Installation

Ich versuche gerade die #Fediverse Anwendung #Friendica auf meinem #Raspberry Pi 5 in einem #Podman #Container zu installieren. Aber bei der Datenbank ist Schluss. da bleibt es hängen. Weiß jemand Rat? @Friendica Support zum Beispiel?

version: "3.7"

services:

  mariadb:
    image: docker.io/library/mariadb:latest
    restart: always
    volumes:
      - mydb:/var/lib/mysql
    ports:
      - "6033:3306"
    environment:
      MYSQL_ROOT_PASSWORD: *****
      MYSQL_DATABASE: friendica
      MYSQL_USER: friendica
      MYSQL_PASSWORD: *****

  phpmyadmin:
    container_name: phpmyadmin_9092
    image: docker.io/library/phpmyadmin:latest
    restart: always
    ports:
      - "9092:80"
    environment:
      - PMA_ARBITRARY=1
      - PMA_HOST=mariadb
    depends_on:
      - mariadb

  app:
    image: docker.io/library/friendica
    container_name: friendica_9093
    restart: always
    volumes:
      - friendica:/var/www/html    
    ports:
      - "9093:80"
    environment:
      - MYSQL_HOST=mydb
      - MYSQL_USER=friendica
      - MYSQL_PASSWORD=*****
      - MYSQL_DATABASE=friendica
      - FRIENDICA_ADMIN_MAIL=*****
    depends_on:
      - mariadb

volumes:
  mydb:
  friendica:

networks:
  proxy-tier:

Thx for your link and efforts @Seirdy !

All this said, being part of a decentralized web, as pointed out in this toot, our publicly visible interaction lands on other instances and servers of the #fediVerse and can be scrapped there. I wonder if this situation actually might lead, or should lead, to a federation of servers that share the same robots.txt "ideals".

As @Matthias pointed out in his short investigation of the AI matter, this has (in my eyes) already unimagined levels of criminal and without any doubt unethical behavior, not to mention the range of options rouge actors have at hand.

It's evident why for example the elongated immediately closed down access to X's public tweets and I guess other companies did the same for the same reasons. Obviously the very first reason was to protect their advantage about the hoarded data sets to train their AI in the first place. Yet, considering the latest behavior of the new owner of #twitter, nothing less than at least the creation of #AI driven lists of "political" enemies, and not only from all the collected data on his platform, is to be expected. A international political nightmare of epical proportions. Enough material for dystopian books and articles for people like @Cory Doctorow, @Mike Masnick ✅, @Eva Wolfangel, @Taylor Lorenz, @Jeff Jarvis, @Elena Matera, @Gustavo Antúnez 🇺🇾🇦🇷, to mention a few of the #journalim community, more than one #podcast episode by @Tim Pritlove and @linuzifer, or some lifetime legal cases for @Max Schrems are at hand.

What we are facing now is the fact that we need to protect our and our users data and privacy because of the advanced capabilities of #LLM. We basically are forced to consider to change to private/restricted posts and close down our servers as not only the legal jurisdictions are way to scattered over the different countries and ICANN details, but legislation and comprehension by the legislators is simply none existent, as @Anke Domscheit-Berg could probably agree to.

Like to say, it looks like we need to go dark, a fact that will drive us even more into disappearing as people will have less chance to see what we are all about, advancing further the advantages off the already established players in the social web space.
Just like Prof. Dr. Peter Kruse stated in his take about on YT The network is challenging us min 2:42 more than 14 years ago:
"With semantic understanding we'll have the real big brother. Someone is getting the best out of it and the rest will suffer."

The 2024 IFTAS Needs Assessment Report is Here!

We are pleased to to announce the release of the 2024 Fediverse Trust & Safety Needs Assessment Report. This annual report is a cornerstone of our mission to support the decentralised social web with evidence-based research and actionable recommendations for moderators, community managers, and administrators.

This year’s report reflects the insights of 183 services spanning platforms like Mastodon, Lemmy, and Peertube, collectively hosting over 4.3 million accounts. This year we also heard from volunteer independent moderators on Bluesky. By analysing the experiences and feedback of these moderators and admins across the Fediverse, the report highlights the challenges and opportunities within this rapidly evolving ecosystem.

We will follow up with an analysis of what we’ve seen change since last year’s report, as well as key resources we think can help solve some of the needs identified.

Key Findings

• Resource gaps – only 16% of communities have 24-hour moderator coverage, and nearly half of moderator teams lack formal guidance. That said, we see roughly one moderator for every 1,200 active accounts.
• Top ranked priorities – moderators need tools for CSAM detection, spam prevention, and legal guidance for compliance with regulations like GDPR.
• Burnout is a persistent issue – one in five moderators report experiencing trauma or burnout this year, underlining the need for wellness and resilience resources.
• Financial struggles – most communities operate on donations, and overall our survey participants are not generating enough money to cover costs. Very few moderators are receiving any compensation for their labour.

IFTAS Initiatives

Informed by last year’s findings, IFTAS has developed several solutions and programs, including a Fediverse CSAM scanner, a comprehensive Moderator Handbook (coming soon), and the creation of FediCheck for automated denylist management. Moving forward, we aim to expand resources for moderator wellness, launch our CSAM scanner for broader use (please register your interest), improve tooling for non-consensual image detection, and introduce new community guidelines templates.

We encourage everyone in the Fediverse community to read the full report for a deeper understanding of the challenges facing decentralised moderation and the innovative solutions underway.

➡️ Read the Full Report Here

Get Involved

IFTAS thrives on collaboration. Join our community of practice at IFTAS Connect, use our resources, or support our mission with a charitable donation to help make the Fediverse a safer, more inclusive space for all.

Let’s work together to empower moderators and create a stronger, safer social web!

#TogetherStronger 💙

#ActivityPub #BetterSocialMedia #Bluesky #Fediverse #TogetherStronger