No problem.Thank you for that clear explanation.
Jibe is a google owned (bought) cloud service that hosts RCS infrastructure as well as serves as an interconnect to other global RCS Hubs. So not unless you are a Mobile network operator or own a MVNO, I'm not sure what your interest are in Jibe. You don't need to use Jibe to connect to the RCS Hub, you can create your own.You say that Google's implementation is not proprietary. Is Jibe open source? Where may I download it? I can't find it. All I can find is information about carriers using Google's software/service. There's no mention of it being open or modifiable. Of course, I could have missed that since the Google websites about Jibe that I found are clearly made by marketing people, not engineers.
Go see the GSMA guidelines on how to do so.

RCC.07 RCS Advanced Communications Services and Client Specification Version 14.0
This specification defines the interactions between a client and the network to configure operator services on the device. It is used among others for the configuration of RCS services.

The standard is being contributed to by mobile operators and platform holders which Apple and Google are. Apple had every access to the standard and specification as it is being drafted. They didn't have to wait for the specification to be finalized to adopt features. Google adopted 2.7 before it was even published, they were beta testing features. Apple has no incentive to; you are forgetting they had to be forced to adopt RCS in the first place.Google has implemented RCS UP 2.7, and you say Apple’s implementation of UP 2.4 lacks features. However, 2.7 was issued as a standard in June, suggesting Apple’s implementation began before the release. It’s misleading to say there are many missing features since implementations aren’t released on spec approval. In my experience, supporting later revisions is a marketing decision and subject to product-cycle timelines, unless a company is politically driving the standard (as Google is).
It's been a long struggle to get to this point.It sounds like what you are saying is that the implementation of RCS across different carriers has been borked until quite recently. I agree. We can appreciate the trouble Google has gone through to try to force a clean up of the mess. (Indeed, reading through the history, RCS has been as bad a political nightmare as it gets in industry standards bodies.)
We should definitely criticize Apple for actively refusing to adopt RCS and waiting to be forced to adopt it because they wanted to lock people into Apple ecosystem. Same thing they did with USB C on iPhones even though they helped create and contributed to the standard. Tim cook said "buy an iPhone" to someone who asked when they would make messaging with Android as good as iMessage. Their view is making the experience worse, so you are forced to stay in their ecosystem. I'm not making it up, there have been published emails of Apple executives saying it.We shouldn't criticize Apple for having different priorities from Google. The two companies have always had radically different business models and product development processes and views of the computer industry.
It's not part of the standard but Signal is an open protocol that anyone can adopt. Google published the white paper on how they integrated signal extension on top of RCS. Apple is no stranger in working with Google when it suits them financially to do so.On End-to-end encryption (E2EE)... It isn’t part of the standard. The implementation on Android is a non-standard Google extension using the signal protocol. This extension is unique to Android and isn’t guaranteed to be used by anyone other than Google. So complaints that Apple’s RCS implementation lacks support for Google’s E2EE reflect a misunderstanding of RCS’s scope.
GSMA has announced their plans to add MLS protocol to the Universal Profile spec. MLS specifications were fully published last year. Google has already started implementing it in their messaging app. I can criticize Apple a multitrillion dollar corporation for not adopting features that protect their customers messages when they talk all the time about privacy and security. I don't understand your insistence on shielding a multitrillion dollar corporation from being criticized.Future E2EE support on Android will depend on the proposed MLS standard extension. Until GSMA includes it, Google will be the only one implementing it. Given the likelihood of standard inclusion, Apple may support it in future Messages releases. Criticizing Apple for not implementing it now is misplaced.