$${div_features}
|$${div_screenshots}
|$${div_end}
|$${section_start}
|$${section_end}
|`lowdown -X name $(subst .xml,.md,$@)`
" >>$@ + echo "`$(LOWDOWN) -X name $(subst .xml,.md,$@)`
" >>$@ echo "`lowdown -X title $(subst .xml,.md,$@)`
" >>$@ + echo "`$(LOWDOWN) -X title $(subst .xml,.md,$@)`
" >>$@ echo " `lowdown -X authors $(subst .xml,.md,$@)`" >>$@ - echo " " >>$@ + echo " " >>$@ echo "- Profanity is a console based XMPP client written in C using ncurses and libstrophe, - inspired by Irssi -
- -
- Available on Linux, FreeBSD, OpenBSD, OSX, Windows and Android (Termux)
-
- Do you like Profanity?
- Consider donating!
-
- Latest release:
- profanity-${version}.tar.xz
- sha256: ${tar_xz_sha256}
-
- profanity-${version}.zip
- sha256: ${zip_sha256}
-
Documentation:
- User Guide
- FAQ
- Supported XEPs
- Plugins
- Reporting issues
- How to help out
- Blog
- Theme Gallery
-
Links:
- Github
- Mailing
- list
- Twitter
- xmpp:profanity@rooms.dismail.de
-
Features
-
- -
-
- Supports XMPP chat services -
- MUC chat room support -
- OTR, PGP and OMEMO encryption -
- Roster management -
- Flexible resource and priority settings -
- Desktop notifications -
- Plugins in Python and C -
Screenshots
--
-
- 
- 
- 
- 
- 
- 
- 
- 
-
/account](reference.html#account) command should be used to
+modify the settings below.
+
+The following is an example account configuration file with two configured
+accounts.
+
+```[jabber]
+enabled=true
+priority.online=10
+priority.chat=20
+priority.away=0
+priority.xa=0
+priority.dnd=-10
+jid=someone@jabber.org
+resource=laptop
+presence.last=xa
+presence.login=online
+muc.service=conference.jabber.org
+muc.nick=aperson
+
+[work]
+enabled=true
+priority.online=2
+priority.chat=1
+priority.away=0
+priority.xa=-5
+priority.dnd=-10
+jid=bob.smith@mycompany.org
+server=talk.mycompany.org
+resource=office
+presence.last=online
+presence.login=away
+muc.service=rooms.mycompany.org
+muc.nick=smithy
+```
+
+${section_end}
diff --git a/pagesource/accounts.xml b/pagesource/accounts.xml
deleted file mode 100644
index 13b2ec5..0000000
--- a/pagesource/accounts.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-Contents
- - -Configuring Accounts
- -The /account command should be used to modify the
- settings below.
The following is an example account configuration file with two configured accounts.
-[jabber]
-enabled=true
-priority.online=10
-priority.chat=20
-priority.away=0
-priority.xa=0
-priority.dnd=-10
-jid=someone@jabber.org
-resource=laptop
-presence.last=xa
-presence.login=online
-muc.service=conference.jabber.org
-muc.nick=aperson
-
-[work]
-enabled=true
-priority.online=2
-priority.chat=1
-priority.away=0
-priority.xa=-5
-priority.dnd=-10
-jid=bob.smith@mycompany.org
-server=talk.mycompany.org
-resource=office
-presence.last=online
-presence.login=away
-muc.service=rooms.mycompany.org
-muc.nick=smithy
-+ +There are several ways to do so: + +1. Become a sponsor on [GitHub Sponsors](https://github.com/jublah) +2. Write an email to jubalh@iodoru.org to ask for bank details +3. Send Bitcoin to: bc1qx265eat7hfasqkqmk9qf38delydnrnuvzhzy0x + +${section_end} diff --git a/pagesource/donate.xml b/pagesource/donate.xml deleted file mode 100644 index 5105a20..0000000 --- a/pagesource/donate.xml +++ /dev/null @@ -1,15 +0,0 @@ -
Donating
-Yes, the rumors are true. Developers also have to eat. They also have limited time.
-And yet some of them decide to use their free time to develop free software.
-You can help the development of Profanity and show your appreciation by donating.
- There are several ways to do so:
1. Become a sponsor on GitHub Sponsors
- 2. Write an email to jubalh@iodoru.org to ask for bank details
- 3. Send Bitcoin to: bc1qx265eat7hfasqkqmk9qf38delydnrnuvzhzy0x
eval_password property:
+```
+secret-tool lookup xmpp bob@server.org
+```
+
+On OS X, use the following command for the `eval_password` property:
+```
+security find-generic-password -s bob@server.org -w
+```
+
+You can also use Profanity together with `pass`, see this
+[guide](https://hispagatos.org/post/xmpp_profanity_and_pass)
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](multiaccount)
+#### Can I connect to more than one account at a time?
+
+No, the recommended way is to use multiple terminal windows, or a terminal
+multiplexer like GNU Screen or tmux.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](persistent)
+#### Why are my settings not persistent?
+
+Because you did not use `/save`.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](profrc)
+#### Where is the profrc file format described?
+
+Nowhere. Well, actually you cold read the source code.
+But you should not edit the profrc file yourself anyways.
+Just use the commands to manipulate the settings.
+And don't forget to `/save` before exiting.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](termf1)
+#### Why does the F1 key open terminal help rather than going back to the main console window?
+
+Some terminals have a key binding for F1 to open help. You can use the alt-num
+keys to change windows, or if you prefer to use the F keys, you'll need to
+change the terminal setting to open help with another key.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](utf8encoding)
+#### Why can I not type anything in the input bar?
+
+Profanity uses the ncursesw library to support wide characters, which requires
+a UTF-8 encoding. Try running the following (or the equivalent for your
+language's UTF-8 encoding) in the terminal before running profanity.
+```
+export LANG=en_US.UTF-8
+```
+
+######[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](mucpresence)
+#### How can I hide join/leave messages in MUCs?
+
+You can deactivate those messages with the following command:
+```
+/presence chat none
+```
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](bugs)
+#### I've found a bug/have a feature request who do I tell?
+
+If you have a github account, you can log an issue on the
+[issue tracker](https://github.com/profanity-im/profanity/issues?state=open).
+
+Alternatively you are welcome to post on the
+[mailing list](https://lists.posteo.de/listinfo/profanity).
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](contrib)
+#### I'd like to contribute, what should I do?
+
+A page has been written with some ideas for how to
+[help out](helpout.html).
+Any contributions/ideas are very welcome. Also see the
+[CONTRIBUTING.md](https://github.com/profanity-im/profanity/blob/master/CONTRIBUTING.md)
+file on GitHub.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](donate)
+#### I'd like to donate to Profanity
+
+If you want to pay the developers and maintainers of Profanity a coffee there
+are various ways to do so.
+
+On [GitHub](https://github.com/profanity-im/profanity) there is a *Sponsor*
+button linking to relevant pages. If you want to send the money directly you
+can ask for an IBAN via [email](mailto:jubalh@iodoru.org).
+
+We also got selected for GitHub Sponsors. You can find the link also on the
+*Sponsor* button on GitHub.
+
+There is also the possibility to set a bounty for certain issues via
+[Bountysource](https://www.bountysource.com/teams/profanity).
+So in case you want to see a certain feature implemented or bug fixed you can
+set a bounty there and the person doing the work gets the reward.
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](clients)
+#### Are there more clients like this?
+
+Yes, there are several commandline clients:
+[freetalk](https://www.gnu.org/software/freetalk/),
+[mcabber](https://mcabber.com/),
+[poezio](https://poez.io) and
+[more clients](https://xmpp.org/software/clients.html).
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](tor)
+#### How to connect to XMPP server using Tor
+
+To connect to the XMPP server by the Tor network, you must launch Profanity
+with a tool called "[proxychains-ng](https://github.com/rofl0r/proxychains-ng)".
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](onion)
+#### How to connect to an onion XMPP server
+
+An onion XMPP server is a server which is providing an onion address to reach it
+inside the Tor network. You can specify the onion address with the
+[`/account`](reference.html#account) command in Profanity.
+```
+/account set account_name server address.onion
+```
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](distrobox)
+#### How to run the latest version on old distributions?
+
+Some distributions, like Debian, have backports repositories. You can also run
+Profanity in a container via distrobox. See our
+[blogpost](https://profanity-im.github.io/blog/post/distrobox/).
+
+#####[back to top](top)
+
+${section_end}
+
+${section_start}
+
+[](autoopen)
+#### How do I automatically open chat windows with contacts?
+
+To the right side you can see your roster. It contains all your contacts and
+rooms (MUCs). MUCs can be automatically joined via bookmarks. If you want to
+open a chat window to a user automatically upon the start of profanity you can
+write a script to do that. Put `/msg theusersnickname` into
+`~/.local/share/profanity/scripts/myautoscript`.
+And configure your account to automatically launch that script
+`/account set <account> startscript myautoscript`.
+
+#####[back to top](top)
+
+${section_end}
diff --git a/pagesource/faq.xml b/pagesource/faq.xml
deleted file mode 100644
index d833d73..0000000
--- a/pagesource/faq.xml
+++ /dev/null
@@ -1,280 +0,0 @@
-
- Contents
--
-
-
-
-
-
- How do I connect with multiple accounts? -
- OMEMO doesn't work for me -
- Why are my settings not persistent? -
- Where is the profrc file format described? -
- Will Profanity run on <some platform>? -
- Will Profanity work with Google Talk? -
- Will Profanity work with Facebook Chat? -
- Will Profanity work with Slack? -
- Will Profanity work with MSN/Yahoo/AIM/IRC etc? -
- Can Profanity use my keychain/keyring to retrieve my password? -
- Can I connect to more than one account at a time? -
- Why does the F1 key open terminal help rather than going back to the main - console window? -
- Why can I not type anything in the input bar? -
- How can I hide join/leave messages in MUCs? -
- I've found a bug/have a feature request, who do I tell? -
- I'd like to contribute, what should I do? -
- I'd like to donate to Profanity -
- Are there more clients like this? -
- How to connect to XMPP server using Tor -
- How to connect to an onion XMPP server -
- How to run the latest version on old distributions? -
- How do I automatically open chat windows with contacts? -
-
How do I connect with multiple accounts?
-Profanity only supports one account per instance. But you certainly can run several instances of Profanity! Run Profanity in multiple terminals or use a terminal multiplexer like screen or tmux. An example setup can be seen in this blogpost. -
- -back to top
- -OMEMO doesn't work for me
-OMEMO support was added in 0.7.0. Version 0.11.1 fixed a lot of common bugs. But please make sure to run the latest version of Profanity.
-A common error is that the PEP nodes are wrongly configured. It could be that your server isn't configured the right way or that some client configured - this the wrong way in the past. Profanity tries to correct this but might fail. See issue 1538 for details.
- -back to top
- -Will Profanity run on <some platform>?
-Profanity should run on any POSIX system, see the install guide for specifics. -
- -back to top
- -Will Profanity work with Google Talk?
-Profanity was able to work with Google Talk. But in 2013 after Google merged it's messenger products - Google Talk, Google+ Messenger and Hangouts together XMPP support was dropped. -
- -back to top
- -Will Profanity work with Facebook Chat?
-Facebook have recently announced that they will no longer support the open XMPP chat protocol, so - Profanity will no longer work with Facebook Chat.
- -back to top
- -Will Profanity work with Slack?
-Provided the XMPP gateway has been enabled for your team, Profanity will work. See the - Slack page on gateways.
- -back to top
- -Will Profanity work with MSN/Yahoo/AIM/IRC etc?
-No, Profanity is purely an XMPP chat client.
- -back to top
- -Can Profanity use my keychain/keyring to retrieve my password?
-Yes, the /account command includes an
- eval_password property which can be used to execute a script to retrieve your password.
For example on Ubuntu using gnome-keyring and secret-tool:
To add the password:
-secret-tool store --label="Bobs account" xmpp bob@server.orgYou will be prompted to enter the password.
-Command to use for the account eval_password property:
secret-tool lookup xmpp bob@server.orgOn OS X, use the following command for the eval_password property:
security find-generic-password -s bob@server.org -wYou can also use Profanity together with pass, see this guide
back to top
- -Can I connect to more than one account at a time?
-No, the recommended way is to use multiple terminal windows, or a terminal multiplexer like GNU Screen or - tmux.
- -back to top
- -Why are my settings not persistent?
-Because you did not use /save.
back to top
- -Where is the profrc file format described?
-Nowhere. Well, actually you cold read the source code.
- But you should not edit the profrc file yourself anyways. Just use the commands to manipulate the settings.
- And don't forget to /save before exiting.
back to top
- -Why does the F1 key open terminal help rather than going back to the main console window?
-Some terminals have a key binding for F1 to open help. You can use the alt-num keys to change windows, or - if you prefer to use the F keys, you'll need to change the terminal setting to open help with another - key.
- -back to top
- -Why can I not type anything in the input bar?
-Profanity uses the ncursesw library to support wide characters, which requires a UTF-8 encoding. Try - running the following (or the equivalent for your language's UTF-8 encoding) in the terminal before - running profanity.
-export LANG=en_US.UTF-8back to top
- -How can I hide join/leave messages in MUCs?
-You can deactivate those messages with the following command: -
/presence chat noneback to top
- -I've found a bug/have a feature request who do I tell?
-If you have a github account, you can log an issue on the issue - tracker.
-Alternatively you are welcome to post on the mailing - list.
- -back to top
- -I'd like to contribute, what should I do?
-A page has been written with some ideas for how to help out. - Any contributions/ideas are very welcome. Also see the CONTRIBUTING.md - file on GitHub.
- -back to top
- -I'd like to donate to Profanity
-If you want to pay the developers and maintainers of Profanity a coffee there are various ways to do so. -
-On GitHub there is a Sponsor button - linking to relevant pages. If you want to send the money directly you can ask for an IBAN via email.
-We also got selected for GitHub Sponsors. You can find the link also on the Sponsor button on - GitHub.
-There is also the possibility to set a bounty for certain issues via Bountysource. So in case you want to see a - certain feature implemented or bug fixed you can set a bounty there and the person doing the work gets - the reward.
- -back to top
- -Are there more clients like this?
-Yes, there are several commandline clients: freetalk, mcabber, poezio and more clients.
- -back to top
- -How to connect to XMPP server using Tor
-To connect to the XMPP server by the Tor network, you must launch Profanity with a tool called "proxychains-ng". -
- -back to top
- -How to connect to an onion XMPP server
-An onion XMPP server is a server which is providing an onion address to reach it inside the Tor network.
- You can specify the onion address with the /account command in Profanity.
/account set account_name server address.onionback to top
- -How to run the latest version on old distributions?
-Some distributions, like Debian, have backports repositories. You can also run Profanity in a container via distrobox. See our blogpost
- -back to top
- -How do I automatically open chat windows with contacts?
-To the right side you can see your roster. It contains all your contacts and
- rooms (MUCs). MUCs can be automatically joined via bookmarks. If you want to
- open a chat window to a user automatically upon the start of profanity you can
- write a script to do that. Put
- /msg theusersnickname
- into
- ~/.local/share/profanity/scripts/myautoscript.
- And configure your account to automatically launch that script
- /account set <account> startscript myautoscript.
-
back to top
- -Contents
- - -Use Profanity
- -The easiest way you can help out is just by using Profanity and sending any feedback you have to the mailing list. - Any feedback is welcome, although please keep it polite, and refrain from using profanity (pun intended).
-See Reporting issues for information on where and how to report issues, and how to supply logs/debug information.
-Help with the website
- -The website often has small errors or omissions in documentation etc. The website source is also available at github so feel free to send pull requests there.
-We're always interested to hear about profanity being used in different environments, and if you have any screenshots, we'd be happy to post them at the website.
-Contribute code
- -Code contributions are always very welcome. From the small (spelling fixes) to the large (new XMPP features).
-If you would like to get involved, you can submit a pull request, or if you just want to get involved but don't know how, email jubalh@iodoru.org.
-Also make sure to read the CONTRIBUTING document on GitHub.
-To find a first issue to work on check out the various repositories:
- -Click on the tab called Issues in the repository on GitHub and go through them until you find something that interests you.
-We also tag our issues. So you can easily see if something is a bug or a feature request. Or which part of the code the issue is about, like e.g. UI.
-Especially check out the issues tagged as help wanted.
-You can also check out the milestones where we plan which issues should be solved for certain milestones/releases. The milestone called next contains the issues for the next release.
-People find it often the easiest to work on a bug that affects them personally. Or to implement a feature that they want to have. So think about what you want and need. You can also join our MUC to get help about getting started with development on Profanity
-Donate
- -Yes, the rumors are true. Developers also have to eat. They also have limited time.
-And yet some of them decide to use their free time to develop free software.
-If you want to say "Thank You", please consider donating.
-Contents
- - -Where to report issues
- -The best place to report issues is at the github issue tracker.
-Other options are the mailing list,
-The following would be helpful in diagnosing/reproducing the issue if you can possibly supply it: - environment (OS, OS version, window manager, terminal type), profanity release version or commit hash if - from development, XMPP server and/or recipient's XMPP client if the issue only occurs with certain - servers/clients, finally any information about the build configuration and enabled features.
-If you cant supply the above information, a simple description will do.
-Attaching logs
- -The logs can often help to diagnose an issue. Firstly run Profanity in debug mode to enable full debug - logging:
-profanity -l DEBUGThen recreate the issue and attach the log (or a useful section of it) found in:
-$XDG_DATA_HOME/profanity/logs/profanity.logWhich on most systems is:
-~/.local/share/profanity/logs/profanity.logRemember to remove or obfuscate any private information in the logs. In particular check for credentials - in connection logging. For example the auth mechanism PLAIN sends the credentials as a base64 string - which can be easily reversed to get your username and password, e.g.:
-12/12/2014 14:22:01: conn: DBG: SENT: <auth mechanism="PLAIN" xmlns="urn:ietf:params:xml:ns:xmpp-sasl">AG9saXZlci5tdWVoc2FtAE5oYTEyMDhnIw==</auth>Attaching configuration files
-Some issues are only reproducible using certain configuration options, so attaching your config can also - help. Profanity stores its core config in:
-$XDG_CONFIG_HOME/profanity/profrcWhich on most systems is:
-~/.config/profanity/profrcAccount specific configuration is specified in:
-$XDG_DATA_HOME/profanity/accountsWhich on most systems is:
-~/.local/share/profanity/accountsRemember to remove or obfuscate any usernames/passwords from the configuration before sending, for - example, account configuration will include your password if you have set one using the /account command.
-Getting a backtrace
- -Segfaults and crashes usually result in a coredump which can be useful in debugging the problem. If you - have the time, the following instructions should help when attaching a backtrace from a crash.
- - -Enabling coredumps
-The following command will enable coredumps of unlimited size to be generated in the current terminal - session:
-ulimit -c unlimitedIf you prefer to set a limit, the argument is in Kilobytes, for example to allow coredumps of up to - 100MB:
-ulimit -c 102400Add the command to your ~/.bashrc or equivalent to enable coredumps for all terminal
- sessions.
- -
Rebuild in debug mode
-Profanity needs to be rebuilt from source to enable more useful information in the coredump.
-In the source folder (where you extracted the download, or checked out from git) run the following:
-./bootstrap.sh
-./configure-debug # calls ./configure with debug options
-make clean
-makeThis will only build an executable in the source folder and will not overwrite your system installed - version. To run the newly built version, in the source folder run:
-./profanityNote, if you installed from Homebrew on OSX it is recommended to clone and build from github (checking - out the relevant release tag) using the above steps, unless you are happy with editing and reinstalling - brew formula.
- -- -
Viewing the backtrace
-On Linux, you will need the GDB debugger installed for your distribution.
-The coredump will be created in the folder in which you built and ran profanity, firstly start GDB - pointing to profanity and the coredump:
-gdb ./profanity coreTo view the backtrace in GDB:
-btOn OSX, the coredump can be found somewhere in the system console (usually in - Applications->Utilities->Console in the finder). It should be named with "profanity" and the date and - time of the crash.
- -Contents
- -Overview
-- Profanity supports plugins written in Python and C. The profanity-plugins project - contains various plugins maintained by Profanity's author and other community maintained plugins. -
-- The master branch of the plugins repository is in synch with development in the master branch of - Profanity. Branching is used to maintain plugins for releases of Profanity: -
-| Profanity 0.5.0 | -https://github.com/profanity-im/profanity-plugins/tree/0.5.0 | -
| Profanity 0.5.1 to 0.6.0 | -https://github.com/profanity-im/profanity-plugins/tree/0.5.1 | -
- There is a known issue - that C plugins do not currently work on Cygwin. -
-- To install a Python plugin: -
-/plugins install ~/projects-git/profanity-plugins/say.py
- Any module dependencies for the plugin should be on the Python system path. If a plugin imports modules
- relative to its location, these modules need to manually be copied to
- ~/.local/share/profanity/plugins/
-
- To install a C plugin: -
-/plugins install ~/projects-git/profanity-plugins/pid/pid.so
- See the /plugins command for more information on
- installing and enabling/disabling plugins.
-
- If a plugin registers it's own commands, the usual /help
- command can be used to find out more information:
-
/help sayFeatured Plugins
-- This section list some of the plugins currently available. -
-ascii.py |
- Convert text to ascii art text and send to the current recipient or room. | -
browser.py |
- Open received links in the system default browser. | -
clients.py |
- Show client software used by each occupant in the current chat room, using xep-0092 Software - Version. | -
imgur.py |
- Send a local image file or a screenshot to a recipient or chat room using imgur.com. | -
paste.py |
- Send the contents of the clipboard to the current recipient or room. | -
termuxnotify.py |
- Notifications for Termux on Android. - See also notifycmd.py for a generic version to run any system
- command on new messages. |
-
presence_notify.py |
- Configure desktop notifications for presence updates from contacts. | -
say.py |
- Read out loud messages from recipients or in chat rooms. | -
sounds.py |
- Play sounds when messages received. | -
syscmd.py |
- Display the result shell commands in a new window. - Send results of shell commands to recipients or chat rooms. |
-
wikipedia-prof.py |
- Search wikipedia and show search results, pages, links etc in a new window. | -
Developing Plugins
-- Profanity provides an API for plugins to access various functionality. Plugins may also implement - 'hooks' that Profanity will call on specific events. -
- -Python
-
- Python plugins need to import the prof module to access the API.
-
- Profanity may be compiled against Python 2 or Python 3, so plugins should be able to work with both, the - future library can be used in most - cases. -
-
- Full documentation of the prof module and the hooks a plugin may implement can be found
- at:
-
- 0.5.1 to 0.6.0 Python API documentation -
-
- Previous versions:
- 0.5.0
-
C
-
- C plugins need to include the profapi.h header to access the API, and must be linked
- against libprofanity using the linker flag -lprofanity.
-
- C plugins should include a Makefile to build a shared library (a .so file)
- which is the file Profanity will load.
-
- Full documentation of the profapi.h header and the hooks a plugin may implement can be
- found at:
-
- 0.5.1 to 0.6.0 C API documentation -
-
- Previous versions:
- 0.5.0
-
Themes and Settings
-- Plugins may make use of themes and settings by accessing the following files: -
-~/.local/share/profanity/plugin_themes
-~/.local/share/profanity/plugin_settings- Example theme properties for syscmd.py: -
-[system]
-command=cyan
-result=green- Example settings for say.py: -
-[say]
-args=-v english -s 120
-enabled=active- API functions are available to read and write to the settings and theme files. -
-- Plugins should contain documentation on the available settings and colours, most plugins have a command - to manipulate settings. -
-Contributing Plugins
-- Submit a pull request to the profanity-plugins project. -
-- If the current API doesn't have what you need, raise an issue at the Profanity repository. -
-Userguides
--
-
- For latest development version -
- For version 0.17.0 -
- For version 0.16.0 -
- For version 0.15.0 -
- For version 0.14.X -
- For version 0.13.1 -
- For version 0.13.0 -
- For version 0.12.X -
- For version 0.11.1 -
- For version 0.11.0 -
- For version 0.10.X -
- For version 0.9.X -
- For version 0.8.X -
- For version 0.7.X -
No multi-step yet. | +| [XEP-0060: Publish-Subscribe](https://xmpp.org/extensions/xep-0060.html) | 1.15.8 | Since 0.7.0.
Used for OMEMO. | +| [XEP-0077: In-Band Registration](https://xmpp.org/extensions/xep-0077.html) | 2.4 | Since 0.11.0.
Only password change. | +| [XEP-0085: Chat State Notifications](https://xmpp.org/extensions/xep-0085.html) | 2.1 | | +| [XEP-0091: Legacy Delayed Delivery](https://xmpp.org/extensions/xep-0091.html) | 1.4 | | +| [XEP-0092: Software Version](https://xmpp.org/extensions/xep-0092.html) | 1.1 | | +| [XEP-0115: Entity Capabilities](https://xmpp.org/extensions/xep-0115.html) | | | +| [XEP-0157: Contact Addresses for XMPP Services](https://xmpp.org/extensions/xep-0157.html) | 1.1.1 | Since 0.11.0. | +| [XEP-0160: Best Practices for Handling Offline Messages](https://xmpp.org/extensions/xep-0160.html) | 1.0.1 | | +| [XEP-0184: Message Delivery Receipts](https://xmpp.org/extensions/xep-0184.html) | 1.2 | | +| [XEP-0191: Blocking Command](https://xmpp.org/extensions/xep-0191.html) | 1.3 | | +| [XEP-0199: XMPP Ping](https://xmpp.org/extensions/xep-0199.html) | 2.0.1 | | +| [XEP-0203: Delayed Delivery](https://xmpp.org/extensions/xep-0203.html) | 2.0 | | +| [XEP-0245: The /me Command](https://xmpp.org/extensions/xep-0245.html) | 1.0 | | +| [XEP-0249: Direct MUC Invitations](https://xmpp.org/extensions/xep-0249.html) | 1.0 | | +| [XEP-0256: Last Activity in Presence](https://xmpp.org/extensions/xep-0256.html) | 1.1 | | +| [XEP-0280: Message Carbons](https://xmpp.org/extensions/xep-0280.html) | 0.12.1 | | +| [XEP-0308: Last Message Correction](https://xmpp.org/extensions/xep-0308.html) | 1.2.0 | Since 0.9.0. | +| [XEP-0359: Unique and Stable Stanza IDs](https://xmpp.org/extensions/xep-0359.html) | 0.6.1 | Since 0.8.0.
Only </origin-id>,
no </stanza-id> yet.| +| [XEP-0363: HTTP File Upload](https://xmpp.org/extensions/xep-0363.html) | 1.0.0 | | +| [XEP-0364: Current Off-the-Record Messaging Usage](https://xmpp.org/extensions/xep-0364.html) | 0.3.2 | | +| [XEP-0374: OpenPGP for XMPP Instant Messaging](https://xmpp.org/extensions/xep-0374.html) | 0.2.0 | Since 0.11.0. | +| [XEP-0377: Spam Reporting](https://xmpp.org/extensions/xep-0377.html) | 0.3 | Since 0.11.0. | +| [XEP-0384: OMEMO Encryption](https://xmpp.org/extensions/xep-0384.html) | 0.3.0 | Since 0.7.0. | +| [XEP-0392: Consistent Color Generation](https://xmpp.org/extensions/xep-0392.html) | 0.7.0 | Since 0.8.0. | +| [XEP-0454: OMEMO Media sharing](https://xmpp.org/extensions/xep-0454.html) | 0.1.0 | Since 0.10.0. | + +${section_end} diff --git a/pagesource/xeps.xml b/pagesource/xeps.xml deleted file mode 100644 index 7118ae6..0000000 --- a/pagesource/xeps.xml +++ /dev/null @@ -1,175 +0,0 @@ - - -
| XEP | -Supported Version | -Notes | - - -
|---|---|---|
| XEP-0012: Last Activity | -2.0 | -- |
| XEP-0027: Current Jabber OpenPGP Usage | -1.4 | -- |
| XEP-0030: Service Discovery | -- | - |
| XEP-0045: Multi-User Chat | -- | - |
| XEP-0048: Bookmarks | -1.2 | -- |
| XEP-0050: Ad-Hoc Commands | -1.3.0 | -Since 0.6.0. No multi-step yet. | -
| XEP-0060: Publish-Subscribe | -1.15.8 | -Since 0.7.0. Used for OMEMO. | -
| XEP-0077: In-Band Registration | -2.4 | -Since 0.11.0. Only password change. | -
| XEP-0085: Chat State Notifications | -2.1 | -- |
| XEP-0091: Legacy Delayed Delivery | -1.4 | -- |
| XEP-0092: Software Version | -1.1 | -- |
| XEP-0115: Entity Capabilities | -- | - |
| XEP-0157: Contact Addresses for XMPP Services | -1.1.1 | -Since 0.11.0. | -
| XEP-0160: Best Practices for Handling Offline Messages | -1.0.1 | -- |
| XEP-0184: Message Delivery Receipts | -1.2 | -- |
| XEP-0191: Blocking Command | -1.3 | -- |
| XEP-0199: XMPP Ping - | -2.0.1 | -- |
| XEP-0203: Delayed Delivery | -2.0 | -- |
| XEP-0245: The /me Command | -1.0 | -- |
| XEP-0249: Direct MUC Invitations | -1.0 | -- |
| XEP-0256: Last Activity in Presence | -1.1 | -- |
| XEP-0280: Message Carbons | -0.12.1 | -- |
| XEP-0308: Last Message Correction | -1.2.0 | -Since 0.9.0. | -
| XEP-0359: Unique and Stable Stanza IDs | -0.6.1 | -Since 0.8.0. Only </origin-id>, no </stanza-id> yet. | -
| XEP-0363: HTTP File Upload | -1.0.0 | -- |
| XEP-0364: Current Off-the-Record Messaging Usage | -0.3.2 | -- |
| XEP-0374: OpenPGP for XMPP Instant Messaging | -0.2.0 | -Since 0.11.0. | -
| XEP-0377: Spam Reporting | -0.3 | -Since 0.11.0. | -
| XEP-0384: OMEMO Encryption | -0.3.0 | -Since 0.7.0. | -
| XEP-0392: Consistent Color Generation | -0.7.0 | -Since 0.8.0. | -
| XEP-0454: OMEMO Media sharing | -0.1.0 | -Since 0.10.0. | -