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

@blort@social.tchncs.de boy, when @johnonolan@mastodon.xyz said "next week" he wasn't kidding.

@miaq@flipboard.social @jerry@infosec.exchange for sure, just look at the number of instances spanning multiple software!

@naturzukunft@mastodon.social signature issues vanished? Does that mean you can send DMs to me now

@silverpill@mitra.social it sounds like @fedify@hollo.social was generating one activity for each recipient, which if combined with relatively heavy database calls, would scale quite poorly, even when processed asynchronously. Batching those db calls is always a low hanging fruit in terms of code optimization.

@johnonolan@mastodon.xyz no worries, and thanks! Will do.

@eeeee it is likely due to audience. So, what happens on your end is you make a topic and mention the Lemmy community. When NodeBB federates that post out, the Lemmy community is included in the mentions, but it also specifies your category 18, World Chat, in audience. If Lemmy sees that, and it doesn't know about that community already, it will drop the activity immediately. If it does, then it will likely slot the post into the "World Chat on isurg.com" community on that Lemmy instance. Lemmy removed audience checking, so this might be a non-issue. Once that Lemmy instance updates to the latest version, it'll hopefully post to the correct community. That's a tricky one, though, because which community should it post to? "Medicine" on mander.xyz, or "World Chat" on isurg.com?

NodeBB is gearing up for a major release this month that brings full two way federation and content discoverability to forums as well! We've been working on it all last year! @activitypub