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

@hongminhee@hollo.social username-based IDs was incredibly short-sighted of Mastodon (and others) to adopt. Using an incrementing id or uuid is not novel, merely baseline expectation for something expected to be mutable like a username.

@osma@mas.to the default assumption is that announces are delivered back to the origin server in order to close the loop. However it is not a requirement. For example I am considering not doing so for group announces.

https://community.nodebb.org/topic/18647/the-state-of-conversational-contexts-february-2025

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

@openrisk@mastodon.social not a bad idea. NodeBB actually already does this. We have a configurable max on hashtag usage, and so if a post comes in with > 5 (the default) we just remove everything after the fifth hashtag. They're still in the post content, but only the first five count in indexing, etc.

@wjmaggos@liberal.city that's true for Mastodon, but not for other servers with more of a community focused aspect, like NodeBB.