Connectivity between Friendica and Hubzilla does not work always

[rocky-III]

Connectivity between Friendica and Hubzilla does not work always and i asked the main DEV of HZ for reason. That is what he wrote to me:

Hab da mal jetzt nachgesehn. Sind wohl drei Sachen die schief laufen:

    Unter bestimmten Umständen fehlte beim Hubzilla Profil hcard Info die vom Diaspora Protokoll benötigt wird (is gefixt)
    
friendica ruft beim verbinden eine hardcoded URL auf die es bei Hubzilla schon lange nicht mehr gibt "https://github.com/friendica/friendica/blob/765af10f00728b1421a9eb633e0afc1948168eee/src/Network/Probe.php#L845
    

Bei Friendica sollte man beim verbinden sichercheitshalber immer das gewünschte Protokoll für die Verbindung angeben. Das geht in der Form [activitypub]nick@server.tld oder eben [friendica-over-diaspora]nick@server.tld

thanks for having a look into it

[annando]

That probe line doesn't matter, since this is only for informational purposes, since we don't support Zot. But is good to know, that one has to provide some workaround in Hubzilla to provide the protocol. In Friendica we simply collect a list of supported protocols on the other side and then chose the best one. We prioritize ActivityPub here.

[rocky-III]

thanks... so what does prevent connectivity between Friendica and Hubzilla from you perspective? It is a pity that this two project do not connect without total fail outs . What could be done to make things better here?
thanks for looking in to it.

[annando]

Well, I could imagine that Hubzilla has got problems, when we reply via ActivityPub although the connection had been established via Diaspora, but this is a very wild guess. I also don't know, if Hubzilla supports the field we added in our ActivityPub posts, so that replies via ActivityPub from Friendica systems can be relayed to Diaspora systems.

[git-marijus]

@annando the supported protocols in Hubzilla can vary by channel. I have tested with a channel where AP was disabled. The connection request via diaspora protocol returned 202 from Friendica but the request itself never appeared in the UI at my testaccount on libranet.de

[rocky-III]

Ok here what i found out with some help:

The problem is that in the past things between HZ and Friendica have worked with the Diaspora Protocol - but Friendica has increasingly switched to ActivityPub, which also affects communication with HZ.

Unfortunately, HZ does not currently automatically switch to ActivityPub when a contact request is sent to Friendica. But you can force this by putting an [activitypub] in front of the address to be contacted.e.g. if you want to contact to channel @name@server.tld

you enter [activitypub]name@server.tld

in the contact request under

/connections

Unfortunately, things seem to get tangled up due to previous failed attempts via the Diaspora protocol... So please do the test with a very fresh HZ channel... i.e. one that has not yet tried to contact name@server.tld via the diaspora protocol.

created an fresh channel under:

/manage

and see if things work better