@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.