Federation / ActivityPub

Gancio largely follows ActivityPub’s server-to-server specification.

Supported federation protocols and standards

Supported FEPs

ActivityPub

Each instance has only one AP Actor of type Application named events@instance.tld by default (was relay before 1.24), which publishes each event as Event type.
Each AP enabled software could decide how to interact with coming events, e.g. on Mastodon and forks you can see it with minimal information, with Friendica events are added into your own calendar, GoToSocial does not support Event type.

We are considering the introduction of other Actor but they will not be linked to users, rather to places, tags or collections. There are no personal timeline of people you follow, everyone has a sort of local timeline of the instance, it’s an anti filter-bubble feature.

Since v1.10.0 each instance could follow other instances or actors (Admin > Federation > Add trusted node) and use the events incoming from the federation to fill choosen collections (Admin > Collections).

Note that events coming from the federation will be removed after the end.

All federation’s related operations uses /federation as endpoint. You can disable it via a specific setting (Admin > Federation > Disable federation).

Supported operations

Operation Since Note
Follow Gancio from Fediverse 0.15.0  
Send an Event 0.15.0 Sent as Event type.
Receive a Note 0.21.0 Adds images, audio and notes to an event with a simple reply
Delete a Note 0.21.0  
Update a Note 0.21.0  
Follow an Actor 1.10.0  
Receive an Event 1.10.0  
Update an Event 1.10.0  
Delete an Event 1.10.0  

Moderation

  • Hide or remove a remote event
  • Block a remote user
  • Block a remote instance