Merge help-weights to default
--- a/hugo/content/help/bonjour.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,11 +0,0 @@
----
-title: "Bonjour"
-date: 2019-08-07T18:20:21-04:00----
-Bonjour is a serverless messaging protocol developed by Apple, Inc. ([Apple article on Bonjour](http://www.apple.com/macosx/technology/bonjour.html)) based on XMPP that operates only on a local network. [This XMPP extension](http://xmpp.org/extensions/xep-0174.html) defines the protocol.-### Can I use Windows Pidgin for Bonjour?-Yes. You must install Apple's [Bonjour Print Services for Windows](http://support.apple.com/kb/DL999) to use this functionality.--- a/hugo/content/help/contactus.md Thu Aug 08 00:03:25 2019 -0400
+++ b/hugo/content/help/contactus.md Tue Aug 20 21:44:03 2019 -0400
@@ -2,6 +2,7 @@
date: 2019-05-19T14:33:54-04:00
If you'd like to contact the Pidgin team, please take a look at our [Community](/community) page for resources that will be helpful to you!
\ No newline at end of file
--- a/hugo/content/help/gadugadu.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
----
-title: "Gadu-Gadu"
-date: 2019-06-11T19:59:34-04:00----
-Gadu-Gadu is an IM protocl popular in Poland. You can find more about it [here](http://www.gadu-gadu.pl) (website in Polish).-### I compiled Pidgin from source. Why doesn't it have Gadu-Gadu support?-We use an external libgadu. Install your distro's `libgadu-dev` (Debian-based systems) or `libgadu-devel` (RPM systems) and rebuild Pidgin (making sure to re-run `./configure` in the top of the source tree).--- a/hugo/content/help/groupwise.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,14 +0,0 @@
----
-title: "GroupWise"
-date: 2019-08-07T22:08:46-04:00----
-GroupWise is a messaging and collaboration platform originally developed by WordPerfect Corporation and later acquired by Novell but now owned by [Micro Focus](https://www.microfocus.com/en-us/products/groupwise/overview). (see [this Wikipedia article](https://en.wikipedia.org/wiki/GroupWise) for details). The Groupwise protocol within Pidgin specifically supports the instant messaging portion of the GroupWise platform. Much of Pidgin's support for the GroupWise Messenger service was generously provided by Novell several years ago.-### Are there any public servers?-No. This protocol is designed to connect with a GroupWise Messenger server running on a corporate LAN. There are no known public servers.-### I can't get it to work.-We are told this protocol plugin works only with the GroupWise Messenger for Linux server or the GroupWise Messenger SP2 (or later) server running on NetWare or Windows, and then only if the server is secure (SSL/TLS-enabled).--- a/hugo/content/help/irc.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,53 +0,0 @@
----
-title: "IRC"
-date: 2019-06-04T00:12:17-04:00----
-### How do I join a channel?-Create an IRC account and sign into it. After you've signed on, you can use the _Buddies_ -> _Join a Chat_ menu option on the Buddy List window to join a channel. In any window, either a conversation or a chat, in which your IRC user is the sender, you can also use the `/join` command to connect to a new channel.-### Can I hide messages from NickServ, ChanServ, etc. on login?-### How do I automatically authenticate or identify on login?-Try the [irchelper](https://bitbucket.org/pidgin/purple-plugin-pack/src/default/irchelper/) plugin from the [Purple Plugin Pack](https://bitbucket.org/pidgin/purple-plugin-pack/). This plugin provides fields to enter the services bot's nickname and your services password. It also automatically suppresses messages from the services bots sent on connection. Note that this plugin _does_, in fact, work with Q on Quakenet, and networks that use AuthServ, not just networks that use NickServ.-Alternatively, see the next question for a way using Pidgin's built in features.-### How do I authenticate/identify with a buddy pounce or send a message to a user on login?- * Create (if necessary) and enable your IRC account.- * Add the nick of the services bot to your buddy list using _Buddies_ -> _Add Buddy_.- * Right-click the new buddy and click "Add Buddy Pounce" to create a new pounce.- * Make sure "Signs on" is the only checked box in the "Pounce When Buddy..." section.- * Make sure "Send a message" is checked under "Action".- * Enter the message, such as `identify mypassword` if you're trying to authenticate.- * Ensure "Recurring" is checked beneath "Options" or the pounce will only work once.- * Click "Save" to save the pounce.-Note that you do **_NOT_** include `/msg nickname` as part of the message in the pounce.-### Can I automatically join channels on login?-Absolutely. In the Buddy List window, select _Buddies_ -> _Add Chat_. Use this dialog to add the chat to your buddy list. Once the chat appears in the buddy list, right-click the chat and select "Auto-Join". The channel will autojoin whenever you sign onto your IRC account.-### Is it possible to change the username that appears in username@hostname?-In the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_. Click the "Advanced" tab. Enter a name in the Username field.-### How can I set/change my real name?-In the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_. Click the "Advanced" tab. Enter a name in the Real Name field.-### Why does text display incorrectly?-IRC has no comprehension of character sets or encodings. It simply sends (almost) any random chunk of data a user enters. Pidgin by default assumes everything is UTF-8. If this is not the case, you will need to edit your account (in the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_) and change the Encoding setting on the "Advance"d" tab. You will need to enter the correct encoding for your channels there. You can specify multiple encodings in a comma-delimited list, such as `UTF-8,ISO-8859-15`, to cause Pidgin to attempt multiple encodings. In this case, each encoding is tried in succession until a successful decode happens or all encodings listed are exhausted.-### How can I hide join/part messages?-In the Buddy List window, select _Tools_ -> _Plugins_. Find and checkmark "Join/Part Hiding" and click the "Configure Plugin" button. Configure the plugin as you like.--- a/hugo/content/help/otherprotocols.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,20 +0,0 @@
----
-title: "Other Protocols"
-date: 2019-08-07T22:06:02-04:00----
-### Pidgin used to support MXit, Yahoo! Messenger, AIM, and ICQ. What gives?-MXit and AIM no longer exist. MXit as a company no longer exists and their website is gone. AOL terminated AIM in December 2017.-Yahoo! Messenger and ICQ changed protocols and Pidgin doesn't have the developer resources to support these protocols ourselves. See the [Plugins](/plugins/) page for community-maintained plugins for these and other services.-### What happened to Facebook Chat support?-Facebook terminated their XMPP support in April 2014. Pidgin doesn't have the developer resources to support an alternative implenetation ourselves. See the [Plugins](/plugins/) page for community-maintained plugins for this and other services.-### Why doesn't Pidgin support CyanChat, Microsoft LCS/Skype for Business, Skype, NateOn, NetSoul, etc.?-It is an incredible amount of work to implement and maintain support for a protocol. Pidgin's developers are volunteers who work on Pidgin in their spare time. As spare time is a limited resource, Pidgin's developers can maintain only a limited number of protocols.-If you are willing and able to implement and maintain a plugin for a protocol that you use, we welcome and encourage you to do so! The beauty of Pidgin and libpurple is its plugin system, allowing anyone to enhance and extend Pidgin.-You can find community-supported (third-party) plugins on our [Plugins page](/plugins/).--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/_index.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,8 @@
+title: "Services (Protocols)" +date: 2019-08-08T00:43:03-04:00 +This group of pages houses Service-specific questions. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/bonjour.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,12 @@
+date: 2019-08-07T18:20:21-04:00 +Bonjour is a serverless messaging protocol developed by Apple, Inc. ([Apple article on Bonjour](http://www.apple.com/macosx/technology/bonjour.html)) based on XMPP that operates only on a local network. [This XMPP extension](http://xmpp.org/extensions/xep-0174.html) defines the protocol. +### Can I use Windows Pidgin for Bonjour? +Yes. You must install Apple's [Bonjour Print Services for Windows](http://support.apple.com/kb/DL999) to use this functionality. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/gadugadu.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,13 @@
+date: 2019-06-11T19:59:34-04:00 +Gadu-Gadu is an IM protocl popular in Poland. You can find more about it [here](http://www.gadu-gadu.pl) (website in Polish). +### I compiled Pidgin from source. Why doesn't it have Gadu-Gadu support? +We use an external libgadu. Install your distro's `libgadu-dev` (Debian-based systems) or `libgadu-devel` (RPM systems) and rebuild Pidgin (making sure to re-run `./configure` in the top of the source tree). --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/groupwise.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,15 @@
+date: 2019-08-07T22:08:46-04:00 +GroupWise is a messaging and collaboration platform originally developed by WordPerfect Corporation and later acquired by Novell but now owned by [Micro Focus](https://www.microfocus.com/en-us/products/groupwise/overview). (see [this Wikipedia article](https://en.wikipedia.org/wiki/GroupWise) for details). The Groupwise protocol within Pidgin specifically supports the instant messaging portion of the GroupWise platform. Much of Pidgin's support for the GroupWise Messenger service was generously provided by Novell several years ago. +### Are there any public servers? +No. This protocol is designed to connect with a GroupWise Messenger server running on a corporate LAN. There are no known public servers. +### I can't get it to work. +We are told this protocol plugin works only with the GroupWise Messenger for Linux server or the GroupWise Messenger SP2 (or later) server running on NetWare or Windows, and then only if the server is secure (SSL/TLS-enabled). --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/irc.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,54 @@
+date: 2019-06-04T00:12:17-04:00 +### How do I join a channel? +Create an IRC account and sign into it. After you've signed on, you can use the _Buddies_ -> _Join a Chat_ menu option on the Buddy List window to join a channel. In any window, either a conversation or a chat, in which your IRC user is the sender, you can also use the `/join` command to connect to a new channel. +### Can I hide messages from NickServ, ChanServ, etc. on login? +### How do I automatically authenticate or identify on login? +Try the [irchelper](https://bitbucket.org/pidgin/purple-plugin-pack/src/default/irchelper/) plugin from the [Purple Plugin Pack](https://bitbucket.org/pidgin/purple-plugin-pack/). This plugin provides fields to enter the services bot's nickname and your services password. It also automatically suppresses messages from the services bots sent on connection. Note that this plugin _does_, in fact, work with Q on Quakenet, and networks that use AuthServ, not just networks that use NickServ. +Alternatively, see the next question for a way using Pidgin's built in features. +### How do I authenticate/identify with a buddy pounce or send a message to a user on login? + * Create (if necessary) and enable your IRC account. + * Add the nick of the services bot to your buddy list using _Buddies_ -> _Add Buddy_. + * Right-click the new buddy and click "Add Buddy Pounce" to create a new pounce. + * Make sure "Signs on" is the only checked box in the "Pounce When Buddy..." section. + * Make sure "Send a message" is checked under "Action". + * Enter the message, such as `identify mypassword` if you're trying to authenticate. + * Ensure "Recurring" is checked beneath "Options" or the pounce will only work once. + * Click "Save" to save the pounce. +Note that you do **_NOT_** include `/msg nickname` as part of the message in the pounce. +### Can I automatically join channels on login? +Absolutely. In the Buddy List window, select _Buddies_ -> _Add Chat_. Use this dialog to add the chat to your buddy list. Once the chat appears in the buddy list, right-click the chat and select "Auto-Join". The channel will autojoin whenever you sign onto your IRC account. +### Is it possible to change the username that appears in username@hostname? +In the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_. Click the "Advanced" tab. Enter a name in the Username field. +### How can I set/change my real name? +In the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_. Click the "Advanced" tab. Enter a name in the Real Name field. +### Why does text display incorrectly? +IRC has no comprehension of character sets or encodings. It simply sends (almost) any random chunk of data a user enters. Pidgin by default assumes everything is UTF-8. If this is not the case, you will need to edit your account (in the Buddy List window, select _Accounts_ -> your IRC account -> _Edit Account_) and change the Encoding setting on the "Advance"d" tab. You will need to enter the correct encoding for your channels there. You can specify multiple encodings in a comma-delimited list, such as `UTF-8,ISO-8859-15`, to cause Pidgin to attempt multiple encodings. In this case, each encoding is tried in succession until a successful decode happens or all encodings listed are exhausted. +### How can I hide join/part messages? +In the Buddy List window, select _Tools_ -> _Plugins_. Find and checkmark "Join/Part Hiding" and click the "Configure Plugin" button. Configure the plugin as you like. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/otherprotocols.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,21 @@
+title: "Other Protocols" +date: 2019-08-07T22:06:02-04:00 +### Pidgin used to support MXit, Yahoo! Messenger, AIM, and ICQ. What gives? +MXit and AIM no longer exist. MXit as a company no longer exists and their website is gone. AOL terminated AIM in December 2017. +Yahoo! Messenger and ICQ changed protocols and Pidgin doesn't have the developer resources to support these protocols ourselves. See the [Plugins](/plugins/) page for community-maintained plugins for these and other services. +### What happened to Facebook Chat support? +Facebook terminated their XMPP support in April 2014. Pidgin doesn't have the developer resources to support an alternative implenetation ourselves. See the [Plugins](/plugins/) page for community-maintained plugins for this and other services. +### Why doesn't Pidgin support CyanChat, Microsoft LCS/Skype for Business, Skype, NateOn, NetSoul, etc.? +It is an incredible amount of work to implement and maintain support for a protocol. Pidgin's developers are volunteers who work on Pidgin in their spare time. As spare time is a limited resource, Pidgin's developers can maintain only a limited number of protocols. +If you are willing and able to implement and maintain a plugin for a protocol that you use, we welcome and encourage you to do so! The beauty of Pidgin and libpurple is its plugin system, allowing anyone to enhance and extend Pidgin. +You can find community-supported (third-party) plugins on our [Plugins page](/plugins/). --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/sametime.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,15 @@
+date: 2019-08-07T18:30:15-04:00 +### Are there any public Sametime servers? +Apart from a demonstration server hosted by Lotus/IBM, no. This protocol is designed to connect to a Lotus/IBM Sametime server running on a corporate LAN. +### Why doesn't Sametime appear in the protocols list? +Sametime support in Pidgin depends on a separate library called Meanwhile. You will need to install the Meanwhile library and the `libpurple-meanwhile` (or similar, depending on distribution) package to enable Sametime support. If you are building Pidgin from source, then `libpurple-meanwhile` will be built automatically if you have the development headers for Meanwhile installed. +### Why do I get the error "Not Authorized" when connecting? +The Sametime server to which you're attempting to connect has been configured with a whitelist of acceptable clients. This error indicates that the client ID used by Pidgin (`0x1700`) is apparently not in that whitelist, so the server denies your login. You can cause Pidgin to masquerade as the default Sametime Connect client by setting the "Hide client identity" option in your account preferences. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/silc.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,15 @@
+date: 2019-06-17T23:14:46-04:00 +SILC is an open, security-focused end-to-end encrypted protocol. Its website is currently hosted at [silc.github.io](https://silc.github.io). +### What do I need to use the SILC protocol? +You need to install the SILC Toolkit and the libpurple SILC plugin. These were generally provided as packages in several Linux distributions, however, many distributions have begun dropping these packages due to being "unmaintained." If you're compiling Pidgin and libpurple yourself, see the `./configure --help` for specifying the location of the SILC headers and libraries. If you're compiling with an SRPM, use `--with-silc` to build the `purple-silc` RPM +On Windows, the SILC Toolkit is installed with Pidgin. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/xmpp/_index.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,155 @@
+date: 2019-06-04T00:16:51-04:00 +### What is the difference between Jabber and XMPP? +Jabber and XMPP are the same protocol. The only difference is that Jabber is a trademarked name and XMPP is the official name of the protocol. +### Does Pidgin support Nimbuzz, Web.de Messenger, GMX Messenger, or 1&1 Messenger? +Yes; they are simply services that use the XMPP protocol. +### How do I choose which XMPP server to use or configure an XMPP account? +The XMPP server is part of your XMPP ID. For example, in the ID `foo@bar.com`, `bar.com` would be the server to use. When entering your XMPP account information into Pidgin, specify everything _before_ the `@` (in the example, this would be `foo`) in the Username field and everything _after_ the `@` (in the example, this would be `bar.com`) in the Domain field. +### What is the "Resource" field for in the account editor? +The resource field specifies the XMPP resource you are using. The use of unique resources allows you to connect to your XMPP server from multiple locations simultaneously. Resources migfht have meaningful names, such as Home, Work, Mobile, etc. or something else entirely that you choose. Pidgin defaults to a blank resource, as most servers will assign one if the client doesn't specify. +### How do I change my resource string? +Go to _Accounts_ -> _Add/Edit_. Uncheck the "Enabled" box for your XMPP account. Then select the account and click the "Modify" button. Change the string in the Resource field, or put something there if it's blank. +### How can I configure resource priority? +Libpurple does not currently support user-configurable priorities. We have a static priority list that's used: +### How do I use Pidgin with MeiVZ/StudiVZ's chat box? +These services use XMPP. Create an XMPP account using the e-mail address you log in with, but replace the "at sign" (`@`) with `\40`. Set the Domain to `vz.net`. You won't need to change anything on the Advanced tab. +## XMPP Buddies (Contacts) +### How can I deauthorize a buddy from seeing my status? +Right-click the buddy in the Buddy List and select "Cancel Presence Notification". Note that the buddy will have to request authorization again to be able to see your presence. +### What does "Cancel Presence Notification" do? +See the previous question. +### What does "Unsubscribe" do? +If you select this, you will no longer see that buddy's presence. That means you will not see their online or offline status or if they're away, extended away, idle, etc. If you select this option and later change your mind, you must re-request authorization to resume seeing the buddy's presence. +## Multi-User Conferences (Chat Rooms) +### How do I create a conference? +There are two ways to do this. One is by joining the conference and the other is by adding it to your Buddy List. +#### Join the conference +1. In the Buddy List window, select _Buddies_ -> _Join A Chat_. +1. Select your XMPP account. +1. Fill in the fields you see. + 1. **Room** should be the short name fo the conference, for example, "myconference". + 1. **Server** is the server on which the conference will be created. It must be a MUC server, such as `conference.jabber.org`. The chat's ID will be Room@Server, so the example "myconference" would have the ID "myconference@..." + 1. **Handle** is the name you wish to be displayed in the chat. It is similar in concept to a nickname on IRC. +1. You will see a dialog asking you about creating the new room. You can either accept the default configuration or configure to your liking, at your option. +#### Add the conference to your roster (buddy list) +1. In the Buddy List window, select _Buddies_ -> _Add Chat_. +1. Select your XMPP account. +1. Fill in the fields you see. + 1. **Room** should be the short name fo the conference, for example, "myconference". + 1. **Server** is the server on which the conference will be created. It must be a MUC server, such as `conference.jabber.org`. The chat's ID will be Room@Server, so the example "myconference" would have the ID "myconference@..." + 1. **Handle** is the name you wish to be displayed in the chat. It is similar in concept to a nickname on IRC. + 1. **Password** is optional for creating a new room. You probably don't want to fill this field in. + 1. **Alias** is the alias (display name) you wish to assign to the chat. By assigning an alias, you can display a useful description in the buddy list instead of the chat's name. + 1. **Group** is the group in your buddy list (roster) in which you wish the chat to appear. +1. Find the chat in your Buddy List and double-click it. +1. You will see a dialog asking you about creating the new room. You can either accept the default configuration or configure to your liking, at your option. +### How do I invite someone to a conference? +In the chat's tab, select _Conversation_ -> _Invite_. Note that you can only invite people to a conversation that is already a chat/conference--you can't "promote" a one-on-one conversation to a multi-user chat. +### Why can't I send a file? +There are a number of possible reasons for this. +* If the user you're trying to send to is using the old Google Talk client, it isn't possible, as that client doesn't use the standard XMPP file transfer mechanisms. +* The XMPP server you're using may not support a file transfer proxy and your network doesn't allow direct incoming connections. In this case, you may be able to specify an alternative file transfer proxy in the "Advanced" settings of your XMPP account. +* The file transfer proxy in use may be broken. (See [Ticket 5840](https://developer.pidgin.im/ticket/5840).) +### Does Pidgin support Service Discovery or Transports? +Service discovery and transport _registration_ are supported in Pidgin using the XMPP Service Discovery plugin. +If a transport has already been registered in another client, or does not require registration, Pidgin also supports this. +If you want to use a protocol that Pidgin and libpurple natively support, we recommend using Pidgin's own implementation instead of an XMPP transport. +### Why do I get a "Server does not use any supported authentication method" error? +If you get this error, have a look in your debug log (_Help_ -> _Debug Window_ in the Buddy List window) to see if you also get the error message `sasl: sasl_state is -1, failing the mech and trying again`. If you are getting this, a possible workaround is to try adding your hostname (from `/etc/hostname`) to your `/etc/hosts` as an alias for `127.0.0.1` then trying to reconnect. +### Why do I get a "Not authorized" error after turning on two-factor authentication? +If you get this error, you might need to allow "less secure apps" to connect via [this Google page](https://www.google.com/settings/security/lesssecureapps) or set an app password for Pidgin via [this Google page](https://security.google.com/settings/security/apppassowrds). +### I'm using Google Apps with a non-Google e-mail address. How can I use this with Pidgin? +You can't. This is a server-side restriction. +Using Google Talk with a non-Google e-mail address (that is, an e-mail account that doesn't live on a Google server) is not a good idea because these accounts appear to other users as `<some terrible number>@talk.google.com` rather than using something someone could remember. +### How do I configure Pidgin to connect to Google Talk for my domain hosted on GSuite (Google Apps)? +Put your username (the part before the `@` in your e-mail address) in the "Username" field and your domain (the part after the `@` in your e-mail address) in the Domain field. Enter your password in the Password field. This should be all that's needed unless two-factor authentication is enabled. +If this doesn't work, it is likely because your domain doesn't have the appropriate DNS SRV records set up, or your local DNS doesn't handle SRV records. See the next question for more information. +If you are unable to fix the NDS settings, as a workaround you can specify `talk.google.com` in the "Connect Server" field on the account's "Advanced" tab. Note that you may get SSL/TLS certificate warnings if you do this. +See [Google's help page](https://www.google.com/support/a/bin/answer.py?hl=en&answer=49147) for more information. +### What are these DNS SRV records you talk about? +DNS SRV records are special entries in the domain name system that allow clients such as Pidgin to find specific services. In the case of XMPP and Google Talk, these records specify what servers on the Internet provide the XMPP service for a given domain. +Many home routers, especially older ones, are broken and can't handle the SRV record lookups required for Pidgin to automatically determine the server to which to connect. If this is the case, in the debug log (on the Buddy List window, _Help_ -> _Debug Window_), you will see `dnssrv: found 0 SRV entries`. You can confirm this by running `dig +short SRV __xmpp-client._tcp.<server>` on Linux or `nslookup -type=SRV _xmpp-client._tcp.<server>` on Windows, where `<server>` is the domain, such as `gmail.com`. If these commands return no results, then you will need to reconfigure the router to not act as the DNS server for the client computers. Typically, this setting is labeled something along the lines of "Use Router as DNS server" (this should be disabled) in the router's configuration. +If you are using OpenWRT, you can fix this by editing `/etc/dnsmasq.conf` and commenting out the following line by adding a `#` in front of it: `filterwin2k`. OpenWRT 10.03.1 "Backfire" needs dnsmasq's "Domain Needed" option to be disabled. In LuCI, this can be found under _Network_ -> _DHCP_ and _DNS_ -> _General_ -> _Domain Required_ (unchecked). From the command line, remove the following option from the `dnsmasq` section in `/etc/config/dhcp`. +If your GSuite (Google Apps for Your Domain) domain does not have SRV records, add [the following entries](http://support.google.com/a/bin/answer.py?hl=en&answer=34143): + _xmpp-server._tcp.yourdomain.com. IN SRV 5 0 5269 xmpp-server.l.google.com. + _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt1.xmpp-server.l.google.com. + _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt2.xmpp-server.l.google.com. + _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt3.xmpp-server.l.google.com. + _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt4.xmpp-server.l.google.com. +How you do this will differ depending on your your DNS server or provider works. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/xmpp/supportedxep.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,62 @@
+title: "Supported XEP's" +date: 2019-06-11T19:06:50-04:00 +This is an attempt to document the various XMPP Extensions +([XEP's](https://xmpp.org/extensions/)) supported by XMPP protocol plugin in +libpurple. Please note that this list is **_incomplete_** and that libpurple +almost certainly supports more XEP's than are listed here! +| XEP | Feature Name | Status | Notes | +|------------------|--------------|--------|-------| +| {{% xep 0004 %}} | Data Forms | Final | Since at least 2.4.1 | +| {{% xep 0012 %}} | Last Activity | Final | | +| {{% xep 0020 %}} | Feature Negotiation | Draft | (for file transfers) | +| {{% xep 0022 %}} | Message Events | Obsolete | Superseded by {{% xep 0085 %}}, support updated. | +| {{% xep 0030 %}} | Service Discovery | Final | (no UI implementation in Finch) | +| {{% xep 0038 %}} | Icon Styles | Deferred | For smileys. Standard seems abandoned? Last revised 2003. | +| {{% xep 0045 %}} | Multi-User Chat | Draft | | +| {{% xep 0047 %}} | In-band Bytestreams (IBB) | Final | Since 2.6.0 | +| {{% xep 0050 %}} | Ad-Hoc Commands | Draft | | +| {{% xep 0054 %}} | vcard-temp | Active (Historical) | | +| {{% xep 0055 %}} | Jabber Search | Active (Historical) | | +| {{% xep 0060 %}} | Publish-Subscribe | Draft | (partial/minimal support, used for PEP) | +| {{% xep 0065 %}} | SOCKS5 Bytestreams | Draft | | +| {{% xep 0066 %}} | Out of Band Data | Draft | | +| {{% xep 0071 %}} | XHTML-IM | Draft | | +| {{% xep 0077 %}} | In-Band Registration | Final | | +| {{% xep 0084 %}} | User Avatar | Draft | v1.1 | +| {{% xep 0085 %}} | Chat State Notifications | Final | | +| {{% xep 0091 %}} | Legacy Delayed Delivery | Obsolete | Deprecated in favour of {{% xep 203 %}}. Still around. | +| {{% xep 0092 %}} | Software Version | Draft | | +| {{% xep 0095 %}} | Stream Initiation | Draft | | +| {{% xep 0096 %}} | SI File Transfer | Draft | (SOCKS5 bytestreams, IBB) | +| {{% xep 0100 %}} | Gateway Interaction | Active | minimal support in Pidgin/Finch | +| {{% xep 0107 %}} | User Mood | Draft | | +| {{% xep 0115 %}} | Entity Capabilities | Draft | v1.5 since 2.6.0 | +| {{% xep 0118 %}} | User Tune | Draft | | +| {{% xep 0124 %}} | Bidirectional-streams Over Synchronous HTTP (BOSH) | Draft | Since 2.6.0 | +| {{% xep 0146 %}} | Remote Controlling Clients | Active | Since 2.2.1 | +| {{% xep 0153 %}} | vCard-Based Avatars | Active (Historical) | | +| {{% xep 0156 %}} | Discovering Alternate XMPP Connection Methods | Draft | partial support since 2.6.0 (for BOSH) | +| {{% xep 0163 %}} | Personal Eventing Protocol | Draft | | +| {{% xep 0166 %}} | Jingle | Draft | Since 2.6.0 | +| {{% xep 0167 %}} | Jingle RTP Sessions | Draft | Since 2.6.0 when compiled with voice and video support | +| {{% xep 0172 %}} | User Nickname | Draft | | +| {{% xep 0174 %}} | Serverless Messaging | Final | (via the Bonjour prpl) | +| {{% xep 0176 %}} | Jingle ICE-UDP Transport Method | Draft | Since 2.6.0 when compiled with voice and video support | +| {{% xep 0177 %}} | Jingle Raw-UDP Transport Method | Draft | Since 2.6.0 when compiled with voice and video support | +| {{% xep 0191 %}} | Simple Communications Blocking | Draft | Since 2.5.4 | +| {{% xep 0199 %}} | XMPP Ping | Final | | +| {{% xep 0202 %}} | Entity Time | Final | | +| {{% xep 0203 %}} | Delayed Delivery | Final | Since 2.2.1 | +| {{% xep 0206 %}} | XMPP Over BOSH | Draft | Since 2.6.0 | +| {{% xep 0224 %}} | Attention | Draft | Started life as a Pidgin "buzz" extension in 2007, now an XEP :-) | +| {{% xep 0231 %}} | Bits of Binary | Draft | Since 2.5.2, used for custom emoticons. | +| {{% xep 0232 %}} | Software Information | Deferred | Intended to replace {{% xep 0092 %}} using {{% xep 0115 %}} | +| {{% xep 0237 %}} | Roster Versioning | Obsolete | Since 2.6.5. XEP now part of [RFC-4621](http://tools.ietf.org/html/rfc6121) | +| {{% xep 0245 %}} | The /me Command | Active | Since forever. | +| {{% xep 0249 %}} | Direct MUC Invitations | Draft | Support added in 2.6.4 | +| {{% xep 0256 %}} | Last Activity in Presence | Draft | Since 2.6.0 | +| {{% xep 0264 %}} | Jingle Content Thumbnails | Experimental | Thumbnails disabled in XMPP since 2.7.2 until it gets Draft status. | --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/hugo/content/help/protocols/zephyr.md Tue Aug 20 21:44:03 2019 -0400
@@ -0,0 +1,30 @@
+date: 2019-08-07T18:47:42-04:00 +Zephyr is an IM protocol developed at MIT for use with Project Athena. Its features include Kerberos 4 authentication and multi-level chats (aka "subscriptions"). You're probably using this because your college/employer/organization uses it as a local IM/chat system. If not, you probably don't have a server to connect to. +### Other Zephyr clients (zwgc, owl, tzc) work, but Pidgin dies with "Couldn't initialize zephyr" +Your site might require the use of Kerberos 4 for authentication, though few prepackaged Pidgin binaries use Kerberos. One solution is to compile Pidgin with the `--with-krb4` flag to point to the location of your Kerberos 4 devel files, usually one of `/usr`, `/usr/local`, or `/usr/athena`, e.g. `./configure --with-krb4=/path/to/kerberos4` +### Pidgin isn't working, but I never got any other Zephyr client working +You need to have zhm (which comes with the standard Zephyr distribution) installed, and running, and pointed at your Zephyr servers. e.g. `zhm z1.example.com z2.example.com z3.example.com` +Alternatively, there might be a firewall or a NAT between you and the Zephyr servers. Zephyr generally doesn't work in an environment where incoming connections cannot be made to arbitrary UDP ports. +### How do I avoid compiling Pidgin with Kerberos 4 support? +See the next question; the same trick for firewall traversal applies to avoiding building with Kerberos support. +### How do I use Zephyr from behind my firewall? +You can use tzc ("Trivial Zephyr Client") and ssh to run Zephyr from a machine that is behind a firewall or NAT. First, make sure that tzc is installed and working on the remote machine. The best version of tzc to use can be found [here](http://www.club.cc.cmu.edu/debian/dists/testing/contrib/source/tzc-cclub_001-3.tar.gz). +Make sure that you can make a passwordless ssh connection to the remote machine and get Kerberos 4 tickets. Then, click the Advanced tab in the account editor, enable "Use tzc", and set the tzc command to `/path/to/ssh username@hostname /path/to/tzc -e "%s"` +Alternately, if you have tzc working on your machine, you can enable "Use tzc", and set the tzc command to `/path/to/tzc -e "%s"` +### Why can't I use Zephyr on Windows? +Pidgin does not support Zephyr on Windows due to upstream technical limitations. The current libzephyr library does not compile on the Windows platform and there are no known usable builds of "zhm" available for Windows. If you are a Windows user, you most likely do not have any use for Zephyr anyway. --- a/hugo/content/help/sametime.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,14 +0,0 @@
----
-title: "Sametime"
-date: 2019-08-07T18:30:15-04:00----
-### Are there any public Sametime servers?-Apart from a demonstration server hosted by Lotus/IBM, no. This protocol is designed to connect to a Lotus/IBM Sametime server running on a corporate LAN.-### Why doesn't Sametime appear in the protocols list?-Sametime support in Pidgin depends on a separate library called Meanwhile. You will need to install the Meanwhile library and the `libpurple-meanwhile` (or similar, depending on distribution) package to enable Sametime support. If you are building Pidgin from source, then `libpurple-meanwhile` will be built automatically if you have the development headers for Meanwhile installed.-### Why do I get the error "Not Authorized" when connecting?-The Sametime server to which you're attempting to connect has been configured with a whitelist of acceptable clients. This error indicates that the client ID used by Pidgin (`0x1700`) is apparently not in that whitelist, so the server denies your login. You can cause Pidgin to masquerade as the default Sametime Connect client by setting the "Hide client identity" option in your account preferences.--- a/hugo/content/help/silc.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,14 +0,0 @@
----
-title: "SILC"
-date: 2019-06-17T23:14:46-04:00----
-SILC is an open, security-focused end-to-end encrypted protocol. Its website is currently hosted at [silc.github.io](https://silc.github.io).-### What do I need to use the SILC protocol?-You need to install the SILC Toolkit and the libpurple SILC plugin. These were generally provided as packages in several Linux distributions, however, many distributions have begun dropping these packages due to being "unmaintained." If you're compiling Pidgin and libpurple yourself, see the `./configure --help` for specifying the location of the SILC headers and libraries. If you're compiling with an SRPM, use `--with-silc` to build the `purple-silc` RPM-On Windows, the SILC Toolkit is installed with Pidgin.--- a/hugo/content/help/windows.md Thu Aug 08 00:03:25 2019 -0400
+++ b/hugo/content/help/windows.md Tue Aug 20 21:44:03 2019 -0400
@@ -1,6 +1,7 @@
title: "Windows-Specific Questions"
date: 2019-05-19T13:47:02-04:00
### Can I manually install spell-checking support?
--- a/hugo/content/help/xmpp/_index.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,154 +0,0 @@
----
-title: "XMPP (Jabber)"
-date: 2019-06-04T00:16:51-04:00----
-### What is the difference between Jabber and XMPP?-Jabber and XMPP are the same protocol. The only difference is that Jabber is a trademarked name and XMPP is the official name of the protocol.-### Does Pidgin support Nimbuzz, Web.de Messenger, GMX Messenger, or 1&1 Messenger?-Yes; they are simply services that use the XMPP protocol.-### How do I choose which XMPP server to use or configure an XMPP account?-The XMPP server is part of your XMPP ID. For example, in the ID `foo@bar.com`, `bar.com` would be the server to use. When entering your XMPP account information into Pidgin, specify everything _before_ the `@` (in the example, this would be `foo`) in the Username field and everything _after_ the `@` (in the example, this would be `bar.com`) in the Domain field.-### What is the "Resource" field for in the account editor?-The resource field specifies the XMPP resource you are using. The use of unique resources allows you to connect to your XMPP server from multiple locations simultaneously. Resources migfht have meaningful names, such as Home, Work, Mobile, etc. or something else entirely that you choose. Pidgin defaults to a blank resource, as most servers will assign one if the client doesn't specify.-### How do I change my resource string?-Go to _Accounts_ -> _Add/Edit_. Uncheck the "Enabled" box for your XMPP account. Then select the account and click the "Modify" button. Change the string in the Resource field, or put something there if it's blank.-### How can I configure resource priority?-Libpurple does not currently support user-configurable priorities. We have a static priority list that's used:-### How do I use Pidgin with MeiVZ/StudiVZ's chat box?-These services use XMPP. Create an XMPP account using the e-mail address you log in with, but replace the "at sign" (`@`) with `\40`. Set the Domain to `vz.net`. You won't need to change anything on the Advanced tab.-## XMPP Buddies (Contacts)-### How can I deauthorize a buddy from seeing my status?-Right-click the buddy in the Buddy List and select "Cancel Presence Notification". Note that the buddy will have to request authorization again to be able to see your presence.-### What does "Cancel Presence Notification" do?-See the previous question.-### What does "Unsubscribe" do?-If you select this, you will no longer see that buddy's presence. That means you will not see their online or offline status or if they're away, extended away, idle, etc. If you select this option and later change your mind, you must re-request authorization to resume seeing the buddy's presence.-## Multi-User Conferences (Chat Rooms)-### How do I create a conference?-There are two ways to do this. One is by joining the conference and the other is by adding it to your Buddy List.-#### Join the conference-1. In the Buddy List window, select _Buddies_ -> _Join A Chat_.-1. Select your XMPP account.-1. Fill in the fields you see.- 1. **Room** should be the short name fo the conference, for example, "myconference".- 1. **Server** is the server on which the conference will be created. It must be a MUC server, such as `conference.jabber.org`. The chat's ID will be Room@Server, so the example "myconference" would have the ID "myconference@..."- 1. **Handle** is the name you wish to be displayed in the chat. It is similar in concept to a nickname on IRC.-1. You will see a dialog asking you about creating the new room. You can either accept the default configuration or configure to your liking, at your option.-#### Add the conference to your roster (buddy list)-1. In the Buddy List window, select _Buddies_ -> _Add Chat_.-1. Select your XMPP account.-1. Fill in the fields you see.- 1. **Room** should be the short name fo the conference, for example, "myconference".- 1. **Server** is the server on which the conference will be created. It must be a MUC server, such as `conference.jabber.org`. The chat's ID will be Room@Server, so the example "myconference" would have the ID "myconference@..."- 1. **Handle** is the name you wish to be displayed in the chat. It is similar in concept to a nickname on IRC.- 1. **Password** is optional for creating a new room. You probably don't want to fill this field in.- 1. **Alias** is the alias (display name) you wish to assign to the chat. By assigning an alias, you can display a useful description in the buddy list instead of the chat's name.- 1. **Group** is the group in your buddy list (roster) in which you wish the chat to appear.-1. Find the chat in your Buddy List and double-click it.-1. You will see a dialog asking you about creating the new room. You can either accept the default configuration or configure to your liking, at your option.-### How do I invite someone to a conference?-In the chat's tab, select _Conversation_ -> _Invite_. Note that you can only invite people to a conversation that is already a chat/conference--you can't "promote" a one-on-one conversation to a multi-user chat.-### Why can't I send a file?-There are a number of possible reasons for this.-* If the user you're trying to send to is using the old Google Talk client, it isn't possible, as that client doesn't use the standard XMPP file transfer mechanisms.-* The XMPP server you're using may not support a file transfer proxy and your network doesn't allow direct incoming connections. In this case, you may be able to specify an alternative file transfer proxy in the "Advanced" settings of your XMPP account.-* The file transfer proxy in use may be broken. (See [Ticket 5840](https://developer.pidgin.im/ticket/5840).)-### Does Pidgin support Service Discovery or Transports?-Service discovery and transport _registration_ are supported in Pidgin using the XMPP Service Discovery plugin.-If a transport has already been registered in another client, or does not require registration, Pidgin also supports this.-If you want to use a protocol that Pidgin and libpurple natively support, we recommend using Pidgin's own implementation instead of an XMPP transport.-### Why do I get a "Server does not use any supported authentication method" error?-If you get this error, have a look in your debug log (_Help_ -> _Debug Window_ in the Buddy List window) to see if you also get the error message `sasl: sasl_state is -1, failing the mech and trying again`. If you are getting this, a possible workaround is to try adding your hostname (from `/etc/hostname`) to your `/etc/hosts` as an alias for `127.0.0.1` then trying to reconnect.-### Why do I get a "Not authorized" error after turning on two-factor authentication?-If you get this error, you might need to allow "less secure apps" to connect via [this Google page](https://www.google.com/settings/security/lesssecureapps) or set an app password for Pidgin via [this Google page](https://security.google.com/settings/security/apppassowrds).-### I'm using Google Apps with a non-Google e-mail address. How can I use this with Pidgin?-You can't. This is a server-side restriction.-Using Google Talk with a non-Google e-mail address (that is, an e-mail account that doesn't live on a Google server) is not a good idea because these accounts appear to other users as `<some terrible number>@talk.google.com` rather than using something someone could remember.-### How do I configure Pidgin to connect to Google Talk for my domain hosted on GSuite (Google Apps)?-Put your username (the part before the `@` in your e-mail address) in the "Username" field and your domain (the part after the `@` in your e-mail address) in the Domain field. Enter your password in the Password field. This should be all that's needed unless two-factor authentication is enabled.-If this doesn't work, it is likely because your domain doesn't have the appropriate DNS SRV records set up, or your local DNS doesn't handle SRV records. See the next question for more information.-If you are unable to fix the NDS settings, as a workaround you can specify `talk.google.com` in the "Connect Server" field on the account's "Advanced" tab. Note that you may get SSL/TLS certificate warnings if you do this.-See [Google's help page](https://www.google.com/support/a/bin/answer.py?hl=en&answer=49147) for more information.-### What are these DNS SRV records you talk about?-DNS SRV records are special entries in the domain name system that allow clients such as Pidgin to find specific services. In the case of XMPP and Google Talk, these records specify what servers on the Internet provide the XMPP service for a given domain.-Many home routers, especially older ones, are broken and can't handle the SRV record lookups required for Pidgin to automatically determine the server to which to connect. If this is the case, in the debug log (on the Buddy List window, _Help_ -> _Debug Window_), you will see `dnssrv: found 0 SRV entries`. You can confirm this by running `dig +short SRV __xmpp-client._tcp.<server>` on Linux or `nslookup -type=SRV _xmpp-client._tcp.<server>` on Windows, where `<server>` is the domain, such as `gmail.com`. If these commands return no results, then you will need to reconfigure the router to not act as the DNS server for the client computers. Typically, this setting is labeled something along the lines of "Use Router as DNS server" (this should be disabled) in the router's configuration.-If you are using OpenWRT, you can fix this by editing `/etc/dnsmasq.conf` and commenting out the following line by adding a `#` in front of it: `filterwin2k`. OpenWRT 10.03.1 "Backfire" needs dnsmasq's "Domain Needed" option to be disabled. In LuCI, this can be found under _Network_ -> _DHCP_ and _DNS_ -> _General_ -> _Domain Required_ (unchecked). From the command line, remove the following option from the `dnsmasq` section in `/etc/config/dhcp`.-If your GSuite (Google Apps for Your Domain) domain does not have SRV records, add [the following entries](http://support.google.com/a/bin/answer.py?hl=en&answer=34143):- _xmpp-server._tcp.yourdomain.com. IN SRV 5 0 5269 xmpp-server.l.google.com.- _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt1.xmpp-server.l.google.com.- _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt2.xmpp-server.l.google.com.- _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt3.xmpp-server.l.google.com.- _xmpp-server._tcp.yourdomain.com. IN SRV 20 0 5269 alt4.xmpp-server.l.google.com.-How you do this will differ depending on your your DNS server or provider works.--- a/hugo/content/help/xmpp/supportedxep.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,62 +0,0 @@
----
-title: "Supported XEP's"
-date: 2019-06-11T19:06:50-04:00----
-This is an attempt to document the various XMPP Extensions-([XEP's](https://xmpp.org/extensions/)) supported by XMPP protocol plugin in-libpurple. Please note that this list is **_incomplete_** and that libpurple-almost certainly supports more XEP's than are listed here!-| XEP | Feature Name | Status | Notes |-|------------------|--------------|--------|-------|-| {{% xep 0004 %}} | Data Forms | Final | Since at least 2.4.1 |-| {{% xep 0012 %}} | Last Activity | Final | |-| {{% xep 0020 %}} | Feature Negotiation | Draft | (for file transfers) |-| {{% xep 0022 %}} | Message Events | Obsolete | Superseded by {{% xep 0085 %}}, support updated. |-| {{% xep 0030 %}} | Service Discovery | Final | (no UI implementation in Finch) |-| {{% xep 0038 %}} | Icon Styles | Deferred | For smileys. Standard seems abandoned? Last revised 2003. |-| {{% xep 0045 %}} | Multi-User Chat | Draft | |-| {{% xep 0047 %}} | In-band Bytestreams (IBB) | Final | Since 2.6.0 |-| {{% xep 0050 %}} | Ad-Hoc Commands | Draft | |-| {{% xep 0054 %}} | vcard-temp | Active (Historical) | |-| {{% xep 0055 %}} | Jabber Search | Active (Historical) | |-| {{% xep 0060 %}} | Publish-Subscribe | Draft | (partial/minimal support, used for PEP) |-| {{% xep 0065 %}} | SOCKS5 Bytestreams | Draft | |-| {{% xep 0066 %}} | Out of Band Data | Draft | |-| {{% xep 0071 %}} | XHTML-IM | Draft | |-| {{% xep 0077 %}} | In-Band Registration | Final | |-| {{% xep 0084 %}} | User Avatar | Draft | v1.1 |-| {{% xep 0085 %}} | Chat State Notifications | Final | |-| {{% xep 0091 %}} | Legacy Delayed Delivery | Obsolete | Deprecated in favour of {{% xep 203 %}}. Still around. |-| {{% xep 0092 %}} | Software Version | Draft | |-| {{% xep 0095 %}} | Stream Initiation | Draft | |-| {{% xep 0096 %}} | SI File Transfer | Draft | (SOCKS5 bytestreams, IBB) |-| {{% xep 0100 %}} | Gateway Interaction | Active | minimal support in Pidgin/Finch |-| {{% xep 0107 %}} | User Mood | Draft | |-| {{% xep 0115 %}} | Entity Capabilities | Draft | v1.5 since 2.6.0 |-| {{% xep 0118 %}} | User Tune | Draft | |-| {{% xep 0124 %}} | Bidirectional-streams Over Synchronous HTTP (BOSH) | Draft | Since 2.6.0 |-| {{% xep 0146 %}} | Remote Controlling Clients | Active | Since 2.2.1 |-| {{% xep 0153 %}} | vCard-Based Avatars | Active (Historical) | |-| {{% xep 0156 %}} | Discovering Alternate XMPP Connection Methods | Draft | partial support since 2.6.0 (for BOSH) |-| {{% xep 0163 %}} | Personal Eventing Protocol | Draft | |-| {{% xep 0166 %}} | Jingle | Draft | Since 2.6.0 |-| {{% xep 0167 %}} | Jingle RTP Sessions | Draft | Since 2.6.0 when compiled with voice and video support |-| {{% xep 0172 %}} | User Nickname | Draft | |-| {{% xep 0174 %}} | Serverless Messaging | Final | (via the Bonjour prpl) |-| {{% xep 0176 %}} | Jingle ICE-UDP Transport Method | Draft | Since 2.6.0 when compiled with voice and video support |-| {{% xep 0177 %}} | Jingle Raw-UDP Transport Method | Draft | Since 2.6.0 when compiled with voice and video support |-| {{% xep 0191 %}} | Simple Communications Blocking | Draft | Since 2.5.4 |-| {{% xep 0199 %}} | XMPP Ping | Final | |-| {{% xep 0202 %}} | Entity Time | Final | |-| {{% xep 0203 %}} | Delayed Delivery | Final | Since 2.2.1 |-| {{% xep 0206 %}} | XMPP Over BOSH | Draft | Since 2.6.0 |-| {{% xep 0224 %}} | Attention | Draft | Started life as a Pidgin "buzz" extension in 2007, now an XEP :-) |-| {{% xep 0231 %}} | Bits of Binary | Draft | Since 2.5.2, used for custom emoticons. |-| {{% xep 0232 %}} | Software Information | Deferred | Intended to replace {{% xep 0092 %}} using {{% xep 0115 %}} |-| {{% xep 0237 %}} | Roster Versioning | Obsolete | Since 2.6.5. XEP now part of [RFC-4621](http://tools.ietf.org/html/rfc6121) |-| {{% xep 0245 %}} | The /me Command | Active | Since forever. |-| {{% xep 0249 %}} | Direct MUC Invitations | Draft | Support added in 2.6.4 |-| {{% xep 0256 %}} | Last Activity in Presence | Draft | Since 2.6.0 |-| {{% xep 0264 %}} | Jingle Content Thumbnails | Experimental | Thumbnails disabled in XMPP since 2.7.2 until it gets Draft status. |--- a/hugo/content/help/zephyr.md Thu Aug 08 00:03:25 2019 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,29 +0,0 @@
----
-title: "Zephyr"
-date: 2019-08-07T18:47:42-04:00----
-Zephyr is an IM protocol developed at MIT for use with Project Athena. Its features include Kerberos 4 authentication and multi-level chats (aka "subscriptions"). You're probably using this because your college/employer/organization uses it as a local IM/chat system. If not, you probably don't have a server to connect to.-### Other Zephyr clients (zwgc, owl, tzc) work, but Pidgin dies with "Couldn't initialize zephyr"-Your site might require the use of Kerberos 4 for authentication, though few prepackaged Pidgin binaries use Kerberos. One solution is to compile Pidgin with the `--with-krb4` flag to point to the location of your Kerberos 4 devel files, usually one of `/usr`, `/usr/local`, or `/usr/athena`, e.g. `./configure --with-krb4=/path/to/kerberos4`-### Pidgin isn't working, but I never got any other Zephyr client working-You need to have zhm (which comes with the standard Zephyr distribution) installed, and running, and pointed at your Zephyr servers. e.g. `zhm z1.example.com z2.example.com z3.example.com`-Alternatively, there might be a firewall or a NAT between you and the Zephyr servers. Zephyr generally doesn't work in an environment where incoming connections cannot be made to arbitrary UDP ports.-### How do I avoid compiling Pidgin with Kerberos 4 support?-See the next question; the same trick for firewall traversal applies to avoiding building with Kerberos support.-### How do I use Zephyr from behind my firewall?-You can use tzc ("Trivial Zephyr Client") and ssh to run Zephyr from a machine that is behind a firewall or NAT. First, make sure that tzc is installed and working on the remote machine. The best version of tzc to use can be found [here](http://www.club.cc.cmu.edu/debian/dists/testing/contrib/source/tzc-cclub_001-3.tar.gz).-Make sure that you can make a passwordless ssh connection to the remote machine and get Kerberos 4 tickets. Then, click the Advanced tab in the account editor, enable "Use tzc", and set the tzc command to `/path/to/ssh username@hostname /path/to/tzc -e "%s"`-Alternately, if you have tzc working on your machine, you can enable "Use tzc", and set the tzc command to `/path/to/tzc -e "%s"`-### Why can't I use Zephyr on Windows?-Pidgin does not support Zephyr on Windows due to upstream technical limitations. The current libzephyr library does not compile on the Windows platform and there are no known usable builds of "zhm" available for Windows. If you are a Windows user, you most likely do not have any use for Zephyr anyway.
