Yes. At least if we are talking about backward-incompatible changes listed in the summary thread: Summary: Desired changes for a future revision of ActivityPub and ActivityStreams - #2 by SorteKanin
I don’t see anything there that requires major backward incompatible changes. For example:
- JSON-LD is already not required (according to the ActivityPub spec). This only needs to be articulated more clearly.
- Issues with software switching are solved by data portability.
- HTTP signatures are not part of AP spec, embedded signatures are specified in FEP-8b32
- A separate inbox can be used for receiving batched activities
- The work on developing a better standard for federated groups is ongoing
- …
The real challenge is implementing these things in a coordinated way. This is what we’re trying to do here on SocialHub and with FEPs.