{"id":19484159,"url":"https://github.com/karusb/bazcrypt","last_synced_at":"2025-02-25T17:48:12.728Z","repository":{"id":129859208,"uuid":"88442837","full_name":"karusb/BazCrypt","owner":"karusb","description":"Clone Conversations.im Client, (to be used for implementation of bazcrypt)","archived":false,"fork":false,"pushed_at":"2017-04-17T00:29:47.000Z","size":20490,"stargazers_count":1,"open_issues_count":0,"forks_count":1,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-01-08T07:42:22.919Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/karusb.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":".github/CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-04-16T21:12:40.000Z","updated_at":"2019-10-26T05:12:23.000Z","dependencies_parsed_at":"2023-03-11T14:00:15.598Z","dependency_job_id":null,"html_url":"https://github.com/karusb/BazCrypt","commit_stats":null,"previous_names":[],"tags_count":142,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/karusb%2FBazCrypt","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/karusb%2FBazCrypt/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/karusb%2FBazCrypt/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/karusb%2FBazCrypt/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/karusb","download_url":"https://codeload.github.com/karusb/BazCrypt/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240718957,"owners_count":19846483,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-10T20:19:38.188Z","updated_at":"2025-02-25T17:48:12.720Z","avatar_url":"https://github.com/karusb.png","language":"Java","funding_links":["https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick\u0026hosted_button_id=CW3SYT3KG5PDL"],"categories":[],"sub_categories":[],"readme":"# Conversations\n\nConversations: the very last word in instant messaging\n\n[![Google Play](https://conversations.im/images/en-play-badge.png)](https://play.google.com/store/apps/details?id=eu.siacs.conversations\u0026referrer=utm_source%3Dgithub) [![Amazon App Store](https://images-na.ssl-images-amazon.com/images/G/01/AmazonMobileApps/amazon-apps-store-us-black.png)](http://www.amazon.com/dp/B00WD35AAC/)\n\n![screenshots](https://raw.githubusercontent.com/siacs/Conversations/master/screenshots.png)\n\n## Design principles\n\n* Be as beautiful and easy to use as possible without sacrificing security or\n  privacy\n* Rely on existing, well established protocols (XMPP)\n* Do not require a Google Account or specifically Google Cloud Messaging (GCM)\n* Require as few permissions as possible\n\n## Features\n\n* End-to-end encryption with [OMEMO](http://conversations.im/omemo/), [OTR](https://otr.cypherpunks.ca/), or [OpenPGP](http://openpgp.org/about/)\n* Send and receive images as well as other kind of files\n* Share your location via an external [plug-in](https://play.google.com/store/apps/details?id=eu.siacs.conversations.sharelocation\u0026referrer=utm_source%3Dgithub)\n* Indication when your contact has read your message\n* Intuitive UI that follows Android Design guidelines\n* Pictures / Avatars for your Contacts\n* Syncs with desktop client\n* Conferences (with support for bookmarks)\n* Address book integration\n* Multiple accounts / unified inbox\n* Very low impact on battery life\n\n\n### XMPP Features\n\nConversations works with every XMPP server out there. However XMPP is an\nextensible protocol. These extensions are standardized as well in so called\nXEP's. Conversations supports a couple of these to make the overall user\nexperience better. There is a chance that your current XMPP server does not\nsupport these extensions; therefore to get the most out of Conversations you\nshould consider either switching to an XMPP server that does or — even better —\nrun your own XMPP server for you and your friends. These XEP's are:\n\n* [XEP-0065: SOCKS5 Bytestreams](http://xmpp.org/extensions/xep-0065.html) (or mod_proxy65). Will be used to transfer\n  files if both parties are behind a firewall (NAT).\n* [XEP-0163: Personal Eventing Protocol](http://xmpp.org/extensions/xep-0163.html) for avatars and OMEMO.\n* [XEP-0191: Blocking command](http://xmpp.org/extensions/xep-0191.html) lets you blacklist spammers or block contacts\n  without removing them from your roster.\n* [XEP-0198: Stream Management](http://xmpp.org/extensions/xep-0198.html) allows XMPP to survive small network outages and\n  changes of the underlying TCP connection.\n* [XEP-0280: Message Carbons](http://xmpp.org/extensions/xep-0280.html) which automatically syncs the messages you send to\n  your desktop client and thus allows you to switch seamlessly from your mobile\n  client to your desktop client and back within one conversation.\n* [XEP-0237: Roster Versioning](http://xmpp.org/extensions/xep-0237.html) mainly to save bandwidth on poor mobile connections\n* [XEP-0313: Message Archive Management](http://xmpp.org/extensions/xep-0313.html) synchronize message history with the\n  server. Catch up with messages that were sent while Conversations was\n  offline.\n* [XEP-0352: Client State Indication](http://xmpp.org/extensions/xep-0352.html) lets the server know whether or not\n  Conversations is in the background. Allows the server to save bandwidth by\n  withholding unimportant packages.\n* [XEP-0363: HTTP File Upload](http://xmpp.org/extensions/xep-0363.html) allows you to share files in conferences\n  and with offline contacts.\n\n## Team\n\n#### Head of Development\n\n* [Daniel Gultsch](https://github.com/inputmice)\n\n#### Code Contributions\n\n(In order of appearance)\n\n* [Rene Treffer](https://github.com/rtreffer) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3Artreffer+is%3Amerged))\n* [Andreas Straub](https://github.com/strb) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3Astrb+is%3Amerged))\n* [Alethea Butler](https://github.com/alethea) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3Aalethea+is%3Amerged))\n* [M. Dietrich](https://github.com/emdete) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3Aemdete+is%3Amerged))\n* [betheg](https://github.com/betheg) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3Abetheg+is%3Amerged))\n* [Sam Whited](https://github.com/SamWhited) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3ASamWhited+is%3Amerged))\n* [BrianBlade](https://github.com/BrianBlade) ([PRs](https://github.com/siacs/Conversations/pulls?utf8=%E2%9C%93\u0026q=is%3Apr+author%3ABrianBlade+is%3Amerged))\n\n#### Logo\n* [Ilia Rostovtsev](https://github.com/qooob) (Progress)\n* [Diego Turtulici](http://efesto.eigenlab.org/~diesys) (Original)\n* [fiaxh](https://github.com/fiaxh) (OMEMO)\n\n#### Translations\nTranslations are managed on [Transifex](https://www.transifex.com/projects/p/conversations/)\n\n## FAQ\n\n### General\n\n#### How do I install Conversations?\n\nConversations is entirely open source and licensed under GPLv3. So if you are a\nsoftware developer you can check out the sources from GitHub and use Gradle to\nbuild your apk file.\n\nThe more convenient way — which not only gives you automatic updates but also\nsupports the further development of Conversations — is to buy the App in the\nGoogle [Play Store](https://play.google.com/store/apps/details?id=eu.siacs.conversations\u0026referrer=utm_source%3Dgithub).\n\nBuying the App from the Play Store will also give you access to our [beta test](#beta).\n\n#### I don't have a Google Account but I would still like to make a contribution\n\nI accept donations over PayPal, Bitcoin and Flattr. For donations via PayPal you\ncan use the email address `donate@siacs.eu` or the button below.\n\n[![Donate with PayPal](https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick\u0026hosted_button_id=CW3SYT3KG5PDL)\n\n**Disclaimer:** I'm not a huge fan of PayPal and their business policies. For\nlarger contributions please get in touch with me beforehand and we can talk\nabout bank transfer (SEPA).\n\nMy Bitcoin Address is: `1NxSU1YxYzJVDpX1rcESAA3NJki7kRgeeu`\n\n\n[![Flattr this!](http://api.flattr.com/button/flattr-badge-large.png)](https://flattr.com/submit/auto?user_id=inputmice\u0026url=http%3A%2F%2Fconversations.siacs.eu\u0026title=Conversations\u0026tags=github\u0026category=software)\n\n#### How do I create an account?\nXMPP, like email, is a federated protocol, which means that there is not one company you can create an *official XMPP account* with. Instead there are hundreds, or even thousands, of providers out there. One of those providers is our very own [conversations.im](https://account.conversations.im). If you don’t like to use *conversations.im* use a web search engine of your choice to find another provider. Or maybe your university has one. Or you can run your own. Or ask a friend to run one. Once you've found one, you can use Conversations to create an account. Just select *register new account* on server within the create account dialog.\n\n##### Domain hosting\nUsing your own domain not only gives you a more recognizable Jabber ID, it also gives you the flexibility to migrate your account between different XMPP providers. This is a good compromise between the responsibilities of having to operate your own server and the downsides of being dependent on a single provider.\n\nLearn more about [conversations.im Jabber/XMPP domain hosting](https://account.conversations.im/domain/). \n\n##### Running your own\nIf you already have a server somewhere and are willing and able to put the necessary work in, one alternative-in the spirit of federation-is to run your own. We recommend either [Prosody](https://prosody.im/) or [ejabberd](https://www.ejabberd.im/). Both of which have their own strengths. Ejabberd is slightly more mature nowadays but Prosody is arguably easier to set up.\n\nFor Prosody you need a couple of so called [community modules](https://modules.prosody.im/) most of which are maintained by the same people that develop Prosody.\n\nIf you pick ejabberd make sure you use the latest version. Linux Distributions might bundle some very old versions of it.\n\n#### Where can I set up a custom hostname / port\nConversations will automatically look up the SRV records for your domain name\nwhich can point to any hostname port combination. If your server doesn’t provide\nthose please contact your admin and have them read\n[this](http://prosody.im/doc/dns#srv_records). If your server operator is unwilling\nto fix this you can enable advanced server settings in the expert settings of\nConversations.\n\n#### I get 'Incompatible Server'\n\nAs regular user you should be picking a different server. The server you selected\nis probably insecure and/or very old.\n\nIf you are a server administrator you should make sure that your server provides\nSTARTTLS. XMPP over TLS (on a different port) is not sufficient.\n\nOn rare occasions this error message might also be caused by a server not providing\na login (SASL) mechanism that Conversations is able to handle. Conversations supports\nSCRAM-SHA1, PLAIN, EXTERNAL (client certs) and DIGEST-MD5.\n\n#### How do XEP-0357: Push Notifications work?\nYou need to be running the Play Store version of Conversations and your server needs to support push notifications.¹ Because *Google Cloud Notifications (GCM)* are tied with an API key to a specific app your server can not initiate the push message directly. Instead your server will send the push notification to the Conversations App server (operated by us) which then acts as a proxy and initiates the push message for you. The push message sent from our App server through GCM doesn’t contain any personal information. It is just an empty message which will wake up your device and tell Conversations to reconnect to your server. The information send from your server to our App server depends on the configuration of your server but can be limited to your account name. (In any case the Conversations App server won't redirect any information through GCM even if your server sends this information.)\n\nIn summary Google will never get hold of any personal information besides that *something* happened. (Which doesn’t even have to be a message but can be some automated event as well.) We - as the operator of the App server - will just get hold of your account name (without being able to tie this to your specific device).\n\nIf you don’t want this simply pick a server which does not offer Push Notifications or build Conversations yourself without support for push notifications. (This is available via a gradle build flavor.) Non-play store source of Conversations like the Amazon App store will also offer a version without push notifications. Conversations will just work as before and maintain its own TCP connection in the background.\n\n ¹ Your server only needs to support the server side of [XEP-0357: Push Notifications](http://xmpp.org/extensions/xep-0357.html). If you use the Play Store version you do **not** need to run your own app server. The server modules are called *mod_cloud_notify* on Prosody and *mod_push* on ejabberd.\n\n#### Conversations doesn't work for me. Where can I get help?\n\nYou can join our conference room on `conversations@conference.siacs.eu`.\nA lot of people in there are able to answer basic questions about the usage of\nConversations or can provide you with tips on running your own XMPP server. If\nyou found a bug or your app crashes please read the Developer / Report Bugs\nsection of this document.\n\n#### I need professional support with Conversations or setting up my server\n\nI'm available for hire. Contact me at `inputmice@siacs.eu`.\n\n#### How does the address book integration work?\n\nThe address book integration was designed to protect your privacy. Conversations\nneither uploads contacts from your address book to your server nor fills your\naddress book with unnecessary contacts from your online roster. If you manually\nadd a Jabber ID to your phones address book Conversations will use the name and\nthe profile picture of this contact. To make the process of adding Jabber IDs to\nyour address book easier you can click on the profile picture in the contact\ndetails within Conversations. This will start an \"add to address book\" intent\nwith the JID as the payload. This doesn't require Conversations to have write\npermissions on your address book but also doesn't require you to copy/paste a\nJID from one app to another.\n\n#### I get 'delivery failed' on my messages\n\nIf you get delivery failed on images it's probably because the recipient lost\nnetwork connectivity during reception. In that case you can try it again at a\nlater time.\n\nFor text messages the answer to your question is a little bit more complex.\nWhen you see 'delivery failed' on text messages, it is always something that is\nbeing reported by the server. The most common reason for this is that the\nrecipient failed to resume a connection. When a client loses connectivity for a\nshort time the client usually has a five minute window to pick up that\nconnection again. When the client fails to do so because the network\nconnectivity is out for longer than that all messages sent to that client will\nbe returned to the sender resulting in a delivery failed.\n\nInstead of returning a message to the sender both ejabberd and prosody have the\nability to store messages in offline storage when the disconnecting client is\nthe only client. In prosody this is available via an extra module called\n```mod_smacks_offline```. In ejabberd this is available via some configuration\nsettings.\n\nOther less common reasons are that the message you sent didn't meet some\ncriteria enforced by the server (too large, too many). Another reason could be\nthat the recipient is offline and the server doesn't provide offline storage.\n\nUsually you are able to distinguish between these two groups in the fact that\nthe first one happens always after some time and the second one happens almost\ninstantly.\n\n#### Where can I see the status of my contacts? How can I set a status or priority?\n\nStatuses are a horrible metric. Setting them manually to a proper value rarely\nworks because users are either lazy or just forget about them. Setting them\nautomatically does not provide quality results either. Keyboard or mouse\nactivity as indicator for example fails when the user is just looking at\nsomething (reading an article, watching a movie). Furthermore automatic setting\nof status always implies an impact on your privacy (are you sure you want\neverybody in your contact list to know that you have been using your computer at\n4am‽).\n\nIn the past status has been used to judge the likelihood of whether or not your\nmessages are being read. This is no longer necessary. With Chat Markers\n(XEP-0333, supported by Conversations since 0.4) we have the ability to **know**\nwhether or not your messages are being read.  Similar things can be said for\npriorities. In the past priorities have been used (by servers, not by clients!)\nto route your messages to one specific client. With carbon messages (XEP-0280,\nsupported by Conversations since 0.1) this is no longer necessary. Using\npriorities to route OTR messages isn't practical either because they are not\nchangeable on the fly. Metrics like last active client (the client which sent\nthe last message) are much better.\n\nUnfortunately these modern replacements for legacy XMPP features are not widely\nadopted. However Conversations should be an instant messenger for the future and\ninstead of making Conversations compatible with the past we should work on\nimplementing new, improved technologies and getting them into other XMPP clients\nas well.\n\nMaking these status and priority optional isn't a solution either because\nConversations is trying to get rid of old behaviours and set an example for\nother clients.\n\n#### How do I backup / move Conversations to a new device?\nOn the one hand Conversations supports Message Archive Management to keep a server side history of your messages so when migrating to a new device that device can display your entire history. However that does not work if you enable OMEMO due to its forward secrecy. (Read [The State of Mobile XMPP in 2016](https://gultsch.de/xmpp_2016.html) especially the section on encryption.)\n\nIf you migrate to a new device and would still like to keep your history please use a third party backup tool like [oandbackup](https://github.com/jensstein/oandbackup) or ```adb backup``` from your computer.  It is important that your deactivate your account before backup and activate it only after a successful restore. Otherwise OMEMO might not work afterwards. \n\n#### Conversations is missing a certain feature\n\nI'm open for new feature suggestions. You can use the [issue tracker][issues] on\nGitHub.  Please take some time to browse through the issues to see if someone\nelse already suggested it. Be assured that I read each and every ticket. If I\nlike it I will leave it open until it's implemented. If I don't like it I will\nclose it (usually with a short comment). If I don't comment on an feature\nrequest that's probably a good sign because this means I agree with you.\nCommenting with +1 on either open or closed issues won't change my mind, nor\nwill it accelerate the development.\n\n#### You closed my feature request but I want it really really badly\n\nJust write it yourself and send me a pull request. If I like it I will happily\nmerge it if I don't at least you and like minded people get to enjoy it.\n\n#### I need a feature and I need it now!\n\nI am available for hire. Contact me via XMPP: `inputmice@siacs.eu`\n\n### Security\n\n#### Why are there three end-to-end encryption methods and which one should I choose?\n\n* OTR is a legacy encryption method. It works out of the box with most contacts as long as they are online.\n* OMEMO works even when a contact is offline, and works with multiple devices. It also allows asynchronous file-transfer when the server has [HTTP File Upload](http://xmpp.org/extensions/xep-0363.html). However, OMEMO is not as widely supported as OTR and is currently implemented only by Conversations and Gajim. OMEMO should be preferred over OTR for contacts who use Conversations.\n* OpenPGP (XEP-0027) is a very old encryption method that has some advantages over OTR but should only be used by experts who know what they are doing.\n\n#### How do I use OpenPGP\n\nBefore you continue reading you should note that the OpenPGP support in\nConversations is experimental. This is not because it will make the app unstable\nbut because the fundamental concepts of PGP aren't ready for widespread use.\nThe way PGP works is that you trust Key IDs instead of JID's or email addresses.\nSo in theory your contact list should consist of Public-Key-IDs instead of\nJID's. But of course no email or XMPP client out there implements these\nconcepts. Plus PGP in the context of instant messaging has a couple of\ndownsides: It is vulnerable to replay attacks, it is rather verbose, and\ndecrypting and encrypting takes longer than OTR. It is however asynchronous and\nworks well with message carbons.\n\nTo use OpenPGP you have to install the open source app\n[OpenKeychain](http://www.openkeychain.org) and then long press on the account in\nmanage accounts and choose renew PGP announcement from the contextual menu.\n\n#### OMEMO is grayed out. What do I do?\nOMEMO has two requirements: Your server and the server of your contact need to support PEP. Both of you can verify that individually by opening your account details and selecting ```Server info``` from the menu. The appearing table should list PEP as available. The second requirement is mutual presence subscription. You can verify that by opening the contact details and see if both check boxes *Send presence updates* and *Receive presence updates* are checked.\n\n#### How does the encryption for conferences work?\n\nFor conferences only OMEMO and OpenPGP are supported as encryption method. (OTR\ndoes not work with multiple participants).\n\n##### OMEMO\n\nOMEMO encryption works only in private (members only) conferences that are non-anonymous.\nYou need to have presence subscription with every member of the conference.\nYou can verify that by going into the conference details, long press every member and start\na conversation with them. (Or select 'contact details' if they are already in your contact\nlist)\n\nThe owner of a conference can make a public conference private by going into the conference\ndetails and hit the settings button (the one with the gears) and select both *private* and\n*members only*.\n\nIf OMEMO is grayed out long pressing the lock icon will reveal some quick hints on why OMEMO\nis disabled.\n\n##### OpenPGP\n\nEvery participant has to announce their OpenPGP key (see answer above).\nIf you would like to send encrypted messages to a conference you have to make\nsure that you have every participant's public key in your OpenKeychain.\nRight now there is no check in Conversations to ensure that.\nYou have to take care of that yourself. Go to the conference details and\ntouch every key id (The hexadecimal number below a contact). This will send you\nto OpenKeychain which will assist you on adding the key.  This works best in\nvery small conferences with contacts you are already using OpenPGP with. This\nfeature is regarded experimental. Conversations is the only client that uses\nXEP-0027 with conferences. (The XEP neither specifically allows nor disallows\nthis.)\n\n#### Why is Conversations not end-to-end encrypted by default\nWe briefly had OMEMO as the default E2EE but it turned out to be a usability nightmare and thus we reverted that. You can find more information in [the commit message](https://github.com/siacs/Conversations/commit/035d0c79572d5981c53d1bff7f30b484c6542f17) of that change.\n\nQuick reminder that Conversations **always** uses TLS to connect to your server. It won‘t even connect to a server without TLS.\n\n#### What is Blind Trust Before Verification / why are messages marked with a red lock?\n\nRead more about the concept on https://gultsch.de/trust.html\n\n### What clients do I use on other platforms\nThere are XMPP Clients available for all major platforms.\n#### Windows / Linux\nFor your desktop computer we recommend that you use [Gajim](https://gajim.org). You need to install the plugins `OMEMO`, `HTTP Upload` and `URL image preview` to get the best compatibility with Conversations. Plugins can be installed from within the app.\n#### iOS\nUnfortunately we don‘t have a recommendation for iPhones right now. There are two clients available [ChatSecure](https://chatsecure.org/) and [Monal](https://monal.im/). Both with their own pros and cons.\n\n\n### Development\n\n\u003ca name=\"beta\"\u003e\u003c/a\u003e\n#### Beta testing\nIf you bought the App on [Google Play](https://play.google.com/store/apps/details?id=eu.siacs.conversations)\nyou can get access to the latest beta version by joining the\n[Conversations Beta Testers](https://plus.google.com/communities/107649347599361240873)\ncommunity on Google+ and then using [this link](https://play.google.com/apps/testing/eu.siacs.conversations)\nto sign up for the beta test.\n\n#### How do I build Conversations\n\nMake sure to have ANDROID_HOME point to your Android SDK. Use the Android SDK Manager to install missing dependencies.\n\n    git clone https://github.com/siacs/Conversations.git\n    cd Conversations\n    ./gradlew assembleFreeDebug\n\nThere are two build flavors available. *free* and *playstore*. Unless you know what you are doing you only need *free*.\n\n\n[![Build Status](https://travis-ci.org/siacs/Conversations.svg?branch=development)](https://travis-ci.org/siacs/Conversations)\n\n#### How do I update/add external libraries?\n\nIf the library you want to update is in Maven Central or JCenter (or has its own\nMaven repo), add it or update its version in `build.gradle`. If the library is\nin the `libs/` directory, you can update it using a subtree merge by doing the\nfollowing (using `minidns` as an example):\n\n    git remote add minidns https://github.com/rtreffer/minidns.git\n    git fetch minidns\n    git merge -s subtree minidns master\n\nTo add a new dependency to the `libs/` directory (replacing \"name\", \"branch\" and\n\"url\" as necessary):\n\n    git remote add name url\n    git merge -s ours --no-commit name/branch\n    git read-tree --prefix=libs/name -u name/branch\n    git commit -m \"Subtree merged in name\"\n\n#### How do I debug Conversations\n\nIf something goes wrong Conversations usually exposes very little information in\nthe UI (other than the fact that something didn't work). However with adb\n(android debug bridge) you can squeeze some more information out of Conversations.\nThese information are especially useful if you are experiencing trouble with\nyour connection or with file transfer.\n\nTo use adb you have to connect your mobile phone to your computer with an USB cable\nand install `adb`. Most Linux systems have prebuilt packages for that tool. On\nDebian/Ubuntu for example it is called `android-tools-adb`.\n\nFurthermore you might have to enable 'USB debugging' in the Developer options of your\nphone. After that you can just execute the following on your computer:\n\n    adb -d logcat -v time -s conversations\n\nIf need be there are also some Apps on the PlayStore that can be used to show the logcat\ndirectly on your rooted phone. (Search for logcat). However in regards to further processing\n(for example to create an issue here on Github) it is more convenient to just use your PC.\n\n#### I found a bug\n\nPlease report it to our [issue tracker][issues]. If your app crashes please\nprovide a stack trace. If you are experiencing misbehavior please provide\ndetailed steps to reproduce. Always mention whether you are running the latest\nPlay Store version or the current HEAD. If you are having problems connecting to\nyour XMPP server your file transfer doesn’t work as expected please always\ninclude a logcat debug output with your issue (see above).\n\n[issues]: https://github.com/siacs/Conversations/issues\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkarusb%2Fbazcrypt","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkarusb%2Fbazcrypt","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkarusb%2Fbazcrypt/lists"}