We noticed an unfortunately problem today with our work in progress implementation of #ActivityPub
, which is also deployed to this server.
Due to the fact that #Friendica
released their (awesome!) release which switches connections to prefer ActivityPub, if the target server supports it, we seem to have gone into a situation with updated Friendica servers at the moment where they will see the limited AP implementation on #Socialhome
side when a contact request is made from
Friendica, and thus mark the contact as "ActivityPub".
This makes total sense, but unfortunately our AP implementation only covers actors (ie profiles), #webfinger
and some other #ActivityStreams2
serialization. This means remote AP implementations can discover
profiles, but not actually federate with them, leaving a broken connection.
Unfortunately doing an interim fix would require a lot of if/else added to the #federation
library as it is designed to handle as much as possible transparently instead of the application needing to know about the federation code. Thus I made the decision that we wont be implementing a temporary fix for this issue. Instead, efforts to implement the remaining AP parts, starting with "follow" activity, will be prioritized.
Sorry about the inconvenience for those who have had contacts do a follow from Friendica side. We suggest doing a re-follow once AP support is added for at least the follow part.