Darkscribes Community

bh4-tech that's good to know, thank you!

> One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.

Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.

phoenix you can always test with ActivityPub.academy, live Mastodon servers can sometimes be delayed.

Thanks! It's something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn't support natively yet — mention spamming doesn't count.)

The use case seems clear: actual DMs on the fediverse. How does this interop with existing implementations that utilise direct addressing (and intentional omission of as:Public) as a form of direct messaging? As usual I am assuming we will have to support both.

chartung ah... Yes usually they're in there for a reason hehe Glad you figured it out!

[email protected] let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!

eugene_thedev are you referring to specifically the oauth2-multiple plugin? I'm not exactly sure whether that is supported in the current iteration of the plugin.

AMAARETS I think all you really need to do is have your plugin change req.session.uid and req.uid to the target uid. Although in practice there might be some cases I did not consider.

Hey [email protected] have you tried updating to the latest NodeBB? You can post to Lemmy communities from there too!