Open Free and open source, read the code

Getting the app working

Something not working, or not behaving the way the page said it would? Write to support@flamenetmessenger.com. A real mailbox, read by the people who build this. If somebody is harassing or threatening you, that is a different page and a faster one.

Things worth trying first

Sign-in refused, and you are sure the passphrase is right. Accounts are tied to the relay you created them on. If you have changed which server the app points at, the account is not there, it is on the other one.

A call rings and then stops, or never rings at all. On Android this is almost always the permission a call needs to take over the screen; the app's notification settings say when it is missing and take you to the switch. On an iPhone, check that notifications are allowed at all.

Messages arriving late. Both apps hold a connection open and are woken by a push. Battery savers on some Android phones close that connection; the phone's own battery settings, set to unrestricted for Flamenet, fix it.

A file with no name, or a story that will not open. Worth writing in about, with the version number from the app. That is usually a real bug.

What to put in the email

Which phone and which version, what you did, and what happened instead. A screenshot helps more than a description of a screenshot. If it is about a specific message, say roughly when it was sent.

Never send us your passphrase or your recovery words. Nobody here will ask for them, and anybody who does is not us. They are the only thing that opens your account and your files, and we cannot use them for anything except reading your messages, which is the one thing this whole project exists to make impossible.

What we can see, and what we cannot

Almost nothing. Messages, files and calls are encrypted on your device, and the server holds ciphertext it has no key for. So "can you check what my message said" is not a thing anyone here can do, however much we would like to help. What we can see is whether a device is reaching the server at all, and whether something failed on our side.

That cuts both ways and it is worth being plain about it: it is the reason the server cannot be made to hand your conversations to anybody, and the reason we cannot recover them for you if you lose your passphrase. There is no reset. A backup you made and kept the passphrase for is the only way back.

Reporting a bug properly

If you would rather file it where you can watch it get fixed, the community page has the issue trackers. A vulnerability goes to security instead, privately, and please not to a public issue.

Every address

One page listing all of them, and what each is for.