Conversation

Notices

1. Embed this notice
   Troed Sångberg (troed@masto.sangberg.se)'s status on Thursday, 12-Oct-2023 17:53:04 JST Troed Sångberg

   • Matthias Pfefferle

   Something seems off with the wordpress.com ActivityPub integration. When I (and others) check my blog profile (@blog.troed.se) on Mastodon, while it displays, there's also a brief error 500 popping up. That seems to then mean that it's not possible to read/comment on the blog.

   The FediFetcher script also reports errors when trying to fetch posts from the wordpress.com profiles:

   2023-10-12 10:41:04.089201 CEST: Error getting host node info for public-api.wordpress.com. Status Code: 404
   2023-10-12 10:41:04.089245 CEST: server blog.troed.se not found for post

   2023-10-12 10:41:02.320425 CEST: Error getting host node info for public-api.wordpress.com. Status Code: 404
   2023-10-12 10:41:02.320470 CEST: server pfefferle.wordpress.com not found for post

   ping @pfefferle

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 17:53:02 JST Matthias Pfefferle

     in reply to

     @troed @blog.troed.se I also realized the 500 error, but this is because Mastodon seem to search for an endpoint that seems not available. Will dig into that, but everything (commenting, ...) works as expected. Seems to be an UI only issue.

     Can you send me a link to the FediFetcher script you use? There seem to be more than one :)

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:12:13 JST Matthias Pfefferle

     in reply to

     @troed I see!

     I had a quick look at the code and I assume that FediFetcher has issues with the API (inbox, outbox, followers, ...) beeing on a different domain then the blog (public-api.wordpress.com and blog.troed.se). The NodeInfo and WebFinger endpoint are (and has to be) on blog.troed.se (https://blog.troed.se/.well-known/nodeinfo) but all other endpoints are on public-api.wordpress.com.

   • Embed this notice
     Troed Sångberg (troed@masto.sangberg.se)'s status on Thursday, 12-Oct-2023 18:12:15 JST Troed Sångberg

     in reply to

     • Matthias Pfefferle

     @pfefferle Of course! This is the one I use: https://github.com/nanos/FediFetcher

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:12:21 JST Matthias Pfefferle

     in reply to

     @troed FediFetcher seems to not make a difference here and seems to search every endpoint (including nodeinfo) on public-api.wordpress.com.

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:26:31 JST Matthias Pfefferle

     in reply to

     • Michael

     @troed @michael perfect!

   • Embed this notice
     Troed Sångberg (troed@masto.sangberg.se)'s status on Thursday, 12-Oct-2023 18:26:33 JST Troed Sångberg

     in reply to

     • Michael

     Alright - let's ping @michael into the discussion. If it's easy to figure out what call should go where then it sounds like something that's hopefully quick to fix :)

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:45:05 JST Matthias Pfefferle

     in reply to

     • Michael

     @michael @troed shame on me! good catch!

     will check why this is broken

   • Embed this notice
     Michael (michael@mstdn.thms.uk)'s status on Thursday, 12-Oct-2023 18:45:11 JST Michael

     in reply to

     • Matthias Pfefferle

     @pfefferle @troed

     LOL. I think that the WordPress AP integration is broken:

     https[://]blog.troed[.]se/.well-known/nodeinfo

     returns a properly formatted nodeinfo response pointing to

     https[://]public-api.wordpress[.]com/wpcom/activitypub-1.0/sites/861438/nodeinfo

     But that URL returns a 404, so until that's fixed there is nothing that FediFetcher can do.

   • Embed this notice
     Michael (michael@mstdn.thms.uk)'s status on Thursday, 12-Oct-2023 18:45:20 JST Michael

     in reply to

     • Matthias Pfefferle

     @pfefferle @troed

     Hm. I haven't looked into WordPress’ AP implementation yet, so I don't know if FediFetcher can support it. But generically what I would say is that FediFetcher does the following:

     1. Using a combination of the .well-known/nodeinfo and .well-known/host-meta endpoints it determines the host software (https://github.com/nanos/FediFetcher/blob/95b644d4319a8755684f5347ef47ce6b2a38cae1/find_posts.py#L1101)

     2. It then uses that info to determine if the host supports the mastodon, misskey, or lemmy API (https://github.com/nanos/FediFetcher/blob/95b644d4319a8755684f5347ef47ce6b2a38cae1/find_posts.py#L1205)

     If the server identifies as supporting any of these APIs, FediFetcher fetches comments using the detected API. Otherwise it will not try to fetch comments, because it only supports these three APIs.

     So, from my POV the questions are:

     1) Does the WordPress AP integration support any of these 3 APIs?

     2) Does the WordPress AP integration use either the nodeinfo or host-meta endpoint to identify itself?

     If the answer to both of these is ‘yes’, FediFetcher can easily support the WordPress AP integration. Otherwise it gets more complicated.

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:45:29 JST Matthias Pfefferle

     in reply to

     • Michael

     @michael @troed and sorry for the "blaming" :(

   • Embed this notice
     Michael (michael@mstdn.thms.uk)'s status on Thursday, 12-Oct-2023 18:49:14 JST Michael

     in reply to

     • Matthias Pfefferle

     @pfefferle no worries at all!

     Does the WordPress integration support the mastodon, pixelfed, or misskey API?

     @troed

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 18:49:14 JST Matthias Pfefferle

     in reply to

     • Michael

     @michael @troed there is a difference between the WordPress plugin and how we integrated it in WordPress.com. For WordPress self hosted, there is a plugin that supports the Mastodon API and we are evaluating if we can bundle that into WordPress.com too. Long story short: not yet. We focused on the "standards" so far.

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 19:15:11 JST Matthias Pfefferle

     in reply to

     • Michael

     @michael try https://alex.kirk.at/

   • Embed this notice
     Michael (michael@mstdn.thms.uk)'s status on Thursday, 12-Oct-2023 19:15:12 JST Michael

     in reply to

     • Matthias Pfefferle

     @pfefferle really good to know, thanks! Can you tell me the URL of a Wordpress blog that has the mastodon compatible plugin installed? I’d love to pull the node info from there, so that fedifetcher can support it.

     Hoping the hosted version will support it too, soon 🙏😉

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 19:16:43 JST Matthias Pfefferle

     in reply to

     • Michael
     • Alex Kirk

     @michael /cc @alex

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 12-Oct-2023 23:51:43 JST Matthias Pfefferle

     in reply to

     • Michael

     @michael @troed fixed!