Place to discuss general issues of interop between implementations?

Hi all, is there a place to discuss general Fediverse interoperability on the application layer? Not on a spec level but for topics like “let’s brainstorm how various AP-compatible servers could interpret an Article object type and render it for their users” or discussing general principles of interoperability.

I could imagine a sub-category for interoperability under Software, but maybe somewhere else would make sense?

1 Like

hi darius! A similar topic is Content, text/plain, and fallback behaviors for limited clients, which is focused on rich text support specifically.

In general, I think concerns of interoperability are always a concern for the community group. Even if it’s not a discussion about hard requirements, things like codifying best practices, hashing out general principles, and coming to consensus on guides to implementation are definitely things the process can help with. Overall, I’d recommend using the #activitypub topic—#software is designed to be focused on specific implementations.

1 Like

Another topic you might be interested in is Resolving the Note vs. Article distinction, which dives into a lot of thoughts about what people are intending when they use Article

Thanks, I’ll post this kind of stuff in #activitypub.

Maybe we could use an #interop tag or similar to keep things easy to follow.

1 Like