BulletTooth_Tony

Grrrr… in 2021** to lead off that 2nd paragraph.

Correct, there is not. And it’s probably the one that would be the best to do.

Those are 2022 stats? There’s been 1 game, so 16 teams have yet to host a game.

https://www.sportsbusinessjournal.com/Daily/Closing-Bell/2022/01/11/NFL-Attendance.aspx

In 2022, NFL set a record high in attendance; this as new stadiums get smaller to drive up the ticket prices you’ve mentioned. This is higher than the previous record set in 2019 – the last year every team had 100% stadium capacities before the pandemic. 2020 had 0 fans, 2021 had limited capacities to start in many places, then opened up fully as the year went on.

Commercials are sold based on the number of eyes that will witness them. Broadcast TV has the highest ratings, eyeballs, so broadcast TV spends the most money to secure rights. Going behind a paywall would crush their revenues. It’ll never happen. TV ratings are up, to an average of 17.1 million TV sets per game, and less than 2 million subscribe to Sunday Ticket – which has always been a money loser for DirecTV. The money is in broadcast TV.

https://www.cnn.com/2022/01/13/media/nfl-ratings-regular-season/index.html
https://www.cnbc.com/2022/06/24/disney-apple-and-amazon-keep-waiting-as-nfl-considers-sunday-ticket-offers.html

And then for boxing and MMA, they are both routinely on Fox Sports and ESPN. The PPVs are streamed.

The contract ends after the 2023 season. So that’ll be soon enough.

No. The blackout rule has been gone for like a decade. Sellouts are up. OTA games ARE the corporate contracts. Zero.

Why do you think you can’t move an eSIM phone to phone? It’s just as simple as moving a physical one, but in button-press form. Go into Settings, Cellular, Add Cellular, then your plans will show up if it’s iPhone-to-iPhone and you just tap and confirm on the other phone. If you’re doing this as part of a new phone purchase, it’s part of the setup process where you scan that fuzzy blue circle.

On Android you do it thru their website, it’s not as frictionless as the iPhone, but the article is about iPhones. Anyway, Android, you register the new eSIM on the carrier website, and then deactivate the one phone, then activate the new.

RCS is a standard proposed by the GSMA. But Google forked it and created Google Messages RCS. It can not send messages into Jibe, and Jibe can not send messages to Google Messages. They’re 2 different apps even, Android Messages and Google Messages. In any event, ZERO US carriers currently support RCS. Each has ended development of it and outsourced it to Google. And carriers old systems? Yeah, they can’t send messages to Google RCS either. Google RCS is an over-the-top service that completely circumvents carriers. Sorry, I expected better from you.

"Commercial product availability expected in 2024."

Expected isn’t a term of certainty. Something coming out next week, however…

Carriers have to support the standard… carriers. Not an OEM. It isn’t a physical port like your USB example. It’s part of an air interface, and would just exist if it were an adopted standard, they’d have no option. Google’s implementation is an over-the-top instant messaging service using the name "RCS". It’s a just-another-app solution, like WhatsApp, Signal, etc, yet is less feature-rich than any of those.

The standard is SMS. RCS was a proposed standard… in 2008. 2008. It lists WINDOWS PHONE as supporting it still. It’s long been lapped in features and functionality by every other instant message client, and it ignores that dumb phones are still a thing. Carriers gave up on RCS, so it will never be available by default like SMS. If it were an adopted standard, Apple would have no choice but to add as it would just be there out of the box when they implement their radio interface. You know, those standards called LTE and NR? Yeah, those standards. SMS exists, by default, from GSM to UMTS to LTE to NR.

They are following the standard. The standard is SMS. It’s available to literally everyone with a mobile phone on the planet, including dumb phones.

Ok, since you’re incorrect, allow me to give you the answer.

There’s zero. No other apps can send an RCS message to Google Messages other than Google Messages. It’s a closed user group.

There may be many RCS apps. None talk to each other, none talk to Google Messages. There were a couple that did on the old jibe service, those services are being replaced by Google Messages since carriers were blocking jibe.

iMessage was offered to carriers as a replacement to SMS. They turned it down.

And yes, standards are built-in… after being agreed to by the industry players. Like, the 3GPP developed the standard of UMTS (W-CDMA), LTE and NR. The GSMA adopted them as standards. Everything in the spec… is built in. SMS is built in. You can’t NOT have SMS and deploy these radio technologies. It became so used that CDMA carriers stapled it on top of their network.

They don’t operate together. Android Messages is the old Jibe service. Samsung Messages could be configured to connect to the old Jibe service. This is Google Messages, an entirely new service. Why does it exist? Because with both those other 2 apps, companies like Verizon and AT&T would alter the server setups to point to their own proprietary RCS systems, blocking the use of Jibe entirely. AT&T even did it to Google Messages that’s over-the-top.

And both those apps you mentioned, they don’t work with Google Messages RCS. And support for both is ending.

Rrrright. So point me to all the other apps that can send an RCS message to Google Messages. Because that’s the app and system under discussion. All others are no longer supported and will slowly disappear. I’ll wait.

Your interpretation of a statement being called asinine, is itself asinine. At no point did I call anything other than your statement or request asinine.

And, to repeat – Google gave Jibe (the platform it purchased when it bought Jibe Mobile) to the GSMA as their first attempt to solve the problem with cross-carrier interoperability. Google Messages RCS can not send to Jibe. Nor can Jibe send an RCS message to Google Messages RCS. Why? Because Verizon and AT&T would not allow Android Messages, or Samsung Messages to link to Jibe. So Google went alone and launched their own over-the-top service. Key words. Over-the-top. It circumvents carriers so that any user can just install the app and get it. It may use the Universal Profile the GSMA adopted, which Google created anyway, but it is NOT GSMA RCS.

Can you see the problem yet? This is complex, and they keep using the same terms to continue to make it even muddier. There’s many Jibe platforms in use, none speak to Google Messages RCS. It’s a Closed-User Group, which Google alone controls the access to.

Your statement and request are both foolish. If you feel that makes you, as an individual, foolish then that’s a self-esteem problem and not an insult.

And my statements are facts, if you don’t know these series of facts then you haven’t been paying attention for the past 10 years. RCS deployments lack interoperability. That’s why the CCMI existed in the first place. Each system was disparate. The CCMI folding is why Google went alone and set up their own servers outside of carrier systems, to make them independent and not be stuck with a Verizon and AT&T blocking them from enabling Jibe in Android Messages, which they did. Carrier control made Samsung Messages on AT&T use a different server than other carriers with Samsung phones. These are all facts. Google went alone, Google controls the server, Google doesn’t allow third party access, Google Messages is the only app with guaranteed cross carrier capability.

Oh, and even if you have Google Messages, companies like AT&T can bork it.

https://www.androidauthority.com/att-rcs-google-3121088/

Do you even know what the word means, because it’s not an insult. It means foolish. Your statement is foolish, because it ignores all the facts I provided. Your request that I provide proof that something doesn’t exist is foolish, because then it would exist – you’re using circular logic. It’s foolish.

I can’t provide you proof that something doesn’t exist. I can continue to point you to developer.google.com and ask you to find one, which will result in you discovering one doesn’t exist. I can’t punch those keys for you. This isn’t GSMA RCS. This is Google RCS. I don’t know what’s so hard to understand here and why you insist on referencing the literally abandoned GSMA platform. Google may have given them Jibe, but Jibe can not send RCS to Google Messages. How can I prove that? I can’t. You need to go try yourself.

In any event, this is a 14 year old service that has long been surpassed in features and functionality by virtually every instant message client, including iMessage. You seem to enjoy the idea of RCS, as it was proposed those 14 years ago in LTE’s infancy. That does not, and will never, exist. This is Google’s latest futile attempt to "win" messaging, they control the servers for a reason – they want the metadata and the data at-rest on your device. This will never be federated. And any SMS replacement needs to be a radio technology/carrier solution. And carriers have given up on RCS, there’s no money in it for them – so the actual solution might come, if we’re lucky, with whatever 6G is at the end of this decade.

Insult? Where, precisely?

And I have provided articles. And as far as things that don’t exist, what do you want me to post? I can’t provide something that doesn’t exist! How asinine a request that is.

Ok. So your belief is that Google uses GSMA API’s? That’s… asinine. If that were true, why doesn’t Android Messages (Jibe) have the capability to send an RCS message to Google Messages RCS? That’s right, 2 different Google services providing RCS don’t have compatibility. How come each "UP" server can’t send a message to any other UP server; eg, AT&T Messages can not send to Verizon Messages+?

There’s no interoperable RCS deployment. The only one that works across carriers is, at this point in 2022, Google RCS; which carriers have now outsourced RCS to. Google uses exclusively Google servers. They are not federated. Period.

No, Google is not willing. There are no third party APIs to interact with it, if they were willing, there would be. There is no Federation of RCS servers to support a standardization of RCS, if they were willing, there would be. There’s only ONE total app that does Google RCS, and that’s Google Messages; if they were willing, there would be more. It’s entirely closed source, following the RCS feature set.

Apple, however, was absolutely willing to offer iMessage to the carriers as the universal replacement. Carriers turned them down.

Here’s the Wall Street Journal article if you can get past the paywall:

https://www.wsj.com/articles/ugh-green-bubbles-apples-imessage-makes-switching-to-android-hard-1539867600?mod=e2tw

If you can’t, the direct quote:

"We approached the carriers to pursue adding features to the existing texting systems and removing the additional customer costs," explains Scott Forstall. "For various reasons, from the difficulty of extending the existing standards, to challenges with interoperability between texting systems and carriers, to the desire of carriers to protect a significant revenue stream, these explorations didn’t pan out."

It will fall back to SMS/MMS. It will not send an RCS message between opposing RCS platforms. Google Messages can’t even send a message to joyn, as an example. This is a problem of all RCS deployments, and there was a cross carrier working group that formed long enough to have a press release, then promptly disbanded. What’s being pushed now is Google’s closed system, as anyone can just install the app even if the carrier hasn’t adopted that app as their default. Google could release said app on iOS right now, literally. It just wouldn’t have SMS/MMS fallback, which they’ll never get. So it’s an "old man yells at cloud" moment for them.

Sorry for the 3rd. Edit timers and whatnot but at least I can elaborate more now.

The reason why looking at the GSMA API data from any year, is that yes, you could develop an RCS platform yourself using it. However, it will never communicate with Google RCS. It’ll just be yet another closed RCS system like every other carrier RCS system that came before it. Why would Apple ever bother to do that when iMessage is far better than RCS? It would at no point ever fall back to RCS, iMessage would sit higher in the hierarchy.