trwnh@mastodon.social Yes, you're right. There are nuances and situations where you would explicitly not want to inherit the root object's context.
I am dealing with the typical day-to-day use case of replying to an object with the expectation that is be part of the same existing context.
However I am more than happy to make this clear in the FEP and spell out alternative situations where context inheritance would not apply.
The situation I found myself in was one where anybody can (and does) include whatever context they want. In that case, it's difficult to determine whether disparate contexts are actually referring to a common set of the same objects, or whether they were disparate on purpose (i.e. a fork.)
To that end, it meant that as a receiver there was no guarantee that any contexts I'd be sent would map to any contexts I know.
Strict root-level inheritance for the common use-case would at least disambiguate a lot of this.