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 🙂
@pfefferle 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 the acct: protocol.
So yeah, not WP fault at all, just a combination of a bug and missing feature 🙂 Now both should be fixed.
It's been quite a cold and rainy March and April, but with a couple nice days in between and warmer days ahead, I'm looking forward to getting outside more.
In the meantime, there's been quite a bit of compatibility fixing and incremental updates to the ActivityPub branch, so there hasn't been anything major to report, but nevertheless, we're getting closer and closer to an alpha.
@oplik0 has been helping me this month with some of the trickier aspects, so thank you!
Here's a short summary of what's been tackled on our backlog, in no particular order:
Posts from the fediverse can now be linked to, if you wish to share them with others. The "Copy Permalink" button will copy a shareable link to your clipboard, and "View Original Post" will allow you to view the content from its original source instance.
Next up would be bigger items like content pruning and better reply handling.
In coordination with @angusmcleod from Discourse, we are also working on our category-to-category mirroring implementation. This would be used by the SWICG Forum and Link Sharing Task Force, since we're hoping to have asynchronous discussion via the fediverse.
Finding time to test is hard given our respective time zones, but we're getting close!
Oh, one last (huge!) thing to add is that @oplik0 added basic support for the .
Accepting this means that reports from other servers can be appropriately responded to from NodeBB.
While it's not yet on the version running here, upstream the Flag activity now works two-way and even sends/handles Undo for rescinding/deleting a flag (did you know that NodeBB supported rescinding a report? Probably not since it wasn't actually exposed via any UI, just in the API... Well, I'm finally fixing that too 🙂 ). I think we might be the first/only AP service that can undo flags (but maybe someone will correct me, I only checked Mastodon, Mbin and Lemmy).
So very soon you'll be able to report something here and the moderators on the original instance will see it too.
Some small quirks currently:
Mastodon uses the instance agent for reports, I think most other software reports as the user instead and the former messes a bit with NodeBB report deduplication - so sadly for now you can only get one report per Mastodon instance, others will be rejected as duplicate.
The initial reason choice in Mastodon doesn't seem to be federated, just the user-added note...
for NodeBB default reasons are just shortcuts to basic user notes in a report...
For now reports are only forwarded to source instance. Mastodon offers forwarding to all mentioned instances, which makes some sense - since instances that are mentioned inside are very likely to contain that post anyway, so if it's something that should be removed it might be good for them to know too.
As I mentioned I don't think anything else supports rescinding reports yet
