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.
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.
-
@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.
How does the account management work? Just curious cause I haven't saw anyone deploy Pigeon with a centralized, well managed system.
However you want depending on the back end. OpenFire will just tie in to Active Directory, if you want, or LDAP. Or it will run its own database.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@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.
How does the account management work? Just curious cause I haven't saw anyone deploy Pigeon with a centralized, well managed system.
However you want depending on the back end. OpenFire will just tie in to Active Directory, if you want, or LDAP. Or it will run its own database.
I know Spark as a client for OpenFire is popular, but that only works with Windows/Mac/Linux... Everywhere I've setup OpenFire I've only ever had it done internal since Spark isn't available for mobile. Since Pidgin is available on Android and iOS... Could you point it external?
-
@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:
@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.
However you want depending on the back end. OpenFire will just tie in to Active Directory, if you want, or LDAP. Or it will run its own database.
I know Spark as a client for OpenFire is popular, but that only works with Windows/Mac/Linux... Everywhere I've setup OpenFire I've only ever had it done internal since Spark isn't available for mobile. Since Pidgin is available on Android and iOS... Could you point it external?
OpenFire is just an XMPP server. Spark, Pidgin and others are just XMPP clients. They are all generic. it's all just XMPP.
-
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@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:
@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.
However you want depending on the back end. OpenFire will just tie in to Active Directory, if you want, or LDAP. Or it will run its own database.
I know Spark as a client for OpenFire is popular, but that only works with Windows/Mac/Linux... Everywhere I've setup OpenFire I've only ever had it done internal since Spark isn't available for mobile. Since Pidgin is available on Android and iOS... Could you point it external?
OpenFire is just an XMPP server. Spark, Pidgin and others are just XMPP clients. They are all generic. it's all just XMPP.
Can OF be configured to point externally then? I haven't tried it on mobile but I figure with some DNS entries and a firewall rule, I don't see why not...
-
@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:
@scottalanmiller said in Extending Pidgin to Support Google Hangouts:
@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.
How does the account management work? Just curious cause I haven't saw anyone deploy Pigeon with a centralized, well managed system.
However you want depending on the back end. OpenFire will just tie in to Active Directory, if you want, or LDAP. Or it will run its own database.
I know Spark as a client for OpenFire is popular, but that only works with Windows/Mac/Linux... Everywhere I've setup OpenFire I've only ever had it done internal since Spark isn't available for mobile. Since Pidgin is available on Android and iOS... Could you point it external?
OpenFire is just an XMPP server. Spark, Pidgin and others are just XMPP clients. They are all generic. it's all just XMPP.
Can OF be configured to point externally then? I haven't tried it on mobile but I figure with some DNS entries and a firewall rule, I don't see why not...
Of course, XMPP is just a web protocol, just like HTTP. You just expose it and done. XMPP is XML, just like HTML. That's how 99% of deployments work. Think about Google Chat, that's XMPP.
