LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

Initial commit

Browse source
This commit is contained in:
ポール ウェッブ 2019-03-19 17:56:32 -05:00
parent 832c502cf5
commit c906e8498c
20 changed files with 59 additions and 59 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.env.sample
View file

@ -6,7 +6,7 @@ DAEMON_URL=
# /developer-program
GITHUB_APP_ID=
GITHUB_APP_SECRET=
REWARD_URL=api.lbry.io
REWARD_URL=api.lbry.com
# https://developer.github.com/apps/building-oauth-apps/creating-an-oauth-app
# We use this to show the GitHub feed on the homepage

2
CONTRIBUTING.md
View file

@ -1,6 +1,6 @@
# Contributing
This project follows the global contributing standards for all LBRY projects, to read those go [here](https://lbry.io/faq/contributing).
This project follows the global contributing standards for all LBRY projects, to read those go [here](https://lbry.com/faq/contributing).
You can contribute to this project by [creating a pull request](https://help.github.com/articles/creating-a-pull-request).

6
README.md
View file

@ -5,7 +5,7 @@
</div>
<div align="center">
Technical documentation website for <a href="https://lbry.io">the LBRY protocol</a>.
Technical documentation website for <a href="https://lbry.com">the LBRY protocol</a>.
</div>
<div align="center">
@ -56,9 +56,9 @@ For more details, see [CONTRIBUTING.md](CONTRIBUTING.md).
This project is MIT licensed. For the full license, see [LICENSE](LICENSE).
## Security
We take security seriously. Please contact [security@lbry.io](mailto:security@lbry.io) regarding any security issues.
We take security seriously. Please contact [security@lbry.com](mailto:security@lbry.com) regarding any security issues.
[Our PGP key is here](https://keybase.io/lbry/key.asc) if you need it.
## Contact
The primary contact for this project is [@netoperatorwibby](https://github.com/netoperatorwibby) (paul@lbry.io).
The primary contact for this project is [@netoperatorwibby](https://github.com/netoperatorwibby) (paul@lbry.com).

4
app/components/client/devprogram-scripts.js
View file

@ -60,7 +60,7 @@ function syncWithApi(data) { // eslint-disable-line no-unused-vars
document.querySelector("developer-program").innerHTML =
"<p><strong>There was an issue with accessing GitHub's API. Please try again later.</strong></p>";
fetch(`https://api.lbry.io/reward/new?github_token=${code}&reward_type=github_developer&wallet_address=${address}`)
fetch(`https://api.lbry.com/reward/new?github_token=${code}&reward_type=github_developer&wallet_address=${address}`)
.then(response => response.json())
.then(result => {
switch(true) {
@ -72,7 +72,7 @@ function syncWithApi(data) { // eslint-disable-line no-unused-vars
case result.success:
result = result.data;
document.querySelector("developer-program").innerHTML =
`<p><strong>Success!</strong> Your wallet has been credited with ${result.reward_amount} LBC.</p><p>We have a great reference for the <a href="/api/sdk">LBRY SDK here</a> to help you get started.</p><p>You can see proof of this transaction on <a href="https://explorer.lbry.io/tx/${result.transaction_id}">our Blockchain Explorer</a>.</p>`;
`<p><strong>Success!</strong> Your wallet has been credited with ${result.reward_amount} LBC.</p><p>We have a great reference for the <a href="/api/sdk">LBRY SDK here</a> to help you get started.</p><p>You can see proof of this transaction on <a href="https://explorer.lbry.com/tx/${result.transaction_id}">our Blockchain Explorer</a>.</p>`;
break;
default:

6
app/components/feature-links.js
View file

@ -6,12 +6,12 @@
const links = [
{
href: "https://chat.lbry.io",
href: "https://chat.lbry.com",
image: "https://spee.ch/b432346bfd641990f3dc3dbceda057b4ededa360/discord-bg.jpg",
title: "Chat (Discord)"
},
{
href: "https://discourse.lbry.io",
href: "https://discourse.lbry.com",
image: "https://spee.ch/e59dcbe6a533934eb82e73bb335b7e43cb8a9f7d/atmosphere.png",
title: "Developer Forum"
},
@ -26,7 +26,7 @@ const links = [
title: "Reddit"
},
{
href: "https://lbry.io/join-us",
href: "https://lbry.com/join-us",
image: "https://spee.ch/6db68b3ebf22386fcd9d04237d11bfaff5ba2a95/minimalisticrubikcube.png",
title: "Join Our Team"
},

2
app/components/footer.js
View file

@ -29,7 +29,7 @@ export default state => {
<div class="inner-wrap">
<ul>
<li>
<a href="//${process.env.NODE_ENV === "development" ? "localhost:8000" : "lbry.io"}" title="Rediscover content freedom">← LBRY.io</a> |
<a href="//${process.env.NODE_ENV === "development" ? "localhost:8000" : "lbry.com"}" title="Rediscover content freedom">← LBRY.io</a> |
${editLink(state.href)}
</li>

2
app/components/navigation.js
View file

@ -15,7 +15,7 @@ export default currentUrl => {
{
name: "LBRY.io",
title: "Escape the techno scene",
url: process.env.NODE_ENV === "development" ? "http://localhost:8000" : "https://lbry.io"
url: process.env.NODE_ENV === "development" ? "http://localhost:8000" : "https://lbry.com"
},
{
name: "Overview",

2
app/dist/humans.txt vendored
View file

@ -7,7 +7,7 @@ Paul Anthony Webb - Creator, Designer, and Developer
/* THANKS */
LBRY - https://lbry.io
LBRY - https://lbry.com
Viewers like you

6
app/helpers/fetch-metadata.js
View file

@ -280,11 +280,11 @@ function memePublishMessaging(source) {
<br/><br/>
To see Proof of Work (lol) that your meme is on the LBRY blockchain, <a href="https://explorer.lbry.io/tx/${source.result.output.txid}?address=${source.result.claim_address}" rel="noopener noreferrer" target="_blank" title="Your meme, on our blockchain explorer">check it out</a> on our blockchain explorer! Please note that it may take a couple minutes for the transaction to be confirmed.
To see Proof of Work (lol) that your meme is on the LBRY blockchain, <a href="https://explorer.lbry.com/tx/${source.result.output.txid}?address=${source.result.claim_address}" rel="noopener noreferrer" target="_blank" title="Your meme, on our blockchain explorer">check it out</a> on our blockchain explorer! Please note that it may take a couple minutes for the transaction to be confirmed.
<br/><br/>
You can also check out your meme (once the transaction is confirmed) on <a href="https://open.lbry.io/${source.result.lbrytech_claim_name}#${source.result.claim_id}" rel="noopener noreferrer" target="_blank" title="Your meme, on LBRY">LBRY</a> or <a href="https://spee.ch/${source.result.claim_id}/${source.result.lbrytech_claim_name}" rel="noopener noreferrer" target="_blank" title="Your meme, on spee.ch">Spee.ch</a>!
You can also check out your meme (once the transaction is confirmed) on <a href="https://open.lbry.com/${source.result.lbrytech_claim_name}#${source.result.claim_id}" rel="noopener noreferrer" target="_blank" title="Your meme, on LBRY">LBRY</a> or <a href="https://spee.ch/${source.result.claim_id}/${source.result.lbrytech_claim_name}" rel="noopener noreferrer" target="_blank" title="Your meme, on spee.ch">Spee.ch</a>!
</p>
<br/>
@ -294,7 +294,7 @@ function memePublishMessaging(source) {
function tipCompletionMessaging(source) {
return `
<p class="playground__description success">
If you want proof of the tip you just gave on behalf of LBRY, <a href="https://explorer.lbry.io/tx/${source.result.txid}" rel="noopener noreferrer" target="_blank" title="Your tip, on our blockchain explorer">check it out</a> on our blockchain explorer! Please note that it may take a couple minutes for the transaction to be confirmed.
If you want proof of the tip you just gave on behalf of LBRY, <a href="https://explorer.lbry.com/tx/${source.result.txid}" rel="noopener noreferrer" target="_blank" title="Your tip, on our blockchain explorer">check it out</a> on our blockchain explorer! Please note that it may take a couple minutes for the transaction to be confirmed.
</p><br/>
`;
}

6
app/sass/partials/_navigation.scss
View file

@ -65,7 +65,7 @@
flex: 1;
}
&:not(:first-of-type):not([href="http://localhost:8000"]):not([href="https://lbry.io"]) {
&:not(:first-of-type):not([href="http://localhost:8000"]):not([href="https://lbry.com"]) {
&::after {
width: 100%; height: 3px;
left: 0;
@ -96,13 +96,13 @@
line-height: 4rem;
}
&:not([href="http://localhost:8000"]):not([href="https://lbry.io"]) {
&:not([href="http://localhost:8000"]):not([href="https://lbry.com"]) {
padding-right: 0.5rem;
padding-left: 0.5rem;
}
&[href="http://localhost:8000"],
&[href="https://lbry.io"] {
&[href="https://lbry.com"] {
color: $lbry-white;
margin-right: 0.5rem;
padding-right: 1rem;

4
app/sockets.js
View file

@ -351,7 +351,7 @@ function getGitHubUserToken(socket) {
async function getTrendingContent() {
try {
const response = await got("https://api.lbry.io/file/list_trending");
const response = await got("https://api.lbry.com/file/list_trending");
return JSON.parse(response.body); // eslint-disable-line padding-line-between-statements
} catch(error) {
return error;
@ -380,7 +380,7 @@ async function newsletterSubscribe(data, socket) {
}
try {
await got.post(`https://api.lbry.io/list/subscribe?email=${encodeURIComponent(email)}&tag=developer`);
await got.post(`https://api.lbry.com/list/subscribe?email=${encodeURIComponent(email)}&tag=developer`);
return send(socket, {
html: "Thank you! Please confirm subscription in your inbox.",

4
app/views/home.js
View file

@ -86,8 +86,8 @@ export default () => html`
<p>There's literally <a href="https://spee.ch/@lbrytech/dozens.mp4">12<sup>n</sup></a> of us.</p>
<ul>
<li><a href="//chat.lbry.io" title="LBRY on Discord">Chat</a></li>
<li><a href="//discourse.lbry.io" title="LBRY on Discourse">Forum</a></li>
<li><a href="//chat.lbry.com" title="LBRY on Discord">Chat</a></li>
<li><a href="//discourse.lbry.com" title="LBRY on Discourse">Forum</a></li>
<li><a href="//www.reddit.com/r/lbry" title="LBRY on Reddit">Reddit</a></li>
</ul>
</div>

20
documents/build.md
View file

@ -184,9 +184,9 @@ You can download the latest version from the [releases page](https://github.com/
| OS | URL |
| --- | --- |
| Linux | [lbry.io/releases/lbry.deb](https://lbry.io/releases/lbry.deb) |
| macOS | [lbry.io/releases/lbry.dmg](https://lbry.io/releases/lbry.dmg) |
| Windows | [lbry.io/releases/lbry.exe](https://lbry.io/releases/lbry.exe) |
| Linux | [lbry.com/releases/lbry.deb](https://lbry.com/releases/lbry.deb) |
| macOS | [lbry.com/releases/lbry.dmg](https://lbry.com/releases/lbry.dmg) |
| Windows | [lbry.com/releases/lbry.exe](https://lbry.com/releases/lbry.exe) |
#### Using the SDK
@ -208,9 +208,9 @@ You can download the latest version from the [releases page](https://github.com/
| OS | URL |
| --- | --- |
| Linux | [lbry.io/releases/chainquery.deb](https://lbry.io/releases/chainquery.deb) |
| macOS | [lbry.io/releases/chainquery.dmg](https://lbry.io/releases/chainquery.dmg) |
| Windows | [lbry.io/releases/chainquery.exe](https://lbry.io/releases/chainquery.exe) |
| Linux | [lbry.com/releases/chainquery.deb](https://lbry.com/releases/chainquery.deb) |
| macOS | [lbry.com/releases/chainquery.dmg](https://lbry.com/releases/chainquery.dmg) |
| Windows | [lbry.com/releases/chainquery.exe](https://lbry.com/releases/chainquery.exe) |
Note: chainquery has both 32-bit and 64-bit builds, which the redirect URLs do not handle. Check the [releases page](https://github.com/lbryio/chainquery/releases) to ensure you get the right one.
@ -228,9 +228,9 @@ You can download the latest version from the [releases page](https://github.com/
| OS | URL |
| --- | --- |
| Linux | [lbry.io/releases/lbrycrd.deb](https://lbry.io/releases/lbrycrd.deb) |
| macOS | [lbry.io/releases/lbrycrd.dmg](https://lbry.io/releases/lbrycrd.dmg) |
| Windows | [lbry.io/releases/lbrycrd.exe](https://lbry.io/releases/lbrycrd.exe) |
| Linux | [lbry.com/releases/lbrycrd.deb](https://lbry.com/releases/lbrycrd.deb) |
| macOS | [lbry.com/releases/lbrycrd.dmg](https://lbry.com/releases/lbrycrd.dmg) |
| Windows | [lbry.com/releases/lbrycrd.exe](https://lbry.com/releases/lbrycrd.exe) |
#### Using lbrycrd
@ -246,7 +246,7 @@ A full list of methods is available [here](https://lbry.tech/api/blockchain).
Trouble? Questions? Want to share your progress? Interact with other devs!
- Join the #dev channel [in our chat](https://chat.lbry.io)
- Join the #dev channel [in our chat](https://chat.lbry.com)
- Introduce yourself or ask a question in [the forum](https://forum.lbry.tech/).
- Every LBRY repository on our [GitHub](https://github.com/lbryio) contains contact information for the maintainer.

12
documents/contribute.md
View file

@ -39,7 +39,7 @@ If you want to contribute to LBRY, there's definitely something for you! The fir
| Domain | Language (Toolset) | What Is It
--- | --- | ---
| [lbry.tech](https://github.com/lbryio/lbry.tech) | JavaScript (Node, Choo) | You're on it.
| [lbry.io](https://github.com/lbryio/lbry.io) | PHP (vanilla) | A website for LBRY end-users and creators.
| [lbry.com](https://github.com/lbryio/lbry.com) | PHP (vanilla) | A website for LBRY end-users and creators.
| [lbry.fund](https://github.com/lbryio/lbry.fund) | HTML | A website for receiving funding from LBRY, Inc.
### Auxiliary Services and Applications
@ -56,7 +56,7 @@ Several hundred extremely good-looking, wise and moral people, as well as our CT
### How To Contribute Code
1. **Join the Community**. By joining our [chat](https://chat.lbry.io) or our [forum](https://discourse.lbry.io), you can interact with other developers when you have questions, ideas, or problems.
1. **Join the Community**. By joining our [chat](https://chat.lbry.com) or our [forum](https://discourse.lbry.com), you can interact with other developers when you have questions, ideas, or problems.
1. **Identify the component you want to work on**. LBRY has code bases that deal with everything from cryptography and distributed systems to end-user graphic user-interfaces. We use Python, JavaScript, C++, Go, and more. See [ecosystem overview](#ecosystem-overview) to find the right project.
1. **Get set up.** Each repo has a [[README]] with clear instructions on how to get the repo up and running properly. Thanks, [Repository Standards](https://lbry.tech/resources/repository-standards)!
1. **Find something to work on**. All actively developed repositories should have issues tagged "Good First Issues" specifically for new contributors. You are also welcome to work on something not currently filed if you have your own idea. Additionally, all repositories have contact information for the maintainer if you have trouble finding an issue to work on.
@ -68,7 +68,7 @@ Several hundred extremely good-looking, wise and moral people, as well as our CT
Web and application designers are requested to be able to work directly on CSS in the project they'd be contributing to. Please follow the [Coding](#coding) instructions for any website or application you want to improve.
We're happy to provide assistance if you're used to working in HTMl and CSS but are having trouble getting started. Check out [our chat](https://chat.lbry.io) or [our forum](https://discourse.lbry.io).
We're happy to provide assistance if you're used to working in HTMl and CSS but are having trouble getting started. Check out [our chat](https://chat.lbry.com) or [our forum](https://discourse.lbry.com).
## Writing
@ -87,8 +87,8 @@ A number of our code bases ([[lbrycrd]], [[lbry-sdk]], all applications, more...
### Ways to Test
- "Watch" the repo on GitHub. You will receive an email with release notes whenever a release candidate is out and you can [raise an issue](#raising-issues).
- Join the #early-testing channel in our [chat](https://chat.lbry.io).
- For the hardcore, run master from source and/or the latest builds from [build.lbry.io](http://build.lbry.io).
- Join the #early-testing channel in our [chat](https://chat.lbry.com).
- For the hardcore, run master from source and/or the latest builds from [build.lbry.com](http://build.lbry.com).
Opening well-specified issues against release candidates or master builds is extremely useful in helping us create quality software.
@ -124,7 +124,7 @@ Feature requests are welcome. Before you submit one be sure to:
Sometimes, you may have a problem but an issue isn't appropriate (or you're not sure if it's a real issue).
Join our [chat](https://chat.lbry.io), our [forum](https://discourse.lbry.io), or another [community](https://lbry.tech/community) and talk to others about it.
Join our [chat](https://chat.lbry.com), our [forum](https://discourse.lbry.com), or another [community](https://lbry.tech/community) and talk to others about it.
## Appreciation

2
documents/glossary.md
View file

@ -101,7 +101,7 @@ A node which can definitively decide whether a transaction is valid or not, with
### Genesis Block
The first block in the blockchain. The genesis block is not mined, but is hard-coded into the protocol. It has no reference to a previous block. The LBRY genesis block was released on [28 Oct 2015](https://explorer.lbry.io/blocks/0). The first real block was mined was on [23 Jun 2016](https://explorer.lbry.io/blocks/1).
The first block in the blockchain. The genesis block is not mined, but is hard-coded into the protocol. It has no reference to a previous block. The LBRY genesis block was released on [28 Oct 2015](https://explorer.lbry.com/blocks/0). The first real block was mined was on [23 Jun 2016](https://explorer.lbry.com/blocks/1).
#### Hard Fork

4
documents/resources/api-wrappers.md
View file

@ -1,11 +1,11 @@
---
title: API Wrappers
description: Find LBRY API wrappers for your favorite language.
description: Find LBRY API wrappers for your favorite language.
---
This document contains a comprehensive list of all available API wrappers for the LBRY protocol and blockchain. API wrappers allow for easier integration of the LBRY APIs into your codebase. They still require you to run either the [LBRY protocol](https://github.com/lbryio/lbry) or the [LBRY blockchain](https://github.com/lbryio/lbrycrd).
Interested in creating one for a language not shown below? See our [bounties page](https://lbry.io/bounty/lbry-binding) for details.
Interested in creating one for a language not shown below? See our [bounties page](https://lbry.com/bounty/lbry-binding) for details.
## List of API wrapper resources
| Language | Creator/Contact | GitHub Repository / Other Links | Status |

4
documents/resources/claim-signing.md
View file

@ -16,7 +16,7 @@ Reilly wants to publish _Terror on the Midway_ to the channel he claimed `lbry:/
"licenseUrl": "",
"nsfw": false,
"preview": "",
"thumbnail": "https://s3.amazonaws.com/files.lbry.io/thumbnails/superman1940-thumb.png",
"thumbnail": "https://s3.amazonaws.com/files.lbry.com/thumbnails/superman1940-thumb.png",
"title": "Terror on the Midway - Superman Ep 9",
"version": "_0_1_0"
},
@ -99,7 +99,7 @@ Now he add this signature to the claim:
"licenseUrl": "",
"nsfw": false,
"preview": "",
"thumbnail": "https://s3.amazonaws.com/files.lbry.io/thumbnails/superman1940-thumb.png",
"thumbnail": "https://s3.amazonaws.com/files.lbry.com/thumbnails/superman1940-thumb.png",
"title": "Terror on the Midway - Superman Ep 9",
"version": "_0_1_0"
},

2
documents/resources/claimtrie.md
View file

@ -52,7 +52,7 @@ print("leaf hash is {}".format(hexlify(hash_leaf(tx, nout, at_height)[::-1])))
## How is the root hash calculated?
Let's start with a ClaimTrie holding a single claim.
The claim is named `mindblown` and was included at block 102 with the same details as the last section. It's actually a real claim as [you can see in the block explorer](https://explorer.lbry.io/blocks/102). This block has the first claim ever, so the ClaimTrie was the simple case being explained in here.
The claim is named `mindblown` and was included at block 102 with the same details as the last section. It's actually a real claim as [you can see in the block explorer](https://explorer.lbry.com/blocks/102). This block has the first claim ever, so the ClaimTrie was the simple case being explained in here.
We start with the leaf hash:
1. Hash the leaf hash using double sha-256.
2. For each character of the name (nodes of the trie), the hash of a node is the double sha-256 of the node's character concatenated with the children hash.

18
documents/resources/daemon-settings.md
View file

@ -1,18 +1,18 @@
---
title: SDK Settings
description: The daemon provided by the LBRY SDK has many settings. This resource lists them all and what they mean. Ready, set, settings!
---
---
This document outlines how to configure SDK daemon settings and what options are available. They can be found on the lbry GitHub repository in [conf.py](https://github.com/lbryio/lbry/blob/master/lbrynet/conf.py).
## Daemon settings configuration
## Daemon settings configuration
The easiest way to configure the settings is by editing the `daemon_settings.yml` file (may need to be created) that resides in the default [lbrynet directory](https://lbry.io/faq/lbry-directories). These settings can also be configured via the [settings_set](https://lbry.tech/api/sdk#settings_set) API call. The [settings_get](https://lbry.tech/api/sdk#settings_get) API call can be used to retrieve current values. Some values will require an SDK restart after being set via the API call.
The easiest way to configure the settings is by editing the `daemon_settings.yml` file (may need to be created) that resides in the default [lbrynet directory](https://lbry.com/faq/lbry-directories). These settings can also be configured via the [settings_set](https://lbry.tech/api/sdk#settings_set) API call. The [settings_get](https://lbry.tech/api/sdk#settings_get) API call can be used to retrieve current values. Some values will require an SDK restart after being set via the API call.
Sample daemon_settings.yml file:
```
tcp_port: 3335
lbryum_servers: ['lbryumx1.lbry.io:50001','lbryumx2.lbry.io:50001']
lbryum_servers: ['lbryumx1.lbry.com:50001','lbryumx2.lbry.com:50001']
download_directory: 'c:\lbry\Downloads'
use_upnp: false
```
@ -25,7 +25,7 @@ Configuration options are organized by their respective areas: Files, Wallet, Ne
### Files
| Setting | Format | Default value | Sample Values | Description |
|------------------------|---------|------------------------------------------------------|--------------------|--------------------------------------------------------------------------------------|
| data_dir | string | [varies by OS](https://lbry.io/faq/lbry-directories) | 'c:\lbry\lbrynet\' | Where to store the lbrynet folder, which includes blob files, logs and config data |
| data_dir | string | [varies by OS](https://lbry.com/faq/lbry-directories) | 'c:\lbry\lbrynet\' | Where to store the lbrynet folder, which includes blob files, logs and config data |
| delete_blobs_on_remove | boolean | true | false | Delete blobs on a file_delete call? |
| download_dir | string | local downloads folder | 'c:\lbry\lbrynet\' | Location of downloaded output files |
@ -33,8 +33,8 @@ Configuration options are organized by their respective areas: Files, Wallet, Ne
| Setting | Format | Default value | Sample Values | Description |
|-------------------------------|---------|------------------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------|
| blockchain_name | string | 'lbrycrd_main' | 'lbrycrd_regtest' | Blockchain network to connect to |
| lbryum_servers | list | ['lbryumx1.lbry.io:50001','lbryumx2.lbry.io:50001'] | ["mylbryum.lbry.io:50001] | SPV wallet server address |
| wallet_dir | string | [varies by OS](https://lbry.io/faq/lbry-directories) | 'c:\lbry\lbryum\' | Wallet data location |
| lbryum_servers | list | ['lbryumx1.lbry.com:50001','lbryumx2.lbry.com:50001'] | ["mylbryum.lbry.com:50001] | SPV wallet server address |
| wallet_dir | string | [varies by OS](https://lbry.com/faq/lbry-directories) | 'c:\lbry\lbryum\' | Wallet data location |
| max_key_fee | json | {'currency': 'USD', 'amount': 50.0} | {'currency': 'LBC', 'amount': 5.0} | Max payment allowed for content |
| wallet | string | 'lbryum' | 'lbrycrd' | Choice of wallet software, SPV (lbryum) vs full node (lbrycrd). Currently only lbryum supported |
| use_keyring | boolean | false | true | Store wallet password in keyring (not currently available) |
@ -49,13 +49,13 @@ Configuration options are organized by their respective areas: Files, Wallet, Ne
| download_timeout | integer | 30 | 60 | Time, in seconds, to allow download to get data blobs |
| announce_head_blobs_only | boolean | true | false | Only announce first data blob |
| concurrent_blob_announcers | integer | 10 | 0 | Threads used in order to announce blobs. 0 means disabled |
| known_dht_nodes | list | ['lbrynet1.lbry.io:4444'] | ['myDHT.lbry.io:4444'] | Bootstrap nodes for network connectivity |
| known_dht_nodes | list | ['lbrynet1.lbry.com:4444'] | ['myDHT.lbry.com:4444'] | Bootstrap nodes for network connectivity |
| max_connections_per_stream | integer | 5 | 10 | Threads used to download blobs |
| seek_head_blob_first | boolean | true | false | Search for first data blob after downloading sd blob |
| tcp_port | integer | 3333 | 3334 | Port the SDK will listen on |
| concurrent-reflector-uploads| integer | 5 | 10 | Connections to use while uploading data to reflector |
| reflect_streams | boolean | true | false | Send published data to reflector servers |
| reflector_servers | list | ['reflector.lbry.io'] | ['myreflector.lbry.io'] | Server data will be reflected to |
| reflector_servers | list | ['reflector.lbry.com'] | ['myreflector.lbry.com'] | Server data will be reflected to |
| fixed-peer-delay | integer | 2 | 5 | Time, in mintues, to allow download from P2P before trying fixed peer |
| peer_connect_timeout | integer | 30 | 15 | Time, in seconds, to allow download to find peers |
| node_rpc_timeout | integer | 5 | 10 | Time, in seconds, to allow connection over DHT |

10
documents/resources/repository-standards.md
View file

@ -1,7 +1,7 @@
---
title: Repository Documentation Standards
description: All repository documentation at LBRY complies with a single standard, outlined in this resource article.
---
---
This document outlines the standards for all public, open-source repositories used by LBRY.
@ -51,7 +51,7 @@ This document exists to introduce a project to a new visitor. It may also serve
* A single header labeled "Contributing" should appear as an h2
* This should be the same message: "Contributions to this project are welcome, encouraged, and compensated. For more details, see [CONTRIBUTING.md](*CONTRIBUTING.md*)”
* If CONTRIBUTING.md does not exist in the project, it should link to [https://lbry.io/faq/contributing](https://lbry.io/faq/contributing) (soon to be lbry.tech/contributing)
* If CONTRIBUTING.md does not exist in the project, it should link to [https://lbry.com/faq/contributing](https://lbry.com/faq/contributing) (soon to be lbry.tech/contributing)
### (Additional Headings)
@ -65,12 +65,12 @@ This document exists to introduce a project to a new visitor. It may also serve
### Security
* "We take security seriously. Please contact [security@lbry.io](mailto:security@lbry.io) regarding any security issues. Our PGP key is [here](https://keybase.io/lbry/key.asc) if you need it."
* "We take security seriously. Please contact [security@lbry.com](mailto:security@lbry.com) regarding any security issues. Our PGP key is [here](https://keybase.io/lbry/key.asc) if you need it."
### Contact
* A single header labeled "Contact" should appear as an h2
* This should be the same or a similar message to the following: "The primary contact for this project is [@XXX](https://github.com/@XXX) ([xxx@lbry.io](mailto:xxx@lbry.io))"
* This should be the same or a similar message to the following: "The primary contact for this project is [@XXX](https://github.com/@XXX) ([xxx@lbry.com](mailto:xxx@lbry.com))"
### Additional Info and Links
@ -84,7 +84,7 @@ This document explains anything a visitor would need to know to contribute to th
This document should cover the following:
* First, it should contain a single sentence: "This project follows the global contributing standards for all LBRY projects, to read those go < here >.”
* A "Code Overview" section explaining some basic design choices and how to begin stepping through the code. An example would be explaining that Daemon.py is the primary entry point for the daemon code, and one can begin to trace through the code by looking for jsonrpc_xxx, where xxx is one of the api calls listed [here](https://lbry.io/api)
* A "Code Overview" section explaining some basic design choices and how to begin stepping through the code. An example would be explaining that Daemon.py is the primary entry point for the daemon code, and one can begin to trace through the code by looking for jsonrpc_xxx, where xxx is one of the api calls listed [here](https://lbry.com/api)
* A "Testing" section explaining how to run tests and stating that tests are necessary
* Information on how to submit pull requests, and what to expect afterwards (e.g. a link to our [branching doc](https://github.com/lbryio/lbry/wiki/Branching-and-Merging), commands to run before submitting PR, tests must pass, changelog entry, etc). If you find this gets repetitive, it may be best to link to a global doc
* Anything else a new visitor to a repository should know about contributing to that specific repository (linting, generating documentation, etc)