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.
-
@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.
-
No, I don't because I guess I don't understand what the goal of this thread is? It started out talking about Pidgen adding support to talk to Hangouts and moved onto talking about a good solution for voice/text/video. Not sure when it moved over to corporate.
Even so.. I don't see that you can have both though.. you either have to have two totally separate solutions.. one for consumer... and another for business.. even though users absolutely don't want that.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
No, I don't because I guess I don't understand what the goal of this thread is? It started out talking about Pidgen adding support to talk to Hangouts and moved onto talking about a good solution for voice/text/video. Not sure when it moved over to corporate.
It started that way. Pidgen and Hangouts are both big time corporate solutions.
-
@Dashrender said in Extending Pidgin to Support Google Hangouts:
Even so.. I don't see that you can have both though.. you either have to have two totally separate solutions.. one for consumer... and another for business.. even though users absolutely don't want that.
That's what I always advocate. Using consumer for business sucks. Only problem is, so many businesses only use consumer.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
Skype is actually a great example of things not working. Sure it kinda works for consumers. But only kinda, and only for consumers.
I don't always log into ML to read threads, but when I do, I upvote posts like this.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@Dashrender said in Extending Pidgin to Support Google Hangouts:
No, I don't because I guess I don't understand what the goal of this thread is? It started out talking about Pidgen adding support to talk to Hangouts and moved onto talking about a good solution for voice/text/video. Not sure when it moved over to corporate.
It started that way. Pidgen and Hangouts are both big time corporate solutions.
How do you figure that? Every company I've saw using consumer messaging because they are either:
*Too cheap to purchase a good solution, or...
*Do not have enough knowledge or talent to setup a good open source/free solution.Of the janky company IM setups, I've typically noticed something like 90% use Pidgeon and 10% use anything else (mostly Hangouts). It's all a janky setup, no central management, and everyone using their personal accounts. I don't see how that is big time corporate solutions.
I would think more "big time corporate" would be ANYTHING else... Whether it works or not, Lync/SfB, Telegram, Slack, OpenFire, RocketChat, etc...
-
@BBigford said in Extending Pidgin to Support Google Hangouts:
Of the janky company IM setups, I've typically noticed something like 90% use Pidgeon and 10% use anything else (mostly Hangouts). It's all a janky setup, no central management, and everyone using their personal accounts. I
Pidgin is just a client. It can easily be used in a well managed, centralized corporate environment. I've never seen it any other way.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@BBigford said in Extending Pidgin to Support Google Hangouts:
Of the janky company IM setups, I've typically noticed something like 90% use Pidgeon and 10% use anything else (mostly Hangouts). It's all a janky setup, no central management, and everyone using their personal accounts. I
Pidgin is just a client. It can easily be used in a well managed, centralized corporate environment. I've never seen it any other way.
Ah, I have saw businesses using it in a terrible way then (i.e. mostly just personal accounts). I've never deployed it. What is the backend you typically see with it?
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@BBigford said in Extending Pidgin to Support Google Hangouts:
Of the janky company IM setups, I've typically noticed something like 90% use Pidgeon and 10% use anything else (mostly Hangouts). It's all a janky setup, no central management, and everyone using their personal accounts. I
Pidgin is just a client. It can easily be used in a well managed, centralized corporate environment. I've never seen it any other way.
How does the account management work? Just curious cause I haven't saw anyone deploy Pigeon with a centralized, well managed system.
-
@BBigford said in [Extending Pidgin to Support Google Hangouts](/topic/9033/extending-pidgin-
90% use Pidgeon
Pidgin*. I forgot my spelling cap at home today. Not to be confused with the pigeon bird.
-
@BBigford said in Extending Pidgin to Support Google Hangouts:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@BBigford said in Extending Pidgin to Support Google Hangouts:
Of the janky company IM setups, I've typically noticed something like 90% use Pidgeon and 10% use anything else (mostly Hangouts). It's all a janky setup, no central management, and everyone using their personal accounts. I
Pidgin is just a client. It can easily be used in a well managed, centralized corporate environment. I've never seen it any other way.
Ah, I have saw businesses using it in a terrible way then (i.e. mostly just personal accounts). I've never deployed it. What is the backend you typically see with it?
OpenFire. But this thread is about how Hangouts is an option. You can use it with almost anything, but OpenFire would be the closest thing to a native option.
