Slashdot Mirror


Google Is 'Pausing' Work On Allo In Favor 'Chat,' An RCS-Based Messaging Standard (theverge.com)

An anonymous reader shares an exclusive report from The Verge about Google's next big fix for Android's messaging mess: Instead of bringing a better app to the table, it's trying to change the rules of the texting game, on a global scale. Google has been quietly corralling every major cellphone carrier on the planet into adopting technology to replace SMS. It's going to be called "Chat," and it's based on a standard called the "Universal Profile for Rich Communication Services." SMS is the default that everybody has to fall back to, and so Google's goal is to make that default texting experience on an Android phone as good as other modern messaging apps. As part of that effort, Google says it's "pausing" work on its most recent entry into the messaging space, Allo. It's the sort of "pause" that involves transferring almost the entire team off the project and putting all its resources into another app, Android Messages. Google won't build the iMessage clone that Android fans have clamored for, but it seems to have cajoled the carriers into doing it for them. In order to have some kind of victory in messaging, Google first had to admit defeat. Some of the new features associated with Chat include read receipts, typing indicators, full-resolution images and video, and group texts. It's important to keep in mind that it's a carrier-based service, not a Google service. It won't be end-to-end encrypted, and it will follow the same legal intercept standards. The new Chat services will be switched on in the near future, but ultimately carriers will dictate exactly when Chat will go live. Also, you may be persuaded to upgrade your data plan since Chat messages will be sent with your data plan instead of your SMS plan.

85 of 146 comments (clear)

  1. Nope ... by Anonymous Coward · · Score: 2, Informative

    Don't have a data plan, don't want a data plan.

    Fuck you and your data plan, you better keep supporting SMS, because it's not going anywhere.

    1. Re:Nope ... by VeryFluffyBunny · · Score: 1

      It probably won't work on iPhones either. I regularly get garbled SMS messages from friends who use iPhones because they didn't use an SMS app to send it. All I want is a messaging service that everyone on any cell, mobile, or smartphone, no matter which carrier, no matter which make of hardware, that just works. For the history of mobile phones, that's been SMS. I see SMS as like email: For all its issues, it's the least bad messaging system we all have.

      --
      Debate is a form of harassment. Do not question my truth.
  2. data pkan instead of sms plan? by houghi · · Score: 1

    That would mean they have to give up the cash cow that is SMS. I get 4000 sms for 'free' with my pre-paid card and 4GB of data fora month for 25EUR. After a minth I use the 25 to buy 500MB and that is good enough. The other 15 i use for SMS as I have to pay for them.
    Having that included in my data would make me buy less. That will be their profit that is gone.

    Now I pay 0.10 Eur per sms for 120 characters of data. So they already make a shitload on them. Doubt they will drop ot fast.

    --
    Don't fight for your country, if your country does not fight for you.
    1. Re:data pkan instead of sms plan? by phayes · · Score: 1

      Cash cow? Depends where you live.

      My free.fr plan is unlimited SMS & 4G data for 15.99€/month.

      What exactly does Google Chat bring me that I do not already have using MMS? Nothing as far as I can see, so I don't see this gaining any more traction than WEP did.

      WEP, for those who don't remember, was a web portal tech that was pushed by operators so they could control (and MONETIZE!) cell-phone connections to the Internet. It had a minor point back when phones weren't powerful enough to browse the web directly but died when Safari/iPhone was rendering web pages directly.

      --
      Democracy is a sheep and two wolves deciding what to have for lunch. Freedom is a well armed sheep contesting the issue
    2. Re:data pkan instead of sms plan? by 110010001000 · · Score: 1

      In Europe you have to pay per SMS? How backward.

    3. Re:data pkan instead of sms plan? by Joce640k · · Score: 1

      Nobody cares because we all have gigabytes of data in our plans.

      Google needs to do some basic research. No European will ever use this if it's based on SMS.

      --
      No sig today...
    4. Re:data pkan instead of sms plan? by laie_techie · · Score: 1

      I think in the US they pay to receive SMS. Which is by the way a weakness of using internet data for a chat protocol : you'll have to pay for the bytes even to read messages sent to you. Unless.. the carriers sort this out. So in countries with cheap carriers or carrier competition perhaps this RCS carrier protocol may be interesting. In particular they may have offers that give RCS chat acess but no Internet access. That's good if you don't want Internet on a phone.

      Back when we had a limited number of SMS messages we paid to send and receive. I admit it's backwards to pay to receive, but c'est la vie. With most of our plans carrying unlimited messages, we don't care anymore.

    5. Re:data pkan instead of sms plan? by houghi · · Score: 1

      Only part of the time and because I have a pre-paid.
      Say sta of nanuary I add 25 EUR. When I do that, I can use 4GB data and send 4.000 SMS. What I would need to pay for is calls. I hardly call (VoiP is data). This is valid for 1 month. So the 1st pof befruary I use 10 EUR of that 25 EUR to buy 500 MB for a month. I then pay for my SMS and calls.
      That I do with the 15 EUR I have left. Even if I would use that all, I would be paying 25 EUR per two months.

      OTOH I could take a plan of 25 EUR per month. No extra costs for SMS. The one is 25 EUR per two months. the other is 50 EUR per 2 months.

      You really think your SMS are free? How cute. And I do not pay for receiving calls, not SMS and I have free roaming in a lot of countries.

      --
      Don't fight for your country, if your country does not fight for you.
    6. Re:data pkan instead of sms plan? by OrangeTide · · Score: 1

      I pay about $6.75/mo for my data plan. If I mainly use it for instant messaging and email, so there is no way I can use up even a tenth of my data plan.

      --
      “Common sense is not so common.” — Voltaire
    7. Re:data pkan instead of sms plan? by MichaelSmith · · Score: 1

      I had to pay to read your post on my desktop. Whats the difference?

    8. Re:data pkan instead of sms plan? by TheRaven64 · · Score: 1

      Depends on the plan. I pay 2p per SMS and 1p/MB of data on a pre-pay plan, but if you're on a contract you typically get a bundled SMS allowance that's more than anyone who isn't a teenager can possibly use or unlimited on the less-cheap plans. I don't send more than a dozen SMS messages in a month, so paying 2p each cost me very much in aggregate (I typically spend under £1/month in total on my phone, which is less than the cheapest contracts with inclusive allowances). SMS is, per byte, very expensive. One SMS is 140 bytes, so I'm paying more than 14 times as much for SMS than data. That's gone down a lot - about 15 years ago, I was paying around £500/MB for SMS data, and a tiny fraction of that for IP data - but carriers are still milking SMS.

      --
      I am TheRaven on Soylent News
  3. SMS will stick around by Comboman · · Score: 4, Informative

    Since SMS is baked into the cellphone signaling protocol (and is the last thing still working in an emergency when data and voice are overloaded), I suspect it will be sticking around for a while.

    --
    Support Right To Repair Legislation.
    1. Re:SMS will stick around by jaymemaurice · · Score: 1

      Since data is trivially tiered especially when dealing with services the carriers provide in house, expect to be able to get cheap limited data plans with unlimited "Chat". Or you might find even though Chat uses data, the carrier might charge a small premium to have access onto their Chat infrastructure.

      It might also be similar how you can get a LTE phone where the operators do VoLTE, yet offer plans without data or charge you for minutes at voice rates instead of the VoLTE data rate.

      --
      120 characters ought to be enough for anyone
    2. Re:SMS will stick around by JackieBrown · · Score: 1

      If you have a plan that doesn't have unlimited voice, it's because you either did zero research or wanted the cheapest plan you could find.

      I have not seen a limited voice plan in 5 years.

    3. Re:SMS will stick around by Anonymous Coward · · Score: 1

      I've never paid for an unlimited voice plan. What's the point? Who wants to pay $30 or more for basic cell phone service?

    4. Re:SMS will stick around by JackieBrown · · Score: 1

      Which is fine. But then don't bitch that you are on a limited plan

    5. Re:SMS will stick around by sexconker · · Score: 1

      I have not seen a limited voice plan in 5 years.

      Most of the popular prepaid plans are limited.
      People value data more than voice, and only want enough minutes to handle the occasional emergency or maybe the one month you're job hunting.

    6. Re:SMS will stick around by el_smurfo · · Score: 1

      That's what they said about analog TV, then they needed the bandwidth and it's gone...

    7. Re:SMS will stick around by el_smurfo · · Score: 1

      I have a 750 voice minute plan. I probably use 5 minutes a month. I keep it because it's grandfathered unlimited data at $40 a line. Even the reps are impressed when I call in.

    8. Re: SMS will stick around by bobmajdakjr · · Score: 1

      i think att changed mine from 450min to unlimited and i still only use 5 of them. wish i could just have data and sms without voice.

  4. Why does it need to be carrier based? by nine-times · · Score: 4, Insightful

    Maybe I'm missing the point, but why are we working on a carrier-based replacement for SMS at all? Building services into the fabric of cell carriers makes everything less transparent and portable, and opens opportunities for them to play hanky-panky with pricing and restrictions. In my view, carriers should accept a role as a dumb-pipe wireless Internet service, and services should be platform agnostic.

    Could we just come up with a messaging standard that everyone can agree to? Get Facebook, Google, Apple, and Microsoft all to agree on a set of protocols and standards. The same way that a Gmail user can email and Office 365 user, a user of Apple Messages should be able to message a Facebook user. Why is that so hard?

    As far as I can tell, it's not. It's just that all these companies all want their own little walled gardens so that they can abuse their customers, or else are suffering from Not-Invented-Here syndrome.

    1. Re:Why does it need to be carrier based? by gehrehmee · · Score: 5, Insightful

      It's called XMPP. It's an open IETF standard, and it supports federation in exactly the way you're talking about -- multiple organizations can run their own infrastructure, and talk to each other, just like you can with email. It's extensible, and it *used* to be exactly how Google Talk works.

      The key feature it's missing is the lock-in walled-garden features all the major players want.

      --
      "You know, Hobbes, some days even my lucky rocketship underpants don't help" -- Calvin
    2. Re:Why does it need to be carrier based? by Archangel+Michael · · Score: 1

      Google Talk

      Is all but dead. It was killed off for "hangouts". If anything remains of Gtalk, it is just a skeleton of the service.

      And I'm still bitter.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    3. Re:Why does it need to be carrier based? by Anonymous Coward · · Score: 4, Insightful

      Could we just come up with a messaging standard that everyone can agree to?

      Good (no-brainer!) idea.

      Get Facebook, Google, Apple, and Microsoft all to agree on a set of protocols and standards.

      Whoa, stop. You suddenly jerked to 180 degrees away from the previous sentence. Those are the enemies of standards. Those companies are why you're not already using a standard. The only reason to invite them to the table, would be if you'd like them to sabotage progress.

      Use a standard (XMPP). All the power is in users' hands. And then those companies can join the game, or they can be left out. But they need to be led; under no circumstances should you be asking any of them to lead, because they have reasons to prevent you from using a standard. They want you to use their app and look at the ads they were paid to show, and have your plaintext go through their marketing analytics. We've been through this before and it's part of the reason why people switched away from standards to proprietary IM where users are locked into using specific apps instead of having competing implementations using interoperable protocols.

      You have to choose between getting what your want xor using those companies' products.

    4. Re:Why does it need to be carrier based? by bigpat · · Score: 1

      Building services into the fabric of cell carriers makes everything less transparent and portable, and opens opportunities for them to play hanky-panky with pricing and restrictions. In my view, carriers should accept a role as a dumb-pipe wireless Internet service, and services should be platform agnostic.

      Could we just come up with a messaging standard that everyone can agree to? Get Facebook, Google, Apple, and Microsoft all to agree on a set of protocols and standards. The same way that a Gmail user can email and Office 365 user, a user of Apple Messages should be able to message a Facebook user. Why is that so hard?

      As far as I can tell, it's not. It's just that all these companies all want their own little walled gardens so that they can abuse their customers, or else are suffering from Not-Invented-Here syndrome.

      I agree completely with this. I think the problem has been the addressing not the actual messaging protocols. Meaning we have email addresses @gmail.com @icloud.com @microsoft.com which are interoperable and addressable across Internet providers and then we have phone numbers which are interoperable and addressable across phone networks.

      Universal addressability is the challenge, otherwise how do you send a message to someone?

      I would much prefer to see communication standards based on existing email addresses rather than phone numbers.

      We should build on the email standards so people can send messaging requests or video requests or other forms of communications requests to someone@domain.com and the server passes on the request based on the protocol. And if the server handling messages for @domain doesn't understand the protocol, then it should just ignore the message.

      No need to reinvent the wheel, just need to reinvent email without breaking basic email. Far better than trying to reinvent SMS just for phones.

    5. Re:Why does it need to be carrier based? by DontBeAMoran · · Score: 1

      Even if Facebook, Google, Apple, and Microsoft are the enemies of standards as you say, it doesn't matter since that's what people are using. Either we can demand and force them to use XMPP or something similar and open, or you can try forcing everyone to stop using Facebook, macOS, iOS and Windows. Hint: this will never happen.

      --
      #DeleteFacebook
    6. Re:Why does it need to be carrier based? by Junta · · Score: 1

      The problem is that none of those companies want a federated standard, *and* at least Google, Facebook, and Apple all have the resources to out-compete any standard.

      Otherwirse, XMPP (which already exists) would be more viable. None of the services want to endorse a system that allows communicating with users of their platform without first becoming a user of their platform yourself. Sadly, an alternative approach is unlikely to be a sound business plan, and the marketing dollars and such that come with a business plan are currently more important to adoption than any consideration like federated capability.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    7. Re:Why does it need to be carrier based? by el_smurfo · · Score: 1

      I think most users would be happy with iMessage but Apple won't open it up. RCS is trying to force Apple's hand at interoperability.

    8. Re:Why does it need to be carrier based? by 93+Escort+Wagon · · Score: 1

      At this point - unless/until someone develops a trivial-to-install OTR-style encryption utility which can transparently sit on top of this service, I don't see any reason for me to use this instead of SMS.

      --
      #DeleteChrome
    9. Re:Why does it need to be carrier based? by msauve · · Score: 1

      "Maybe I'm missing the point, but why are we working on a carrier-based replacement for SMS at all?"

      Good quesiton. Why not just use email, which is available on any modern phone? It's easily accessed from multiple devices, even a web browser in many cases. No real limit to size. You can attach documents. All the kids seem to like the limitations of SMS for some reason.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    10. Re:Why does it need to be carrier based? by sg_oneill · · Score: 1

      Presumably this isn't designed for TCP/IP style internet transmission but rather the S7 network, or whatever it is they use in the 4G/LTE era.

      Regardless, a standard isn't much of a standard if it isn't supported. XMPP is an awesome protocol, my last company was premised around it, and Ideally it IS what should be used, but we can moan and complain all we want about "standards"., but it Android and IOS use something else, then whatever that something else is, its the real standard.

      (For reference I'm fairly sure facetime uses SIP/RTP and the desktop component at least of iMessage uses XMPP, but I may be wrong about that. Both are closed communication networks and likely embraced and extended beyond recognition regardless)

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    11. Re: Why does it need to be carrier based? by Reverend+Green · · Score: 1

      Yeah.... Wasn't this problem totally solved ten years ago? The reason we now have 20 different, incompatible, yet feature-identical messaging apps is not technical. It's financial. Apparently there is no money to be made providing seamless, convenient, compatible messaging.

      The venture capitalist oligarchy is betting big on the "walled garden" prison state model. Amusingly, Uncle Sam's demand for positive ID on all communications means most of these incompatible messenger apps are using the carrier phone number as primary user ID. Making it really easy to switch to a different messenger app without losing contacts.

    12. Re:Why does it need to be carrier based? by TheRaven64 · · Score: 3, Informative

      The problem with XMPP is fragmentation. The core protocol is an IETF standard, but it's very minimal (messages, presence notifications, basically nothing else, including how clients authenticate with servers). Everything else is handled via XEPs and for every feature there are 3-4 XEPs describing incompatible ways of providing it. Google did a pretty good job with Jingle, which provided file transfer and a way of setting up streams to use for video / voice, but clients all implement different file transfer mechanisms. I don't think I found a single pair of Android XMPP clients that could exchange files, for example. There are multiple mechanisms for publishing avatars. The last time I looked, the most widely supported one was vcard-temp, which involves setting an base64-encoded image in an XML encoding of a vcard that you publish inside your presence stanzas. This XEP was deprecated as soon as it was published because it had a bunch of well-known problems and was intended as a temporary stop-gap. The replacement was built on top of PEP (personal eventing via PubSub) which was, in turn, built on top of PubSub. The PubSub XEP is fiendishly complicated to implement and PEP adds even more complexity, so it was years between the standard being published and any clients or servers properly supporting it.

      This last point really highlights the problem with the XMPP standards process. The IETF requires two interoperable implementations for an RFC to advance. The XMPP Foundation happily publishes standards-track XEPs with zero implementations. They never produced a reference implementation of a client library. Some newer open IM standards have learned from this mistake. For example, Tox provides a client library that is used by multiple clients and serves as a reference implementation. Unfortunately, it's not GPLv3, so anyone wanting to implement a non-GPL Tox client must reimplement the protocol (it's still better than no reference implementation though, and providing an incentive to implement a second client library may be good for the protocol in the long term).

      --
      I am TheRaven on Soylent News
    13. Re:Why does it need to be carrier based? by TheRaven64 · · Score: 1

      Their stated reason for dropping XMPP support was spam. XMPP makes it possible to validate the server that a message is coming from, but it's still possible for a new XMPP server to pop up, send spam until it's blacklisted, and then shut down and restart with a new domain name and IP address. Within a walled-garden network, you can require some external identification for new users and rate limit them until other people have added them to their rosters and validated that they're probably useful. Within an open federated network, this is much harder (and, unlike email, if you block suspicious instant messages for a few hours until you've learned if the server is malicious, users get really grumpy).

      None of the newer distributed IM systems have really done anything to tackle this problem either. You really need some form of distributed, anonymous, reputation system, but designing such a thing is really hard.

      --
      I am TheRaven on Soylent News
    14. Re:Why does it need to be carrier based? by nine-times · · Score: 1

      Addressing isn't really the problem. The format of "username@domain" is already used for a lot of things, not just email, and including instant messaging.

      I wouldn't suggest doing instant messaging email standards, though. Email protocols aren't great. It'd be better to develop a new set of standards for messaging, both email and instant messaging. The problem is, you'd need major vendors to buy into the same standards. You'd need Facebook, Microsoft, Apple, Google, and others to all agree to support the same standards, which isn't going to happen.

      The problem here isn't technical, it's economic and political.

  5. Rich Communibation Services by rossdee · · Score: 1, Funny

    So its just for the 1% then

    1. Re:Rich Communibation Services by BoRegardless · · Score: 1

      Hey, allowing the cell carriers to book more profit and do the heavy lifting of advertising and persuasion for Google, so they don't have to do it. Smart for Google. Glad I don't have to opt in.

  6. Color me surprised by OneHundredAndTen · · Score: 4, Insightful

    Google dropping the ball on a project. Who would have thunk. Google has shown to be pretty good at two things. First, at launching products that are supposed to be kind of flagship, only to abandon them completely after a while. Two, at making sure that their product naming is as confusing as possible. The Google culture, indeed.

    1. Re:Color me surprised by omnichad · · Score: 1

      Two, at making sure that their product naming is as confusing as possible.

      I still give Microsoft credit for winning at that. When they first released "Pixelsense" they called it the Microsoft Surface. And then a few years later rebranded only four months before reusing the name for their laptops.

    2. Re:Color me surprised by OneHundredAndTen · · Score: 1

      Your point is well taken. However, much as I despise MS (and I despise it cordially) I still think that Google outdoes them in this department.

    3. Re:Color me surprised by Dragonslicer · · Score: 2

      Microsoft Office has been the de facto standard for so long that nobody notices how bad the names are anymore. Word is the only one with an obvious connection between the name and the functionality. Outlook, Excel, and Powerpoint are all pretty meaningless names.

    4. Re:Color me surprised by TheRaven64 · · Score: 2

      These names are all pretty self explanatory. Outlook is a pun, as in 'look out, you're forced to work with Exchange!'. Excel is also pretty obvious. The ex- prefix means dead, and cells are the things that you find in spreadsheets: it's where data goes to die. Powerpoint refers to mains sockets, as in 'I would rather stick my fingers in a mains socket than watch another Powerpoint presentation'. Access is a credit card brand, and the name is intended to signify that you'll pay for putting your data in an Access database. Word is used in the singular to highlight the fact that it doesn't work so well with sentences or paragraphs.

      --
      I am TheRaven on Soylent News
    5. Re:Color me surprised by Dragonslicer · · Score: 1

      Very nicely done. /hattip

  7. Because using standards is so 2000 & late by ArhcAngel · · Score: 5, Insightful

    XMPP (formerly known as Jabber) has been around since 1999 and has most if not all of these features. Any it is missing can be submitted and added as it's an open standard. Google has essentially embraced its role as the new Microsoft and has begun their EEE march. Chrome has become the new IE6 with all of the non-standard extensions they've rolled out without so much as submitting anything to W3C for consideration. I'm now looking for alternatives to all Google properties.

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    1. Re:Because using standards is so 2000 & late by geek · · Score: 3, Interesting

      I've been 100% google free for a little over 2 years now. It's surprisingly easy to do.

    2. Re:Because using standards is so 2000 & late by jouassou · · Score: 5, Informative
      This. I've recently gone through a phase where I've been trying to get monopolies and clouds out of my life myself. If you need any inspiration, this is what I've ended up with:
      • * KolabNow as an email provider instead of GMail. They have a good privacy policy, are hosted in Switzerland which has fair privacy laws, and costs about $3/month.
      • * Syncthing for making your own open-source "cloud storage" as a replacement for Dropbox and Google Drive. I've played around with a few alternatives, but this was my favourite; it's very straight-forward to set up, fully peer-to-peer so you don't need a centralized server if you don't want one, and it has clients for most operating systems. The Android app lets you set it to only sync when it's on WiFi and/or charging.
      • * Maps is an alternative to Google Maps, which uses OpenStreetMaps, the "Wikipedia of navigation". It doesn't have the same knowledge of local shops and restaurants as Google Maps does, but it is "good enough" for most of my needs, and in contrast to other clients like OsmAnd, the interface is actually quite slick.
      • * CopperheadOS for my phone. It's still partially in the Google ecosystem, by being an Android distribution that requires a Nexus or Pixel. But Android itself is still mostly open-source, and this comes with all Google apps and services stripped out. (Lineage works as well, but Copperhead is more focused on privacy and security.)
      • * Yalp. Some apps are simply not available outside Google Store (e.g. online banking apps in my case); this helps you install such apps without having to install the full Google Services platform on your phone.
      • * Firefox Focus/Klar. In contrast to the usual Firefox browser, this new app is actually useable on a phone; and last time I checked it had better privacy settings than the Chrome browsers you find on most androids.
    3. Re:Because using standards is so 2000 & late by ArhcAngel · · Score: 1

      Thanks for the information. My biggest hang-up is Waze. I was disappointed when Google bought them since I knew it was only a matter of time before they screwed it up. Sure enough an update this week implemented Google's "flat" or material design UI and now it looks like a 2 year old's drawing. I'll take a look at the other apps. For my browser I've had great success with Waterfox. It's only recently been ported to Android but it works well and since I use it on all of my other devices the interface is the same across everything I use from Linux to Windows.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    4. Re:Because using standards is so 2000 & late by b0bby · · Score: 1

      How good at blocking spam is KolabNow? Google's spam filtering was the reason I switched to them in the first place.

       

    5. Re:Because using standards is so 2000 & late by omnichad · · Score: 2

      If Google thought that XMPP was good enough, they would have used it. It was the basis for Google Talk and based their protocol for Google Wave on it. Phones don't have always-on connections despite our best wishes, so they would need something a little bit different.

    6. Re:Because using standards is so 2000 & late by Luthair · · Score: 1

      It doesn't need to be that way - Google Talk was based on Jabber. Ultimately the client doesn't even need to be XMPP based, we just need the service to support XMPP federation so we don't have a walled garden.

    7. Re:Because using standards is so 2000 & late by Junta · · Score: 2

      Strange to say email addresses should be considered antiquated and turn around and say that phone numbers shouldn't be.

      email addresses continue to be a universally known thing and are popularly used.

      The problem is that in practice, email is very permissive and as such you can email from your provider to a provider they've never heard of (with unfortunate security implications that have not been overcome). In XMPP, your chat server administrator has to explicitly do something to establish a relationship with every org that you might want to talk to. As a federated technology, it falls short.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    8. Re:Because using standards is so 2000 & late by sexconker · · Score: 2

      You ever tried to coach someone weaned on modern tablet interfaces through the process of setting up an XMPP client and entering the arcane data you need to connect to a server? And then it doesnâ(TM)t work right and they didnâ(TM)t enter what you said exactly and you have to help them letter by letter?

      And how do you get from your friendâ(TM)s tel number to find them on XMPP anyway? Or do a real name search? You canâ(TM)t.

      XMPP is way too complex to catch on with the public and doesnâ(TM)t offer features like real name search that people want to find their friends and stuff.

      Believe it or not the world is not solely the basement dwelling nerd set. People have lives and they donâ(TM)t want to spend all their time messing with arcane things.

      Have you ever tried to tell an Apple user to use regular fucking apostrophes instead of the various curly abominations?

    9. Re:Because using standards is so 2000 & late by unrealmp3 · · Score: 1

      If you want your own "cloud" storage I'd point you towards Nextcloud, which seems to be quite solid and privacy-focused. Syncthing is a nice P2P file sync protocol though (not too complex to set-up once you understand the general concept), I use it to keep my phone user partition continuously backed up with my main computer just in case.

    10. Re:Because using standards is so 2000 & late by Anonymous Coward · · Score: 1

      XMPP works perfectly fine on intermittent connections: there are push notifications, interruptable connections, offline delivery, history retrieval, etc. Google abandoned it because they wanted everyone to use Google. The only reason they can't do the same thing (and they are clearly trying!) with Gmail is still too many people have non-Gmail addresses and they would genuinely lose users if they killed SMTP.

    11. Re:Because using standards is so 2000 & late by Junta · · Score: 1

      Ok, guess my experience was limited, I was setting up an xmpp to talk to google hangouts users, but I couldn't seem to make it work without having a google account.

      Of course I could be recalling something incorrectly, it was a long time ago and ultimately abandoned the effort.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    12. Re:Because using standards is so 2000 & late by jouassou · · Score: 1

      Thanks for the WaterFox tip, I'll look into it! The Wikipedia overview seems intriguing :).

  8. Mind your own damn business by Comboman · · Score: 1

    Some of the new features associated with Chat include read receipts, typing indicators,

    If I want to pretend I didn't get someone's message, that should be my own damn business. Ditto for "typing indicators" which I assume is what insecure people look at to see if someone is typing them a reply (pathetic fools).

    --
    Support Right To Repair Legislation.
    1. Re:Mind your own damn business by Anonymous Coward · · Score: 1

      How do you keep an idiot in suspense?
      (Anonymous Coward is typing)

  9. SMS is a useful "last resort" by Chrisq · · Score: 4, Interesting

    SMS can be used when there is a very weak signal, and no data connectivity. It has been used by hikers, people in sinking ships, and all sorts. This is really the only reason to use it now, but it is important

    1. Re: SMS is a useful "last resort" by Anonymous Coward · · Score: 1

      From the summary, add this other reason: SMS will work when the voice capability of cellular networks is unavailable because too many people are trying to make calls at the same time. Think mass panic.

    2. Re:SMS is a useful "last resort" by dryeo · · Score: 2

      My main reason for using it is that it is free and just works. I don't want to pay extra on my pay as you go plan for data, which is even more expensive here in Canada then the States, and I don't need anything more then text.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    3. Re:SMS is a useful "last resort" by MMC+Monster · · Score: 3, Insightful

      For me, the "always works" aspect is important. If you send a message and the receiver is a cell phone, they will get the message at some point.

      That's much more important than getting it immediately or not at all (as is sometimes the case with Apple's iMessage). And Apple understands that. Which is why when iMessage fails, they give the opportunity to resend as SMS.

      --
      Help! I'm a slashdot refugee.
  10. Google Sure is good at by RonVNX · · Score: 1

    Giving people what they do not want, no matter how many times they're told what people want. Google you see, knows better than you, what you want.

    1. Re:Google Sure is good at by Junta · · Score: 2

      You jest, but on this front, Google has gone through so many trials and changed their minds to try a new approach, either because it failed to catch on or they didn't do it in a way that enables enough profit.

      People use Android, Maps, Google search, and email. They use youtube, but google paid for that, unable to organically come up with something. Google Plus, Wave, Allo, and tons of other things have not achieved success, areas that Google desperately wants to be a part of.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  11. Re:Oh Greaaaaaat! by Octorian · · Score: 3, Funny

    I'd argue the most annoying feature of Apple's iMessage is convincing iPhone users that "texting" has all these features, so they'll freely use them when communicating with you... Thus forcing you to experience the pain of crappy MMS when talking with them.

  12. Re:I know this one! by Joce640k · · Score: 1

    Also: Based on SMS so that carriers can charge us per-message.

    --
    No sig today...
  13. RCS also means Revision Control System by Antique+Geekmeister · · Score: 1

    Did anyone else reading this summary think of the old source control system, RCS? RCS underlies CVS source control, and creates local ",v" files to record source control changes? I still use it occasionally, locally, when I merely want to record changes in a specific configuration file and not be burdened by git or subversion trying to report on all changes in the directory.

    I acknowledge that those would be confusing to send via a telephone based messaging system.

    1. Re:RCS also means Revision Control System by OrangeTide · · Score: 1

      Context matters. And you should stop worrying about obsolete software unless you're a computer historian.

      --
      “Common sense is not so common.” — Voltaire
    2. Re:RCS also means Revision Control System by Antique+Geekmeister · · Score: 1

      In my case, I am old enough, and and active enough, to be part of computer history. RCS, the source control software, is still useful in very old or extremely tiny environments which have individual files requiring source control. It's also sometimes useful put local files in local source control, in parallel with what Subversion or or CVS or Perforce do, and save local working changes without committing them upstream during local development. Ideally one configures the parallel source control to ignore anything named "*,v" or "RCS"

      I demonstrated this a few days ago to someone faced with editing local configuration files whose default contents were in a central source control system. I've found that old tool to be _very_ useful.

    3. Re:RCS also means Revision Control System by OrangeTide · · Score: 1

      I still have SCCS setup on two systems. I used to keep all my DNS configs in RCS, but I've switch them over to Git a few years ago. And I hacked a MUD's back-end text database to co/ci with RCS, which made it easier to track down what people have built or altered. But I'm not geezer enough to go on about the virtues of RCS.

      Having a scratch area by combining RCS and Subversion is equivalent to staging a change in Git. So it might be worthwhile to just switch to Git, Hg or Fossil. And with P4 you can create change lists without applying them to your branch, but you need network access to do that.

      --
      “Common sense is not so common.” — Voltaire
    4. Re:RCS also means Revision Control System by Antique+Geekmeister · · Score: 1

      I agree that a local git repo can be quite useful: I also use that. _But_ being able to source control individual files, without having to exclude anything else, has occasionally proven quite useful.

      The RCS tracked scratch files, on top of a Subversion workspace, may look like using git locally at a casual glance. But once again, the ability to source control one file only without having to exclude or handle the other files at all can help avoid confusion. I won't insist that it's the best approach: it can be a useful tool, which is why "RCS" remains associated with t hat set of tools.

  14. Will you just look at that.... by cjjjer · · Score: 1

    Instead of bringing a better app to the table, it's trying to change the rules of the texting game, on a global scale. Google has been quietly corralling every major cellphone carrier on the planet into adopting technology to replace SMS

    Hello Microsoft 2.0

  15. Re:I know this one! by Kozar_The_Malignant · · Score: 1

    Or "Telegram" or "Signal", but with extra data charges.

    --
    Some mornings it's hardly worth chewing through the restraints to get out of bed.
  16. The problem is timing... by Junta · · Score: 3, Interesting

    Certain modern norms tha tbenefit the enduser are a result of happening at just the right time.

    The network companies of the time could not keep up with the internet, and as such there were no players to prevent email from settling into the unassailable role it had gotten. It's possible that if AOL had played things a tad bit differently, we'd all be using AOL mail instead and email would be like XMPP, this idealistic concept that no one uses because it can't reach most people. None of the business folk at the time that had the resources was able to foresee a strategy to 'own' that. In this century however, federated standards have generally failed to succeed, as the stakeholders now have a handle on how to prevent that from happening again.

    Same with drm-free music. When wired internet became feasible to transfer music, but maybe not quite stream it as well as music players that couldn't realistically connect to the internet, attempts at DRM failed so badly they had to give up on the concept. By the time video became feasible, so to had network connectivity evolved to the point where any video playback device could pretty much have some network access at all times, or maybe it was the move away from hardware device provided interface towards 'apps' to consume a video content providers product.

    If you strike and get some fundamental truth about technology established, it's hard to get rid of, but the companies are *all* over messaging and won't stand for it.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  17. Still using hangouts.... by HockeyPuck · · Score: 1

    Allo, Chat, whatever comes next...

    I'm still using hangouts since it's built into the gmail web interface and the iPhone app isn't that bad either.

    1. Re:Still using hangouts.... by powerlord · · Score: 1

      Still built into the gmail web interface ... for now.

      --
      This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
  18. Why there's no SMS 2.0? by qaz123 · · Score: 2

    I don't understand why SMS is not updated. They create G3, G4, G5, VoLTE. Why SMS is still the same? They could at least make messages longer.

    1. Re:Why there's no SMS 2.0? by qaz123 · · Score: 1

      MMS loads its content via data connection over GPRS/3G/4G. No data connection - no MMS. While SMS can work without data connection, and therefore is more reliable. What I'm talking about is a new SMS that can work without data connection same as the old SMS

  19. Re:Figure this out by doom · · Score: 1

    Upload them to a child porn site while you're at it.

    Google's new AI-enhanced image processing combined with unencrypted trafficing can automatically identify naked baby photos and upload them to child porn sites without any intervention on your part-- tremendously convenient, with your deniability completely protected. /P

  20. Have we not solved the chat problem yet? by OrangeTide · · Score: 1

    I'm pretty sure we had widely available instant messaging clients back in the mid-1990's. 20+ years later and we still can't settle on a standard and live with a fractured set of incompatible networks.

    The whole point of the Information Age is for everyone to be connected and able to communicate with each other. Several proprietary chat protocols that are deprecated by their vendor every 5 years goes against progress.

    --
    “Common sense is not so common.” — Voltaire
  21. Re:New history by sexconker · · Score: 1

    Did you use iMessage to type that? Turn off your shitty fucking curly quotes.

  22. I'm still morning Wave by DalM · · Score: 1

    Wave really was awesome. It was everything anyone needed or wanted it to be. AND it was opensource and cross platform. If it had been baked into the heart of Gmail from the start it would have taken over the world.

    But sadly it was killed by pride and personal fiefdoms.

  23. no end-to-end encryption by Anonymous Coward · · Score: 1

    Why in the world would anyone develop a messaging app nowadays without end-to-end encryption? C'MON, Google!

    JFC. One step forward; two steps back.

  24. Re:Not Encrypted? by OrangeTide · · Score: 1

    I suspect it's typical Google culture where perfect is the enemy of good enough. They resisted encrypting Chrome passwords for so long because they felt that storing passwords locally was insecure. But somehow forgot that storing clear text passwords is even worse.

    I can run OMEMO over XMPP. I wonder if, with the right phone software, OMEMO could tunnel over SMS as well. Might be worthwhile to research.

    --
    “Common sense is not so common.” — Voltaire
  25. Google just released another service named Chat by thisisauniqueid · · Score: 1

    Google's left hand never knows what the right hand is doing. Less than a couple of months ago, Google released Hangouts for Business under the name Hangouts Chat. And thus the product branding confusion continues.