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

lbry-app > lbry-desktop (#674)

Browse source 
find + replace
This commit is contained in:
Thomas Zarebczan 2018-07-12 12:45:21 -07:00 • committed by GitHub
parent 4bd5884156
commit beddd1bafa
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
28 changed files with 64 additions and 66 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/bounty/app-i18n.md
View file

@ -8,7 +8,7 @@ date: '2016-07-01'
The LBRY App is currently lacking support for internationalization. The LBRY App is currently lacking support for internationalization.
To complete this bounty, [lbry-app](https://github.com/lbryio/lbry-app) must be modified as follows: To complete this bounty, [lbry-desktop](https://github.com/lbryio/lbry-desktop) must be modified as follows:
- Add [gettext](https://en.wikipedia.org/wiki/Gettext) internationalization calls to the React app - Add [gettext](https://en.wikipedia.org/wiki/Gettext) internationalization calls to the React app
- Store selected language in the user settings - Store selected language in the user settings

2
content/bounty/automatic-app-updates.md
View file

@ -8,7 +8,7 @@ date: '2017-07-22'
The LBRY app currently does not update itself automatically, however electron does support this feature. The LBRY app currently does not update itself automatically, however electron does support this feature.
To complete this bounty, [lbry-app](https://github.com/lbryio/lbry-app) must be modified as follows: To complete this bounty, [lbry-desktop](https://github.com/lbryio/lbry-desktop) must be modified as follows:
- Detect when a new latest release is available, download it and prompt the user with a "Restart LBRY" / "I'll do it later" dialog to have the update take effect. - Detect when a new latest release is available, download it and prompt the user with a "Restart LBRY" / "I'll do it later" dialog to have the update take effect.
- Parse the changelog for the latest release, if it contains `Security` items carry out the update automatically without presenting the "I'll do it later" option. - Parse the changelog for the latest release, if it contains `Security` items carry out the update automatically without presenting the "I'll do it later" option.

2
content/bounty/pkg-installer-for-osx.md
View file

@ -3,7 +3,7 @@ category: osx
title: PKG Installer for OS X title: PKG Installer for OS X
award: 1500 award: 1500
status: complete status: complete
pr: https://github.com/lbryio/lbry-app/pull/99 pr: https://github.com/lbryio/lbry-desktop/pull/99
date: '2016-07-01' date: '2016-07-01'
--- ---

2
content/bounty/wallet-ui.md
View file

@ -7,7 +7,7 @@ pr: https://github.com/lbryio/lbry-web-ui/pull/23
date: '2016-07-01' date: '2016-07-01'
--- ---
Add a basic wallet interface to the LBRY Browser [`lbry-app`](https://github.com/lbryio/lbry-app). Add a basic wallet interface to the LBRY Browser [`lbry-desktop`](https://github.com/lbryio/lbry-desktop).
The interface must support: The interface must support:

12
content/faq/contributing.md
View file

@ -28,13 +28,13 @@ Whether you want to report an issue, contribute to the code, or help test the so
| Component | Language | What Is It | Use This Repo For..| | Component | Language | What Is It | Use This Repo For..|
--- | --- | --- | --- --- | --- | --- | ---
| [lbry](https://github.com/lbryio/lbry) | Python | A daemon that runs in the background and allows your computer to speak LBRY. | Issues with downloading or uploading. <br/><br/> Anything related to output in `lbrynet.log`. <br/><br/> Issues unrelated to or deeper than the interface that does not deal with blockchain credits. | | [lbry](https://github.com/lbryio/lbry) | Python | A daemon that runs in the background and allows your computer to speak LBRY. | Issues with downloading or uploading. <br/><br/> Anything related to output in `lbrynet.log`. <br/><br/> Issues unrelated to or deeper than the interface that does not deal with blockchain credits. |
| [lbry-app](https://github.com/lbryio/lbry-app) | JavaScript | A graphical browser for the LBRY protocol | Problems with or features missing from the browser interface. <br/><br/> Issues with using, installing or running the LBRY app **other** than network, connection, or performance issues. | | [lbry-desktop](https://github.com/lbryio/lbry-desktop) | JavaScript | A graphical browser for the LBRY protocol | Problems with or features missing from the browser interface. <br/><br/> Issues with using, installing or running the LBRY app **other** than network, connection, or performance issues. |
| [lbryum](https://github.com/lbryio/lbryum) | Python | Server for the thin wallet bundled with lbry/lbry-app | Issues related to credit/wallet functionality.<br><br><em>This is a fork of <a href="https://github.com/spesmilo">electrum</a>.</em> | [lbryum](https://github.com/lbryio/lbryum) | Python | Server for the thin wallet bundled with lbry/lbry-desktop | Issues related to credit/wallet functionality.<br><br><em>This is a fork of <a href="https://github.com/spesmilo">electrum</a>.</em>
| [lbrycrd](https://github.com/lbryio/lbrycrd) | C++ | The LBRY blockchain and standalone wallet | Running a full node, or direct access to the LBRY blockchain.<br><br> <em>(This wallet is not bundled with the application. You only want this if you downloaded/installed this package specifically.)</em> | [lbrycrd](https://github.com/lbryio/lbrycrd) | C++ | The LBRY blockchain and standalone wallet | Running a full node, or direct access to the LBRY blockchain.<br><br> <em>(This wallet is not bundled with the application. You only want this if you downloaded/installed this package specifically.)</em>
| [lbry-schema](https://github.com/lbryio/lbryschema) | Protobuf, Python | The structure of the metadata stored in the LBRY blockchain. | You want to change the metadata LBRY stores about digital content. | | [lbry-schema](https://github.com/lbryio/lbryschema) | Protobuf, Python | The structure of the metadata stored in the LBRY blockchain. | You want to change the metadata LBRY stores about digital content. |
| [lbryio](https://github.com/lbryio/lbry.io) | PHP | The lbry.io website. | Edits to the site, FAQ/KB requests or additions. | [lbryio](https://github.com/lbryio/lbry.io) | PHP | The lbry.io website. | Edits to the site, FAQ/KB requests or additions.
The vast majority of issues will be filed in either `lbry-app` or `lbry`. The vast majority of issues will be filed in either `lbry-desktop` or `lbry`.
## Raising Issues {#raising-issue} ## Raising Issues {#raising-issue}
@ -86,13 +86,13 @@ If you're a writer, designer, or communicator, you can also contribute to LBRY.
### Writing {#writing} ### Writing {#writing}
If you want to update or edit existing written copy, it likely exists in either [lbry.io](https://github.com/lbryio/lbry.io) (the website) or [lbry-app](https://github.com/lbryio/lbry-app) (the browser). Try searching the respective repo for a string (in quotes) related to the copy that you want to adjust. You can likely figure out how to edit text via the GitHub interface. If not, you can point out issues to [Tom](mailto:tom@lbry.io). If you want to update or edit existing written copy, it likely exists in either [lbry.io](https://github.com/lbryio/lbry.io) (the website) or [lbry-desktop](https://github.com/lbryio/lbry-desktop) (the browser). Try searching the respective repo for a string (in quotes) related to the copy that you want to adjust. You can likely figure out how to edit text via the GitHub interface. If not, you can point out issues to [Tom](mailto:tom@lbry.io).
If you want to contribute new written copy, such as a blog post or other content, please contact [Jeremy](mailto:jeremy@lbry.io), or join or [chat](https://chat.lbry.io) and post a message in #general. If you want to contribute new written copy, such as a blog post or other content, please contact [Jeremy](mailto:jeremy@lbry.io), or join or [chat](https://chat.lbry.io) and post a message in #general.
### Designing {#designing} ### Designing {#designing}
If you're a web designer, you can contribute to either [lbry.io](https://github.com/lbryio/lbry.io) (the website) or [lbry-app](https://github.com/lbryio/lbry-app) (the browser) by opening a pull request. If you're a web designer, you can contribute to either [lbry.io](https://github.com/lbryio/lbry.io) (the website) or [lbry-desktop](https://github.com/lbryio/lbry-desktop) (the browser) by opening a pull request.
If you're a graphic designer, creating engaging graphics, GIFs, explainers, HOWTOs, wallpapers, and other related graphical content is a huge help! You can submit or discuss contributions by emailing [Jeremy](mailto:jeremy@lbry.io) or joining the #design channel in our [chat](https://chat.lbry.io). If you're a graphic designer, creating engaging graphics, GIFs, explainers, HOWTOs, wallpapers, and other related graphical content is a huge help! You can submit or discuss contributions by emailing [Jeremy](mailto:jeremy@lbry.io) or joining the #design channel in our [chat](https://chat.lbry.io).
@ -108,7 +108,7 @@ Translations are not managed through Git or GitHub. Email [Josh](mailto:josh@lbr
If you aren't a coder, or you're a lazy coder, one of the best ways you can contribute is testing! If you aren't a coder, or you're a lazy coder, one of the best ways you can contribute is testing!
Both `lbry` and `lbry-app` go through regular release cycles where new versions are shipped every few weeks. Testing release candidates or builds of a master is a great way to help us identify issues and ship bug-free code. Both `lbry` and `lbry-desktop` go through regular release cycles where new versions are shipped every few weeks. Testing release candidates or builds of a master is a great way to help us identify issues and ship bug-free code.
For any repos, you want to be a tester on, "Watch" the repo on GitHub. You will receive an email with release notes whenever a release candidate is out. For any repos, you want to be a tester on, "Watch" the repo on GitHub. You will receive an email with release notes whenever a release candidate is out.

6
content/faq/how-to-clean-install-preserve.md
View file

@ -21,7 +21,7 @@ Note: after a clean install, you may be prompted again for your email. This is n
2. `blobs.db` - reference data for the blob files which are used for hosting purposes 2. `blobs.db` - reference data for the blob files which are used for hosting purposes
3. `lbryfile_info.db` - Downloads and Publishes data 3. `lbryfile_info.db` - Downloads and Publishes data
4. `blockchainname.db` - Supports downloads data 4. `blockchainname.db` - Supports downloads data
8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-app/releases "Github App Page"). If prompted to allow through Windows Firewall, click Allow 8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-desktop/releases "Github App Page"). If prompted to allow through Windows Firewall, click Allow
9. LBRY should start immediately after install. If you kept your data, your balance and content would be reflected 9. LBRY should start immediately after install. If you kept your data, your balance and content would be reflected
## MacOS ## MacOS
@ -36,7 +36,7 @@ Note: after a clean install, you may be prompted again for your email. This is n
4. `blockchainname.db` - Supports downloads data 4. `blockchainname.db` - Supports downloads data
6. In Finder - click Go menu on top, choose "Go To Folder", type. ~/.lbryum and then click go 6. In Finder - click Go menu on top, choose "Go To Folder", type. ~/.lbryum and then click go
7. If performing a clean install, delete the entire contents of this folder **(!!THIS WILL DELETE YOUR WALLET!!)** and proceed to the next step, otherwise delete just the `blockchain_headers` file 7. If performing a clean install, delete the entire contents of this folder **(!!THIS WILL DELETE YOUR WALLET!!)** and proceed to the next step, otherwise delete just the `blockchain_headers` file
8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-app/releases "Github App Page") 8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-desktop/releases "Github App Page")
9. Launch LBRY by starting it from the Applications folder. You can add it to your dock for easier access. If you kept your data and wallet, your balance and content would be reflected 9. Launch LBRY by starting it from the Applications folder. You can add it to your dock for easier access. If you kept your data and wallet, your balance and content would be reflected
## Ubuntu / Linux ## Ubuntu / Linux
@ -51,6 +51,6 @@ Note: after a clean install, you may be prompted again for your email. This is n
2. `blobs.db` - reference data for the blob files which are used for hosting purposes 2. `blobs.db` - reference data for the blob files which are used for hosting purposes
3. `lbryfile_info.db` - Downloads and Publishes data 3. `lbryfile_info.db` - Downloads and Publishes data
4. `blockchainname.db` - Supports downloads data 4. `blockchainname.db` - Supports downloads data
8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-app/releases "Github App Page") 8. Install the latest version of LBRY from: [Github App Page](https://github.com/lbryio/lbry-desktop/releases "Github App Page")
9. Click the Search button on the toolbar, type LBRY and then hit Enter to launch LBRY. You can pin it to your taskbar for easier access. If you kept your data, your balance and content would be reflected 9. Click the Search button on the toolbar, type LBRY and then hit Enter to launch LBRY. You can pin it to your taskbar for easier access. If you kept your data, your balance and content would be reflected

2
content/faq/incompatible-protocol-version.md
View file

@ -12,7 +12,7 @@ The most likely cause of this error is an old version was running during the ins
1. Click `Quit Daemon` in the LBRY app to kill the LBRY network process. 1. Click `Quit Daemon` in the LBRY app to kill the LBRY network process.
1. Restart your PC or ensure that any processes with "lbry" in the name are not running. 1. Restart your PC or ensure that any processes with "lbry" in the name are not running.
1. [Download](https://github.com/lbryio/lbry-app/releases) and re-install the latest version of LBRY. 1. [Download](https://github.com/lbryio/lbry-desktop/releases) and re-install the latest version of LBRY.
1. Start LBRY 1. Start LBRY
If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support. If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support.

6
content/faq/startup-troubleshooting.md
View file

@ -19,14 +19,14 @@ LBRY operates on a couple of different ports, and if there are conflicts/firewal
### This is my first time running LBRY, and it won't start ### This is my first time running LBRY, and it won't start
- Port 3333 already in use. This issue would reveal itself in the log file. You can see how to change this port [here](https://lbry.io/faq/how-to-change-port). If the port is properly forwarding correctly, you are able to successfully see port 3333 Open on this [port checker tool](http://www.canyouseeme.org). - Port 3333 already in use. This issue would reveal itself in the log file. You can see how to change this port [here](https://lbry.io/faq/how-to-change-port). If the port is properly forwarding correctly, you are able to successfully see port 3333 Open on this [port checker tool](http://www.canyouseeme.org).
- Port 50001 wallet connection fails. This issue would reveal itself in the log file. Typical things to check would be firewall/security settings that may block this connection. - Port 50001 wallet connection fails. This issue would reveal itself in the log file. Typical things to check would be firewall/security settings that may block this connection.
- On Linux, LBRY may fail to start(home page won't load, missing authentication token in Help) because of missing authentication capability. Please see [GitHub issue](https://github.com/lbryio/lbry-app/issues/386) or possible workaround below. - On Linux, LBRY may fail to start(home page won't load, missing authentication token in Help) because of missing authentication capability. Please see [GitHub issue](https://github.com/lbryio/lbry-desktop/issues/386) or possible workaround below.
- On Windows, LBRY may fail to start because of non-ASCII characters in your Windows username. Check your c:\users\<username> path to see if there are any such characters. Please see [GitHub issue](https://github.com/lbryio/lbry/issues/794) or workaround below. - On Windows, LBRY may fail to start because of non-ASCII characters in your Windows username. Check your c:\users\<username> path to see if there are any such characters. Please see [GitHub issue](https://github.com/lbryio/lbry/issues/794) or workaround below.
### LBRY used to work previously, but now it won't start ### LBRY used to work previously, but now it won't start
First and foremost, please ensure you are on the [latest version](https://lbry.io/get) of LBRY. Reinstalling the latest version may alleviate some start-up issues. Before installing, either make sure no LBRY/lbrynet processes or simply reboot your computer. First and foremost, please ensure you are on the [latest version](https://lbry.io/get) of LBRY. Reinstalling the latest version may alleviate some start-up issues. Before installing, either make sure no LBRY/lbrynet processes or simply reboot your computer.
- On Windows, if you get stuck on the "Starting daemon" green screen, the lbrynet-daemon file may be missing. The workaround is to rerun the [latest](https://lbry.io/get) LBRY installation file and try again. - On Windows, if you get stuck on the "Starting daemon" green screen, the lbrynet-daemon file may be missing. The workaround is to rerun the [latest](https://lbry.io/get) LBRY installation file and try again.
- On older MAC installations, you may run into an issue with the daemon shutting down immediately. Please see [this GitHub issue](https://github.com/lbryio/lbry-app/issues/291) for troubleshooting. - On older MAC installations, you may run into an issue with the daemon shutting down immediately. Please see [this GitHub issue](https://github.com/lbryio/lbry-desktop/issues/291) for troubleshooting.
- On older Linux/Mac installs you may see `Cannot read property 'match' of undefined`, install the [latest version](https://lbry.io/get) to fix this. - On older Linux/Mac installs you may see `Cannot read property 'match' of undefined`, install the [latest version](https://lbry.io/get) to fix this.
- Other typical startup troubleshooting would be to ensure that LBRY or lbrynet-daemon is not already running in the background. If the processes cannot be killed, a restart of your computer may be required. - Other typical startup troubleshooting would be to ensure that LBRY or lbrynet-daemon is not already running in the background. If the processes cannot be killed, a restart of your computer may be required.
@ -34,7 +34,7 @@ First and foremost, please ensure you are on the [latest version](https://lbry.i
#### Stuck at blockchain sync {#sync} #### Stuck at blockchain sync {#sync}
If you are stuck on the blockchain sync step or it shows a block count that doesn't decrease, you may need to clear your blockchain cache. To do so, Shut LBRY down completely by closing it from the system tray(check for running LBRY/lbrynet-daemon processes), delete the `blockchain_headers` file in the [lbryum folder](https://lbry.io/faq/lbry-directories) and then start LBRY again. If you are stuck on the blockchain sync step or it shows a block count that doesn't decrease, you may need to clear your blockchain cache. To do so, Shut LBRY down completely by closing it from the system tray(check for running LBRY/lbrynet-daemon processes), delete the `blockchain_headers` file in the [lbryum folder](https://lbry.io/faq/lbry-directories) and then start LBRY again.
#### Linux auth_token requirements {#auth} #### Linux auth_token requirements {#auth}
Currently, LBRY requires an authorization token to be generated using the [keytar](https://github.com/atom/node-keytar) libraries. Please ensure libsecret and keytar are installed. On some distributions, LBRY won't run unless gnome-keyring is also installed/operational. See [GitHub issue](https://github.com/lbryio/lbry-app/issues/386) for more information. If you get a GLIBCXX_3.4.2 error, please see [this issue](https://github.com/lbryio/lbry-app/issues/423#issuecomment-327519486). Currently, LBRY requires an authorization token to be generated using the [keytar](https://github.com/atom/node-keytar) libraries. Please ensure libsecret and keytar are installed. On some distributions, LBRY won't run unless gnome-keyring is also installed/operational. See [GitHub issue](https://github.com/lbryio/lbry-desktop/issues/386) for more information. If you get a GLIBCXX_3.4.2 error, please see [this issue](https://github.com/lbryio/lbry-desktop/issues/423#issuecomment-327519486).
#### Windows user path has non-ASCII characters #### Windows user path has non-ASCII characters
Currently, the LBRY app may fail to start because it does not support non-ASCII / non-English letters in the c:\Users\<username> directory where it tries to create your LBRY wallet, downloads and application data. As a workaround, you can manually set these directories in the `daemon_settings.yml` file within the [lbrynet folder](https://lbry.io/faq/lbry-directories). If this file does not exist in your [lbrynet folder](https://lbry.io/faq/lbry-directories), you can create one, or you can use [this sample](https://goo.gl/opybNE). Currently, the LBRY app may fail to start because it does not support non-ASCII / non-English letters in the c:\Users\<username> directory where it tries to create your LBRY wallet, downloads and application data. As a workaround, you can manually set these directories in the `daemon_settings.yml` file within the [lbrynet folder](https://lbry.io/faq/lbry-directories). If this file does not exist in your [lbrynet folder](https://lbry.io/faq/lbry-directories), you can create one, or you can use [this sample](https://goo.gl/opybNE).

6
content/faq/support.md
View file

@ -9,7 +9,7 @@ For live help, you can join [our chat](https://chat.lbry.io) and post in the #he
## Help via Email ## Help via Email
You can also [email LBRY](mailto:help@lbry.io) 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](https://lbry.io/faq/how-to-find-lbry-log-file) and attach with your email. You can also [email LBRY](mailto:help@lbry.io) 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](https://lbry.io/faq/how-to-find-lbry-log-file) and attach with your email.
### Reporting Issues ### Reporting Issues
@ -20,6 +20,4 @@ To report an issue, you can do one of the following:
1. Go to the "Help" page of the app and then click the "Submit a Bug Report" button. 1. Go to the "Help" page of the app and then click the "Submit a Bug Report" button.
![help](https://spee.ch/8/Fix-broken.png) ![help](https://spee.ch/8/Fix-broken.png)
1. 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-app/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. 1. 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.

2
content/jobs/application-engineer-lead.md
View file

@ -9,7 +9,7 @@ As the touch and interaction point for the vast majority of LBRY users, applicat
LBRY maintains three applications. All three use either ReactJS or React Native. LBRY maintains three applications. All three use either ReactJS or React Native.
- [lbry-desktop](http://github.com/lbryio/lbry-app), an Electron based desktop browser and wallet. - [lbry-desktop](http://github.com/lbryio/lbry-desktop), an Electron based desktop browser and wallet.
- [lbry-android](https://github.com/lbryio/lbry-android), a browser and wallet for Android, currently in alpha. - [lbry-android](https://github.com/lbryio/lbry-android), a browser and wallet for Android, currently in alpha.
- [spee.ch](https://github.com/lbryio/spee.ch), a web-based image and video sharing and self-hosting tool that syncs to the LBRY network. - [spee.ch](https://github.com/lbryio/spee.ch), a web-based image and video sharing and self-hosting tool that syncs to the LBRY network.

2
content/jobs/lead-designer.md
View file

@ -7,6 +7,6 @@ url: https://hire.withgoogle.com/public/jobs/lbryio/view/P_AAAAAADAAADDIkS8VwCnP
--- ---
Like designing things? Great, because this position involves designing all the things. Like designing things? Great, because this position involves designing all the things.
The Lead Designer at LBRY is responsible for design, look, feel, and aesthetics of [our logo](https://lbry.io/img/lbry-dark.svg), our applications ([1](http://github.com/lbryio/lbry-app) [2](https://github.com/lbryio/lbry-android) [3](http://github.com/lbryio/spee.ch)), our websites ([1](https://lbry.io) [2](https://beta.lbry.tech)), and [our CEO's hair](https://spee.ch/5/hair.jpg). The Lead Designer at LBRY is responsible for design, look, feel, and aesthetics of [our logo](https://lbry.io/img/lbry-dark.svg), our applications ([1](http://github.com/lbryio/lbry-desktop) [2](https://github.com/lbryio/lbry-android) [3](http://github.com/lbryio/spee.ch)), our websites ([1](https://lbry.io) [2](https://beta.lbry.tech)), and [our CEO's hair](https://spee.ch/5/hair.jpg).
We prefer to work with designers who can go from idea to implementation, including working directly in CSS. We prefer to work with designers who can go from idea to implementation, including working directly in CSS.

2
content/news/114-coinomiwallet.md
View file

@ -7,7 +7,7 @@ date: '2017-06-02 00:14:00'
![LBRY Coinomi Screenshot](https://spee.ch/lbrycoinomi) ![LBRY Coinomi Screenshot](https://spee.ch/lbrycoinomi)
As our focus has been on building out a [great application](https://github.com/lbryio/lbry-app), we haven't put much emphasis on a standalone way to manage your LBRY credits. However, we have noticed the demand for easy backups and a simple, secure way to move credits between accounts. As our focus has been on building out a [great application](https://github.com/lbryio/lbry-desktop), we haven't put much emphasis on a standalone way to manage your LBRY credits. However, we have noticed the demand for easy backups and a simple, secure way to move credits between accounts.
That's why we're excited to announce integration with Coinomi! That's why we're excited to announce integration with Coinomi!

2
content/news/129-lbry-release-first-run-wallet-invites-rewards.md
View file

@ -7,7 +7,7 @@ The latest LBRY app, v0.15 and the first update since open beta, is now availabl
## Release Notes ## Release Notes
The release notes are below. These notes are copied from the [GitHub releases page](https://github.com/lbryio/lbry-app/releases), which is the official source of release notes. The release notes are below. These notes are copied from the [GitHub releases page](https://github.com/lbryio/lbry-desktop/releases), which is the official source of release notes.
For immediate notification of releases, you can watch the project on GitHub. For immediate notification of releases, you can watch the project on GitHub.

4
content/news/147-lbry-shifting-into-high-gear.md
View file

@ -14,8 +14,8 @@ You'll find all this (and a lot more) in LBRY v0.19 - **[get it here](https://lb
## Release Notes ## Release Notes
### Added ### Added
* [Subscriptions](https://github.com/lbryio/lbry-app/issues/715). File and channel pages now show a subscribe button. A new "Subscriptions" tab appears on the homepage shows the most recent content from subscribed channels. * [Subscriptions](https://github.com/lbryio/lbry-desktop/issues/715). File and channel pages now show a subscribe button. A new "Subscriptions" tab appears on the homepage shows the most recent content from subscribed channels.
* [LBC acquisition widget](https://github.com/lbryio/lbry-app/issues/609). Convert other popular cryptos into LBC via a ShapeShift integration. * [LBC acquisition widget](https://github.com/lbryio/lbry-desktop/issues/609). Convert other popular cryptos into LBC via a ShapeShift integration.
* [Flow](https://flow.org/) static type checking. This is a dev-only feature but will make development faster, less error-prone, and better for newcomers. * [Flow](https://flow.org/) static type checking. This is a dev-only feature but will make development faster, less error-prone, and better for newcomers.
### Changed ### Changed

2
content/news/157-verified-awesome.md
View file

@ -12,4 +12,4 @@ LBRY v0.20 is live, and if you've been waiting in vain for verification, your da
Users can now use SMS to verify that they're human. We've also automated the app upgrade process, updated the LBRY daemon, added a "dark" mode for evening viewing, and fixed an [Electron security issue](https://electronjs.org/blog/protocol-handler-fix). Users can now use SMS to verify that they're human. We've also automated the app upgrade process, updated the LBRY daemon, added a "dark" mode for evening viewing, and fixed an [Electron security issue](https://electronjs.org/blog/protocol-handler-fix).
You can read the [full release notes here](https://github.com/lbryio/lbry-app/releases/tag/v0.20.0). If you haven't downloaded the app yet, [what are you waiting for](lbry.io/get)? You can read the [full release notes here](https://github.com/lbryio/lbry-desktop/releases/tag/v0.20.0). If you haven't downloaded the app yet, [what are you waiting for](lbry.io/get)?

2
content/news/158-LBRY-in-2017-2018.md
View file

@ -157,7 +157,7 @@ Want to help LBRY build a free and open internet? Here’s how:
1. [Download the LBRY app](https://lbry.io/) and try it out. 1. [Download the LBRY app](https://lbry.io/) and try it out.
2. If you have an idea that could make the app better (or if something breaks while you’re using it!) [open a new issue on Github](https://github.com/lbryio/lbry-app/issues) and tell us about it. 2. If you have an idea that could make the app better (or if something breaks while you’re using it!) [open a new issue on Github](https://github.com/lbryio/lbry-desktop/issues) and tell us about it.
3. Tell your friends and family about LBRY. With SMS Rewards verification in the [newest version of the app](https://lbry.io/news/verified-awesome), it’s easier than ever to earn LBC which can then be used to publish, view paid content or tip your favorite creators on LBRY. 3. Tell your friends and family about LBRY. With SMS Rewards verification in the [newest version of the app](https://lbry.io/news/verified-awesome), it’s easier than ever to earn LBC which can then be used to publish, view paid content or tip your favorite creators on LBRY.

10
content/news/159-lbry-development-community-update-Jan-2018.md
View file

@ -14,20 +14,20 @@ To skip the tech stuff and see what’s happened and what’s next in the LBRY c
[Skip to **Community Happenings**](#com-updates) [Skip to **Community Happenings**](#com-updates)
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md).
### App and Protocol Quick Summary ### App and Protocol Quick Summary
As you may know from our previous update, the LBRY App is undergoing a redesign which is taking up a large chunk of the team’s time, but we still managed to ship multiple patch releases to version 0.19 that enabled users to continue enjoying the main functions of the LBRY app. We also finished off January with [version 0.20](https://github.com/lbryio/lbry-app/releases/tag/v0.20.0) which enables a more streamlined LBRY app update process, phone number verification for [LBRY Rewards](https://lbry.io/faq/rewards) that makes it easier for new users to earn some LBC, added automated dark theme mode, patched a security hole introduced by [Electron](https://electronjs.org/blog/protocol-handler-fix) and a bit of code refactoring. On the protocol side, we ran into a showstopper related to how files are handled and were forced to go back to the drawing board to re-engineer a better solution. Our protocol devs also had to deal with growing pains on [spee.ch](https://spee.ch) which continues to uncover invaluable insights into scaling the LBRY as it’s the biggest user of the protocol to date! As you may know from our previous update, the LBRY App is undergoing a redesign which is taking up a large chunk of the team’s time, but we still managed to ship multiple patch releases to version 0.19 that enabled users to continue enjoying the main functions of the LBRY app. We also finished off January with [version 0.20](https://github.com/lbryio/lbry-desktop/releases/tag/v0.20.0) which enables a more streamlined LBRY app update process, phone number verification for [LBRY Rewards](https://lbry.io/faq/rewards) that makes it easier for new users to earn some LBC, added automated dark theme mode, patched a security hole introduced by [Electron](https://electronjs.org/blog/protocol-handler-fix) and a bit of code refactoring. On the protocol side, we ran into a showstopper related to how files are handled and were forced to go back to the drawing board to re-engineer a better solution. Our protocol devs also had to deal with growing pains on [spee.ch](https://spee.ch) which continues to uncover invaluable insights into scaling the LBRY as it’s the biggest user of the protocol to date!
### Documentation, Organization and Development Processes ### Documentation, Organization and Development Processes
A considerable amount of effort went into documenting an app side [contributing process](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md) along with [tagging and organization](https://github.com/lbryio/lbry/wiki/Labels) of GitHub issues which required a careful review of all outstanding issues across multiple repositories. The result was a clearer and more organized depiction of what’s on the plate for our developers to work on but it also provides a more welcoming environment for contributors and potential LBRY developers to get started. A considerable amount of effort went into documenting an app side [contributing process](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md) along with [tagging and organization](https://github.com/lbryio/lbry/wiki/Labels) of GitHub issues which required a careful review of all outstanding issues across multiple repositories. The result was a clearer and more organized depiction of what’s on the plate for our developers to work on but it also provides a more welcoming environment for contributors and potential LBRY developers to get started.
During the past month, we’ve also transitioned to a more agile development methodology we like to call [scrum-lite](https://github.com/lbryio/lbry/wiki/Development-Process-&-Standards) which enables the team to reassess and refocus our efforts on a bi-monthly basis. In addition to creating a more structured framework around development processes, this also forces us to break down large tasks into smaller, easier to tackle initiatives which allow for a transition from “I’m still working on it” to “completed part 1A, onto the next one!”. During the past month, we’ve also transitioned to a more agile development methodology we like to call [scrum-lite](https://github.com/lbryio/lbry/wiki/Development-Process-&-Standards) which enables the team to reassess and refocus our efforts on a bi-monthly basis. In addition to creating a more structured framework around development processes, this also forces us to break down large tasks into smaller, easier to tackle initiatives which allow for a transition from “I’m still working on it” to “completed part 1A, onto the next one!”.
![Scrum overview](https://spee.ch/b/AgileProjectManagementbyPlanbox.png) ![Scrum overview](https://spee.ch/b/AgileProjectManagementbyPlanbox.png)
### App Redesign ### App Redesign
The LBRY App redesign is in full swing, and a good amount of progress has been made to date - you can follow along on [GitHub](https://github.com/lbryio/lbry-app/issues/848) for the latest status and updates. Not only does it include a facelift, but much of the underlying framework and navigation will be revamped as well. This also includes changes to the way searching is performed and redesigns to other pages like Wallet Overview, claims and file lists. The LBRY App redesign is in full swing, and a good amount of progress has been made to date - you can follow along on [GitHub](https://github.com/lbryio/lbry-desktop/issues/848) for the latest status and updates. Not only does it include a facelift, but much of the underlying framework and navigation will be revamped as well. This also includes changes to the way searching is performed and redesigns to other pages like Wallet Overview, claims and file lists.
![App redesign early preview](https://spee.ch/1/app-redesign-preview.jpeg) ![App redesign early preview](https://spee.ch/1/app-redesign-preview.jpeg)
@ -45,7 +45,7 @@ Our recent [hiring efforts](https://lbry.io/join-us) exposed a weakness in LBRY
A LBRY whitepaper is in the works which will formally document the LBRY ecosystem and protocol specifications. Its creation had been put off for a while since most agree that whitepapers are marketing gimmicks for projects without a product, but as LBRY continues to get more attention, having one will allow us to link a single technical resource into how LBRY functions as opposed to directing users to FAQ posts or other articles. A LBRY whitepaper is in the works which will formally document the LBRY ecosystem and protocol specifications. Its creation had been put off for a while since most agree that whitepapers are marketing gimmicks for projects without a product, but as LBRY continues to get more attention, having one will allow us to link a single technical resource into how LBRY functions as opposed to directing users to FAQ posts or other articles.
### LBRY Wallet Encryption ### LBRY Wallet Encryption
LBRY wallet encryption has been enabled in the latest versions of the daemon (not released yet). With the help of a few community members, we ran through initial tests, and they were successful at a basic level. In order to ensure we didn’t break anything, additional testing will need to be performed once an app is released that uses the new daemon. The final step would be to [integrate this feature](https://github.com/lbryio/lbry-app/issues/762) into the app. This would most likely happen after the app redesign and will come along with a new user walkthrough. LBRY wallet encryption has been enabled in the latest versions of the daemon (not released yet). With the help of a few community members, we ran through initial tests, and they were successful at a basic level. In order to ensure we didn’t break anything, additional testing will need to be performed once an app is released that uses the new daemon. The final step would be to [integrate this feature](https://github.com/lbryio/lbry-desktop/issues/762) into the app. This would most likely happen after the app redesign and will come along with a new user walkthrough.
![Wallet Encryption command line](https://spee.ch/7/walletencryption.png) ![Wallet Encryption command line](https://spee.ch/7/walletencryption.png)

6
content/news/163-lbry-development-community-update-Feb-2018.md
View file

@ -16,7 +16,7 @@ To skip the tech stuff and see what’s happened and what’s next in the LBRY c
[Skip to **Community Happenings**](#com-updates) [Skip to **Community Happenings**](#com-updates)
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://lbry.tech which will also include a StackExchange like a forum for Q&A/troubleshooting. All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://lbry.tech which will also include a StackExchange like a forum for Q&A/troubleshooting.
### App and Protocol Summary ### App and Protocol Summary
As you may know from our previous updates, the LBRY app is undergoing a redesign which is taking up a large chunk of the team’s time but the app team is aiming to release a patch to version 0.20 which brings a few bug fixes, an updated LBRY protocol version and possibly a new feature or two (spee.ch thumbnail uploads from within the app, automated subscription downloads). As you may know from our previous updates, the LBRY app is undergoing a redesign which is taking up a large chunk of the team’s time but the app team is aiming to release a patch to version 0.20 which brings a few bug fixes, an updated LBRY protocol version and possibly a new feature or two (spee.ch thumbnail uploads from within the app, automated subscription downloads).
@ -30,14 +30,14 @@ After this round of protocol enhancements, the team will be focusing on improvin
Stay tuned for an updated version of the LBRY app next week! In the meantime, you can download the current version [here](https://lbry.io/get?auto=1) if you don’t have it installed already! Stay tuned for an updated version of the LBRY app next week! In the meantime, you can download the current version [here](https://lbry.io/get?auto=1) if you don’t have it installed already!
### App Redesign ### App Redesign
The LBRY App redesign continues to make great progress you can follow along on [GitHub](https://github.com/lbryio/lbry-app/issues/848) for the latest status and updates. The latest focus has been on refactoring the inner workings of the Publish page into a more optimized version using the React framework. We also have a community member, @btzr, who is helping out in migrating the dark theme into the new design. The LBRY App redesign continues to make great progress you can follow along on [GitHub](https://github.com/lbryio/lbry-desktop/issues/848) for the latest status and updates. The latest focus has been on refactoring the inner workings of the Publish page into a more optimized version using the React framework. We also have a community member, @btzr, who is helping out in migrating the dark theme into the new design.
Want to explore a web-based prototype of the new LBRY app design? Head over to [https://design.lbry.io](https://design.lbry.io) to get a preview of what’s to come. This page works best on a Desktop but may display correctly in landscape mode on mobile. *Please note: some of the design features like notifications and commenting are still experimental and most likely will not roll out with the first iteration of the re-design as they require additional support from the protocol to work properly.* Want to explore a web-based prototype of the new LBRY app design? Head over to [https://design.lbry.io](https://design.lbry.io) to get a preview of what’s to come. This page works best on a Desktop but may display correctly in landscape mode on mobile. *Please note: some of the design features like notifications and commenting are still experimental and most likely will not roll out with the first iteration of the re-design as they require additional support from the protocol to work properly.*
![App redesign early preview](https://spee.ch/1/app-redesign-preview.jpeg) ![App redesign early preview](https://spee.ch/1/app-redesign-preview.jpeg)
### Subscription Enhancements in Progress ### Subscription Enhancements in Progress
A new round of enhancements to the Subscription feature is being developed. The goal is to increase interactivity, engagement and notification for users who subscribe to channels on LBRY. This will include an option to automatically download new content as it is added to a channel as well as notification features within the app and email. Have questions or comments, drop us a line on the [GitHub issue](https://github.com/lbryio/lbry-app/issues/994). A new round of enhancements to the Subscription feature is being developed. The goal is to increase interactivity, engagement and notification for users who subscribe to channels on LBRY. This will include an option to automatically download new content as it is added to a channel as well as notification features within the app and email. Have questions or comments, drop us a line on the [GitHub issue](https://github.com/lbryio/lbry-desktop/issues/994).
### LBRY Mobile for Android ### LBRY Mobile for Android
LBRY recently worked with a user interface designer who came up with a very nice and simple design prototype, check out the video below for a preview. The process of incorporating this prototype into React Native code is underway. To solve delays deploying the app changes, we had to come up with a way to build the UI and daemon separately, such that the React Native app can be reloaded without having to rebuild the daemon each time (slow!). This enables testing the UI changes relatively quickly against any stable or development build of the daemon. There is a good chance that we will have a basic working mobile Android app in a few weeks! LBRY recently worked with a user interface designer who came up with a very nice and simple design prototype, check out the video below for a preview. The process of incorporating this prototype into React Native code is underway. To solve delays deploying the app changes, we had to come up with a way to build the UI and daemon separately, such that the React Native app can be reloaded without having to rebuild the daemon each time (slow!). This enables testing the UI changes relatively quickly against any stable or development build of the daemon. There is a good chance that we will have a basic working mobile Android app in a few weeks!

2
content/news/164-if-you-still-havent-found-what-youre-searching-for.md
View file

@ -15,4 +15,4 @@ Users will also get a popup notification when a new video is added to a channel
We've upgraded the LBRY Protocol from version 0.18.2 to 0.19.1., which should improve reliability and help download performance and a number of other back-end processes. Get caught up on all changes in the release notes for [0.19.0](https://github.com/lbryio/lbry/releases/tag/v0.19.) and [0.19.1](https://github.com/lbryio/lbry/releases/tag/v0.19.1). We've upgraded the LBRY Protocol from version 0.18.2 to 0.19.1., which should improve reliability and help download performance and a number of other back-end processes. Get caught up on all changes in the release notes for [0.19.0](https://github.com/lbryio/lbry/releases/tag/v0.19.) and [0.19.1](https://github.com/lbryio/lbry/releases/tag/v0.19.1).
You can read the [full release notes for v0.21.2 here](https://github.com/lbryio/lbry-app/releases). And if you haven't downloaded the app yet, [what are you waiting for](https://lbry.io/get?auto=1)? You can read the [full release notes for v0.21.2 here](https://github.com/lbryio/lbry-desktop/releases). And if you haven't downloaded the app yet, [what are you waiting for](https://lbry.io/get?auto=1)?

12
content/news/165-lbry-development-community-update-Mar-2018.md
View file

@ -15,7 +15,7 @@ To skip the tech stuff and see what’s happened and what’s next in the LBRY c
[Skip to **Community Happenings**](#com-updates) [Skip to **Community Happenings**](#com-updates)
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://LBRY.tech, which is not live yet, but you can check out our progress on [GitHub](https://github.com/lbryio/lbry.tech). All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://LBRY.tech, which is not live yet, but you can check out our progress on [GitHub](https://github.com/lbryio/lbry.tech).
### App and Protocol Summary ### App and Protocol Summary
We know it's been a long wait, but we're very happy with our latest app release. And the wait will be worth it when you experience the improved LBRY daemon - it's the first major protocol update since last November, and it's a big step in the right direction. You can read about specific enhancements in the changelogs ([0.19.0](https://github.com/lbryio/lbry/releases/tag/v0.19.0) and [0.19.1](https://github.com/lbryio/lbry/releases/tag/v0.19.1)) but in general we’ve noticed improvements in network availability and streaming speed (time from when play is clicked to when the download starts). We know it's been a long wait, but we're very happy with our latest app release. And the wait will be worth it when you experience the improved LBRY daemon - it's the first major protocol update since last November, and it's a big step in the right direction. You can read about specific enhancements in the changelogs ([0.19.0](https://github.com/lbryio/lbry/releases/tag/v0.19.0) and [0.19.1](https://github.com/lbryio/lbry/releases/tag/v0.19.1)) but in general we’ve noticed improvements in network availability and streaming speed (time from when play is clicked to when the download starts).
@ -43,7 +43,7 @@ Other enhancements include improved results with partial search terms and a bett
If you run into search issues while testing the app or not happy with search results, give us some feedback on [GitHub](https://github.com/lbryio/lighthouse/issues)! If you run into search issues while testing the app or not happy with search results, give us some feedback on [GitHub](https://github.com/lbryio/lighthouse/issues)!
### App Redesign {#redesign-updates} ### App Redesign {#redesign-updates}
The LBRY app redesign has been merged into the master branch and is available to [run from source](https://github.com/lbryio/lbry-app) for those interested in checking out an early preview. We have identified a number of issues which block a release candidate from being built yet and they are marked with a [redesign label](https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3Aredesign) on the issues page. Before submitting any new design related issues, be sure to review those first. We are extremely excited and eager to get the redesign into the hands of community members, stay tuned! The LBRY app redesign has been merged into the master branch and is available to [run from source](https://github.com/lbryio/lbry-desktop) for those interested in checking out an early preview. We have identified a number of issues which block a release candidate from being built yet and they are marked with a [redesign label](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aissue+is%3Aopen+label%3Aredesign) on the issues page. Before submitting any new design related issues, be sure to review those first. We are extremely excited and eager to get the redesign into the hands of community members, stay tuned!
![App-preview](https://spee.ch/c/app-preview.jpeg) ![App-preview](https://spee.ch/c/app-preview.jpeg)
@ -53,11 +53,11 @@ Channel subscriptions give users a reason to return to the LBRY app on a daily o
### Cool App Features in the Pipeline {#features-update} ### Cool App Features in the Pipeline {#features-update}
Check out the below pull requests to get a sense of a few exciting features coming to the LBRY app. Check out the below pull requests to get a sense of a few exciting features coming to the LBRY app.
[Spee.ch URL Links](https://github.com/lbryio/lbry-app/pull/1222) - This will allow creators and consumers to quickly share a https://spee.ch URL for content or channels they find in the LBRY app. This will be available for free content that’s an image/video/GIF and for all channels. [Spee.ch URL Links](https://github.com/lbryio/lbry-desktop/pull/1222) - This will allow creators and consumers to quickly share a https://spee.ch URL for content or channels they find in the LBRY app. This will be available for free content that’s an image/video/GIF and for all channels.
[Ability to update thumbnail to spee.ch from Publish screen](https://github.com/lbryio/lbry-app/pull/1248) - A common frustration among publishers is having to upload their thumbnails on spee.ch separately or using another website to do so. With this enhancement, the LBRY app will allow direct thumbnail uploading to spee.ch which will significantly increase the publisher experience. [Ability to update thumbnail to spee.ch from Publish screen](https://github.com/lbryio/lbry-desktop/pull/1248) - A common frustration among publishers is having to upload their thumbnails on spee.ch separately or using another website to do so. With this enhancement, the LBRY app will allow direct thumbnail uploading to spee.ch which will significantly increase the publisher experience.
[Auto Updating channels on the LBRY Discover page](https://github.com/lbryio/lbry-app/pull/1267) - Currently the LBRY discover page is fairly static besides the trending and community sections (or when we update the page with featured content). This change will allow us to specify a channel name instead of specific claims to include on the Discover page. The main benefit is that the Discover page will dynamically update when new content is posted to those channels! [Auto Updating channels on the LBRY Discover page](https://github.com/lbryio/lbry-desktop/pull/1267) - Currently the LBRY discover page is fairly static besides the trending and community sections (or when we update the page with featured content). This change will allow us to specify a channel name instead of specific claims to include on the Discover page. The main benefit is that the Discover page will dynamically update when new content is posted to those channels!
### spee.ch Update ### spee.ch Update
Over the past few weeks, we’ve been converting the code base of spee.ch so that it can be imported and customized in a variety of applications. Keep an eye out for an announcement soon which will fully explain how you can use the spee.ch code base to implement your own content hosting web app that uses the LBRY network! Want to get a headstart? Check out the [spee.ch server section below](#speech-host) and subscribe to our [speech admin mailing list](https://lbry.io/speech-admin) to be notified when we schedule a live Google Hangouts demo which will walk through the process of setting up your own portal. Over the past few weeks, we’ve been converting the code base of spee.ch so that it can be imported and customized in a variety of applications. Keep an eye out for an announcement soon which will fully explain how you can use the spee.ch code base to implement your own content hosting web app that uses the LBRY network! Want to get a headstart? Check out the [spee.ch server section below](#speech-host) and subscribe to our [speech admin mailing list](https://lbry.io/speech-admin) to be notified when we schedule a live Google Hangouts demo which will walk through the process of setting up your own portal.
@ -88,7 +88,7 @@ Significant progress has been made on the white paper and a first draft is very
Wallet encryption has been implemented on the daemon but is not yet available in the LBRY app. If you want to use this feature ASAP, check out the [CLI](https://lbryio.github.io/lbry/cli/#wallet_encrypt) documentation - the wallet will need to be [unlocked](https://lbryio.github.io/lbry/cli/#wallet_unlock) manually before app startup. Feel free to reach out on Discord with any questions! Wallet encryption has been implemented on the daemon but is not yet available in the LBRY app. If you want to use this feature ASAP, check out the [CLI](https://lbryio.github.io/lbry/cli/#wallet_encrypt) documentation - the wallet will need to be [unlocked](https://lbryio.github.io/lbry/cli/#wallet_unlock) manually before app startup. Feel free to reach out on Discord with any questions!
The UI redesign was recently merged on our lbry-app repo and we should have a release candidate to share with early testers this/next week. See [App Redesign development update above](#redesign-updates). The UI redesign was recently merged on our lbry-desktop repo and we should have a release candidate to share with early testers this/next week. See [App Redesign development update above](#redesign-updates).
And last but not least, the Search algorithm has undergone a number of optimizations (see [search update above](#search-updates)) which have added up to much better search results - give it a shot and let us know what you think! There's still a lot more work to do here when categories and tags come online, and we need your feedback! And last but not least, the Search algorithm has undergone a number of optimizations (see [search update above](#search-updates)) which have added up to much better search results - give it a shot and let us know what you think! There's still a lot more work to do here when categories and tags come online, and we need your feedback!

6
content/news/167-lbry-development-community-update-Apr-2018.md
View file

@ -14,10 +14,10 @@ To skip the tech stuff, see what’s happened and what’s next in the LBRY comm
[Skip to **Community Happenings**](#com-updates) [Skip to **Community Happenings**](#com-updates)
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next month, we’ll be releasing a technical reference site which will be developer focused at [https://LBRY.tech](#lbry-tech). All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next month, we’ll be releasing a technical reference site which will be developer focused at [https://LBRY.tech](#lbry-tech).
### App and Protocol Summary ### App and Protocol Summary
Due to travel time for and participation at [LBRY’s All Hands](#all-hands) gathering, development activities were on the lighter side this past month. The app team released version [0.21.3](https://github.com/lbryio/lbry-app/releases/tag/v0.21.3) which included a small patch to block content deemed infringing according to DMCA laws (see next section for more information). Otherwise, the main focus on the app side has been on testing and bug squashing on the [redesign](#redesign-updates). Part of this effort was spent on separating out the [lbry-redux](https://github.com/lbryio/lbry-redux) code into its own repository so that the the mobile and desktop apps can re-use redux states and functionality. We ran into a few quirks during this process but we were able to get things running smoothly! Due to travel time for and participation at [LBRY’s All Hands](#all-hands) gathering, development activities were on the lighter side this past month. The app team released version [0.21.3](https://github.com/lbryio/lbry-desktop/releases/tag/v0.21.3) which included a small patch to block content deemed infringing according to DMCA laws (see next section for more information). Otherwise, the main focus on the app side has been on testing and bug squashing on the [redesign](#redesign-updates). Part of this effort was spent on separating out the [lbry-redux](https://github.com/lbryio/lbry-redux) code into its own repository so that the the mobile and desktop apps can re-use redux states and functionality. We ran into a few quirks during this process but we were able to get things running smoothly!
On the Protocol side of the house, [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) is undergoing refactoring and improvements to the way blob announcement is handled and other DHT enhancements around peer availability. We were able to bring the blob announce times from 1 or 2 per second, to 25 per second (our target is 100 per second!). With these changes, our team hopes to improve the consistency of content availability on the network. A fair amount of time was also spent identifying and fixing our reflector servers to ensure that content uploaded by users is passed correctly to our content nodes. Before these changes, certain content would not be reflected properly which resulted in unavailable content if the original uploader was not online. Finally, development efforts on both the client and server side of our [wallet functionality](#wallet) have been progressing nicely. On the Protocol side of the house, [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) is undergoing refactoring and improvements to the way blob announcement is handled and other DHT enhancements around peer availability. We were able to bring the blob announce times from 1 or 2 per second, to 25 per second (our target is 100 per second!). With these changes, our team hopes to improve the consistency of content availability on the network. A fair amount of time was also spent identifying and fixing our reflector servers to ensure that content uploaded by users is passed correctly to our content nodes. Before these changes, certain content would not be reflected properly which resulted in unavailable content if the original uploader was not online. Finally, development efforts on both the client and server side of our [wallet functionality](#wallet) have been progressing nicely.
@ -41,7 +41,7 @@ The majority of our effort on the spee.ch codebase has been to convert the [spee
### App Redesign {#redesign-updates} ### App Redesign {#redesign-updates}
Since our last update, we’ve squashed a number of critical bugs and the LBRY app redesign has moved into a release candidate phase where we’ve invited testers from our Discord community to perform more rigorous testing and gather additional feedback. Want to help out? Join us on [Discord](https://chat.lbry.io) and ask about becoming an early tester. In addition to previewing the redesign before its officially released, you can earn LBRY Credits by finding bugs or providing suggestions. Since our last update, we’ve squashed a number of critical bugs and the LBRY app redesign has moved into a release candidate phase where we’ve invited testers from our Discord community to perform more rigorous testing and gather additional feedback. Want to help out? Join us on [Discord](https://chat.lbry.io) and ask about becoming an early tester. In addition to previewing the redesign before its officially released, you can earn LBRY Credits by finding bugs or providing suggestions.
We’ve identified a number of issues which are marked with the [redesign label](https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3Aredesign) on GitHub. Before submitting any new design related issues, be sure to review those first. We’ve also identified show stoppers, which prevent a public release, with the [release-blocker tag](https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3Arelease-blocker) so you can have a better idea when it’s ready for primetime! We believe that a full release is near once these bugs are squashed, but you never know what new issues could creep up. We’ve identified a number of issues which are marked with the [redesign label](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aissue+is%3Aopen+label%3Aredesign) on GitHub. Before submitting any new design related issues, be sure to review those first. We’ve also identified show stoppers, which prevent a public release, with the [release-blocker tag](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aissue+is%3Aopen+label%3Arelease-blocker) so you can have a better idea when it’s ready for primetime! We believe that a full release is near once these bugs are squashed, but you never know what new issues could creep up.
![App-preview](https://spee.ch/8/redesign-dark.jpeg) ![App-preview](https://spee.ch/8/redesign-dark.jpeg)

8
content/news/172-lbry-development-community-update-May-2018.md
View file

@ -14,10 +14,10 @@ To skip the tech stuff, see what’s happened and what’s next in the LBRY comm
[Skip to **Community Happenings**](#com-updates) [Skip to **Community Happenings**](#com-updates)
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In June, we’ll be releasing [LBRY.tech](#lbry-tech), a technical reference / guide website which will be developer and contributor focused to drive more apps and services on top of LBRY. All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In June, we’ll be releasing [LBRY.tech](#lbry-tech), a technical reference / guide website which will be developer and contributor focused to drive more apps and services on top of LBRY.
### App and Protocol Summary ### App and Protocol Summary
The app team released a few patches on the pre-redesign version of the desktop app, you can find all the release notes on our [GitHub release page](https://github.com/lbryio/lbry-app/releases). The fixes/features in these patches allow us to rename the lbry-app repo to lbry-desktop, send emails with a link to open LBRY to various pages like the Rewards section of the app, prevent errors when opening invalid URLs, give us the ability to roll out new rewards like [Welcome Back to LBRY](#wb-reward), and provide a long-awaited daemon upgrade to [0.19.3](https://github.com/lbryio/lbry/releases/tag/v0.19.3) which enables faster blockchain sync. On the app redesign side of the fence, we’ve progressed to a 2nd round of community testing and are close to a final release, [read more below](#redesign-updates). The app team released a few patches on the pre-redesign version of the desktop app, you can find all the release notes on our [GitHub release page](https://github.com/lbryio/lbry-desktop/releases). The fixes/features in these patches allow us to rename the lbry-desktop repo to lbry-desktop, send emails with a link to open LBRY to various pages like the Rewards section of the app, prevent errors when opening invalid URLs, give us the ability to roll out new rewards like [Welcome Back to LBRY](#wb-reward), and provide a long-awaited daemon upgrade to [0.19.3](https://github.com/lbryio/lbry/releases/tag/v0.19.3) which enables faster blockchain sync. On the app redesign side of the fence, we’ve progressed to a 2nd round of community testing and are close to a final release, [read more below](#redesign-updates).
On the protocol side of the house, our engineers have been deep in the weeds with [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) tuning our DHT implementation in order to increase consistency and availability of P2P data. We’ve discovered and fixed a number of issues which should make the overall network run smoother. Peers now know when other peers are offline and drop them from their routing tables - something that was not being done previously. We’ve also improved the process to allow peers to connect to multiple hosts when searching for data. We are also making sure that these changes are backwards compatible with nodes on older versions, and expect to put out a release in the next week or two. For wallet server and client updates, see [below](#wallet). On the protocol side of the house, our engineers have been deep in the weeds with [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) tuning our DHT implementation in order to increase consistency and availability of P2P data. We’ve discovered and fixed a number of issues which should make the overall network run smoother. Peers now know when other peers are offline and drop them from their routing tables - something that was not being done previously. We’ve also improved the process to allow peers to connect to multiple hosts when searching for data. We are also making sure that these changes are backwards compatible with nodes on older versions, and expect to put out a release in the next week or two. For wallet server and client updates, see [below](#wallet).
@ -34,7 +34,7 @@ If you are eligible for [LBRY Rewards](https://lbry.io/faq/rewards), you may hav
![welcome back](https://spee.ch/7/welcome-back2.jpeg) ![welcome back](https://spee.ch/7/welcome-back2.jpeg)
### Pop-out Player ### Pop-out Player
A new community contributor, dan1d on Discord, has resurrected our efforts to bring a pop-out player to the LBRY app. Based on initial testing, he’s getting quite close to a finished 1.0 version of this and you can follow along with his [PR on GitHub](https://github.com/lbryio/lbry-app/pull/1523) to learn more. The last known bug that exists is a hiccup where the player goes back to a “waiting for metadata” state when switching from the claim page to pop out mode. If this can be fixed, we hope to include it with the app redesign release. The next steps in v2.0 would be to make it draggable to other parts of the screen. A new community contributor, dan1d on Discord, has resurrected our efforts to bring a pop-out player to the LBRY app. Based on initial testing, he’s getting quite close to a finished 1.0 version of this and you can follow along with his [PR on GitHub](https://github.com/lbryio/lbry-desktop/pull/1523) to learn more. The last known bug that exists is a hiccup where the player goes back to a “waiting for metadata” state when switching from the claim page to pop out mode. If this can be fixed, we hope to include it with the app redesign release. The next steps in v2.0 would be to make it draggable to other parts of the screen.
![popout](https://spee.ch/b/pop-out.png) ![popout](https://spee.ch/b/pop-out.png)
@ -44,7 +44,7 @@ Long time community developer, btzr on Discord, has made yet another great addit
![markdown](https://spee.ch/0/markdown-preview.jpeg) ![markdown](https://spee.ch/0/markdown-preview.jpeg)
### Autoplay Free and Downloaded media {#autoplay} ### Autoplay Free and Downloaded media {#autoplay}
A local Manchester, NH contributor, Travis, added the ability to autoplay free and downloaded media files to the LBRY app. This means that videos will start automatically and photos/other media will open when entering the claim page. By default, this setting will be shipped in an off state and users will be able to enable it on content pages or in the settings area. Looking to contribute? We want to make the styling fancier, and it’s a great place for a new developer to start - see this [GitHub issue](https://github.com/lbryio/lbry-app/issues/1539). A local Manchester, NH contributor, Travis, added the ability to autoplay free and downloaded media files to the LBRY app. This means that videos will start automatically and photos/other media will open when entering the claim page. By default, this setting will be shipped in an off state and users will be able to enable it on content pages or in the settings area. Looking to contribute? We want to make the styling fancier, and it’s a great place for a new developer to start - see this [GitHub issue](https://github.com/lbryio/lbry-desktop/issues/1539).
![autoplay](https://spee.ch/0/lbry-autoplay-redesign.jpeg) ![autoplay](https://spee.ch/0/lbry-autoplay-redesign.jpeg)

12
content/news/176-lbry-development-community-update-June-2018.md
View file

@ -33,7 +33,7 @@ To skip the tech stuff, see what’s happened and what’s next in the LBRY comm
# Development Updates {#dev-updates} # Development Updates {#dev-updates}
### App and Protocol Summary {#summary} ### App and Protocol Summary {#summary}
We are extremely excited to announce that the LBRY app redesign, codename Austen, was launched on June 26th! You can read [our blog post](https://lbry.io/news/austen) which details the most important updates in the new app and introduces the LBRY app naming system. Full release notes can be found on our [GitHub page](https://github.com/lbryio/lbry-app/releases/tag/v0.22.0) We are extremely excited to announce that the LBRY app redesign, codename Austen, was launched on June 26th! You can read [our blog post](https://lbry.io/news/austen) which details the most important updates in the new app and introduces the LBRY app naming system. Full release notes can be found on our [GitHub page](https://github.com/lbryio/lbry-desktop/releases/tag/v0.22.0)
For a deeper perspective of this process from the eyes of our lead developer Sean, check our his [blog post here](https://lbry.io/news/lbry-desktop-redesign). For a deeper perspective of this process from the eyes of our lead developer Sean, check our his [blog post here](https://lbry.io/news/lbry-desktop-redesign).
@ -47,7 +47,7 @@ To celebrate LBRY’s second birthday and the redesign launch, we’re DOUBLING
![redesign](https://spee.ch/0/redesign-reward.jpg) ![redesign](https://spee.ch/0/redesign-reward.jpg)
### File Renderer enhancements and 3D/PDF Support! ### File Renderer enhancements and 3D/PDF Support!
Community member [btzr](https://github.com/btzr-io) has been working on two PRs that greatly improve the LBRY app’s ability to support additional file types. First, the [File Renderer PR](https://github.com/lbryio/lbry-app/pull/1576) refactors the current code which will allow passing certain file types to different viewer types (i.e. if it’s a PDF, use a PDF viewer). To showcase this feature, he’s also added a [3D file viewer](https://github.com/lbryio/lbry-app/pull/1558) which currently supports previewing of STL files in-app! This will also be expanded to OBJ files in the future. Community member [btzr](https://github.com/btzr-io) has been working on two PRs that greatly improve the LBRY app’s ability to support additional file types. First, the [File Renderer PR](https://github.com/lbryio/lbry-desktop/pull/1576) refactors the current code which will allow passing certain file types to different viewer types (i.e. if it’s a PDF, use a PDF viewer). To showcase this feature, he’s also added a [3D file viewer](https://github.com/lbryio/lbry-desktop/pull/1558) which currently supports previewing of STL files in-app! This will also be expanded to OBJ files in the future.
![3D](https://spee.ch/b/3d-support.jpg) ![3D](https://spee.ch/b/3d-support.jpg)
@ -59,12 +59,12 @@ A big limitation in previous LBRY versions was related to search results - it wo
![search](https://spee.ch/d/search-results.jpg) ![search](https://spee.ch/d/search-results.jpg)
### Channels on Homepage, with CryptoCandor! ### Channels on Homepage, with CryptoCandor!
We are currently experimenting with a more dynamic LBRY Explore page with [@CryptoCandor’s](https://open.lbry.io/@CryptoCandor) channel which is updated as soon as she uploads new content. This is different from our previous approach where the rest of the homepage is static LBRY URLs as opposed to a specific channel. Once we improve [the UX around this experience](https://github.com/lbryio/lbry-app/issues/1717), we will be adding more channels to use this scheme. We are currently experimenting with a more dynamic LBRY Explore page with [@CryptoCandor’s](https://open.lbry.io/@CryptoCandor) channel which is updated as soon as she uploads new content. This is different from our previous approach where the rest of the homepage is static LBRY URLs as opposed to a specific channel. Once we improve [the UX around this experience](https://github.com/lbryio/lbry-desktop/issues/1717), we will be adding more channels to use this scheme.
![Candor](https://spee.ch/2/cryptocandor-channel.jpg) ![Candor](https://spee.ch/2/cryptocandor-channel.jpg)
### Easier way to find your wallet, Open Directory Button! ### Easier way to find your wallet, Open Directory Button!
We currently have a [GitHub PR](https://github.com/lbryio/lbry-app/pull/1638) in progress by a community member which will add a Open Wallet Directory button to the wallet backup page. This will make it easier for users to locate their wallet file. The change also includes an easy copy button to copy/paste the wallet directory. We currently have a [GitHub PR](https://github.com/lbryio/lbry-desktop/pull/1638) in progress by a community member which will add a Open Wallet Directory button to the wallet backup page. This will make it easier for users to locate their wallet file. The change also includes an easy copy button to copy/paste the wallet directory.
![Button](https://spee.ch/e/wallet-backup-button.jpg) ![Button](https://spee.ch/e/wallet-backup-button.jpg)
@ -81,7 +81,7 @@ Interested in running your own spee.ch server or clone? Check out the [quick sta
![speech publish time](https://spee.ch/4/speech-timing.jpg) ![speech publish time](https://spee.ch/4/speech-timing.jpg)
### Protocol - Improved Speed {#speed} ### Protocol - Improved Speed {#speed}
[Version 0.20.2](https://github.com/lbryio/lbry-app/releases/tag/v0.22.0) of the protocol greatly improved the LBRY app experience by speeding up resolve calls throughout the app. Resolve calls are used anytime the app needs information about a channel or claim, such as when the homepage is loaded or when you go into a channel. These changes brought the initial homepage load from about a minute down to 4 seconds!! This significantly improves the first run experience for new users as well as the channel browsing speeds. The fix was a combination of optimizing SQL queries along with adapting a faster cryptographic library which sped up verification of data. We hope this is one of many places that can still be further optimized in the LBRY ecosystem. [Version 0.20.2](https://github.com/lbryio/lbry-desktop/releases/tag/v0.22.0) of the protocol greatly improved the LBRY app experience by speeding up resolve calls throughout the app. Resolve calls are used anytime the app needs information about a channel or claim, such as when the homepage is loaded or when you go into a channel. These changes brought the initial homepage load from about a minute down to 4 seconds!! This significantly improves the first run experience for new users as well as the channel browsing speeds. The fix was a combination of optimizing SQL queries along with adapting a faster cryptographic library which sped up verification of data. We hope this is one of many places that can still be further optimized in the LBRY ecosystem.
![speed](https://spee.ch/a/protocol-timing.jpg) ![speed](https://spee.ch/a/protocol-timing.jpg)
@ -140,7 +140,7 @@ LBRY.tech is in the middle of a major overhaul - when we’re done, it will be e
![lbrytech publish](https://spee.ch/9/lbry-tech-publish.jpg) ![lbrytech publish](https://spee.ch/9/lbry-tech-publish.jpg)
# Want to develop on the LBRY protocol? # Want to develop on the LBRY protocol?
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next few weeks we’ll be releasing [lbry.tech](#lbry-tech), a technical reference / guide website which will be developer and contributor focused to drive more apps and services on top of LBRY. All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next few weeks we’ll be releasing [lbry.tech](#lbry-tech), a technical reference / guide website which will be developer and contributor focused to drive more apps and services on top of LBRY.
[Back to **Development Updates**](#dev-updates) [Back to **Development Updates**](#dev-updates)

2
content/news/35-why-doesnt-lbry-just-use-bitcoin.md
View file

@ -32,7 +32,7 @@ If LBRY starts growing exponentially, we don’t want to worry about contributin
One of the main draws of Bitcoin has always been its relative decentralization of control and independence from existing legal and financial systems. Similarly, using LBC as an “appcoin” gives LBRY some healthy autonomy from Bitcoin while allowing for the technical innovations explained above. One of the main draws of Bitcoin has always been its relative decentralization of control and independence from existing legal and financial systems. Similarly, using LBC as an “appcoin” gives LBRY some healthy autonomy from Bitcoin while allowing for the technical innovations explained above.
An appcoin, as described by LBRY’s Mike Vine on [Decentral Vancouver’s “#Blocktalk”](http://blog.lbry.io/lbry-app-sneak-peak-big-questions-answered-lbry-on-blocktalk-last-night/) and in [CoinTelegraph](http://cointelegraph.com/news/the-appcoin-revolution-interview-with-mike-vine-of-lbry), is a cryptocurrency that is designed specifically to power an application, with only that application’s precise functions in mind. The purpose of this appcoin is not to compete for a better form of money than Bitcoin, but to function as a special purpose tool in ways Bitcoin cannot. Creating a special tool in the form of a new coin allows us to start fresh, customizing features like the initial allocation and blockchain rules. An appcoin, as described by LBRY’s Mike Vine on [Decentral Vancouver’s “#Blocktalk”](http://blog.lbry.io/lbry-desktop-sneak-peak-big-questions-answered-lbry-on-blocktalk-last-night/) and in [CoinTelegraph](http://cointelegraph.com/news/the-appcoin-revolution-interview-with-mike-vine-of-lbry), is a cryptocurrency that is designed specifically to power an application, with only that application’s precise functions in mind. The purpose of this appcoin is not to compete for a better form of money than Bitcoin, but to function as a special purpose tool in ways Bitcoin cannot. Creating a special tool in the form of a new coin allows us to start fresh, customizing features like the initial allocation and blockchain rules.
In the early days of our protocol, LBRY Inc. will be making a concerted effort to deploy LBC in a non-neutral way. We will be incentivizing early adopters, amazing content publishers, and even nonprofits which share our vision of a free and open internet. We will be retaining a portion to finance the continued development of the ecosystem. LBRY Credits will work on behalf of development of the LBRY content distribution network, not the other way around. In the early days of our protocol, LBRY Inc. will be making a concerted effort to deploy LBC in a non-neutral way. We will be incentivizing early adopters, amazing content publishers, and even nonprofits which share our vision of a free and open internet. We will be retaining a portion to finance the continued development of the ecosystem. LBRY Credits will work on behalf of development of the LBRY content distribution network, not the other way around.

6
lib/thirdparty/Github.class.php vendored
View file

@ -25,7 +25,7 @@ class Github
public static function getAppRelease($cache = true) public static function getAppRelease($cache = true)
{ {
try { try {
return static::get('/repos/lbryio/lbry-app/releases/latest', [], $cache); return static::get('/repos/lbryio/lbry-desktop/releases/latest', [], $cache);
} catch (Exception $e) { } catch (Exception $e) {
} }
@ -48,7 +48,7 @@ class Github
public static function getAppPrereleaseDownloadUrl($os, $cache = true) public static function getAppPrereleaseDownloadUrl($os, $cache = true)
{ {
try { try {
$releases = static::get('/repos/lbryio/lbry-app/releases', [], $cache); $releases = static::get('/repos/lbryio/lbry-desktop/releases', [], $cache);
if (count($releases)) { if (count($releases)) {
$asset = static::findReleaseAssetForOs($releases[0], $os); $asset = static::findReleaseAssetForOs($releases[0], $os);
return $asset ? $asset['browser_download_url'] : null; return $asset ? $asset['browser_download_url'] : null;
@ -103,7 +103,7 @@ class Github
$sets = []; $sets = [];
$allReleases = []; $allReleases = [];
$projects = ['lbry' => 'LBRY Protocol', 'lbry-app' => 'LBRY App']; $projects = ['lbry' => 'LBRY Protocol', 'lbry-desktop' => 'LBRY App'];
foreach ($projects as $project => $projectLabel) { foreach ($projects as $project => $projectLabel) {
$page = 1; $page = 1;

2
view/template/developer/_quickstartCredits.php
View file

@ -62,7 +62,7 @@
<h3>Try the UI</h3> <h3>Try the UI</h3>
<p>LBRY comes with a fully-featured UI so that normal people can use it too. You can download it <a href="https://github.com/lbryio/lbry-app/releases" class="link-primary">here</a>.</p> <p>LBRY comes with a fully-featured UI so that normal people can use it too. You can download it <a href="https://github.com/lbryio/lbry-desktop/releases" class="link-primary">here</a>.</p>
<h3 id="community">You Did It! What's Next?</h3> <h3 id="community">You Did It! What's Next?</h3>
<p> <p>
Start building something awesome! LBRY works as a discovery and distribution backend for everything from films to CAD files. Start building something awesome! LBRY works as a discovery and distribution backend for everything from films to CAD files.

4
view/template/download/_downloadButton.php
View file

@ -27,11 +27,11 @@
<?php if ($os === OS::OS_LINUX): ?> <?php if ($os === OS::OS_LINUX): ?>
<div class="meta"> <div class="meta">
Works with Ubuntu, Debian, or any distro with <code>apt</code> or <code>dpkg</code>. Works with Ubuntu, Debian, or any distro with <code>apt</code> or <code>dpkg</code>.
For other Linux flavors, <a href="https://github.com/lbryio/lbry-app" class="link-primary">see the source</a>. For other Linux flavors, <a href="https://github.com/lbryio/lbry-desktop" class="link-primary">see the source</a>.
</div> </div>
<?php elseif ($sourceLink): ?> <?php elseif ($sourceLink): ?>
<div class="meta"> <div class="meta">
Like source code? Go <a href="https://github.com/lbryio/lbry-app" class="link-primary">here</a>.<P><P> Like source code? Go <a href="https://github.com/lbryio/lbry-desktop" class="link-primary">here</a>.<P><P>
</div> </div>
<?php endif ?> <?php endif ?>
<?php endif ?> <?php endif ?>

4
view/template/page/join-us.php
View file

@ -110,12 +110,12 @@
</tr> </tr>
<tr> <tr>
<td class="center"> <td class="center">
<a href="https://github.com/lbryio/lbry-app">lbry-desktop</a><br/> <a href="https://github.com/lbryio/lbry-desktop">lbry-desktop</a><br/>
<a href="https://github.com/lbryio/lbry-android">lbry-android</a><br/> <a href="https://github.com/lbryio/lbry-android">lbry-android</a><br/>
<a href="https://github.com/lbryio/spee.ch">spee.ch</a> <a href="https://github.com/lbryio/spee.ch">spee.ch</a>
</td> </td>
<td class="center">Lead Application Engineer</td> <td class="center">Lead Application Engineer</td>
<td class="center"><a href="https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issues</a></td> <td class="center"><a href="https://github.com/lbryio/lbry-desktop/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issues</a></td>
</tr> </tr>
<tr> <tr>
<td class="center"><em>(not public)</em></td> <td class="center"><em>(not public)</em></td>