@fauxpseudo@lemmy.world as I learned, the latter—kai oats—is Canadian.

@malikmuaddibsoong@startrek.website it’s been a long road, gettin’ from there to here

@AltCode all three flipboard remote categories seem to be working now :joy:

The remaining questions here are:

• whether preferredUsername is meant to be unique to the instance (in which case having multiple ids point to an identical preferredUsername would be a violation), and
• what exactly AP software should do when it encounters this situation… store a list of “known alias” IDs? There are potential security issues to doing so.

@AltCode I forked this out to a new topic. I think it’s time to loop @pfefferle@mastodon.social into the conversation (at the very least so this could be potentially escalated).

Mattias, it seems that when the WPML and ActivityPub plugins are enabled together, notes federated out by the blog user in another language have different ids but the same preferredUsername.

e.g. ruari@vivaldi.com: https://vivaldi.com/?author=46 and https://vivaldi.com/ja/?author=46

NodeBB interprets this as two different users. Curiously, Mastodon does not, the second ID explicitly does not resolve.

So there can be two solutions here:

1. The underlying issue can be fixed by WordPress, the solution of which is out of scope (for me at least)
2. NodeBB can adopt whatever mechanism Mastodon is using… which is most likely that Mastodon does a two-way when asserting an ID, and ensures that the webfinger resource points to the ID.

@AltCode okay! Thanks for reporting, it sounds like there are two issues going on:

1. Categories losing their handle-to-id association
   • Frustratingly, this read very similarly to #13283, and both remote users and categories share similar logic. I have so far not been able to reproduce it at all on local development.
2. Separate users (different IDs) sharing the same preferredUsername.
   • This is an interesting one, and I am not entirely sure where the fault lies. I wonder how other software handles it?

@fordbeeblebrox@lemmy.world that’s because Discovery is just bad fan fiction.

It makes Enterprise worth watching.

@mario@hub.somaton.com that’s wonderful to hear! Thank you so much.

@scott@loves.tech how does Hubzilla communicate this to other 'za instances?

Something like a boolean for whether the public can post would take you part of the way there.

Hmm… considering that Piefed cross-posts are entirely separate posts, then if the original is edited, then the modification is not carried over to the cross-posted post, correct?

I’m thinking that for NodeBB we could continue to have cross-posts reference the canonical topic. They’d simply be part of a separate audience as well.

Whether this is local-only or not, I am not sure yet. Perhaps for federation purposes we’d still report the original category (if there is one) under audience

@rimu@piefed.social excellent… yes this is the kind of difference I’d love to explore and potentially put together an FEP for…

@mario@hub.somaton.com since Hubzilla posts (incl. yours) are making it in fine I’m assuming this is only for the “forum” feature?

Forgot to cc @mario@hub.somaton.com re: the above.

@scott@loves.tech Hubzilla is formatting its Notes in a manner I wasn’t expecting.

• The group actor is the attributedTo, which is not possible in NodeBB
• The note itself is not addressed to the group actor, only its followers collection
• There is no way to discern without parsing the note content itself who authored the original note.

So at present while I would be able to retrieve the note, without a proper backreference to the group actor, I don’t think I can slot it correctly.

Not sure why the received activity is returning a 403, as well.

@scott@loves.tech can you share an example of a group actor from Hubzilla? Would be interesting to see how that’s handled. Likely it wouldn’t work properly because categories in NodeBB don’t author posts.

Do your group actors send creates on behalf of regular users? That might work ok.

Lastly, there’s no requirement that a NodeBB category be mentioned. It only needs to be addressed. A mention is the easiest way to do that because addressing is abstracted out of the Mastodon UI.

But for things like PieFed, Lemmy, Mbin, and likely Hubzilla, you’re able to change addressing based on where you create the post.

@CWSmith hashtags in NodeBB are only relevant at the topic level — that’s just how it was designed years ago.

You’ll note that on microblogs, tags can be added on any post. While we show them, we don’t consume or index them unless they are the original post.

When you use tags in NodeBB, they are federated outward with the original post.

Hope that helps!

Thanks for the confirmation @jsonculverhouse@flipboard.social, any chance we could have the post list the magazine as a recipient, so that a backreference is established?

See: https://community.nodebb.org/post/104013

@mike@flipboard.social mentioned you, but a typo got in the way :smile:

@AltCode aww, heck yeah!

@AltCode said in Forum specific UX for remote categories: > My thinking was that all the remote categories you follow are listed in your /world page

That might get a little hairy if you follow a lot of categories.

Right now posts from any categories you follow would still show up in your world feed. If you follow a remote category, you would essentially be “tracking” the category, in NodeBB parlance. New topics and posts would show up in your /unread and /recent. If you “watch” the category, then you’ll be notified of every new topic.

@Kichae my fear is that adding in the ability for users to customize the forum index would dilute the importance of local categories.

I’m always a big supporter of community building, and while I am very appreciative of the network effects of activitypub, there is the other local community building side that I would want to keep top of mind as well.