bridgy-fed icon indicating copy to clipboard operation
bridgy-fed copied to clipboard

support Friendica

Open snarfed opened this issue 8 years ago • 3 comments

their current released ostatus support is incomplete. @annando is rewriting it in the new-ostatus branch in his fork: https://github.com/annando/friendica/tree/new-ostatus

more discussion in friendica/friendica#3696.

snarfed avatar Oct 16 '17 21:10 snarfed

The changes are already in the current master of Friendica.

annando avatar Oct 17 '17 08:10 annando

There are currently no known OStatus issues. It is working fine with GNU Social, Pleroma and Mastodon.

annando avatar Mar 27 '18 05:03 annando

thanks for the update!

snarfed avatar Mar 27 '18 05:03 snarfed

Looks like Friendica now supports ActivityPub. I tried liking this post on https://friendica.hubup.pro/ (running Friendica 2022.12) via BF, and when BF tried to fetch https://friendica.hubup.pro/display/174591b4-1563-a455-e2af-046050971897 (the post URL) with AS2 conneg headers, it returned HTTP 503 Temporarily Unavailable. Looks like that was from Cloudflare, checking that my request wasn't a bot.

Not a good sign for at least that instance's federation support. I'll try again on another instance that's not on Cloudflare.

snarfed avatar Jan 17 '23 14:01 snarfed

Success! I successfully liked this post on libranet.de, running Friendica 2023.01. Bridgy Fed log. I'm going to tentatively declare success here.

snarfed avatar Jan 17 '23 18:01 snarfed

Reopening, following Friendica accounts doesn't seem to be working: https://github.com/friendica/friendica/issues/12965

snarfed avatar Mar 31 '23 23:03 snarfed

Maybe not related to your present issue, but HTTP 503 may be related to this, that should be solved by implementing retries with exponential backoff in your backend:

  • https://github.com/friendica/friendica/issues/10131
  • https://github.com/friendica/friendica/blob/develop/doc/Install.md#user-content-your-worker-never-or-rarely-runs

bkil avatar Apr 29 '23 22:04 bkil

Thanks! But the current failure is no longer an HTTP 503. It's accepting async with 202, and then failing during later background processing. Details in https://github.com/friendica/friendica/issues/12965

snarfed avatar Apr 29 '23 23:04 snarfed

Tried again after #442, looks like it's working now!

snarfed avatar Oct 12 '23 04:10 snarfed