Live data from Hacker News

Google Jibe: Better carrier messaging for everyone

jibe.google.com

41–50 of 69 posts

Re: Google Jibe: Better carrier messaging for everyone

#41
post #16

One big question: will carriers still charge exorbitant per-message fees? And one huge question: will iOS support RCS?

Are there still companies that still charge per message fees?

Depending on the contract they do. Often enough it's the GSM modem paging someone for alarms that holds a SIM with some old corporate contract that has no flatrate. And you'd violate the contract if you exchange it for some private contract SIM with all inclusive SMS.

Re: Google Jibe: Better carrier messaging for everyone

#42
post #36

Wow, RCS seems pretty bad from a privacy standpoint. The spec is available on the GSMA website [0]. The relevant section is 2.13.1.3 of "Rich Communication Suite 6.0 Advanced Communications Services and Client Specification Version 7.0-final draft" available in the specification ZIP. TL;DR: Encryption seems to be included but for voice and video only. They have _deliberately_ compromised messaging security to be vuln…

There are a bunch of customers that are countries that have a tight hold on their telecom industry. Which I don't mean to offer as a justification, just as an observation that making allowances for "compliance with legal interception procedures" is not anything new for that industry.

Re: Google Jibe: Better carrier messaging for everyone

#43
post #19
post #15

Earlier quoted context omitted.

Have you tried Telegram?

Hadn't heard about it. Just checked it out, and it looks interesting. Unfortunately, due to network effects and my social circle, 99% of the people I know pretty much only use either Wechat, Facebook, or e-mail, but I look forward to seeing something disrupt this space with something better, more functional, cross-platform, and multi-login. It would be killer if Telegram could interoperate with at least 1 or 2 of the…

I once thought we migrated most of the instant messaging world to Jabber. Now on the desktop side of things a lot of stuff switched to Hipchat, Slack, Skype and what else. On the mobile side of things we see WhatsApp, Threema, Telegram, Signal, Facebook with now some RCS thrown in between. Feels like we're back at the end of the 90s. And now fighting on two fronts for open networks. :( The only communication that stayed open all the time seems to be IRC and email.

Re: Google Jibe: Better carrier messaging for everyone

#44
post #16

One big question: will carriers still charge exorbitant per-message fees? And one huge question: will iOS support RCS?

Are there still companies that still charge per message fees?

Yes, every mobile phone operator in the UK charges for SMS and MMS if you're PAYG user. Users on contracts typically get 1000s of free SMS per month, but I'm not aware of any contracts that have inclusive MMS.

Re: Google Jibe: Better carrier messaging for everyone

#45
post #15
post #7

Ick. I wish we could kill SMS/Whatsapp/Wechat/LINE already and just do everything over e-mail or some other cross-platform, multi-login protocol. I hate being tied up to one device to message people. I change devices on the order of minutes, move over the course of a day between a few locations that all have devices I own, and don't regularly carry or look at my cell phone if I am already staring at something bigger…

Have you tried Telegram?

While Telegram has wonderful UI/UX, their server code isn't open source, and replies from support have been spotty, at best.

I fear it could eventually become another closed garden.

Re: Google Jibe: Better carrier messaging for everyone

#47
post #4

Of note: Project FI has been plagued with short SMS issues for the past year. Some are reporting that this has been fixed, but does concern me if Google is going to get into this space. I'm saying this as someone who is a Android advocate and developer.

I had a bunch of shortcode issues too -- contacted support and they gave me some canned 'its an smpt gateway issue, we cant fix'. Checked online and found that that is incorrect, called support again and linked the support forum discussions and they escalated me to a tech who reset something -- I have since received shortcode texts.

Re: Google Jibe: Better carrier messaging for everyone

#50
post #7

Ick. I wish we could kill SMS/Whatsapp/Wechat/LINE already and just do everything over e-mail or some other cross-platform, multi-login protocol. I hate being tied up to one device to message people. I change devices on the order of minutes, move over the course of a day between a few locations that all have devices I own, and don't regularly carry or look at my cell phone if I am already staring at something bigger…

"I wish we could kill SMS/Whatsapp/Wechat/LINE already and just do everything over e-mail or some other cross-platform, multi-login protocol."

That's an workable idea. What's needed first is to improve the transmission speed of short emails. I was once considering writing a mail forwarder for servers that don't have mailboxes, one that would open an outbound SMTP connection to the destination host before closing the incoming SMTP connection. The message would be forwarded immediately and the status code passed back to the inbound SMTP connection before closing. No mail bounces, ever. This would be the normal case for single-address emails that aren't too big and aren't tagged as spam. It's not essential to do it this way, but a mail server should not delay a short message more than 1 second.

Next, IMAP servers need to implement NOTIFY per RFC 5645. [1] This provides a push notification back to any interested mail client that new mail is available.

Mail clients can then treat emails like message conversations. Maybe using the "colored bubble" display UI on mobile, as with texting. A useful informal standard could be that single-recipient subject-only emails or no-subject emails get that display treatment.

That gives us texting with attachments for images using existing infrastructure. It could kill off a few unnecessary messaging services.

[1] https://tools.ietf.org/html/rfc5465

Post reply on HN