@julian yes we've had this for 6+ months

@beaware@mementomori.social @andypiper@macaw.social as I heard from Peter directly, the legal issues also come from internal pressure. Fediverse integration implies giving up control over content, and that's a huge pill to swallow for a company that is literally described as a data silo.

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

@reiver@mastodon.social no, I am not, I have just been following the fediversehouse hashtag

@julian@fietkau.social sunk cost fallacy is a very real thing. In my case I like having more fine-grained control over my own ActivityPub implementation, but that's just an excuse. Truth be told, if Fedify were around when I looked into starting AP integration in NodeBB, I might've gone that direction.

@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?