c9b154b1a2
archive_is is <stanza-id> or <result id=""> and should identify one message stable and uniquely. See XEP-0359: Unique and Stable Stanza IDs. We need this for example for this situation: * we go online with Profanity * we fetch all messages since yesterday * we add them to the db * we go offline * we go online with Profanity * we fetch all messages since yesterday * we only want to add the new ones So far we don't ask MAM "give me all since last 'id'" but since a certain date. In case no archive_id will be set, it will be `(null)` and thus should be inserted anyways because it won't find a value with (null) in that row. Because when adding we use `message->stanzaid ? message->stanzaid : "",` so it will be empty in such a case. Regards MAM: https://github.com/profanity-im/profanity/issues/660 Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207 |
||
|---|---|---|
| .builds | ||
| .github | ||
| apidocs | ||
| docs | ||
| icons | ||
| src | ||
| tests | ||
| themes | ||
| .clang-format | ||
| .gitignore | ||
| .travis.yml | ||
| bootstrap.sh | ||
| Brewfile.travis | ||
| CHANGELOG | ||
| ci-build.sh | ||
| configure-debug | ||
| configure-plugins | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| Dockerfile.arch | ||
| Dockerfile.debian | ||
| Dockerfile.fedora | ||
| Dockerfile.tumbleweed | ||
| Dockerfile.ubuntu | ||
| LICENSE.txt | ||
| Makefile.am | ||
| prof.supp | ||
| profanity.spec | ||
| profrc.example | ||
| README.md | ||
| RELEASE_GUIDE.md | ||
| SPONSORS.md | ||
| theme_template | ||
Profanity
Profanity is a console based XMPP client inspired by Irssi.
If you like Profanity consider becoming a sponsor or donate some money.
See the User Guide for information on installing and using Profanity.
Project
This project is about freedom, privacy and choice. We want to enable people to chat with one another in a safe way. Thus supporting encryption (OTR, PGP, OMEMO) and being decentralized, meaning everyone can run their own server. We believe XMPP is a great proven protocol with an excellent community serving this purpose well.
Feel free to follow us on twitter, join our mailing list and/or MUC.
Installation
Our user guide contains an install section and a section for building from source yourself.
Donations
We would highly appreciate it if you support us via GitHub Sponsors. Especially if you make feature requests or need help using Profanity. Sponsoring enables us to spend time on Profanity.
GitHub matches every donation in the first year.
An alternative way to support us would be via Patreon or ask for our IBAN.
Issues backed by a sponsor will be tagged with the sponsored label. Feature requests that we consider out of scope, either because of interest or because of time needed to implement them, will be marked with the unfunded label.
Another way to sponsor us or get an issue solved is to create a bug bounty. Here one sets a bounty on a certain task and once the task is completed you send the money to the person who did the work.
Tasks from our sponsors will be tackled first.
Thank you! <3
How to contribute
We tried to sum things up on our helpout page. Additionally you can check out our blog where we have articles like: How to get a backtrace and Contributing a Patch via GitHub. For more technical details check out our CONTRIBUTING.md file.
Getting help
To get help, first read our User Guide then check out the FAQ. If you have are having a problem then first search the issue tracker. If you don't find anything there either come to our MUC or create a new issue depending on what your problem is.
Links
Website
URL: https://profanity-im.github.io
Repo: https://github.com/profanity-im/profanity-im.github.io
Blog
URL: https://profanity-im.github.io/blog
Repo: https://github.com/profanity-im/blog
Mailinglist
Mailing List: https://lists.notraces.net/mailman/listinfo/profanity
Thanks to @toogley!
Chatroom
MUC: profanity@rooms.dismail.de
Plugins
Plugins repository: https://github.com/profanity-im/profanity-plugins