@gargron no offense you just have a LOT of followers and also secondarily I'm too lazy to set up caching
@nightpool @Gargron I mean, if we want capabilities for replies, you can't just accept a toot which is supposed to be a reply, you have to check its ancestor. And check that its ancestor is itself allowed to exist, and so on. Since it's unbounded it's an issue.
Also, what if one of the ancestors isn't available to you? (Widening of audience, block, or temporary failure)
I fail to see how it's like ResolveThreadWorker: you have to know every ancestor is valid before validating the toot you intended to process. Otherwise, you might accept a reply without proper capability to a toot you don't know yet if there's a malicious actor.
@nightpool @Gargron I imagine you'd require reply caps to avoid getting your mentions flooded by unwanted replies. With your suggestion, it takes only one instance not implementing ocaps to start a “valid” thread mentioning you (I mean, one user could still mention you in relation to your toot without it being a reply, but still)
Cybrespace is an instance of Mastodon, a social network based on open web protocols and free, open-source software. It is decentralized like e-mail.