Interconnectivity Meeting

Just in case, you missed it.
An extra meeting, was proposed by Steffen in

Please choose your dates …

1 Like

The meeting will be, 2022-04-14T16:00:00Z
and you can join here: Meeting-URL

What do i expect from the interconnectivity meeting?
I’d like it to be an open and open ended meeting. Ideas and questions are welcome, we’ll then can see what kind of cooperations can come out of it. I’d like to share our process and findings so far and would like to show which kind of questions are still open ended. Agenda will be:

  • Interconnectivity - Quick Recap: What, Why and How
  • How to raise support for the topic?
  • Search for Co-Authors to build trust

Looking forward!

1 Like

We had a productive discussion! Thanks for the ones participating. Delivering interconnectivity will continue to be an open community effort, which we are looking forward to.

Here’s a recap:

Interconnectivity Meeting

14th of April 2022, 18:00 Present: Will Murphy (, Yoda (Community Builder), Sebastian Lasse (, Steffen (, Martin (

Question 1: Is the use case interconnectivity needed? i. e. that users of applications which offer different functionality should be enabled to communicate aswell.

  • In the meeting there was quite consensual agreement, that yes, those use cases clearly exist.

Question 2: Is a standardized fallback mechanism required, to ensure communication across ends?

  • This questions remained open.
  • We discussed how e.g. redaktor handles incompatibilities, by showing links if objects are not recognized (see also generator property)
  • A Markup would help to directly embed content
  • Vocabularies allow systems to describe themselves. Systems should be able to querry each other, which vocabularies they have implemented (Interoperability-Check)
  • An open community question about the vision of the Fediverse remains: will (or should) the fediverse at some point reach its full extent with clear boundaries, so that all extension can be fixed and full data portability can be achieved. Or will there always be innovative extensions, that are not implemented by every instance.

Question 3: How can we raise support for the topic?

  • Find out what the community thinks about the topic. We tested a survey, but the feedback was that a poll directly on mastodon will likely leed to more results.
  • Support beyond AP: The world needs more Fediverse and the need of a Fediverse Advertiser came up again.
  • Finances: Open communication is in public interested - common efforts to secure funding.
  • Keep it human: Surveys and polls are cold. Meetings are more engaging and talking brings people closer. A community effort requires active community building.
  • Observation: Support for interconnectivity seems there, while finding people who have time to build and discuss it is another thing. (The invitation to the meeting got shared by more than twice as many people, than actually attended in the end. Several excused themselfes, because they currently do not have the time for extra meetings.)
  • Look for testimonials by people who support interconnectivity targeted, not included in a general survey. Maybe something similar to the web0 manifesto

Question 4: How to proceed:

  • Socialhub will be the central place to discuss interconnectivity for AP.
  • Two topics will be opened:
    A: Is a fallback mechanism needed? This will address the open community question raised above, to discuss on the common vision of the fediverse. How tech-open shall it be?
    B: How will this look in detail? Here the technical discussion will take openly take place. Gathering what’s already there and what needs to be done.
  • The W3C interop-remedies group shall be included in this process. But because their internal communication via email is confusing at times, we hope they’ll join us on socialhub
  • iconet soon posts a draft on how they’d build interconnectivity, which can be a starting point for critical discussion

Interesting for the vision of interconnectivity to understand what needs future applications could bring. = Connected 3D worlds - like a federated metaverse is allowing to login to multiple instances with the same identity, by implementing all three oauth components.

  • real time layer is left to instance itself
  • slow, persistent cross-server communication via AP
  • e.g. follow requests to share locations