Yesterday I tried to setup my own version of OCRbot@fedi.lynnesbian.space, which does #OCR on pictures attached to posts on the #Fediverse, which I find an intriguing idea. During the process to set this up I was lazy and asked #ChatGPT to guide me through the whole process, which is fairly easy to be honest, but I an playing around with this #AI for fun.

I wanted to run the OCR #bot on my own #Friendica server, because I like to run on my own tech too.

So I asked Chatty to guide me and it worked well, I logged in with the Python bot and wanted to start it and got an API error, it was only then when I told ChatGPT that I am actually trying this with Frienidca and that the API might have its limits.
I then looked up the API documentation of the Mastodon API that Friendica implemented and asked ChatGPT if there is any essential parts missing that are needed to run the bot.

ChatGPT 'read' the documentation of both, the bot and the Mastodon API of Friendica and explained:
"Since Friendica doesn't support the Mastodon streaming API, the OCRbot, which relies on these endpoints, may not be compatible with Friendica without significant modifications to either the bot or the Friendica server."

Just wanted to write a bit about this experience with Friendica, the bot and ChatGPT.

Maybe I will setup a #Pleroma instance for this, a single user instance for me and the bot, maybe better a Mastodon instance?

cc !Friendica Support

I'm super excited about the #Fediverse. I've been online since the 90s, been through most evolution stages of the internet, and it feels like we're changing it once again - and this time in a good way.

Quoting this post anonymously because I don’t want to be the one to burst their newly reformed bubble. However I believe the honeymoon’s almost over with Threads entering the space, regardless of their intentions. They’re just too massive of a player not to shift the power dynamics in their favor.

People have long been angry at Gargron for sucking most of the Fediverse attention towards Mastodon through no particular fault of their own, and I believe it’s about to change, and not necessarily for the better.

For fringe projects like #Friendica, it won’t change much though, we never were prominent in the space and Threads’ arrival will not change that. @Michael Vogel ’s willing, we’ll start supporting the new API quirks Threads will inevitably put forth and leave the decision to interact with Threads or not to Friendica administrators and individual users.

Hilfe | Friendica: Beiträge mit fehlenden Bildern

Ich bekomme öfters Beiträge in denen etwas fehlt, ja die Bilder. Ich hatte eben mit @Matthias ✔ darüber und schreibe deshalb jetzt mal hier. Als Beispiel nehme ich den Beitrag über welchen wir es gerade hatten. Dieser Beitrag kam bei mir im Stream/Timeline Weitergesagt an:

Wenn ich den Beitrag inline aufrufe sieht er so aus:

Und wenn ich den Beitrag direkt auf dem Ursprungsserver aufrufe so:

Das es der VPN ist, konnten wir schon mal ausschließen. Der ist gerade nicht aktiv. Aber evtl. ist es ja ein kleiner Haken in den Einstellungen den ich nicht gesetzt oder entfernt habe.

Hat einer von Euch eine Idee wo das Problem liegen könnte?

Danke für Eure Hilfe und Tipps im Voraus! 😀

Tags: #Hilfe #Frage #Friendica #Beiträge #Bilder #Darstellung #Sascha #2023-12-23 !Friendica Support

Matthias ⁂

2023-12-23 21:22:24

wow

♲ @archillect@dis-le.de:

Aesthetic AI Mood

When writing the initial version of our project plan as signed and agreed with by NlNet we didn’t know yet about the dynamics of the community, specifically about how the cooperation between the maintainers of the #WordPress #ActivityPub plugin and #Mobilizon would be like. The level of collaboration with other #Fediverse developers would determine whether our project goals could only be achieved through a series of workarounds, or whether we could work together to strengthen interoperability and compatibility in the Fediverse.

Mobilizon was, until our project, the only Fediverse application with true event federation. #Gancio limits its ActivityPub capabilities to sending notes, but is working on a true federation of events, and other services like #Friendica have a very different approach to events: their implementation focuses on sending invitations rather than publishing events. As is usual with any software, you will find a lot of small bugs if you have not done any tests beforehand. In the case of Mobilizon, this was not possible since there were no alternative platforms to do the tests with, so the only option was to test the Federation with other Mobilizon servers. We seem to be the first and we are fascinated and incredibly grateful for the willingness and prioritization that such issues have among the other developers (thanks to tcit and les). The issues may seem small, but they have a big impact: 304, 33, 321, 1509, 1507, 1392, 1385, 1388, 1387, 1378, 1376.

The other deciding factor for us was that we didn’t know how close the interaction with the upstream WordPress AktivityPub project would be. The exchange of ideas and the desire for a joint solution is strong. We would like to thank @pfefferle again for the regular exchange, his ideas and inspiration, without his commitment to the community our project would be less sustainable.

Tasks done (almost)

• We published a repository that aims to make it easy for other developers, including ourselves to start developing and debugging WordPress along with Mobilizon.
• We have created a pull request to add management of various ActivityPub transformers to the admin interface. The current implementation basically works, but we have a lot to polish and improve on our roadmap.
• Using that patched ActivityPub plugin we explored writing transformers for two popular event plugins, this gave us a lot insight on what is important. These transformers already have fundamental compatibility with Moblizon.
• Updating our About us page showing some information who we are.

Upcoming tasks

• Implement FEP-2677: Identifying the Application Actor
• Implement the followers list of the application actor in the admin UI along with the ability to reject, approve, and remove followers. We are very inspired by how #PeerTube has solved this in the admin UI. This of course includes a an option as:manuallyApprovesFollowers that can be set for an ActivityPub actor within WordPress.
• Write an initial draft of the user documentation informing about custom ActivityPub transformers and instance-to-instance federation with Mobilizon. The target audience will be non-tech people. Parts of this will also be used as a non-tech description of our project.
• Improve the admin UI and propose a solution to handle the settings for each transformer, if there are any.
• Write more transformers for other popular event plugins to discover common pitfalls.

If you have any questions, ideas, or would like to help us, for example by testing our progress in case your are running a WordPress site with events yourself, please don’t hesitate to contact us. We don’t care if you have technical experience or what your background is: any kind of involvement is valuable to us.

https://event-federation.eu/2023/12/20/it-is-all-about-the-community/

#ActivityPub #Fediverse #Friendica #Gancio #Mobilizon #PeerTube #WordPress

Event Federation

2023-12-20 12:14:07

When writing the initial version of our project plan as signed and agreed with by NlNet we didn’t know yet about the dynamics of the community, specifically about how the cooperation between the maintainers of the #WordPress #ActivityPub plugin and #Mobilizon would be like. The level of collaboration with other #Fediverse developers would determine whether our project goals could only be achieved through a series of workarounds, or whether we could work together to strengthen interoperability and compatibility in the Fediverse.

Mobilizon was, until our project, the only Fediverse application with true event federation. #Gancio limits its ActivityPub capabilities to sending notes, but is working on a true federation of events, and other services like #Friendica have a very different approach to events: their implementation focuses on sending invitations rather than publishing events. As is usual with any software, you will find a lot of small bugs if you have not done any tests beforehand. In the case of Mobilizon, this was not possible since there were no alternative platforms to do the tests with, so the only option was to test the Federation with other Mobilizon servers. We seem to be the first and we are fascinated and incredibly grateful for the willingness and prioritization that such issues have among the other developers (thanks to tcit and les). The issues may seem small, but they have a big impact: 304, 33, 321, 1509, 1507, 1392, 1385, 1388, 1387, 1378, 1376.

The other deciding factor for us was that we didn’t know how close the interaction with the upstream WordPress AktivityPub project would be. The exchange of ideas and the desire for a joint solution is strong. We would like to thank @pfefferle again for the regular exchange, his ideas and inspiration, without his commitment to the community our project would be less sustainable.

Tasks done (almost)

• We published a repository that aims to make it easy for other developers, including ourselves to start developing and debugging WordPress along with Mobilizon.
• We have created a pull request to add management of various ActivityPub transformers to the admin interface. The current implementation basically works, but we have a lot to polish and improve on our roadmap.
• Using that patched ActivityPub plugin we explored writing transformers for two popular event plugins, this gave us a lot insight on what is important. These transformers already have fundamental compatibility with Moblizon.
• Updating our About us page showing some information who we are.

Upcoming tasks

• Implement FEP-2677: Identifying the Application Actor
• Implement the followers list of the application actor in the admin UI along with the ability to reject, approve, and remove followers. We are very inspired by how #PeerTube has solved this in the admin UI. This of course includes a an option as:manuallyApprovesFollowers that can be set for an ActivityPub actor within WordPress.
• Write an initial draft of the user documentation informing about custom ActivityPub transformers and instance-to-instance federation with Mobilizon. The target audience will be non-tech people. Parts of this will also be used as a non-tech description of our project.
• Improve the admin UI and propose a solution to handle the settings for each transformer, if there are any.
• Write more transformers for other popular event plugins to discover common pitfalls.

If you have any questions, ideas, or would like to help us, for example by testing our progress in case your are running a WordPress site with events yourself, please don’t hesitate to contact us. We don’t care if you have technical experience or what your background is: any kind of involvement is valuable to us.

https://event-federation.eu/2023/12/20/it-is-all-about-the-community/

#ActivityPub #Fediverse #Friendica #Gancio #Mobilizon #PeerTube #WordPress

les · GitLab

Framagit

^GitLab

Categories:LAMP, Linux, VPS

rootname@VPShosting:~$ sudo apt update
rootname@VPShosting:~$ sudo apt install apache2 -y

rootname@VPShosting:~$

sudo snap install core; sudo snap refresh core
sudo snap install --classic certbot

rootname@VPShosting:~$ sudo ln -s /snap/bin/certbot /usr/bin/certbot

rootname@VPShosting:~$ sudo certbot --apache

Configure PHP dependencies:
www-data@VPShosting:~$ cd html
www-data@VPShosting:~/html$ bin/composer.phar install --no-dev

rootname@VPShosting:~$ sudo ufw allow ssh
rootname@VPShosting:~$ sudo ufw allow http
rootname@VPShosting:~$ sudo ufw allow https
rootname@VPShosting:~$ sudo ufw enable
rootname@VPShosting:~$ sudo ufw status

rootname@VPShosting:~$

sudo apt install fail2ban -y 
rootname@VPShosting:~$ [code]sudo systemctl enable fail2ban

rootname@VPShosting:~$ systemctl status fail2ban

rootname@VPShosting:~$ sudo reboot

Because of the reboot you will be logged out of your VPS server and will have to log on again to proceed with the installation.

"M" like MySQL/mariaDB and "P" like PHP of "LAMP" installation

rootname@VPShosting:~$ sudo apt update

rootname@VPShosting:~$

sudo apt install mariadb-server php libapache2-mod-php \
     php-common php-gmp php-curl php-intl php-mbstring \
	 php-xmlrpc php-mysql php-gd php-imagick php-xml \
	 php-cli php-zip php-sqlite3 curl git -y

rootname@VPShosting:~$ sudo mysql_secure_installation

MariaDB [(none)]> CREATE DATABASE friendicadb;
Query OK, 1 row affected (0.000 sec)
MariaDB [(none)]> CREATE USER 'friendica'@'localhost' IDENTIFIED BY '<password>';
Query OK, 0 rows affected (0.002 sec)
MariaDB [(none)]> GRANT ALL ON friendicadb.* TO 'friendica'@'localhost';
MariaDB [(none)]> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> EXIT;
Bye

rootname@VPShosting:~#

To log from the console into your DB use the following command:
rootname@VPShosting:~# mysql friendicadb

To exit mariaDB:
MariaDB [friendicadb]> Ctrl-C -- exit!
Aborted
rootname@VPShosting:~#

install automysqlbackup
rootname@VPShosting:~# sudo apt-get install automysqlbackup
rootname@VPShosting:~# sudo automysqlbackup

#debian #linux #friendica #fediVerse #fediTutorial

#bugResearch

Dear Tupambae.org profiles, please add as answers to this post any kind of strange behaviour you might stumble over as inicial notes.

To prevent SPAMing this post please have a look first at the entire post.
Don't create new answers for the same issue, just edit your comment.
thx👍

If possible have a look at the open gitHub issues for #friendica in this link.

#bugResearch
[spoiler=Platform Info: 2023.05 - stable]Friendica Version: 2023.05 - stable
Friendica Source: gitHub 
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit	256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk
[/spoiler][hr]I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.[/spoiler][spoiler=Details of the buggy behavior:]Try to explain in short sentences and with precise wording what happens.[/spoiler][spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three[/spoiler][spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler][spoiler=Screenshots:][img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler][hr]information for dev and server team:[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]

#friendicaBugReport

Clean bug report as seen when you use the code block above

#bugResearch

Platform Info: 2023.05 - stable

Friendica Version: 2023.05 - stable
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk

I did/n't have a look at gitHub

Short bug description:

Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.

Details of the buggy behavior:

Try to explain in short sentences and with precise wording what happens.

¿Possible to reproduce, if so how:

step one to reproduce the problem
step two
step three

Expected result:

¿what should be the correct behavior?
¿what did you expect?

Screenshots:

information for dev and server team:

php.error.log

LEAVE THIS AS IS, the server team will use this report if possible/necessary

Categories: friendica,VPS,github

friendica installation on the VPS hosting
--
Up to this point we basically performed a standard LAMP installation on a ubuntu 22.04 LTS VPS hosting.

The following steps concern the actual friendica server installation.

creating the directory for friendica and the user www-data

rootname@VPShosting:~# sudo chown -R www-data:www-data /var/www
rootname@VPShosting:~# cd /var/www

rootname@VPShosting:~/var/www# sudo -u www-data bash
www-data@VPShosting:~$
(confirmation check if this is where console changes to www-data@VPShosting:~#)

www-data@VPShosting:~$ mv html html.bak
The new /html folder will be created when we clone the gitHub stable branch of friendica in the next step.

www-data@VPShosting:~$ git clone https://github.com/friendica/friendica.git -b stable html

www-data@VPShosting:~$ cd html
www-data@VPShosting:~/html$ bin/composer.phar install --no-dev
(is this the point the SSL install went wrong?)
https://squeet.me/display/962c3e10-1265-2ea9-912d-3cc762780991

www-data@VPShosting:~/html$ mkdir -p view/smarty3
www-data@VPShosting:~/html$ chmod 775 view/smarty3

www-data@VPShosting:~/html$ git clone https://github.com/friendica/friendica-addons.git -b stable addon

www-data@VPShosting:~/html$ cp .htaccess-dist .htaccess

www-data@VPShosting:~/html$ exit
rootname@VPShosting:~/var/www/html#

#debian #linux #friendica #fediVerse #fediTutorial

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-17 15:34:41

As of now I skipped this step as I do have already a DB with password and name on the original installation I will have to migrate to this new VPS.

@helpers@forum.friendi.ca

Server specs and friendica version used:
VPS server | Ubuntu 22.04 LTS
PHP Version 8.1.2-1ubuntu2.14
4 Core CPU, 8 GB Ram with 300GB NVME Disk
Friendica [STABLE] | 'Giant Rhubarb' 2023.05 - 1518

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-17 13:04:10

friendica VPS setup on ubuntu 22.04 LTS

@Friendica Support

Hi,
I'm working on my first #friendica #VPS installation, here you'll find my initial post about general thoughts like what distro to use, size and costs.
I'm using the tutorial "creating a friendica server - ubuntu" by @Hank G ☑️.

As of now I'm doing well in the process and want to start this post to document differences and questions while installing the server.

This server is going to host an already existing friendica node I have to move from another hosting provider. That means that for example the DB doesn't have to be created from scratch but moved and other smaller details.

I will try to address the different steps of installation in answers to this post and appreciate help, ideas and observations.

I'm doing this from a #linux desktop environment from the console but there shouldn't be differences if you want to do this from a #windows machine.

#fediVerse #tutorial #fediHelp #activityPub

Ihr habt vielleicht gemerkt, dass ich seit gestern um die Mittagszeit nicht aktiv war.

Grund ist, dass ich mir einen neuen #vServer #VPS hochgezogen und meine #Friendica #Instanz dorthin migriert habe.

Neben dem Aufwand, den man mit der kompletten #Neuinstallation und #Einrichtung eines Servers from Scratch hat (#SSH mit #Zertifikat, #PHP, #MySQL, #Apache, #LetsEncrypt / #Certbot, #Fail2Ban, #Firewall / #UFW, ...) , kam dann das Backupen von Friendica samt #Datenbank und das Neueinrichten auf dem neuen Server hinzu.

Dabei diverse kleinere Unwegsamkeiten wie dass sich das Datenverzeichnis geändert hat (anderer Apache-Hauptordner) und damit eine weiße Seite beim Aufrufen der Administration --> Speicher kam.
(BTW: Das habe ich durch einen temporären symbolischen Link gelöst).

Und schwups, ist ein guter halber Tag weg 🙈

Übrigens waren nach dem Umzug auf den neuen Server wieder diverse Emoticons aus Profilnamen weg (also lauter ?????).
Durch "Kontaktdaten neu laden" wurden und werden sie wieder korrekt dargestellt.
Dieses Problem verstehe ich noch immer nicht 🤔🤷‍♂️

Was bei den nun ersten Nutzungstests deutlicih besser respektive bislang verschwunden ist, ist das Problem fehlender Profilbilder oder ganzer Fehldarstellung der Seite beim Laden.

Hier war wahrscheinlich mein Webspace, auf dem Friendica bis gestern lief, doch einfach nicht leistungsfähig genug: 1024 MB RAM und 16 Kunden pro CPU-Kern für Mail, 2x #Joomla,1x große #Nextcloud und dann noch Friendica.

Der vServer hat nun 8 Kerne und 12 GB RAM und dümpelt (mit bislang nur Friendica darauf installiert) bei einer Load von < 1.

@Friendica Support