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

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

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

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

@shoppingtonz@mastodon.social if edits from PieFed aren't reflected here that may be a bug.

@trwnh@mastodon.social given that one way a context collection is discovered is via reference via a collection member itself, that's one way to define it. Admittedly, direct access to a context collection is also a legitimate use case (e.g. a NodeBB topic URL itself is the context collection), so something more explicit might be required.

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