I see where you come from, but it’s still a platform, a network.
But that network is not Lemmy or kbin or mbin or piefed. That network is activitypub, the platform is activitypub. Those backends are just what you use to connect to the network, but you could use any other implementation (just that there aren’t that many right now).
Just because an application supports ActivityPub doesn’t mean it will be compatible.
Well of course, but it could be made to be compatible!I feel like we’re kind of missing out here on the threadiverse cause we can’t see all those other things happening elsewhere.
Relevant: the Tesseract front-end for Lemmy provides an automatic embedded player for Loops videos: see e.g. https://tesseract.dubvee.org/c/loops@midwest.social. So those kinds of cross-integrations definitely are happening, but they take time and effort to implement and refine.
But that network is not Lemmy or kbin or mbin or piefed. That network is activitypub, the platform is activitypub. Those backends are just what you use to connect to the network, but you could use any other implementation (just that there aren’t that many right now).
Just because an application supports ActivityPub doesn’t mean it will be compatible.
Lemmy and Peertube are barely compatible. Interoperability between fundamentally different software could be achieved, but is not a priority
Well of course, but it could be made to be compatible!I feel like we’re kind of missing out here on the threadiverse cause we can’t see all those other things happening elsewhere.
Relevant: the Tesseract front-end for Lemmy provides an automatic embedded player for Loops videos: see e.g. https://tesseract.dubvee.org/c/loops@midwest.social. So those kinds of cross-integrations definitely are happening, but they take time and effort to implement and refine.