Application interoperability


Convener: Session Convener:

Participants who chose to record their names here:

  • Adam Nelson
  • Tom Brown
  • Manton Reece (micro.blog)
  • Romain Mekarni
  • Tom Benham
  • Christopher Su
  • Ryan Barrett
  • Ben Pate (@benpate@mastodon.social)
  • Aaron Gray

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

  • Feedback on FEP from multiple attendees: Could this use ActivityPub “native” types (e.g., look at ActivityStreams) for operation identifiers? AI(nikclayton): Go and investigate, update proposal with findings.
  • Ben Pate discussed the difficulty of knowing how a server will treat specific objects. Some examples from others included e.g., Pixelfed restricting itself to Notes that contain images, or Mastodon’s treatment of richer content, which might be accepted by the server but not displayed to the user.
  • Some servers define subtypes that only they understand (e.g,. Bookwyrm) or don’t expose some features as types (e.g., emoji reactions), hindering interoperability.
  • Aaron highlighted the need for well-written standards in this space and implementations that adhere to those standards. The work that Helge’s doing at https://funfedi.dev/support_tables/ is relevant here. As is Johannes’ work at https://feditest.org/ to test the interoperability of different implementations.