1# Cheogram Android
2
3This is a fork of [Conversations](https://conversations.im) to implement features of use to the [Sopranica](https://soprani.ca) project.
4
5The Cheogram Android app allows you to join a worldwide communication network. It especially focuses on features useful to users who want to contact those on other networks as well, such as SMS-enabled phone numbers.
6
7Based on the app Conversations, but with unique features:
8
9* Messages with both media and text, including animated media
10* Unobtrusive display of subject lines, where present
11* Links to known contacts are shown with their name
12* Integrates with gateways' add contact flows
13* When using a gateway to the phone network, integrate with the native Android Phone app
14* Address book integration
15
16Where to get service:
17
18Cheogram Android requires you have an account with a Jabber service. You can run your own service, or use one provided by someone else, for example: https://snikket.org/hosting/
19
20Art in screenshots is from https://www.peppercarrot.com by David Revoy, CC-BY. Artwork has been modified to crop out sections for avatars and photos, and in some cases add transparency. Use of this artwork does not imply endorsement of this project by the artist.
21
22## Getting Help
23
24If you have any questions about this app, or wish to report a bug, please come by the chatroom [in your client](xmpp:discuss@conference.soprani.ca?join) or [on the web](https://anonymous.cheogram.com/discuss@conference.soprani.ca).
25
26## Contributing
27
28If you have code or patches you wish to contribute, the maintainer's preferred mechanism is a git pull request. Push your changes to a git repository somewhere, for example:
29
30 git remote rename origin upstream
31 git remote add origin git@git.sr.ht:~yourname/cheogram-android
32 git push -u origin master
33
34Then generate the pull request:
35
36 git fetch upstream master
37 git request-pull -p upstream/master origin
38
39And copy-paste the result into a plain-text email to: dev@singpolyma.net
40
41You may alternately use a patch-based approach as described on https://git-send-email.io
42
43Contributions follow an inbound=outbound model -- you (or your employer) keep all copyright on your patches, but agree to license them according to this project's COPYING file.