A number of folks are looking at conversation containers, now that this effort has solidified. This solves so many thorny decentralisation issues that at this point if you don't provide containers to do things like groups, circles, comment control, and conversation completion (one of the bullets), you've probably painted yourself into a corner. The only way out of that corner is to track down conversation elements across the fediverse.

Yeah, we did that too - and in case folks haven't noticed, it doesn't scale. So we looked for a solution.

That (scaling) doesn't bother me, because we provide a more intimate and personal social networking experience, but for the projects trying to compete with the corporate  silos;  if it doesn't scale it doesn't actually work. Conversation containers can provide complete, moderated conversations at scale. Moderated by the topic creator, instead of an instance admin that you've never met -- and whose values and anxiety triggers are unknown.

But to do this correctly, we also turned off the public timeline (it's optional) and stopped making everything public by default. These are all personal choices, but in a safer place, the defaults should be for more safety and less harassment potential. And we use OpenWebAuth for one click interactions with remote websites. This allows protected content both over ActivityPub and also to the same audience via the web -- by signing the web requests, just like you would do for requesting ActivityPub objects. OpenWebAuth just does this using webfinger and without requiring your browser to have a copy of your private key (which I probably wouldn't recommend).