#122 Listing federation standards to be used on the project description

Ouvert
créé il y a 2 ans par strypey · 2 commentaires
strypey a commenté il y a 2 ans

Are you planning to use the ActivityPub standard for federation between calendar-social instances, and to allow interaction between them and the rest of the fediverse? Any other federation protocols/ standards you plan to implement? It would be good to see these mentioned in the project description.

Are you planning to use the ActivityPub standard for federation between calendar-social instances, and to allow interaction between them and the rest of the fediverse? Any other federation protocols/ standards you plan to implement? It would be good to see these mentioned in the project description.
gergely a ajouté l’étiquette
question
il y a 2 ans
gergely a supprimé l’étiquette
question
il y a 2 ans
gergely a commenté il y a 2 ans
Propriétaire

Calendars don’t really need a federation; iCal/vCal is a pretty good standard in and out of themselves, and email provides a good(ish) way to share events between people.

However, with CalSoc, i do plan to federate between instances using AP, and that’s where my current plans end. If you have any other protocols in mind, i’m all ears, though!

Calendars don’t really need a federation; iCal/vCal is a pretty good standard in and out of themselves, and email provides a good(ish) way to share events between people. However, with CalSoc, i *do* plan to federate between instances using AP, and that’s where my current plans end. If you have any other protocols in mind, i’m all ears, though!
strypey a commenté il y a 1 an
Publier

@gergely

If you have any other protocols in mind, i’m all ears, though!

What about the CalDAV component of WebDAV? This is used by NextCloud for their calendar synchronization, which I assume will be integrated in some way with the AP-compatible social app they have started to develop.

There are at least two other free code projects that set out to offer federated replacements for the event organizing functions of MeetUp and FB. Mobilizon already implements AP. GetTogether have been considering their options for a while.

From a user POV, it would be great if I could announce an event on instances of any one of these 4 platforms, and get RSVPs and comments from users on any other instance. Allowing users to follow each other and get announcements of new events would be pretty important too. If we could create group accounts that multiple users can admin (eg a ‘Python Lunch in Barcelona’ group), and users can follow like any other user, that would be awesome too. I’m no expert, but I suspect that both AP and CalDAV support on all 4 platforms would be necessary to make this all work smoothly.

@gergely > If you have any other protocols in mind, i’m all ears, though! What about the [CalDAV component of WebDAV](https://tools.ietf.org/html/rfc4791)? This is used by NextCloud for their calendar synchronization, which I assume will be integrated in some way with the [AP-compatible social app](https://github.com/nextcloud/social) they have started to develop. There are at least two other free code projects that set out to offer federated replacements for the event organizing functions of MeetUp and FB. [Mobilizon](https://framagit.org/framasoft/mobilizon) already implements AP. [GetTogether](https://github.com/GetTogetherComm/GetTogether/issues/60) have been considering their options for a while. From a user POV, it would be great if I could announce an event on instances of any one of these 4 platforms, and get RSVPs and comments from users on any other instance. Allowing users to follow each other and get announcements of new events would be pretty important too. If we could create group accounts that multiple users can admin (eg a 'Python Lunch in Barcelona' group), and users can follow like any other user, that would be awesome too. I'm no expert, but I suspect that both AP and CalDAV support on all 4 platforms would be necessary to make this all work smoothly.
Connectez-vous pour rejoindre cette conversation.
Aucun jalon
Pas d'assignataires
2 participants
Notifications
Échéance

Aucune échéance n'a été définie.

Dépendances

Ce ticket n'a actuellement pas de dépendance.

Chargement…
Il n'existe pas encore de contenu.