LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-08-23 17:47:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

went to fix a header, light editing

Browse source
This commit is contained in:
Jeremy Kauffman 2020-05-12 18:58:18 -04:00 • committed by GitHub
parent f4589141ac
commit e217181f64
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/faq/support.md
View file

@ -3,13 +3,15 @@ title: How do I get help or report a bug?
category: troubleshooting
---
### Live help
## Live community help
For live help, you can join [our chat](https://chat.lbry.com) and post in the #help channel. Please share a detailed message with the issue you are experiencing. LBRY log files are a good source of information for us; you can learn how to [find them here](/faq/how-to-find-lbry-log-file).
For live help, you can join [our community chat](https://chat.lbry.com) and post in the #help channel.
## Help via email
You can also [email LBRY](mailto:help@lbry.com) with questions or issues. LBRY log files will help us better understand the issue you are experiencing, you can learn how to [find them here](/faq/how-to-find-lbry-log-file) and attach with your email.
You can also [email LBRY](mailto:help@lbry.com) with questions or issues.
If you're using LBRY Desktop, LBRY log files will help us better understand the issue you are experiencing. You can learn how to [find them here](/faq/how-to-find-lbry-log-file) and attach with your email.
## Reporting issues
@ -19,4 +21,4 @@ To report an issue, you can do one of the following:
2. Go to the "Help" page of the app and then click the "Submit a Bug Report" button.
3. If you're a developer or otherwise technical and want to interact with LBRY developers directly, you're welcome to open an issue directly on GitHub. Please try to open network or protocol related issues [here](https://github.com/lbryio/lbry/issues) and interface, usability, and other application related issues [here](https://github.com/lbryio/lbry-desktop/issues). The penalty for getting this wrong is a mild shaming. We would appreciate a quick search to see if similar issues already exist, as well.
3. If you're a developer or otherwise technical and want to interact with LBRY developers directly, you're welcome to open an issue directly on GitHub. Please try to open network or protocol related issues [here](https://github.com/lbryio/lbry/issues) and interface, usability, and other application related issues [here](https://github.com/lbryio/lbry-desktop/issues). We would appreciate a quick search to see if similar issues already exist, as well.