Author: mangakiko

Google has been unable to field a stable, competitive messaging platform for years and has thoroughly lost the messaging war to products with a long-term strategy. At least some divisions inside the company are waking up to how damaging this is to Google as a company, and now Google’s latest strategy is to… beg its competition for mercy? Google—which has launched 13 different messaging apps since iMessage launched in 2011—now says, “It’s time for Apple to fix texting.”

Google launched a new website called “Get the Message”—a public pressure campaign with a call to “tweet at @Apple to #GetTheMessage and fix texting.” Google hopes public pressure will get Apple to adopt RCS, a minor upgrade to the SMS standard that Apple uses for non-iMessage users. Google has been pushing this strategy since the beginning of the year, but coming from the company with the world’s most dysfunctional messaging strategy, it just comes across as a company tired of reaping what it has been sowing.

Worldwide, iMessage isn’t that popular (people tend to like Whatsapp), but in the US, iMessage is enough of a cultural phenomenon to have Billboard Top 100 songs written about how much it sucks to have a green (SMS) iMessage bubble. One of Apple’s biggest competitors—especially for online services—is Google, and Google’s inability to compete with iMessage has contributed a great deal to the current situation. Google apparently feels iMessage’s dominance is damaging to its brand, so now it’s asking Apple, nicely, to please stop beating it so badly.

Google’s site says, “It’s not about the color of the bubbles. It’s the blurry videos, broken group chats, missing read receipts and typing indicators, no texting over Wi-Fi, and more. These problems exist because Apple refuses to adopt modern texting standards when people with iPhones and Android phones text each other.”

A 14-year-old standard is “modern,” right?

Some of Google’s claims on this website don’t make much sense. Google says, “Apple turns texts between iPhones and Android phones into SMS and MMS, out-of-date technologies from the 90s and 00s. But Apple can adopt RCS—the modern industry standard—for these threads instead.” RCS isn’t a modern standard either—it’s since 2008—and, despite a few middling updates since then, hasn’t kept up with the times.

RCS has hung around so long and is still so poorly implemented because it was created by the carriers (through the GSMA) as a carrier-centric messaging standard. Carriers did this in the heyday of pay-per-message SMS, when carrier messaging was a real revenue stream. Now that carrier messaging is commoditized though, the carriers in control of RCS don’t have an incentive to care about RCS. RCS is a zombie spec.

In Google’s defense, SMS is from 1986, so RCS is more modern than that. This is probably more of a sign that you should never work with the GSMA if you don’t have to, though. If Google and Apple ever teamed up to make a duopoly messaging, they would not need the carriers or their ancient messaging standard.

Google’s proprietary fork of RCS

Being from 2008 means RCS lacks much of what you would want from a modern messaging standard. First of all, as a standard, RCS is carrier messaging, so messages are delivered to a single carrier phone number, rather than multiple devices via the Internet, like how you would expect a modern service to operate. As a standard, there’s no encryption. Google tried to glom features onto the aging RCS spec, but if you consider those part of the RCS sales pitch, which Google does, now it’s more like you selling “Google’s proprietary fork of RCS.” Google would really like it if Apple built its proprietary RCS fork into iMessage.

Google’s version of RCS—the one promoted on the website with Google-exclusive features like optional encryption—is definitely proprietary, by the way. If this is supposed to be a standard, there’s no way for a third-party to use Google’s RCS APIs right now. Some messaging apps, like Beeper, have asked Google about integrating RCS and we were told there’s no public RCS API and no plans to build one. Google has an RCS API already, but only Samsung is allowed to use it because Samsung signed some kind of partnership deal.

If you want to implement RCS, you’ll need to run the messages through some kind of service, and who provides that server? It will probably be Google. Google bought Jibe, the leading RCS server provider, in 2015. Today it has a whole sales pitch about how Google Jibe can “help carriers quickly scale RCS services, iterate in short cycles, and benefit from improvements immediately.” So the pitch for Apple to adopt RCS isn’t just this public-good nonsense about making texts with Android users better; it’s also about running Apple’s messages through Google servers. Google profits in both server fees and data acquisition.

everyone knows about burn outCriterion Games’ beloved, long-dormant collision-centered arcade racing franchise that EA has inexplicably left to gather dust since 2009. The series hit critical mass with Burnout 3: Takedown and, many feel, reached near-perfection with the open-world Burnout Paradise several years later. They’re excellent games; the sort of high-adrenaline racers you’d recommend for newcomers to gaming or seasoned pros alike.

But of course, the series wasn’t exactly firing on all cylinders out of the gate. original burn out, launched in 2001, illustrates humble beginnings, especially compared to what would follow in the years to come. It also very nearly released with some pretty strange titles in Japan, as we’ve been reminded this week.

Lots of games undergo name changes when localized from one region to another. We’ve discussed some of the racing genre’s worst offenders in the past — for example, how TOCA World Touring Cars became Jarrett & Labonte Stock Car Racing. The case with burn out is similar, though maybe not as egregious because it wasn’t as blatantly deceitful, and it never ultimately happened. burn out was supposed to be released in Japan as Grand Heat in 2002 via Sega — not Acclaim, who was responsible for Burnout’s distribution in the rest of the world.

Grand Heat never came out, and nobody knows exactly why. the burn out series didn’t debut in Japan until the second game, which had the exact same title as it did everywhere else — Burnout 2: Point of Impact — even though Japanese gamers would’ve never seen its predecessor on store shelves.

What’s more, Grand Heat wasn’t even the first potential name under consideration. game archivist Comby Laurent — the same guy who brought us Luigi’s demonic cameo in Sega GT — has uncovered another, earlier working title for the Japanese version of Criterion’s racer: Heaven’s Drive.

I’ll show you my latest find, exceptionally, on PS2.

The unreleased Japanese version of Burnout 1. pic.twitter.com/OJNxwmsd3x

– Sega Dreamcast Info (@CombyLaurent1) August 8, 2022

There is something distinctly cursed about that name in the signature burn out font, on the original burn out title screen. As for what it meant, context gives us clues.

See, before burn out was but a glimmer in Criterion’s eye, Konami started on a series of arcade-exclusive racing games titled Thrill Drive. Like burn out, Thrill Drive required players to thread the needle in traffic to defeat their competitors. also like burn outcrashes in Thrill Drive put a hard stop to the racing action: the fidelity of the vehicular carnage was what made the game unique for its day.

If I had to sum it up, the main difference between the two games is tone. Thrill Drive haunts you with screams of agony upon every accident; red and black swirls and blankets the screen as your driver is launched from their vehicle amid flashes of the word “FATALITY” in Japanese. Thrill Drive is overwhelmingly, madly macabre. burn out isn’t, but Criterion was definitely influenced by Konami’s earlier work. Perhaps Heaven’s Drive would’ve signaled to Japanese gamers what the newer game was all about, while also paying homage to its inspiration.

For whatever reason, Heaven’s Drive was replaced with Grand Heat, which Sega never released. The fact Sega would have been on tap to release burn out in Japan, when it was published by Acclaim elsewhere, it is an interesting footnote. Sega had an odd partnership with Acclaim during this time, whereby the defunct, Long Island-based publisher was responsible for distributing a few of Sega’s arcade conversions, like F355 Challenge: Passione Rossa, crazytaxi and 18 Wheeler: American Pro Trucker, on some platforms in the West. I’m not a particularly avid game collector, but I wish Sega had gone through with this one, just so I could have a version of burn out on my shelf with weird box art and an even more cryptic name.