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.

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

@Friendica Support
Hi there,
not sure if this is a bug or just that I'm missing some idea/rule functionality.

#bugResearch

I didn't have a look at gitHub

See image gif in screenshots spoiler

#newHere #neuHier #hola

[img=https://fika.grin.hu/photo/media/411601]Gif scene of the movie "The Martian".

The lonely main actor is sitting on a stone on the inhabited planet he was left on alone.
A text reads:
"First day in the diaspora of the fediVerse .."

The astronaut is depicted how he opens the solar panels of his equipment, presses a big button on it and the hashtags #hola, #neuHier and #newHere appear.

In the last scene he sits again on his stone and the text: ".. wait .." is displayed.

In the first scene that reads the text about the first day in the fediVerse the probably oldest logo of the fediVerse is displayed at the bottom left of the scene. At the horizon on the right the actual logo of the the fediVerse rises behind the landscape.

In the last scene, while our hero is awaiting the outcome of his intent to make contact with the outside world, the old Federated Social Web logo appears in front of the sun.[/img]

#[url=https://tupambae.org/search?tag=fediVerse]fediVerse[/url] #[url=https://tupambae.org/search?tag=fediHelp]fediHelp[/url] #[url=https://tupambae.org/search?tag=fediTips]fediTips[/url] #[url=https://tupambae.org/search?tag=gimp]gimp[/url] #[url=https://tupambae.org/search?tag=gimped]gimped[/url] 
@ gimped@tupambae.org @[url=https://tupambae.org/profile/tutorial]Tutorial[/url]

Screenshots:

Mastodon and today's fediverse are unsafe by design and unsafe by default – and instance blocking is a blunt but powerful safety tool

Parts 1, 2, and 3 of "Golden opportunities for the fediverse – and whatever comes next"

https://privacy.thenexus.today/unsafe-by-design-and-unsafe-by-default/

Over the course of this multi-part series, I'll discuss Mastodon and the fediverse's long-standing problems with abuse and harassment; the strengths and weaknesses of current tools like instance blocking and blocklists; the approaches emerging tools like #TheBadSpace and #Fediseer take, along with potential problems; paths to improving the situation; and how the fediverse as a whole can seize the moment and build on the progress that's being made; . At the end I'll collect it all into a single post, with a revised introduction.

This first installment has three sections:

- Today's fediverse is unsafe by design and unsafe by default

- Instance-level federation choices are a blunt but powerful safety tool

- Instance-level federation decisions reflect norms, policies, and interpretations

#fediverse #mastodon

Preparing to move the DB

Changing the #storage backend to reduce DB size.

Admin panel:

Helpers-page information

Moving storage via SSH

¿correct?:

mkdir /var/www/html/storage
./bin/console config storage.name = Filesystem
./bin/console config storage.filesystem_path = storage
./bin/console storage move

So sieht es bei mir aus:
Momentan kennt dieser Knoten 4.273 Knoten mit insgesamt 2.120.886 registrierten Nutzern, die die folgenden Plattformen verwenden:

• #Friendica (379/4.024) - 10 Nutzer pro Instanz
• #diaspora (304/628.472) - 2.067 Nutzer pro Instanz
• #red (7/64) - 9 Nutzer pro Instanz
• #hubzilla (264/7.687) - 3 Nutzer pro Instanz
• #GNU Social (136/6.425) - 47 Nutzer pro Instanz
• #StatusNet (9/174) - 19 Nutzer pro Instanz
• #Mastodon (2.722/1.451.747) - 901 Nutzer pro Instanz
• #pleroma (446/21.092) - 47 Nutzer pro Instanz
• #socialhome (4/973) - 243 Nutzer pro Instanz
• #ganggo (2/228) - 114 Nutzer pro Instanz

Bei Diaspora scheint es also am kompliziertesten zu sein, eine eigene Instanz zu betreiben (oder die Nutzer vertrauen den Betreibern am meisten 😉 ) und bei Hubzilla ist es am einfachsten (oder die Nutzer sind am mistrauischsten 😉 ).

Da ich mal wissen wollte, wie sich das über die Zeit entwickelt, habe ich mir das von Zeit zu Zeit mal notiert und so sieht es dan aus:

• 8. Januar : 4.253 / 2.349.200 -> Maximale Anzahl an Nutzern
• 9. Januar : 4.241 / 2.345.669
• 10. Januar : 4.231 / 2.330.945
• 11. Januar : 4.226 / 2.334.113
• 13. Januar : 4.229 / 2.039.934
• 14. Januar : 4.259 / 2.054.374
• 15. Januar : 4.252 / 2.059.012
• 16. Januar : 4.246 / 2.007.713
• 27. Januar : 4.215 / 2.025.384
• 7. Februar: 4.208 / 2.124.247
• 10. Februar: 4.245 / 2.131.417
• 23. Februar: 4.267 / 1.769.948
• 27. Februar: 4.243 / 2.181.948
• 3. März: 4.273 / 2.120.880 -> Maximale Anzahl an Instanzen

Die Anzahl der Instanz korreliert also nicht unbedingt mit der Anzahl der Nutzer, auch interessant.

#föderation #Fediverse

There are two ways to add your keys to #FileZilla.

You can add your keys inside the "Site Manager":

Go to:
File -> Site manager ..

Protocol:
In the settings panel for a given site select sFTP:

Add domain IP or domain name:

Logon Type:
Select "Key File"

Add the user name to log onto the server:

Browse for the .ppk you want to add and select it:
FileZilla offers you also to add .pem (privkey.pem) files, that's the #puTTy option for a file containing only the extracted private key of keyfile.ppk. At the same time FileZilla doesn't read/accept .pem files so it will prompt you to transform it into a .ppk file. If your .ppk is protected by a password (it should be), you get prompted to insert the password.
It is not clear if the newly created .ppk file from the .pem file by FileZilla is protected with the same password. It doesn't feel like that.

Save the changes and connect to your server.

The other option to add your key to FileZilla is by adding it directly to the main settings.

Go to:
Edit-> Settings ..

Choose SFTP and select the "Add key file" tab:

Add the key file and save.
If you use the input fields and quick connect options of the main FileZilla window, the keys saved in settings will be retrieved.

#linux #windows #howTo #fediVerse

@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

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-12 18:28:38

what VPS offer fits best for a small friendica instance?

@Friendica Support
@Friendica Admins
@Friendica Developers

Hi there,
in the end I want to try to setup my first own hosted friendica VPS on a small setup:
1gig RAM/1 Core/25gig

The idea is kinda single user instance with a few forum pages.

The hosting provider has the following options:

• debian bullsey - vpn server
• debian bookworm - wireguard server
• debian bookworm - bookworm 2023-07-03
• debian bookworm - bookworm 2023-07-03 LEMP (nginx+php8.2+mariaDB10.5)
• debian bookworm - nextcloud
• ubuntu 22.04.01LTS
• CENTOS8.1 - 2020-05-03
• cleanVPS to upload own ISO

I'm used to debian/devuan on PC, so am obviously inclined to go for debian but have no idea what version would be the best choice.

In the first place the debian LEMP option looks like the way to go.
Latest experience with a new friendica installation seemed to be in need of PHP8.1 instead of PHP8.2.
Is it difficult to downgrade that?

Also, I'm kinda worried about security in general, even tho the data exposed will only be my own, so there is no responsibility with others.
Are there more security risks than on a shared hosting with let's say a standard phpBB forum page?

The idea would be to point the IP from my existing hosting provider to the VPS.

• Do we have some general "how to setup" for a VPS setting from scratch?
• Anyone interested in creating such a "how to" in a conversation with me here to have a refence or base to sum that up for the frindica wiki?
• Could it even be of interest to create a "friendica VPS-ISO installation" with the help of git.friendi.ca for example?

@TupambAdmin
@bitPickup mʕ•ﻌ•ʔm