Earlier quoted context omitted.
> And then we have XMPP which doesn't support things like video or voice calling The Jingle extension is about a decade old and it's what Google based its support on. They even played ball for a while and released a good quality open libjingle, then decided that fighting spam from the other open XMPP networks is not worth their time and killed the whole openness concept - despite being an orders of magnitude simpler…
> I think now the only escape from the walled gardens is regulatory pressure forcing interconnect of the larger players Sounds good on paper, sure, but ultimately it will end up being a predictable bureaucratic mess, causing more harm than good: a) The mandatory 'open' standard that gets produced will end up being designed by committees of management teams from 6-7 major companies, each with their own list of feature…
How did Google Talk change from a dream to a nightmare?
311–320 of 382 posts
Re: How did Google Talk change from a dream to a nightmare?
#312Earlier quoted context omitted.
Signal and WhatsApp require a smartphone though, so not fully cross platform, and tied to their (closed) client software. Not sure if Telegram requires a smartphone too, but it does seem to require a phone number at least.
A smartphone isnt required, only a telephone number for authentification.
Re: How did Google Talk change from a dream to a nightmare?
#313Earlier quoted context omitted.
This sounds like a cynical joke, but for those people who don't use Voice, it's sadly what's really happening. I want to get off Google products for many reasons, but the main reason is becoming that I can't trust them to listen to users.
For people that use Google Voice, that's often the hardest Google service to leave. You can get similar features with https://jmp.chat/ - it supports text and picture messaging (and voicemail transcription) and you can port in your Google Voice number to make the transition seamless for your contacts.
Re: How did Google Talk change from a dream to a nightmare?
#314Re: How did Google Talk change from a dream to a nightmare?
#315Re: How did Google Talk change from a dream to a nightmare?
#316Earlier quoted context omitted.
And this is what happened back in the day. AOL was forced to add interoperability with competitors. But our government today is unwilling to step in front of corporations on behalf of the people.
HN readers don't all have the same government. I assume you mean the US one. The EU has in some cases proved to be willing to confront corporations and/or to defend some consumers right. Not always or in the most efficient way, but here's hoping that it will continue and improve on that path. https://en.wikipedia.org/wiki/Microsoft_Corp_v_Commission
Re: How did Google Talk change from a dream to a nightmare?
#317Earlier quoted context omitted.
True. I was assuming most people have at least one phone number they want to keep long term (even if it's not always active with their cell). Note though that signal will also work fine with non-traditional services that provide free or much cheaper phone numbers like google voice (US), skype, or twilio. It is true though that you do need to maintain a phone number. That is one of the trade-offs they made to allow it…
How does the phone number tie-in make it usable? Phone numbers and SIM cards are about the most user hostile thing I can possibly think of. What's wrong with the way Threema does it for instance, which is essentially to bind the identity to a key pair that you can back up?
Re: How did Google Talk change from a dream to a nightmare?
#318Earlier quoted context omitted.
Recommendations for good clients for desktop systems? Maybe my google-fu is particularly weak today, but I couldn't find a clear statements which clients outside conversations.im fullfill those (obviously only the IM suite, since mobile wouldn't apply)
https://gajim.org/ tends to be best for desktop (binaries exist for most desktop OSes). For macOS, you may want to try Adium or Psi. Or you can use https://movim.eu/ which, though a web client, has fairly good feature support as well.
Re: How did Google Talk change from a dream to a nightmare?
#319Earlier quoted context omitted.
Even if you didn't use Jabber, the #1 reason I recommended Google Talk was that it was very, very lightweight at a time when MSN Messenger and friends were adding stickers and other teenager/young-adult friendly* features. Today, ironically your choices for relatively straightforward messaging on the PC/Mac are: iMessage (Mac only), Skype for Business (the consumer client is too distracting for words), Whatsapp Web,…
Oh man, Slack really is a beast isn't it? I do like the multiple network nature of it (even though everything is saved to Slack's servers) but I find it hard to believe it does so little for it's footprint. They too though made a Google-like transition and went from an open protocol (IRC/XMPP) to a closed/custom API. At least here, the server admin can enable those protocols if they want and the API seems to offer en…
As for the XMPP gateway it's just barely usable. From my personal experience it even tended to drop messages from time to time. It seems Slack added it just to claim XMPP compatibility. Just look at where is Slack placed in this ranking https://conversations.im/compliance/
Re: How did Google Talk change from a dream to a nightmare?
#320Earlier quoted context omitted.
Duo is a mobile only video/voice chat app that uses a experimental transport protocol. Allo is a text chat app with lots of options for stickers and end-to-end encryption disabled by default. I don't have a strong need for either of these apps.
Well, my Motorola G5+, purchased in August and on 7.0, came with an icon for Duo prominently displayed. Hangouts not installed by default. (Nor Allo, I now see.) So, Hangouts is not facing some declared or expected EOL, at this point?