Oh nice! Following a #WordPress blog using #nodebb is working like a charm!Good job @julian #fediverse #activitypub
-
@julian I do that for the blog-wide user. It is from the type group and boosts all posts from every author. But it seems to be not compatible with NodeBB for now?!?
-
@[email protected] what was the issue, are you not able to follow the blog-wide user?
May I have the handle so I can take a look?
-
@julian yes, couldn’t follow! It is @notiz.blog
-
@julian and I have to debug comments... they seem to also be broken
Can you maybe give me a level where I can post more often?
-
Hey @[email protected], I looked into it, and NodeBB can successfully resolve your instance actor via webfinger, but cannot make an S2S GET call to
https://notiz.blog/@notiz.blogI receive the following error:
{ "error":"This method requires an authenticated user" } -
@[email protected] said:
Can you maybe give me a level where I can post more often?
Done! Your local account just needed a couple upvotes I think, so I did that now.
-
@julian ok, comments seem to come through today... maybe a glitch or an issue with missing upvotes?
-
@julian The HTML version (HTTP Request without Accept header) does redirect to the main page, but if you add the Accept header to get the JSON it will work even without signature. (I have not yet enabled AUTHORIZED_FETCH).
I ran some tests and it seems to work up to the Follow `Accept` response where I receive a 500 from the NodeBB inbox.
-
@[email protected] any chance you could let me know the json you're sending during the Accept phase?
-
@julian sure, I will send you a DM!
-
@[email protected] ah sorry, NodeBB cannot accept DMs at this time. Any chance you can message @[email protected] ?
-
-
@[email protected] Should be fixed now in https://github.com/NodeBB/NodeBB/commit/700016649d25ee5bc6c3fa17e03003677d7f5b5d (not yet deployed here).
The issue was that apparently for the blog actor WP sent actor URI and not
username@host- which AFAIK is perfectly valid, NodeBB just assumed the latter was always the case
-
@oplik0 ah, maybe its that we use domain@domain as WebFinger ID?
-
@[email protected] the NodeBB community is updated to include @oplik0's commit, so you can try again
-
@[email protected] it was actually because of
@in actor IDs - the codepath for choosing a webfinger lookup over just accepting the URL as the ID only checked for its presence, and the code for webfinger lookups was only meant to run for theacct:protocol.So yeah, not WP fault at all, just a combination of a bug and missing feature
Now both should be fixed.
