Minor fixes
This commit is contained in:
ポール ウェッブ
parent
91e374d81e
commit
c7bd736b7c
7 changed files with 36 additions and 35 deletions
|
|
@ -5,7 +5,7 @@ title: Development
|
|||
Want to build something on top of LBRY? This is the place to get you started.
|
||||
|
||||
At least, it's the place to get started so long as you have some idea of what LBRY _is_. If you don't, you should read the
|
||||
[Overview](/overview) first.
|
||||
[Overview](/overview/) first.
|
||||
|
||||
## When to Use LBRY
|
||||
|
||||
|
|
@ -50,3 +50,5 @@ Not all applications will want to use the full LBRY protocol, or some applicatio
|
|||
1. lbrycrd documentation
|
||||
|
||||
## Desired Applications
|
||||
|
||||
TBD
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ title: Contributing
|
|||
|
||||
Interested in working on the LBRY protocol, an official LBRY app, or other LBRY infrastructure? Awesome! This guide will get you started.
|
||||
|
||||
This guide is for contributing to the code bases maintained by the LBRY organization. For building on top of the LBRY protocol, see [Build](/build).
|
||||
This guide is for contributing to the code bases maintained by the LBRY organization. For building on top of the LBRY protocol, see [Build](/build/).
|
||||
|
||||
Contributors that provide accepted pull requests, well-specified issues, or assist in testing and quality assurance typically receive LBC tokens as appreciation.
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ Additionally, every technical employee of LBRY outside of the founding team star
|
|||
|
||||
## Designing
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Writing
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ A number of our code bases (`lbrycrd`, `lbry`, all applications, more...) go thr
|
|||
|
||||
For any projects that 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 even harder-core testing, you can follow the `README` instructions in a project and test against the `master` branch of a project at any time. Additionally, `master` builds for some projects are always available via [releases.lbry.io](http://releases.lbry.io/).
|
||||
For even harder-core testing, you can follow the `README` instructions in a project and test against the `master` branch of a project at any time. Additionally, `master` builds for some projects are always available via [releases.lbry.io](http://releases.lbry.io).
|
||||
|
||||
Opening well-specified issues against release candidates or master builds is extremely useful in helping us create quality software.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
LBRY Glossary
|
||||
================
|
||||
---
|
||||
title: LBRY Glossary
|
||||
---
|
||||
|
||||
This glossary will help you understand exact meaning of LBRY and blockchain related terms.
|
||||
|
||||
|
|
@ -329,7 +330,6 @@ An application or a service that helps keeping private keys for signing transact
|
|||
|
||||
Also known as >50% attack or a *double spend* attack. An attacker can make a payment, wait till the merchant accepts some number of *confirmations* and provides the service, then starts mining a parallel chain of blocks starting with a block before the transaction. This parallel blockchain then includes another transaction that spends the same *outputs* on some other address. When the parallel chain becomes more *difficult*, it is considered a *main chain* by all nodes and the original transaction becomes invalid. Having more than a half of total *hashrate* guarantees possibility to overtake chain of any length, hence the name of an attack (strictly speaking, it is "more than 50%", not 51%). Also, even 40% of hashrate allows making a double spend, but the chances are less than 100% and are diminishing exponentially with the number of confirmations that the merchant requires.
|
||||
|
||||
|
||||
About
|
||||
-----
|
||||
Portions of this glossary originated from: https://github.com/oleganza/bitcoin-papers/blob/master/BitcoinGlossary.md
|
||||
|
|
|
|||
|
|
@ -32,6 +32,6 @@ Learn more about how LBRY works from this ecosystem overview.
|
|||
|
||||
## Keep Diving
|
||||
|
||||
- Explore live metadata and add your own blockchain entry on [the Tour](/tour).
|
||||
- Read the whitepaper, the API specification and other documentation in [Resources](/resources).
|
||||
- Learn how to [contribute to LBRY](/contributing) or [build your own application](/build).
|
||||
- Explore live metadata and add your own blockchain entry on [the Tour](/tour.html).
|
||||
- Read the whitepaper, the API specification and other documentation in [Resources](/resources/).
|
||||
- Learn how to [contribute to LBRY](/contribute/) or [build your own application](/build/).
|
||||
|
|
|
|||
|
|
@ -2,4 +2,4 @@
|
|||
title: Sitemap
|
||||
---
|
||||
|
||||
<Sitemap></Sitemap>
|
||||
<Sitemap/>
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ title: Subscribe to our mailing list
|
|||
|
||||
Join our developer mailing list and you will receive updates about LBRY via email.
|
||||
|
||||
<EmailSubscribeLarge></EmailSubscribeLarge>
|
||||
<EmailSubscribeLarge/>
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ var async = require("async");
|
|||
// Express etc
|
||||
var sslRedirect = require('heroku-ssl-redirect');
|
||||
var express = require('express');
|
||||
var path = require('path');
|
||||
var serveStatic = require('serve-static');
|
||||
var request = require('request');
|
||||
var cors = require('cors');
|
||||
|
|
|
|||
Loading…
Reference in a new issue