@mapache@hachyderm.io no clue, I was just trying it on my phone during my kids' dinnertime so I can't actually debug

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

The ForumWG meeting is coming up in one hour. You can join at the following Jitsi link: https://meet.jit.si/ap-forum-wg

@mario@hub.somaton.com of course I think I will need to register a test account on Hubzilla and debug this.

@lokigwyn@vintagepropagand.art yes, on NodeBB. [image: 1740597791331-1000007503.png]

@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

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

> Doesn't this mean Mastodon users et al will no longer get boost notifications when their posts are reshared into a topic? Correct, only OP will be shared. Unless I am mistaken this is how Lemmy implemented it. Announce-ing activities only, and one single Announce(Note) for compatibility with Mastodon.