The Work Continues: What’s Next

Details will follow soon — but the work on events in the #Fediverse is far from complete. Key upcoming milestones include:

• Improvements and new features for the Event Bridge for [b]ActivityPub[/b] plugin for WordPress
  Continued development to maintain, fix issues, enhance, and expand functionality.
• Work on Fediverse Enhancement Proposals (FEPs)
  Ensuring a robust final status of FEP-8a8e and focus on recurring and irregularly scheduled events.
• Support for event interoperability in other Fediverse applications
  Contribute to other Fediverse applications and help them to explore and improve support for Event objects. For example, @linos@graz.social has outlined a potential roadmap for Mastodon.
• Contribution to GatherPress
  Active involvement in the GatherPress project — a modern and truly FLOSS community oriented WordPress event plugin — to ensure full ActivityPub compatibility, including RSVP support and advanced federation features.
• Community engagement and outreach
  Participation in conferences, public talks, and direct conversations to foster knowledge exchange, gather feedback, and grow the ecosystem around federated events.

Additional updates and technical details will be shared soon. Input, testing, and collaboration from interested parties are always welcome. Or if you know any conferences we should attend, let us know.

#ActivityPub #Events #Fediverse #FEP #GatherPress #WordPress

Publicacion scheduled for monday 2025-02-03 18:00
Dear studi0 community

We decided to add an #element #matrix #privateSpace #chatRoom to our setup and called it: tupambaeORGstudi0
Please be patient in any case as this is complete #Neuland for the admin in charge.

At least he managed to onboard a filmmaker, photographer and writer as the first step to understand how invites work!

So, hi there!
.. self-hosting based in Paris, France newbie @ elena@aseachange.com, director of The Illusionists documentary and #FOSDEM2025 traveler for your new proyect:
💌 #TheFutureIsFederated
The one who host's here 📷 photos apparently at @ ele@photos.elenarossini.com.

To begin with we created 3 rooms:

• studi0 community
• APP tutorials

  
  and as the first officialy approved project
  @jesuiSatire …ᘛ⁐̤ᕐᐷ managed to trigger:

• Projekt wahlKarnavalKrampf #foFritzMertz

In the @EDIT | don't follow! profile we creatd already a postString for that Projekt with a very limited time horizon.

Next step will probably be creating a activityPub #podcast handle on cast.tupambae.com by @utopiArte, the admin over there, as content colection and conversation about the idea itself in the EDITing post is already up and running.
Part of the details concerning the cast domain is to figure out how to organize the tools #castopod gives us at hand as it looks like it has quite interesting options to organize cooperation, as stated briefly in a tutorial page created on that site, result of the #learningBYdoing process while installing it: brief Castopod tutorial

Last but not least, we are still trying to drag @lizzischmidt the creator and promotor of the #sundayGimp community experience that is alive and running for over a decade on #diaspora* on to our shores, but federation with diaspora, from a technical point of view, definitely has seen better times in the past. Maybe this very cross community chat option, added right here and now, can help to improve the communication for all of us.

This inicial publication will federate quite well out into the vast space of the #fediVerse, but to see comments from the diaspora bubble and the #activityPub sphear, youll have to visit this original page on this friendica server.
Unless of course you are friendican yourself.

So, with no more further introduction, let's jam the #fediFolks!

https://tube.tchncs.de/w/u7q2ddpNfv6cUd2wcscbEL

EDITion | EN

2025-02-01 11:27:57

edition v.01a

@ studio0@tumpambae.org
Projekt [Vorschlag passend zum] #Karnavalswahlkrampf2025
#communityMediaProjektIdee iniziert von @aiquez und @jesuiSatire …ᘛ⁐̤ᕐᐷ basierend auf einer Idee von @aiquez aufgrund eines toots von @ chrisstoecker@mastodon.social

#FallVonMerz
Delenda die Ideen des foFritz Merz by @aiquez

ein Lied odar gar mehrere Lieder bis ihn zu einem ganzen Album:
-> Soundtrack zur Wahl/Nichtwahl von Merz / CXU

Themen:
Asozialität
Elitismus von Merz.

- hoffnung auf #FallVonMerz
- Ideen des Merz (sind Shyze ..)

-> Fall von #Brandmauer
-> #FallDesMerz #Merz epic fail

soundtrack [01(?)]:
Vorschlag -> Zeilen einer Strophe

Hochgeflogen
auf #BlackRock gelandet
alle Demokraten verprellt
sich Freundschaft mit Alice eingehandelt
#NiemandWillMerz und seine unfähige Rasselbande .. (Linnemann, Klöckner Spahn, CXU)
deren w'politische Ufähigkeit passt auf keinen Bierdeckel

in edition

I'm glad to announce the release of version 2.72 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes the following changes:

Each post can have more than one attachment from the web UI. The maximum number can be configured in server.json via the max_attachments value (default: 4).

Each notification includes a link labelled Context, that leads to a page with the full conversation tree the post is a part of.

Each followed hashtag has now a directly accesible link.

Fixed a search bug (some matches were missed).

Fixed more crashes (contributed by inz).

Fixed link detection in posts (contributed by inz).

Allow multiple editors for command-line posts (contributed by inz).

Separated maximum and default timeline entry count, allowing larger timelines to be requested without having to increase the default (contributed by lxo).

Turned message date into a link to the local post, so that it can be loaded into a separate tab for interacting with (contributed by lxo).

Special thanks to fellow developer inz for bringing my attention to code places where I should have been more careful.

https://comam.es/what-is-snac

If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/

#snacAnnounces

This release has been inspired by the song Songe d'un ange by #KyrieKristmanson and #BrendanPerry.

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?

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

Decentralizacja w #Fediverse.

Zakładacie profile na nowych instancjach?
Zdziwienie, że na starych (innych) instancjach nie widzicie nowych wpisów?

Nieważne, czy to Mastodon, Pixelfed, PeerTube czy inny serwis, warto zadbać o obserwację tych nowych profili na jak największej liczbie popularnych instancji.

Bo ActivityPub działa podobnie do e-mail. Wysyła wpisy jedynie tam, gdzie są adresy i profile, które go obserwują.
Nie ma centralnego repozytorium wszystkich wpisów jak w serwisach centralizowanych (np. Twitter/FB/YouTube).

Więc zanim zaczniecie publikować treści z nowych profili, poproście znajome osoby z różnych instancji, by wasze nowe konto zaobserwowały. A już na pewno zaobserwujcie sami siebie z własnych innych profili. Wtedy te treści mają szansę się federować na inne serwery. Inaczej pozostaną dostępne jedynie na instancji oryginalnej.

Tak to działa od samych początków #fediwersum opartego o protokół #ActivityPub 😀

#FediTipsPL #FediPomoc

📰 O Threats za The Verge:

"Threads przygotowuje się do głębszego wejścia w Fediverse. Dzieje się to dzięki uprzejmości Alessandro Paluzziego, który często dokonuje inżynierii wstecznej i ujawnia funkcje Threads i Instagram. Nowa opcja umożliwia dowolne włączanie i wyłączanie udostępniania Fediverse oraz łatwe kopiowanie nazwy użytkownika sformatowanej dla zdecentralizowanego protokołu społecznościowego #ActivityPub.
Szef Instagrama, Adam Mosseri, powiedział niedawno, że użytkownicy #Threads będą mogli także śledzić konta Fediverse w Threads i wchodzić z nimi w interakcję, choć ich konta będą musiały być w tym celu publiczne."

Żródło (zawiera screen z UI Threats):
https://www.theverge.com/2024/2/4/24061012/threads-is-preparing-to-venture-deeper-into-the-fediverse

Sometimes it is shocking how #intolerant people are here on #ActivityPub/#Mastodon.

Last week I was asked to respond to a divisive question and I [was asked to have] described how the intolerant people could interpret something (#lgbtq related) "the other way". I believe it was factual and politely phrased.

The next few hours resulted:
- four or five generic personal attacks, some quite impolite,
- about same amount of labels put on me ranging from nazi to queerphobian,
- 5 reports to my server ranging from "hate speech" through "racism" up to "queerphobia" as a description. (It is definitely telling, since they had so much hate that even failed to notice that I am my own server admin.) 3 of those were anonymous (sent in through a bot account).

All from random, uknown, uninvolved people. None of them understood the post, none of them was even open to understand how the people they fear think, none of them realised that their aggressive stance actually make neutral people stressed and angry and force them into a similarly aggressive defense loop, which results them being hated, in the long run. They've just seen something they didn't like from an unknown person and they didn't move on, didn't ignore it but started actively attacking.

Extremely close minded approach, even if they feel like, I don't know, hunted animals? But they see an attacker in every corner and they start to fight with about everyone not saying exactly what they wanted, even if it's just a quote, a description of a phenomenon or some mention within a discussion.

I am not really angry at them (while I get pretty annoyed when someone writes to me then blocks me, preventing any answer or reaction, but these people want to hear their own voice only), I'm just baffled at their extreme intolerance and short-sightedness, which is exactly the opposite of what they demand from others.

Well, business as usual.

Rebuilding FourSquare for ActivityPub using OpenStreetMap
https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spending the day at the park".

So, is there a way to recreate that early Web 2.0 experience with open data and ActivityPub? Let's find out!

This quest is divided into two parts.

1. Get nearby "Points of Interest" (POI) from OpenStreetMap.
2. Share a location on the Fediverse.

OpenStreetMap API

OpenStreetMap is the Wikipedia of maps. It is a freely available resource which anyone can edit (if they're skilled enough).

It also comes with a pretty decent API for querying things. For example, nw["amenity"]({{bbox}}); finds all "amenities" near a specific location.

As you can see, it has highlighted some useful areas - a pharmacy and a pub. But it has ignored other useful locations - the train station and the park. It has also included some things that we may not want - bike parking and a taxi rank.

What API call is needed to get useful locations of of OverPass?

It's possible to specify the type of thing to find using nw["amenity"="restaurant"]; - but adding every single type of thing would quickly end up with a very large query containing hundreds of types.

It is also possible to exclude specific types of places. This retrieves all amenities except for fast food joints:

nw["amenity"]({{bbox}});-nw["amenity"="fast_food"]({{bbox}});

Perhaps one solution is just to return everything and let the user decide if they want to check in to a telephone kiosk or a fire hydrant? That's a bit user-hostile.

Instead, this query returns everything which has a name nw["name"]({{bbox}});

That cuts out any unnamed things - like park benches and car-sharing spots. But it does add named roads and train lines.

It is possible to use filters to exclude results from OverPass. The best that I can come up with is: nw["name"][!"highway"][!"railway"][!"waterway"][!"power"]({{bbox}});

That gets everything which has a name, but isn't a highway or railway or waterway or powerline. It isn't perfect - but it will do!

This is the query which will retrieve the 25 nearest things within 100 metres of a specific latitude and longitude. It includes the name and any other tags, the location, and the OSM ID.

overpass-api.de/api/interpreter?data=[out:json];nw["name"][!"highway"][!"railway"][!"waterway"][!"power"](around:100,51.5202,-0.1040);out center qt 25;

ActivityPub

There's good news and bad news here. Firstly, ActivityStreams (which are subscribed to in ActivityPub) supports the concept of "Place" and "Location".

Once the user has a latitude and longitude, the can share it - along with a message, photo, or anything else.

Something like:

{    "@context": "https://www.w3.org/ns/activitystreams",    "type": "Note",    "content": "Here in NYC! <a href=\"https://www.openstreetmap.org/way/958999496\">John Lennon&#039;s Imagine Mosaic</a>.",    "attachment": [        {            "type": "Image",            "mediaType": "image\/jpeg",            "url": "https:\/\/fastly.4sqi.net\/img\/general\/590x786\/56367_9pxuZJD7d1hgPdaMFcFq1pipvTTMynBJsYcpHH-b8mU.jpg",            "name": "A photo of a mosaic which says &#039;Imagine&#039;."        }    ],    "location": {        "name": "John Lennon&#039;s Imagine",        "type": "Place",        "longitude": 40.77563,        "latitude": -73.97474    }}

It is worth noting that Mastodon doesn't (natively) support location - if you view my repost of that PixelFed post you'll see there's no location metadata attached. That's OK! It just means that the status needs to include human-readable data.

Similarly, Mastodon doesn't support the arrive vocabulary. So this will be limited to a message with a location attached.

Other ActivityPub services do support location.

Putting it all together

Well… that's a job for next week. Probably!

• Building a web site which gets the user's location is easy.
• Getting the data from OverPass should be straightforward.
• Creating an ActivityPub server which can post geotagged notes into the Fediverse might be a little beyond my skillset! Some testing with Darius Kazemi's AP Glitch suggests this should work.

If you'd like to help, please leave a comment.

https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

#ActivityPub #fediverse #FOURSQUARE #geolocation #OpenStreetMap

Terence Eden’s Blog

2024-01-27 12:34:55

Rebuilding FourSquare for ActivityPub using OpenStreetMap
https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spending the day at the park".

So, is there a way to recreate that early Web 2.0 experience with open data and ActivityPub? Let's find out!

This quest is divided into two parts.

1. Get nearby "Points of Interest" (POI) from OpenStreetMap.
2. Share a location on the Fediverse.

OpenStreetMap API

OpenStreetMap is the Wikipedia of maps. It is a freely available resource which anyone can edit (if they're skilled enough).

It also comes with a pretty decent API for querying things. For example, nw["amenity"]({{bbox}}); finds all "amenities" near a specific location.

As you can see, it has highlighted some useful areas - a pharmacy and a pub. But it has ignored other useful locations - the train station and the park. It has also included some things that we may not want - bike parking and a taxi rank.

What API call is needed to get useful locations of of OverPass?

It's possible to specify the type of thing to find using nw["amenity"="restaurant"]; - but adding every single type of thing would quickly end up with a very large query containing hundreds of types.

It is also possible to exclude specific types of places. This retrieves all amenities except for fast food joints:

nw["amenity"]({{bbox}});-nw["amenity"="fast_food"]({{bbox}});

Again, that would be complex.

Perhaps one solution is just to return everything and let the user decide if they want to check in to a telephone kiosk or a fire hydrant? That's a bit user-hostile.

Instead, this query returns everything which has a name nw["name"]({{bbox}});

That cuts out any unnamed things - like park benches and car-sharing spots. But it does add named roads and train lines.

It is possible to use filters to exclude results from OverPass. The best that I can come up with is: nw["name"][!"highway"][!"railway"][!"waterway"][!"power"]({{bbox}});

That gets everything which has a name, but isn't a highway or railway or waterway or powerline. It isn't perfect - but it will do!

This is the query which will retrieve the 25 nearest things within 100 metres of a specific latitude and longitude. It includes the name and any other tags, the location, and the OSM ID.

overpass-api.de/api/interpreter?data=[out:json];nw["name"][!"highway"][!"railway"][!"waterway"][!"power"](around:100,51.5202,-0.1040);out center qt 25;

ActivityPub

There's good news and bad news here. Firstly, ActivityStreams (which are subscribed to in ActivityPub) supports the concept of "Place" and "Location".

Once the user has a latitude and longitude, the can share it - along with a message, photo, or anything else.

Something like:

{    "@context": "https://www.w3.org/ns/activitystreams",    "type": "Note",    "content": "Here in NYC! <a href=\"https://www.openstreetmap.org/way/958999496\">John Lennon&#039;s Imagine Mosaic</a>.",    "attachment": [        {            "type": "Image",            "mediaType": "image\/jpeg",            "url": "https:\/\/fastly.4sqi.net\/img\/general\/590x786\/56367_9pxuZJD7d1hgPdaMFcFq1pipvTTMynBJsYcpHH-b8mU.jpg",            "name": "A photo of a mosaic which says &#039;Imagine&#039;."        }    ],    "location": {        "name": "John Lennon&#039;s Imagine",        "type": "Place",        "longitude": 40.77563,        "latitude": -73.97474    }}

For example, here's a PixelFed post with an attached location - and this is the JSON representation. That status can be reposted into other social networks.

It is worth noting that Mastodon doesn't (natively) support location - if you view my repost of that PixelFed post you'll see there's no location metadata attached. That's OK! It just means that the status needs to include human-readable data.

Similarly, Mastodon doesn't support the arrive vocabulary. So this will be limited to a message with a location attached.

Other ActivityPub services do support location.

Putting it all together

Well… that's a job for next week. Probably!

• Building a web site which gets the user's location is easy.
• Getting the data from OverPass should be straightforward.
• Creating an ActivityPub server which can post geotagged notes into the Fediverse might be a little beyond my skillset! Some testing with Darius Kazemi's AP Glitch suggests this should work.

If you'd like to help, please leave a comment.

https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

#ActivityPub #fediverse #FOURSQUARE #geolocation #OpenStreetMap

05 - Find nodes by applying multiple filters

A basic tutorial covering the key features of the Overpass language

^{osm-queries.ldodds.com}

#Facebook inherently isn’t bad

yes it is.

#hashtags

Hashtags are supposed to be from all the contacts that has a server in the #fediVerse, if the posts were published publicly. Their for mastodon.social with it's overwhelming user base should be connected to a very large percentage of the fediverse accounts (that's an interesting percentage investigation to do). It even has introduced full text search and I guess it's using it so that's another tool in one place to get a lot of the total info out there.

#friendica has relays, I never checked that option out but if you dig into it you'll find some answers. In the latest release it added "channels" to create streams of selected gathered information, another thing I haven't digged into yet. Actualy friendica and #hubzilla might be the ones that can tap into most info on the fediverse. Those communities, both inicialized by Mike, have kinda basic goal to create workarounds in the fediVerse to connect to everyone and everything. Thinking about it, friendica might be the oldest thriving #activityPub speaking platform out there.

My recommendation to check out friendica in your case would be squeet.me as it is run by one of the german main devolpers of that platform so it's always on the latest dev branch.

following activitypub, which is an unsorted mess of information overflow

That's an impression I get first of all in the #mastodon stream as every answer pops up like a single unrelated contextles bubble in once universe that most likely might create some declaration of war in some other distant universe that ultimately might just lead to a dog swolling some toy ball.

many () problems can be traced back to Homo Sapiens Sapiens

all of 'em, that's why spanisch is the choosen language in this case as it spells mono sapiens -> #VIATA
At the same time, blaming the user while the boss considers them "dumb fucks" and gives out the instruction "be fast and break things" sounds like kinda victim blaming.

No it never does, it makes your world view distorted

That's what I mean by: their own disconnected reality.
What wasn't to clear in my answer is that apparently they gathered into bubbles on places like fb and went of from there to GAB or apparently now a days #telegram groups.
btw
Every world view is distorted, by default, there is no way around that fact.

It is necessary sometimes to touch foreign subjects, meet new people, read unusual threads, outside your comfort zone. At least that’s my experience.

More than agreed:
#TEDtalk:

That was another bubble.

Or they managed to organize.

Bubbles are fine, not only for marginalized groups and can be helpful and uplifting.
Point is when they lead to radicalization, "Tunnelblick", "Scheuklappen" (blinders).
Actually they create an own norm, an own culture, an own tribe. That can lead to diversification that can be good and useful, why not. Kinda like always it's the concentration that makes it medicine or abused drug, that's why I wrote semipermeable as an important part of the setup.

#GAFAM created a asocial environment, some reasons you mentioned, the first reason because they could and it was good buisenes (for them). So "we" decided to go for the free network (redes libres/freie Neztzwerke) to disentangle and start all over again. My peers are my algorithm that create my feed of input. And as my vibes and emotional situation changes, I'll have to adapt my feed constantly if I want to stay in charge. If I refer that task to my smart watch I'm doomed to become aligned to a (main)stream others decide over. AI is going to make that most likely worse because it's becoming more and more complex and we rely on some coders that say "bad dog! baaad dog!" to the AI. Meanwhile in Myanmar some genocide is fostered, fb traces the data for their AI and the billionairs say:
"Well, some workers died when the golden gate bridge was build, bad luck, that's colateral damage worth it."

how to friendica install for ubuntu VPS
(lot's of spoilers!)

For your acronym dictionary:
#slatfatf
https://pod.geraspora.de/tags/slatfatf

https://pod.geraspora.de/tags/acronymlist

.. and yes, I have long blond hair too ..

Si quieres leerlo en húngaro, pulsa aquí.

@utopiArte

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