Extending Pidgin to Support Google Hangouts
-
what is it about GH you hate? to me it's just another messaging platform.
Granted I want one platform that litterally does it all, voice/text/video all in one and is everywhere - oh wait, we already have that.. it's called Skype.. but now a days.. it kinda sucks..
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
what is it about GH you hate? to me it's just another messaging platform.
Granted I want one platform that litterally does it all, voice/text/video all in one and is everywhere - oh wait, we already have that.. it's called Skype.. but now a days.. it kinda sucks..
Lack of central management and the extremely poor interface and reliability. For me it never works and there is no good way to make it work better.
-
Central management? You mean like Skype for Business? Or Slack?
So you want to maintain two separate solutions? One for work and one for personal?
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
Central management? You mean like Skype for Business? Or Slack?
So you want to maintain two separate solutions? One for work and one for personal?
Yes, at least I do.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
Central management? You mean like Skype for Business? Or Slack?
So you want to maintain two separate solutions? One for work and one for personal?
Yes, like those. And yes, absolutely.
-
To what end? Why do you want centralized control, but don't want private chat tied into your PBX (other thread).
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
To what end? Why do you want centralized control, but don't want private chat tied into your PBX (other thread).
Centralized control because it is the same as anything else in IT. Why do you use company computers, storage, email and such. Because you need to create accounts, support usage, control data locations, provide functionality. It makes things work.
Why not PBX is totally different. I don't want lots of things thrown together on one platform. PBX should handle calls, not IM. it's been shown that IM on the call platform languishes and doesn't get best of breed support, isn't kept up to date, has issues, etc. Just not a good idea.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
it's been shown that IM on the call platform languishes and doesn't get best of breed support, isn't kept up to date, has issues, etc. Just not a good idea.
Why do you think that is? Skype, at least for a long time, did that just fine. At least the consumer version.
But centralized IM control, isn't that a limited system to only a single company? So if you use are part of 3 different Slack systems, you have to have three logons?
Does slack support multiple logons at once?
I'm still waiting for the single global replacement of SMS/MMS. I know Scott hate's it's reliance upon a device/phone number, but even being tied to a phone number is an artificial constraint placed on it by the carriers.
If the phone companies really want to keep themselves in the messaging business they need to find a way to have a person register with a single system that is device agnostic.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
it's been shown that IM on the call platform languishes and doesn't get best of breed support, isn't kept up to date, has issues, etc. Just not a good idea.
Why do you think that is? Skype, at least for a long time, did that just fine. At least the consumer version.
I'm not sure what you are saying. Skype isn't related.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
But centralized IM control, isn't that a limited system to only a single company? So if you use are part of 3 different Slack systems, you have to have three logons?
No reason for it to be. the miracle of federation.
-
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
Voice yes, but not PBX. OpenFire does voice and chat in the same way.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
Voice yes, but not PBX. OpenFire does voice and chat in the same way.
Not PBX, but full typical phone system access - and that replaces the need for real PBX situations in a lot of cases (definitely not saying all/most etc).
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
Voice yes, but not PBX. OpenFire does voice and chat in the same way.
Not PBX, but full typical phone system access - and that replaces the need for real PBX situations in a lot of cases (definitely not saying all/most etc).
But not in a corporate one. Specifically the PBX piece is missing. It's just an ad hoc one to one phone connection. So doesn't apply.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
Voice yes, but not PBX. OpenFire does voice and chat in the same way.
Not PBX, but full typical phone system access - and that replaces the need for real PBX situations in a lot of cases (definitely not saying all/most etc).
But not in a corporate one. Specifically the PBX piece is missing. It's just an ad hoc one to one phone connection. So doesn't apply.
in that situation, you have Lync, I mean SfB.
-
And, I'd consider Skype a failure, not a success. It might be the best ad hoc tool out there, but it totally fails to be as good as a PBX or as an XMPP or as a federated member of a business. Skype is actually a great example of things not working. Sure it kinda works for consumers. But only kinda, and only for consumers.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
not related? Voice and chat.. it's only missing remote control but didn't it have that in the past? or maybe it has that today.
Voice yes, but not PBX. OpenFire does voice and chat in the same way.
Not PBX, but full typical phone system access - and that replaces the need for real PBX situations in a lot of cases (definitely not saying all/most etc).
But not in a corporate one. Specifically the PBX piece is missing. It's just an ad hoc one to one phone connection. So doesn't apply.
in that situation, you have Lync, I mean SfB.
Which is, again, not very good
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
And, I'd consider Skype a failure, not a success. It might be the best ad hoc tool out there, but it totally fails to be as good as a PBX or as an XMPP or as a federated member of a business. Skype is actually a great example of things not working. Sure it kinda works for consumers. But only kinda, and only for consumers.
Skype wasn't ever meant for large companies.. and really not even small ones.. it's meant for consumers.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
And, I'd consider Skype a failure, not a success. It might be the best ad hoc tool out there, but it totally fails to be as good as a PBX or as an XMPP or as a federated member of a business. Skype is actually a great example of things not working. Sure it kinda works for consumers. But only kinda, and only for consumers.
Skype wasn't ever meant for large companies.. and really not even small ones.. it's meant for consumers.
Yup... so do you see why it doesn't apply? It lacks the functionality that we are discussing isolating.
-
It's not that fundamentally voice and IM should be separate. It's that mashing products together in an ad hoc way is bad. OpenFire is not a part of Asterisk and does not leverage it and has no reason to be running on the same server. It's one bad idea on top of another.
If Asterisk had IM built in to it and it was part of the base product, that would be very different. But it is not.
