Interoperability of Events in the Fediverse: status quo and vision
summary
Fediverse event data differs wildly: Gansu treats a single “public” keyword as authoritative while ActivityPub sources use announce/actor/organizer semantics that often conflict, locations land as plain strings or schema.org objects, and start/end times, status (confirmed/cancelled/postponed) and accessibility flags are inconsistently encoded. Masttodon converts events to statuses and only recently accepts updates, so cancellations vanish in many feeds. A proposed FEP on Bberg defines a minimal common event object and ties into Masttodon-led discovery/search work; early implementers include WordPress plugins, Plemor and Mobilizon experiments.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:25Event calendars in Fediverse
- 2:11Visibility and publishing actors
- 3:38Trending and filtering events
- 5:01Physical and virtual locations
- 6:08Start and end time challenges
- 7:11Event status and updates
- 8:14Mastodon’s event handling
- 9:38Diverse event application needs
- 10:01FEP for common event objects
- 11:47Discovery providers for events
- 12:30Q&A
related talks
34mabout:Fediverse - An introduction to the decentralised social network
19mabout: Fediverse
13mDiscover the fediverse in less than 15 minutes
08mHow the Fediverse Could Save Democracy
30mJoin the Fediverse with API Platform!
21mEvents with FHIR: a Simplified Way to Unify Health Data
33mCloudEvents And Beyond!
57mThe bright and exciting future of the decentralized web