IFTAS is happy to announce the public availability of our DSA Guide for Decentralized Services – a practical guide for small and micro services that are subject to the EU’s Digital Services Act.

If your server has member accounts in the EU, or is publicly viewable in the EU, your service is most likely impacted by this regulation, even if you are not based or hosted in the EU.

Developed in collaboration with the great people at Tremau, our DSA Guide is designed to help independent social media service providers navigate these complex regulations and achieve compliance with these new rules without compromising the unique qualities of federated, open social networks.

As part of our Needs Assessment activities, we’ve heard a repeated need for help understanding the complex regulatory landscape that decentralized services need to consider, and this DSA Guide is the first of many in our plan to provide clear, actionable guidance to a range of regulations for the community.

As of February 2024, all online services and digital platforms that offer services in the European Union are required to be fully compliant with the DSA.

However, various portions of the DSA are not applicable to “small and micro” services, and this guide will show you clearly which parts apply and which do not.

For administrators of platforms like Mastodon, PeerTube, and Pixelfed, the DSA Guide can help demystify the requirements and offer practical advice on achieving compliance for the over 27,000 independent operators of these and other decentralized social media services who otherwise may not be able to obtain the guidance and advice that larger operations can afford to invest in.

Download the DSA Guide for Decentralized Fediverse Services.

To join the discussion, visit our community chat service at https://matrix.to/#/#space:matrix.iftas.org or stay tuned to join our community portal in the coming weeks!

https://about.iftas.org/2024/04/09/dsa-guide-for-the-fediverse/

#ActivityPub #BetterSocialMedia #DSA #Fediverse

IFTAS

2024-04-09 12:02:00

IFTAS is happy to announce the public availability of our DSA Guide for Decentralized Services – a practical guide for small and micro services that are subject to the EU’s Digital Services Act.

If your server has member accounts in the EU, or is publicly viewable in the EU, your service is most likely impacted by this regulation, even if you are not based or hosted in the EU.

Developed in collaboration with the great people at Tremau, our DSA Guide is designed to help independent social media service providers navigate these complex regulations and achieve compliance with these new rules without compromising the unique qualities of federated, open social networks.

As part of our Needs Assessment activities, we’ve heard a repeated need for help understanding the complex regulatory landscape that decentralized services need to consider, and this DSA Guide is the first of many in our plan to provide clear, actionable guidance to a range of regulations for the community.

As of February 2024, all online services and digital platforms that offer services in the European Union are required to be fully compliant with the DSA.

However, various portions of the DSA are not applicable to “small and micro” services, and this guide will show you clearly which parts apply and which do not.

For administrators of platforms like Mastodon, PeerTube, and Pixelfed, the DSA Guide can help demystify the requirements and offer practical advice on achieving compliance for the over 27,000 independent operators of these and other decentralized social media services who otherwise may not be able to obtain the guidance and advice that larger operations can afford to invest in.

Download the DSA Guide for Decentralized Fediverse Services.

To join the discussion, visit our community chat service at https://matrix.to/#/#space:matrix.iftas.org or stay tuned to join our community portal in the coming weeks!

https://about.iftas.org/2024/04/09/dsa-guide-for-the-fediverse/

#ActivityPub #BetterSocialMedia #DSA #Fediverse

The extraterritorial implications of the Digital Services Act - DSA Observatory

Laureline Lemoine & Mathias Vermeulen (AWO) As the enforcement of the Digital Services Act (DSA) is gathering speed, a number of non-EU based civil society and research organizations have wondered to what extent the DSA can have an impact on their wo…

^{admin (DSA Observatory)}

HTTP Signature Infinite Loop?
https://shkspr.mobi/blog/2024/02/http-signature-infinite-loop/

I'm trying to get my head round HTTP Signatures as they're used extensively in the Fediverse.

Conceptually, they're relatively straightforward.

You send me a normal HTTP request. For example, you want to POST something to https://example.com/data

You send me these headers:

POST /dataHost: example.comDate: Sat, 24 Feb 2024 14:43:48 GMTAccept-Encoding: gzipDigest: SHA-256=aaC57TDzM0Wq+50We2TkCsdMDvdqON92edg7KI+Hk8M=Content-Type: application/activity+jsonSignature: keyId="https://your_website.biz/publicKey",algorithm="rsa-sha256",headers="(request-target) host date digest content-type",signature="JGQ53kEoIiMWRp9By9jajVGCOCu4n7XBeiA1uY5xLcnAxL2Y1GIgU/...=="Connection: Keep-AliveContent-Length: 751

1. Check the SHA-256 hash of the message matches the content of the "Digest" header.
2. Check the timestamp is somewhat fresh.
3. Check the signature matches.

The first is simple: base64_encode( hash( "sha256", $request_body, true ) ).
The second is a matter of opinion. I might be happy to receive messages from the distant past or far in the future. For the sake of a little clock drift, let's allow 60 seconds either way.
The third gets complicated.

First, I need to get the public key published at keyId="https://your_website.biz/publicKey".

Next, I need to know which algorithm is being used to sign the headers: algorithm="rsa-sha256"

Then, I need to know which headers - and in what order - are being signed: headers="(request-target) host date digest content-type"

So I create a string using the received details which matches those headers in that specific order:

(request-target) POST /dataHost: example.comDate: Sat, 24 Feb 2024 14:43:48 GMTDigest: SHA-256=aaC57TDzM0Wq+50We2TkCsdMDvdqON92edg7KI+Hk8M=Content-Type: application/activity+json

openssl_verify(    $headersString,     $signature,     $publicKey,     $algorithm);

But can you spot the implicit problem?

How do I get your server's public key?

I just GET https://your_website.biz/publicKey - but if your server uses something like Authorised Fetch then I have to sign my request to you.

Which means your server will need to validate my signature by obtaining my public key. Which it will get by signing a request and sending it to me. Which, before I return my public key, I will need to validate your signature by obtaining your public key. Which I will get by signing a request... and so on.

This deadlock loop is documented. The usual way around it is either for the sending server to use an instance-specific signature which can be retrieved by an unsigned request, or to allow any unsigned request to access a user's public key.

I get why things happen this way - I just wish it were easier to implement!

https://shkspr.mobi/blog/2024/02/http-signature-infinite-loop/

#ActivityPub #CyberSecurity #encryption #fediverse #http

Terence Eden’s Blog

2024-02-26 12:34:28

HTTP Signature Infinite Loop?
https://shkspr.mobi/blog/2024/02/http-signature-infinite-loop/

I'm trying to get my head round HTTP Signatures as they're used extensively in the Fediverse.

Conceptually, they're relatively straightforward.

You send me a normal HTTP request. For example, you want to POST something to https://example.com/data

You send me these headers:

POST /dataHost: example.comDate: Sat, 24 Feb 2024 14:43:48 GMTAccept-Encoding: gzipDigest: SHA-256=aaC57TDzM0Wq+50We2TkCsdMDvdqON92edg7KI+Hk8M=Content-Type: application/activity+jsonSignature: keyId="https://your_website.biz/publicKey",algorithm="rsa-sha256",headers="(request-target) host date digest content-type",signature="JGQ53kEoIiMWRp9By9jajVGCOCu4n7XBeiA1uY5xLcnAxL2Y1GIgU/...=="Connection: Keep-AliveContent-Length: 751

In order to verify the contents of the message, I need to do three things:

1. Check the SHA-256 hash of the message matches the content of the "Digest" header.
2. Check the timestamp is somewhat fresh.
3. Check the signature matches.

The first is simple: base64_encode( hash( "sha256", $request_body, true ) ).
The second is a matter of opinion. I might be happy to receive messages from the distant past or far in the future. For the sake of a little clock drift, let's allow 60 seconds either way.
The third gets complicated.

First, I need to get the public key published at keyId="https://your_website.biz/publicKey".

Next, I need to know which algorithm is being used to sign the headers: algorithm="rsa-sha256"

Then, I need to know which headers - and in what order - are being signed: headers="(request-target) host date digest content-type"

So I create a string using the received details which matches those headers in that specific order:

(request-target) POST /dataHost: example.comDate: Sat, 24 Feb 2024 14:43:48 GMTDigest: SHA-256=aaC57TDzM0Wq+50We2TkCsdMDvdqON92edg7KI+Hk8M=Content-Type: application/activity+json

I can verify if the signature - signature="JGQ53kEoIiMWRp9By9jajVGCOCu4n7XBeiA1uY5xLcnAxL2Y1GIgU/...==" matches by:

openssl_verify(    $headersString,     $signature,     $publicKey,     $algorithm);

If that's TRUE then all is well.

But can you spot the implicit problem?

How do I get your server's public key?

I just GET https://your_website.biz/publicKey - but if your server uses something like Authorised Fetch then I have to sign my request to you.

Which means your server will need to validate my signature by obtaining my public key. Which it will get by signing a request and sending it to me. Which, before I return my public key, I will need to validate your signature by obtaining your public key. Which I will get by signing a request... and so on.

This deadlock loop is documented. The usual way around it is either for the sending server to use an instance-specific signature which can be retrieved by an unsigned request, or to allow any unsigned request to access a user's public key.

I get why things happen this way - I just wish it were easier to implement!

https://shkspr.mobi/blog/2024/02/http-signature-infinite-loop/

#ActivityPub #CyberSecurity #encryption #fediverse #http

Authorized Fetch and the Instance Actor

Using an instance actor for mitigating the authorized fetch key retrieval bug seems strange to me so I dug into the historical record to try to understand how this all evolved.

^SocialHub

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

Aktiviert doch das Activity Pub Plugin von Herrn Pfefferle! Das ist kinderleicht und eure Seite ist sofort föderiert! Schickt mir gern den Link, ich abonniere euch.
Activate the Activity Pub plugin from Mr. Pfefferle! It’s child’s play and your site is instantly federated! Send me the link and I’ll subscribe you.
ActivityPub

https://word.undead-network.de/2024/01/10/falls-ihr-einen-wordpress-blog-habt-if-you-have-a-wordpress-blog/

reverend

2024-01-10 12:01:43

Aktiviert doch das Activity Pub Plugin von Herrn Pfefferle! Das ist kinderleicht und eure Seite ist sofort föderiert! Schickt mir gern den Link, ich abonniere euch.
Activate the Activity Pub plugin from Mr. Pfefferle! It’s child’s play and your site is instantly federated! Send me the link and I’ll subscribe you.
ActivityPub

https://word.undead-network.de/2024/01/10/falls-ihr-einen-wordpress-blog-habt-if-you-have-a-wordpress-blog/

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