I have gotten my friend group to switch to using Signal for our group chat. It was pretty hard because I’m the only Android user but I ended up convincing them
having layering(hope that the right word for a group of text, icons and symbols) issue where icons and symbols go missing or get replaced by square boxes
I used Inkscape a lot on PDFs with forms and broken layout. The beauty of it, you can fix other problems, too, use your own font or change the font of existing text. (:
There’s not really much of a point using the RCS Test app, as it’s only a demo of very basic RCS features.
The thing with RCS is that whilst the “official” spec (ie the Universal Profile), as defined by the GSM Alliance, is open, it doesn’t implement or define many modern of the chat features found in modern apps, such as reactions, replies, end-to-end encryption etc. These features however, have been implemented by Google in their Messages app and their Jibe backed service. The problem is that these additions by Google are proprietary and only works via Google’s Messages app, so third-party messaging apps can’t get in on the fun.
I believe Samsung’s Messages app may also have access to some(?) of these features if the cellular carrier also uses Google’s Jibe servers for RCS routing, but don’t quote me on that.
As for Apple, I’m pretty sure that if they implement RCS (supposedly this year), it’ll either be the Universal Profile, or most likely the Universal Profile + some proprietary Apple magic sauce for added features. Not sure about E2E encryption though - they would have to work with Google for that to work (for interoperability with Messages), so we’ll have to see how that goes. If I were to guess, I’d say E2E on Apple would most likely be limited to Apple devices. But at least we can expect basic rich messaging features to work cross-platform, so that’s something I guess.
In any case, the main issue remains that Google hasn’t opened up the API/spec for their version of RCS - and the GSMA is seemingly doing nothing about it either, the Universal Profile hasn’t had any updates in the last four years. You can read about the spec in detail here, and if you do, you’ll see that there’s no mention of modern chat features such as end-to-end encryption…
So on one hand, it’s a good thing that Apple is getting RCS this year, but it’ll likely remain either the at the basic Universal Profile level, or some proprietary Apple stuff thrown in, both of which aren’t really ideal.
For the rest of us, none of this really matters unless Google opens up the spec, because why the heck would you settle for a somewhat insecure and limited protocol, when there are far better messaging apps out there, with a greater userbase and cross-platform interoperability?
So on one hand, it’s a good thing that Apple is getting RCS this year, but it’ll likely remain either the at the basic Universal Profile level, or some proprietary Apple stuff thrown in, both of which aren’t really ideal.
No, I would say the first is the best option. It would create incentive for actually improving the Universal Profile. The “bad ending” would be Apple adopting Google’s proprietary extensions.
Like my USB mouse working with any computer, I used to be able to pick up a phone and text anyone on the planet without having to check which app they’re on. Sure there are the ‘de facto’ apps, but these vary by country and social group. The reason for the proliferation of the third party apps lies squarely on the proprietary, ckosed protocols by each of them and viral growth during the early days when the telcos were still figuring out data-based text and voice - players were playing up their features like ‘security’ and ‘privacy’ and creating the walled gardens as you mentioned. The current leaders grew due to rapid adoption and a person’s social clout. Just try dating nowadays in Asia, where multiple texting apps reside on a typical phone. Don’t kid yourself - the messages mentioned earlier serve only the marketing goals of each app and just lock you in with FOMO or the hassle of switching. The companies don’t give a shit about your privacy, as long as they can monetize your data, feed and activity.
RCS, to me, wants to take us back to industry standardization, so any provider can follow the standard and immediately be connected to everyone, instead of having to deal with different platforms, protocols. An iphone should be able to communicate with an Android and all the flavours without degradation or the color of the bubbles. Sure, the current implementation of RCS is google’s, but the standard is not. Hopefully, managed by a (neutral) standards body, the shortcomings people point out will be patched and adopted by the app developers. Desired featured will be folded into the standards and make their way into then apps. This, again to me, while slower, is preferable than being tied to the whims of a provider, e.g. Whatsapp, iMessage and telegram, does away with the market fragmentation (not competition) and gets rid off all the artificial bullshit like blue/ green bubbles, security lapses and image degredation between apps.
opensource
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.