diff --git a/content/faq/ARCHIVE-development-status..archive b/content/faq/ARCHIVE-development-status..archive index ae66e18a..41d9a9ff 100644 --- a/content/faq/ARCHIVE-development-status..archive +++ b/content/faq/ARCHIVE-development-status..archive @@ -1,8 +1,8 @@ ---- +--- title: What is LBRY’s development status right now? Plans for the future? category: developer --- -LBRY is currently in invite-only beta, with desktop apps for Linux, MacOS, and a pre-release version of Windows. There are approximately 5K active users and hundreds of content creators. The network already hosts big name content like the [feature film *It’s A Disaster*](https://lbry.io/news/launch-a-disaster) and videos from [Adult Swim’s MillionDollarExtreme](https://lbry.io/news/mde-on-lbry). We announce new featured content every Thursday on our [blog](https://lbry.io/news), [Twitter](https://twitter.com/lbryio), and [Facebook](https://www.facebook.com/lbryio). +LBRY is currently in invite-only beta, with desktop apps for Linux, MacOS, and a pre-release version of Windows. There are approximately 5K active users and hundreds of content creators. The network already hosts big-name content like the [feature film *It’s A Disaster*](https://lbry.io/news/launch-a-disaster) and videos from [Adult Swim’s MillionDollarExtreme](https://lbry.io/news/mde-on-lbry). We announce new featured content every Thursday on our [blog](https://lbry.io/news), [Twitter](https://twitter.com/lbryio), and [Facebook](https://www.facebook.com/lbryio). The waitlist to get into the beta is ~150K people long. This shocks even us, and we’re racing to get the user experience and backend technologies to a level where we’re comfortable opening the beta to everyone. The target for open beta is this winter. Mushy target, we know, but these things are hard to time. diff --git a/content/faq/acceptable-use-policy.md b/content/faq/acceptable-use-policy.md index e3b2d6c9..26fb8bc6 100644 --- a/content/faq/acceptable-use-policy.md +++ b/content/faq/acceptable-use-policy.md @@ -1,11 +1,11 @@ ---- +--- title: Acceptable Use Policy category: other --- -If you've read [Art in the Internet Age,](https://lbry.io/what) you know that LBRY believes we are in a post scarcity age in terms of the reproduction of content. There are two things that are still scarce; good quality content, and good reputations. We take respecting the rights of creators very seriously, and we expect the same when it comes to our good name. Here is how we go about protecting that. +If you've read [Art in the Internet Age,](https://lbry.io/what) you know that LBRY believes we are in a post-scarcity age in terms of the reproduction of content. There are two things that are still scarce; good quality content, and good reputations. We take respecting the rights of creators very seriously, and we expect the same when it comes to our good name. Here is how we go about protecting that. -Our trademarks include our name, LBRY, and our official logo, which are owned by LBRY, Inc, a Delaware Corporation. We encourage the use of LBRY's trademarked name and official logo, while maintaining control of them in order to thwart vandalism, theft, and any future misconduct that offends the collective sensibility of LBRY users, creates legal hazards, or otherwise inhibits the free expression and open transactions we prize. +Our trademarks include our name, LBRY, and our official logo, which are owned by LBRY, Inc, a Delaware Corporation. We encourage the use of LBRY's trademarked name and official logo while maintaining control of them in order to thwart vandalism, theft, and any future misconduct that offends the collective sensibility of LBRY users creates legal hazards or otherwise inhibits the free expression and open transactions we prize. #### Our trademark policy has three objectives: @@ -15,9 +15,9 @@ Our trademarks include our name, LBRY, and our official logo, which are owned by ### Obtain Your License -If you are producing video or other content for LBRY, if you've downloaded our client, you've got a license to use the LBRY name and official logo on your blog or web site where you promote your work. That's all there is to it, just stick to the fair use rules if you're sampling or otherwise using copyright content from somewhere else. +If you are producing video or other content for LBRY, if you've downloaded our client, you've got a license to use the LBRY name and official logo on your blog or website where you promote your work. That's all there is to it, just stick to the fair use rules if you're sampling or otherwise using copyright content from somewhere else. -If you are a developer, you will need to complete the verification process before you use the LBRY name and official logo to promote your service or site. The creation of fraudulent sites that appear official are a common problem for blockchain projects. This happened to LBRY early in its history and this process exists to reduce the potential for another such event. +If you are a developer, you will need to complete the verification process before you use the LBRY name and official logo to promote your service or site. The creation of fraudulent sites that appear official is a common problem for blockchain projects. This happened to LBRY early in its history, and this process exists to reduce the potential for another such event. ### Examples Of Acceptable Uses @@ -27,10 +27,10 @@ If you are a developer, you will need to complete the verification process befor ### Examples of Unacceptable Uses - * Creating any service that uses LBRY and presenting it as official product, such as an online wallet. + * Creating any service that uses LBRY and presenting it as an official product, such as an online wallet. * Presenting yourself or implying that you are a representative or agent of LBRY, Inc. * Using LBRY in the title or name of your business in a way that could be construed as being a product of LBRY, Inc. - * Uploading someone else's copyrighted work without their permission, either for free, or attempting to profit. + * Uploading someone else's copyrighted work without their permission, either for free or attempting to profit. * Uploading content that is itself a crime. ### LBRY Service Trademark Usage Policy @@ -39,4 +39,4 @@ As a statement of principle, you are encouraged to associate your project, produ You should not do anything that causes confusion regarding roles. You can describe your company as “Top Shelf Consulting, providers of LBRY development,” but not “The LBRY Development Group.” Registering a domain that could be mistaken for part of LBRY's infrastructure would also be inappropriate. -If you are not sure if your use is within bounds or not, please [come talk with us](https://chat.lbry.io) about it. We know we can only envision some of the innovation that will happen on the LBRY network and would hate to miss a great opportunity over confusion in this area. +If you are not sure if your use is within bounds or not, please [come talk with us](https://chat.lbry.io) about it. We know we can only envision some of the innovation that will happen on the LBRY network and would hate to miss a great opportunity for confusion in this area. diff --git a/content/faq/api-help.md b/content/faq/api-help.md index 88392dad..fd8f2e9b 100644 --- a/content/faq/api-help.md +++ b/content/faq/api-help.md @@ -28,7 +28,7 @@ documented [here](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_l - `USER` and `PASSWORD` can be found in your lbrycrd.conf file. - The `method` field can be any of the supported methods like `getbalance` or `getnewaddress`. -- `9245` is the default port used, but if you chose a custom port for the server, you'll need to use that instead. +- `9245` is the default port used, but if you chose a custom port for the server, you'd need to use that instead. - If the command accepts parameters, they can be passed inside the `params` array. See Also: [important directories](https://lbry.io/faq/lbry-directories). diff --git a/content/faq/backup-data.md b/content/faq/backup-data.md index 48a80b1f..70cf9ff1 100644 --- a/content/faq/backup-data.md +++ b/content/faq/backup-data.md @@ -5,7 +5,7 @@ category: troubleshooting We have covered LBRY wallet backup procedures in the guide [here](https://lbry.io/faq/how-to-backup-wallet), but the purpose of this guide will be how to backup and/or migrate all your LBRY data which includes your downloads, hosted data, wallet and other settings. To follow this guide effectively, it's a good idea to familiarize yourself with LBRY [working directories](https://lbry.io/faq/lbry-directories), especially the `lbrynet` and `lbryum` folders. ***In the case of Mac OS, the `lbrynet` folder contents are stored inside the `LBRY` folder as detailed on the directories page.*** -In addition to those two directories, users may also want to copy their LBRY downloads - this directory is normally set to your local Downloads folder but can also be configured via the LBRY app. To check your LBRY Downloads directory, open the LBRY app and go to Settings - it is listed in the `Download Directory` section. If you chose not to copy over your Downloads folder, the content can be regenerated from the data in your `lbrynet` folder at a later time via the LBRY app. +In addition to those two directories, users may also want to copy their LBRY downloads - this directory is normally set to your local Downloads folder but can also be configured via the LBRY app. To check your LBRY Downloads directory, open the LBRY app and go to Settings - it is listed in the `Download Directory` section. If you chose not to copy over your Downloads folder, the content could be regenerated from the data in your `lbrynet` folder at a later time via the LBRY app. To summarize, the main directories to consider when backing up or migrating a LBRY installation are as follows: ##### - LBRY Wallet - `lbryum` diff --git a/content/faq/benefit-consumers.md b/content/faq/benefit-consumers.md index 0859c4ea..d96c0ae1 100644 --- a/content/faq/benefit-consumers.md +++ b/content/faq/benefit-consumers.md @@ -1,4 +1,4 @@ ---- +--- title: How does LBRY benefit content consumers? Why should I bother caring? category: LBRY 101 order: 2 @@ -7,6 +7,6 @@ Do you watch YouTube? Imagine paying a few cents to eliminate all ads. 100% of t Do you use BitTorrent? Imagine getting paid to seed files into the network. Because there is a marketplace for these files, you can finally find rare songs and films that can’t support a torrent swarm based on popularity alone. -Do you shop on the iTunes Store? Imagine paying less for songs, TV episodes, and music videos and having 100% of the price go directly to the creators. +Do you shop at the iTunes Store? Imagine paying less for songs, TV episodes, and music videos and having 100% of the price go directly to the creators. LBRY is a digital media library at your fingertips. It can store any kind of content and make it available at low cost on demand. In a few years time, LBRY may become your one-stop-shop for everything digital, from ebooks to video games to movies. One app to rule them all – but still leaving more power in your hands because it is decentralized by design. diff --git a/content/faq/block-rewards.md b/content/faq/block-rewards.md index 6aeb0b3c..79c92a0b 100644 --- a/content/faq/block-rewards.md +++ b/content/faq/block-rewards.md @@ -23,7 +23,7 @@ Eventually 1,000,000,000 LBRY credits will exist. They are awarded on the follow * The remaining 600,000,000 are mined in 3 stages: - 1. The first stage goes from block 1 to block 5100, and will take roughly 9 days. Every block in this stage has a reward of 1 credit. This + 1. The first stage goes from block 1 to block 5100 and will take roughly 9 days. Every block in this stage has a reward of 1 credit. This is the testing stage, to ensure that there are no glaring problems with the blockchain. 2. The second stage is the ramp-up. It goes from block 5101 to block 55000 (roughly 3 months of mining). During this stage, the block reward diff --git a/content/faq/claimtrie-implementation.md b/content/faq/claimtrie-implementation.md index 095063e3..aad42351 100644 --- a/content/faq/claimtrie-implementation.md +++ b/content/faq/claimtrie-implementation.md @@ -7,16 +7,16 @@ category: developer This document describes the implementation detail of the ClaimTrie in LBRY. The ClaimTrie is the data structure which LBRY uses to store claims to names. It uses a [Trie](https://en.wikipedia.org/wiki/Trie) to efficiently store all claimed names, which can then be hashed the same way a [Merkle Tree](https://en.wikipedia.org/wiki/Merkle_tree) is hashed. The root hash of the ClaimTrie is stored in the blockheader of each LBRY block, enabling nodes in the LBRY network to efficiently and securely validate the state of the ClaimTrie. -Bids to claim a name must win out against other claims for the same name, before they can be inserted into the ClaimTrie. The short summary is that the bid with the most LBRY credits assigned to it will win the right to claim a name, but the implementation detail is more involved and this is what we aim to cover in this document. Bids to claim a name have four properties tied to it : +Bids to claim a name must win out against other claims for the same name before they can be inserted into the ClaimTrie. The short summary is that the bid with the most LBRY credits assigned to it will win the right to claim a name, but the implementation detail is more involved and, this is what we aim to cover in this document. Bids to claim a name have four properties tied to it : -1. *Name* : The name is a human readable address and is the property that the bids compete to obtain. -2. *Value* : The values is the data that is attached to the name. +1. *Name* : The name is a human-readable address and is the property that the bids compete to obtain. +2. *Value* : The value is the data that is attached to the name. 3. *Quantity* : The quantity is the number of LBRY credits assigned to the bid. 4. *Claim Id* : A unique ID used to identify the bid. There are also three different bid types: claim, update, and support. -1. *Claim*: A claim represent new bids for a name. If a user want to make a claim to a brand new name, or submit a competing claim to an existing name, this bid type is used. +1. *Claim*: A claim represent new bids for a name. If a user wants to make a claim to a brand new name, or submit a competing claim to an existing name, this bid type is used. 2. *Support*: A support adds to the total quantity of credits assigned to any bid by referring to a bid's Claim Id. A support bid can be made by anyone on any bid. It does not have its own Value or its own Claim Id, but it does contain the Claim Id of the bid that it is supporting. 3. *Update*: An update can modify the value and the quantity for a pre-existing claim without changing the Claim Id or the name that it is bidding on. Since the Claim Id of the original bid is not changed, an updated bid will still retain all the supports attached to the original bid. @@ -27,14 +27,14 @@ This section describes how bids are processed by the ClaimTrie in order to deter 1. *Not accepted*: This bid is in a transaction which has not yet been included in a block which has been included in the blockchain. 2. *Accepted*: This bid has been accepted into the blockchain. This happens when the transaction containing the TXout which contains the bid is included in a block which is included in the blockchain. -3. *Active*: This bid is capable of controlling a name. Active bids must be in the “accepted” state and not “expired” or “spent”. Bids are “active” when either of the two conditions below are met: +3. *Active*: This bid is capable of controlling a name. Active bids must be in the “accepted” state and not “expired” or “spent”. Bids are “active” when either of the two conditions below is met: * The current block height exceeds the height of the block at which the bid became accepted plus the activation delay for the name as calculated at either the block at which the bid was accepted or any block after the bid was accepted. The activation delay is calculated as follows: * If, immediately before this block was included in the blockchain, there were no ‘active’ bids for the name and therefore no ‘controlling’ bids, the delay is 0. * If there is a “controlling” bid for the name: Delay = (HeightB - HeightA) / 32 * HeightA = the most recent height at which the bid controlling the name changed * HeightB = the current height * Maximum delay is 7 days of blocks at 2.5 min/block (or 4032 blocks). Thus maximum delay can be reached in 224 (7x32) days. - * The bid’s Claim Id matches the Claim Id of the bid which was the controlling bid immediately before the block containing this bid was included in the blockchain. In other words, it is either an update to the previous controlling bid, or an update to an update to the previous controlling bid if the bid was updated twice in this block, etc. + * The bid’s Claim Id matches the Claim Id of the bid which was the controlling bid immediately before the block containing this bid was included in the blockchain. In other words, it is either an update to the previous controlling bid or update to update to the previous controlling bid if the bid was updated twice in this block, etc. 4. *Controlling*: This bid currently controls the name. When clients ask which bid controls the name as of the current block, this is the bid that will be returned. Must be in the “active” state and only one bid for any name may be in this state. A support cannot be in the “controlling” state. To determine which “active” bid is the “controlling” bid for each name: * Add the quantity of each ‘active’ bid to the quantity of all ‘active’ supports for that bid, and take whichever is greatest. If two bids have the same quantity, older bids take precedence over newer bids. @@ -46,7 +46,7 @@ This section describes how bids are processed by the ClaimTrie in order to deter ## ClaimTrie Transaction Implementation -This section describes how the three ClaimTrie bid types are implemented as transactions on the blockchain. Readers should have prior knowledge of Bitcoin [transactions](https://en.bitcoin.it/wiki/Transaction) and the Bitcoin [scripting system](https://en.bitcoin.it/wiki/Script). LBRY supports three op codes that do not exist in Bitcoin: OP_CLAIM_NAME, OP_SUPPORT_CLAIM, and OP_UPDATE_CLAIM (in Bitcoin they are respectively OP_NOP6, OP_NOP7, and OP_NOP8). Each op code will push a zero on to the execution stack, and in addition will trigger the ClaimTrie to perform calculations necessary for each bid type. Below are the three supported transactions scripts using these op codes. +This section describes how the three ClaimTrie bid types are implemented as transactions on the blockchain. Readers should have prior knowledge of Bitcoin [transactions](https://en.bitcoin.it/wiki/Transaction) and the Bitcoin [scripting system](https://en.bitcoin.it/wiki/Script). LBRY supports three op codes that do not exist in Bitcoin: OP_CLAIM_NAME, OP_SUPPORT_CLAIM, and OP_UPDATE_CLAIM (in Bitcoin they are respectively OP_NOP6, OP_NOP7, and OP_NOP8). Each op code will push a zero on to the execution stack, and in addition, will trigger the ClaimTrie to perform calculations necessary for each bid type. Below are the three supported transactions scripts using these op codes. ```python OP_CLAIM_NAME OP_2DROP OP_DROP [script pubkey] @@ -61,13 +61,13 @@ For example, a claim transaction using a pay to pubkey script will have the belo OP_CLAIM_NAME OP_2DROP OP_DROP OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG ``` -Like any standard Bitcoin transaction output script, it will be associated with a transaction hash, and a transaction output index. The transaction hash and transaction output index is concatenated and hashed using RIPEMD-160 to create the Claim Id for this claim. For the example above, let's say it has a Claim Id X. A support for this bid will have the below full payout script. +Like any standard Bitcoin transaction output script, it will be associated with a transaction hash and a transaction output index. The transaction hash and transaction output index is concatenated and hashed using RIPEMD-160 to create the Claim Id for this claim. For the example above, let's say it has a Claim Id X. A support for this bid will have the below full payout script. ```python OP_SUPPORT_CLAIM OP_2DROP OP_DROP OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG ``` -And now let's say we want to update the original claim to change the value to “Banana”. An update transaction has a special requirement that it must spend the existing claim that it wishes to update in its redeem script. Otherwise, it will be considered invalid and will not make it into the ClaimTrie. Thus it will have the below redeem script to spend the claim created to set name “Fruit” to “Apple”. Note that this is identical to the standard way of redeeming a “pay to pubkey” script in Bitcoin. +And now let's say we want to update the original claim to change the value to “Banana”. An update transaction has a special requirement that it must spend the existing claim that it wishes to update in its redeem script. Otherwise, it will be considered invalid and will not make it into the ClaimTrie. Thus it will have the below redeem script to spend the claim created to set name “Fruit” to “Apple”. Note that this is identical to the standard way of redeeming a “pay to pubkey” script in Bitcoin. ```python diff --git a/content/faq/community-top-bid.md b/content/faq/community-top-bid.md index c09add02..9c7e44a8 100644 --- a/content/faq/community-top-bid.md +++ b/content/faq/community-top-bid.md @@ -18,11 +18,11 @@ For more details on how naming works, please see: [Naming](https://lbry.io/faq/n ### How do I publish to the Community Top Bids area? -1. Begin a standard publish by clicking the "PUBLISH" button in the top of the App. +1. Begin a standard publish by clicking the "PUBLISH" button at the top of the App. 2. When filling out the Content URL, enter the desired claim you want to bid on (one, two, five, eight, etc.) -3. After you have entered the desired URL, the system will automatically show you the minimum amount of LBC you need to deposit to get the claim. This LBC remains yours and the deposit can be undone at any time. +3. After you have entered the desired URL, the system will automatically show you the minimum amount of LBC you need to deposit to get the claim. This LBC remains yours, and the deposit can be undone at any time. 4. Finish the rest of the publishing process. ### How do I know if my content is overtaken? -We do not have a mechanism in place to notify users when they are outbid but one is planned for a future release. For now, you can monitor the Community Top Bids section to see if your content is still available. +We do not have a mechanism in place to notify users when they are outbid, but one is planned for a future release. For now, you can monitor the Community Top Bids section to see if your content is still available. diff --git a/content/faq/content.md b/content/faq/content.md index f34095b0..bb0e576e 100644 --- a/content/faq/content.md +++ b/content/faq/content.md @@ -1,9 +1,9 @@ ---- +--- title: What kind of content can I upload, and what about illegal or infringing content? category: publisher --- -This guide provides answers about questions regarding what you may upload to the LBRY app and network, as well as how to report illegal or infringing content. +This guide provides answers to questions regarding what you may upload to the LBRY app and network, as well as how to report illegal or infringing content. ###What content can I legally upload to LBRY? @@ -11,7 +11,7 @@ You may upload content you created or own that does not infringe on the rights o ###Because LBRY is decentralized, doesn't this mean the content can’t be removed? -It is important to make a distinction between the LBRY protocol and any applications running on top when referring to censorship. The LBRY protocol is fully decentralized and censorship resistant, with it storing metadata and naming on the blockchain, and facilitating data transfers over a peer to peer (P2P) network. +It is important to make a distinction between the LBRY protocol and any applications running on top when referring to censorship. The LBRY protocol is fully decentralized and censorship-resistant, with it storing metadata and naming on the blockchain, and facilitating data transfers over a peer to peer (P2P) network. However, LBRY also makes an app to demonstrate our protocol. Within our app, we will engage in non-arbitrary censorship, meaning only horrific or infringing content will be removed. As a U.S. company, LBRY Inc. and management of our app will follow all U.S. laws, including the CDA and DMCA. If someone made an app or website using the LBRY protocol in some other country, it would have to follow that country's laws, which aren’t necessarily the same as ours. Either app would read the same blockchain, though. @@ -21,7 +21,7 @@ LBRY Inc., makes no guarantee your content will be hosted on the network. The pe Reporting infringing/illegal content in the LBRY App is easy. You can [file a report here](https://lbry.io/dmca) or within the LBRY app. -Open the LBRY App and navigate to the content you wish to report. Underneath the content are two buttons: "Download," and "Report." When you click on the Report button, you will be redirected to a web form to report the content to LBRY, Inc., who can remove the content link from the LBRY App. +Open the LBRY App and navigate to the content you wish to report. Underneath the content, there are two buttons: "Download," and "Report." When you click on the Report button, you will be redirected to a web form to report the content to LBRY, Inc., who can remove the content link from the LBRY App. ###What do I do if I see content that’s illegal or infringing in the LBRY App? @@ -37,4 +37,4 @@ LBRY, Inc. will block access to content deemed infringing in the LBRY App when i ###Can I dispute a DMCA complaint? -Yes, you may. We can't give you legal advice, so check with your local attorney or legal group about how to do this. There are also good resources online to learn about DMCA counter notices. The EFF has published an excellent guide about how to deal with legal issues facing online content creators. +Yes, you may. We can't give you legal advice, so check with your local attorney or legal group about how to do this. There are also good resources online to learn about DMCA counter-notices. The EFF has published an excellent guide about how to deal with legal issues facing online content creators. diff --git a/content/faq/contest-t-and-cs.md b/content/faq/contest-t-and-cs.md index c984b3fc..8e019348 100644 --- a/content/faq/contest-t-and-cs.md +++ b/content/faq/contest-t-and-cs.md @@ -1,26 +1,26 @@ ---- +--- title: LBRY Contest Terms and Conditions category: other --- * Multiple entries are allowed and encouraged. -* In the event of a competition with multiple prizes, one person may only win one prize, excluding a grand prize. +* In the event of competition with multiple prizes, one person may only win one prize, excluding a grand prize. * The promoter is LBRY whose registered office is at 834 Elm Street, Manchester, NH 03101 USA. * Employees of LBRY or their family members or anyone else connected in any way with the competition or helping to set up the competition shall not be permitted to enter competitions. * There is no entry fee and no purchase necessary to enter competitions. * Route to entry for the competition and details of how to enter are [available on our blog](https://lbry.io/news). -* Closing date for entry will be specified in the blog post. After this date the no further entries to the competition will be permitted. If not stated, all times are from 12:01 am to 11:59pm Eastern Time. +* Closing date for entry will be specified in the blog post. After this date, the no further entries to the competition will be permitted. If not stated, all times are from 12:01 am to 11:59 pm Eastern Time. * No responsibility can be accepted for entries not received for whatever reason. * The promoter reserves the right to cancel or amend the competition and these terms and conditions without notice. Any changes will be made via our blog. * All prize details are subject to change and based on availability. * The promoter is not responsible for inaccurate prize details supplied to any entrant by any third party connected with this competition. -* No cash alternative to the prizes will be offered. The prizes are not transferable. Prizes are subject to availability and we reserve the right to substitute any prize without giving notice. +* No cash alternative to the prizes will be offered. The prizes are not transferable. Prizes are subject to availability, and we reserve the right to substitute any prize without giving notice. * Winners will be chosen as per our blog post. The promoter has the right to disqualify any fraudulent entries. * The winner will be notified either via social media or email within 5 days of the closing date. If the winner cannot be contacted or does not claim the prize within 48 hours of notification, we reserve the right to withdraw the prize from the winner and pick a replacement winner. * All winners must be at least 18 years of age. * The promoter will notify the winner when and where the prize can be collected. All prizes will be sent at the end of the competition. For competitions that run multiple stages, the prize will be sent at the end of the final stage. * The promoter’s decision in respect of all matters to do with the competition will be final and no correspondence will be entered into. -* The competition and these terms and conditions will be governed by US law and any disputes will be subject to the exclusive jurisdiction of the courts of the State of New Hampshire. +* The competition and these terms and conditions will be governed by US law, and any disputes will be subject to the exclusive jurisdiction of the courts of the State of New Hampshire. * The winner agrees to the use of his/her name, image, comments or any other information provided in any publicity material. * This promotion is in no way sponsored, endorsed or administered by, or associated with, Facebook, Twitter or any other Social Network. You are providing your information to LBRY and not to any other party. * By entering this competition, an entrant is indicating his/her agreement to be bound by these terms and conditions. diff --git a/content/faq/contributing.md b/content/faq/contributing.md index 67809531..d1b8343e 100644 --- a/content/faq/contributing.md +++ b/content/faq/contributing.md @@ -21,13 +21,13 @@ There are many ways you can get involved. This document covers: ## Ecosystem Overview {#ecosystem-overview} -Typical usage of LBRY does not involve a single piece of software, but instead involves several interacting components. +Typical usage of LBRY does not involve a single piece of software but instead involves several interacting components. Whether you want to report an issue, contribute to the code, or help test the software, it's important to understand which component you want. | 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.

Anything related to output in `lbrynet.log`.

Issues unrelated to or deeper than the interface that do 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.

Anything related to output in `lbrynet.log`.

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.

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.

This is a fork of electrum. | [lbrycrd](https://github.com/lbryio/lbrycrd) | C++ | The LBRY blockchain and standalone wallet | Running a full node, or direct access to the LBRY blockchain.

(This wallet is not bundled with the application. You only want this if you downloaded/installed this package specifically.) @@ -54,7 +54,7 @@ Guidelines for bug reports: 1. **Follow the instructions** - When you open an issue inside of GitHub, each repo contains a template for how to create a good bug report. Please follow it! -Well-specified bug reports save developers lots of time and are extremely appreciated, typically with a LBRY credit tip. +Well-specified bug reports save developers lots of time and are extremely appreciated, typically with an LBRY credit tip. ### Feature Requests {#feature-requests} @@ -94,7 +94,7 @@ If you want to contribute new written copy, such as a blog post or other content 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 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). ### Communicating {#communicating} @@ -108,9 +108,9 @@ 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! -Both `lbry` and `lbry-app` go through regular release cycles where new versions are shipped every few weeks. Testing release candidates or builds of master is a great way to help us identify issues and ship bug-free code. +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. -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. If you're feeling moderately hard-core, you can also test `master` builds via [releases.lbry.io](http://releases.lbry.io/). If you're feeling super hard-core, you can compile `master` yourself, via the README.md or INSTALL.md in the associated repo. diff --git a/content/faq/credit-policy.md b/content/faq/credit-policy.md index 3d56557e..a9baf8b3 100644 --- a/content/faq/credit-policy.md +++ b/content/faq/credit-policy.md @@ -42,9 +42,9 @@ The Operational Fund is 100m LBC reserved for LBRY, Inc. itself. LBRY, Inc. reserves the rights to do whatever it wants with these credits at any time, to be deployed in the best interests of LBRY, Inc. -However, no one believes in the LBRY protocol more, or has more incentive for its success, than LBRY, Inc. We believe LBRY can be a world-altering technology and as such our intentions are to minimize the expenditure of these credits until we've achieved that reality. +However, no one believes in the LBRY protocol more or has more incentive for its success, than LBRY, Inc. We believe LBRY can be a world-altering technology and as such our intentions are to minimize the expenditure of these credits until we've achieved that reality. -Minimal engagement in the market is especially necessary throughout stages of low liquidity, when any action has disproportionate impact. +Minimal engagement in the market is especially necessary throughout stages of low liquidity when any action has a disproportionate impact. Should LBRY make placements from this fund, it will seek long-term engagements and commitments that align interests with LBRY, Inc. and minimize market influence. diff --git a/content/faq/different-alexandria.md b/content/faq/different-alexandria.md index a0e9ab7b..82caa48b 100644 --- a/content/faq/different-alexandria.md +++ b/content/faq/different-alexandria.md @@ -1,8 +1,8 @@ ---- +--- title: How is LBRY different from Decent / SingularDTV / Alexandria? category: differences --- -The first, and biggest, difference is that LBRY exists and has significant traction. As of this writing, Alexandria is the only one of these to release a client to the public, and there hasn’t been much progress since that release. +The first and biggest difference is that LBRY exists and has significant traction. As of this writing, Alexandria is the only one of these to release a client to the public, and there hasn’t been much progress since that release. It's difficult to compare LBRY to something that doesn't exist yet, but as we understand it, no alternative is providing a human-friendly namespace and discovery mechanisms like LBRY. diff --git a/content/faq/different-ipfs.md b/content/faq/different-ipfs.md index 55c1f089..0f85e6d6 100644 --- a/content/faq/different-ipfs.md +++ b/content/faq/different-ipfs.md @@ -5,7 +5,7 @@ category: differences IPFS and BitTorrent are wonderful technologies from which LBRY has drawn a lot of inspiration. However, they both suffer from the same flaws: - Lack of discovery. BitTorrent and IPFS provide decentralized ways to access a unique piece of data or information, but they do not provide an overall catalog that lists all of the available data or information to consume. -- Ugly URLs. BitTorrent only provides access via long, complex magnet URLs. IPFS supports human-friendly naming via IPNS, but this is an after-the-fact hack and does not provide a single, authoritative, user-friendly namespace the way the LBRY does. +- Ugly URLs. BitTorrent only provides access via long, complex magnet URLs. IPFS supports human-friendly naming via IPNS, but this is an after-the-fact hack and does not provide a single, authoritative, user-friendly namespace with the way the LBRY does. - Lack of monetization. Neither BitTorrent nor IPFS support payments to publishers for the content or data they create and publish to the network*; LBRY does. - Incentive problems. BitTorrent and IPFS rely on people being generous with their own resources for data to continue to be available. LBRY creates market incentives for data to be as widespread and available as possible. diff --git a/content/faq/different-storj.md b/content/faq/different-storj.md index ae8eec59..ae6ee5bc 100644 --- a/content/faq/different-storj.md +++ b/content/faq/different-storj.md @@ -2,7 +2,7 @@ title: How is LBRY different from MaidSafe / Storj? category: differences --- -MaidSafe and Storj are attempts to be decentralized platforms that enable many uses, rather than a decentralized protocol designed to serve a singular purpose. +MaidSafe and Storj are attempting to be decentralized platforms that enable many uses, rather than a decentralized protocol designed to serve a singular purpose. LBRY is designed to do one thing and only one thing well: the discovery, access, and (optionally) purchase of digital content. diff --git a/content/faq/different-youtube.md b/content/faq/different-youtube.md index 4375a95b..52ef00a0 100644 --- a/content/faq/different-youtube.md +++ b/content/faq/different-youtube.md @@ -4,4 +4,4 @@ category: differences --- YouTube, Netflix, Apple TV, and other similar services are centralized platforms controlled by a single corporate entity. These companies can change the rules unilaterally, as well as censor content to appease authoritarian governments or corporate partners. -LBRY is a decentralized, open-source protocol that is controlled by its users. LBRY facilitates a similar experience to the aforementioned services, but does it in a way that is entirely decentralized. LBRY can never unilaterally change the rules on publishers or consumers, making it dramatically trustworthy. +LBRY is a decentralized, open-source protocol that is controlled by its users. LBRY facilitates a similar experience to the aforementioned services but does it in a way that is entirely decentralized. LBRY can never unilaterally change the rules on publishers or consumers, making it dramatically trustworthy. diff --git a/content/faq/earn-credits.md b/content/faq/earn-credits.md index cef5dc32..02c5d2a0 100644 --- a/content/faq/earn-credits.md +++ b/content/faq/earn-credits.md @@ -4,7 +4,8 @@ category: getstarted order: 1 --- -Currently, there are several ways to obtain LBRY Credits, or LBC. +======= +There are several ways to obtain LBRY Credits (LBC. 1. LBRY users get an LBC gift by way of in-app [Rewards](https://lbry.io/faq/rewards). 1. LBRY users get LBC for [referring](https://lbry.io/faq/referrals) other users via the LBRY app (see Invites section of the wallet). diff --git a/content/faq/earn-income.md b/content/faq/earn-income.md index 94c4269f..61b284b9 100644 --- a/content/faq/earn-income.md +++ b/content/faq/earn-income.md @@ -1,15 +1,15 @@ ---- +--- title: How does LBRY benefit content creators? Can I make money using LBRY? category: publisher order: 2 --- -In our AMA title, we pitched LBRY as a “community-driven” YouTube alternative that could “save the internet.” That’s a lot of big talk, but what does it mean for the people who care most about the changes happening at YouTube – content creators? +In our AMA title, we pitched LBRY as a “community-driven” YouTube alternative that could “save the internet.” That’s a lot of big talks, but what does it mean for the people who care most about the changes happening at YouTube – content creators? -If you are earning money from your videos on YouTube right now, you are likely familiar with the recent controversies over videos being “de-monetized” for containing content unfriendly to advertisers. It’s no surprise that YouTube caters to advertisers, because those are its ultimate customers. +If you are earning money from your videos on YouTube right now, you are likely familiar with the recent controversies over videos being “de-monetized” for containing content unfriendly to advertisers. It’s no surprise that YouTube caters to advertisers because those are its ultimate customers. LBRY is not an ad-driven media service. In fact, it’s not a traditional media service at all. LBRY is an open protocol that allows you to publish your videos to the network at no cost to you and set a price per stream or download. Because LBRY is a protocol and not a corporate store, there is no approval process for content to be listed and no authority that can “de-monetize” your videos. That’s between you and your fans. -With LBRY, pricing is completely at the discretion of the creator and 100% of that price goes to the creator. Compare this to iTunes’ fixed pricing tiers and 30% cut of every sale. +With LBRY, pricing is completely at the discretion of the creator, and 100% of that price goes to the creator. Compare this to iTunes’ fixed pricing tiers and 30% cut of every sale. Because LBRY uses digital currency (a la Bitcoin), creators can accept micropayments for every view without worrying about credit card processing fees. Or a studio could use LBRY to distribute a theatrical release to independent theaters and charge thousands of dollars per download. The only constraint on pricing is what your viewers are willing to pay. diff --git a/content/faq/gpg-key.md b/content/faq/gpg-key.md index 19b94dd8..c8847e11 100644 --- a/content/faq/gpg-key.md +++ b/content/faq/gpg-key.md @@ -5,7 +5,7 @@ category: other Reporting a security issue? [Click here](/faq/security). -Our GPG is on [Keybase](https://keybase.io/lbry/key.asc), and is reproduced below. +Our GPG is on [Keybase](https://keybase.io/lbry/key.asc) and is reproduced below.