@bentigorlich@gehirneimer.de okay Apologies for not mentioning you up top. I did not know you were the maintainer for mbin, but now I do!

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

@jsit@social.coop that's fair, it's late! As an advocate of long form content on the open social web I'd love to chat about it. There might be some things we can learn!

@reiver@mastodon.social tentatively doable, will have to plan a climbing trip out to Squamish if I'm already out west!

@jwildeboer@social.wildeboer.net Right, there's a possible social engineering vector at play here, which I think makes this a little concerning. I certainly don't like my time wasted either cc @thisismissem@hachyderm.io @mariusor@metalhead.club

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

@deadsuperhero@social.wedistribute.org glad to hear it! I'm planning to continue working on improving our ActivityPub integration in 2025, hopefully with NLNet funding again

Uups, next try https://nrw.social/deck/@FrankM/113606591981853331