How to deal with discrepancies in implementing the ActivityPub protocol?
I've recently installed a Hubzilla instance on my server: classical@ballhaus.community.
The idea is to create a public forum for classical music (and beyond) by letting forum members from other Fediverse instances follow my publications on Hubzilla, while at the same time allowing forum members to contribute from their own platforms: PeerTube, Friendica, Forte, Mastodon, Pixelfed, etc.
As a first step, I'm trying to establish meaningful communication between PeerTube and Hubzilla, and there are already a lot of issues.
Here is an example:
PeerTube and Hubzilla instances are seemingly recognizing each other, but when I post a video on PeerTube, Hubzilla fails to display the content correctly:
https://classical.ballhaus.community/channel/welcome1. The original video link from PeerTube is transformed into a very long link ending in “...-fragmented” in Hubzilla. The original link appears in the source text as:
https://makertube.net/videos/watch/41734e0d-642a-456a-b42c-3d7d3e0edddb2. The PeerTube description field appears as an endless row of text in Hubzilla, without any kind of formatting.
3. The video thumbnail is not visible, although it exists in the source text as:
[video poster="
https://makertube.net/lazy-static/previews/7df1463d-35bf-4cd1-a13b-26eead4780a9.jpg"] ”]
BTW, the PeerTube video is exposed (more or less) correctly in Friendica, Mastodon, and bridged Bluesky accounts (in Mastodon and Bluesky, of course, without the video description).
The big question—and the reason for this post:
How can we get around such discrepancies in implementing the ActivityPub protocol?
If I'm going to use Hubzilla as a content hub integrating other platforms, this has to be dealt with from within Hubzilla. Is that feasible at all?
Have any of you had similar experiences when trying to communicate across different Fediverse instances—beyond simply sharing a line of text?
Thank you
