mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-08-23 17:47:26 +00:00
Some people, when confronted with a problem, think, I know, I'll implement my own CMS. Now they have two problems.
This commit is contained in:
Jeremy Kauffman
parent
8f00ec2341
commit
925d622875
88 changed files with 630 additions and 379 deletions
|
|
@ -58,9 +58,11 @@ class Controller
|
|||
case '/lbry-linux-latest.deb':
|
||||
return static::redirect('https://s3.amazonaws.com/files.lbry.io/linux/lbry_0.2.1_amd64.deb', 307);
|
||||
default:
|
||||
if (preg_match('#^/blog($|/)#', $uri))
|
||||
$blogPattern = '#^/news(/|$)#';
|
||||
if (preg_match($blogPattern, $uri))
|
||||
{
|
||||
return BlogActions::execute($uri);
|
||||
$slug = preg_replace($blogPattern, '', $uri);
|
||||
return $slug ? BlogActions::executePost($slug) : BlogActions::executeIndex();
|
||||
}
|
||||
$noSlashUri = ltrim($uri, '/');
|
||||
if (View::exists('page/' . $noSlashUri))
|
||||
|
|
|
|||
|
|
@ -2,24 +2,16 @@
|
|||
|
||||
class BlogActions extends Actions
|
||||
{
|
||||
public static function execute($uri)
|
||||
{
|
||||
$slug = preg_replace('#^/blog(/|$)#', '', $uri);
|
||||
if ($slug)
|
||||
{
|
||||
return static::executePost($slug);
|
||||
}
|
||||
return static::executeHome();
|
||||
}
|
||||
const URL_STEM = '/news';
|
||||
|
||||
public static function executeHome()
|
||||
public static function executeIndex()
|
||||
{
|
||||
$posts = Blog::getPosts();
|
||||
usort($posts, function(Post $a, Post $b) {
|
||||
return strcasecmp($b->getDate()->format('Y-m-d'), $a->getDate()->format('Y-m-d'));
|
||||
});
|
||||
$page = isset($_GET['page']) ? (int)$_GET['page'] : 1;
|
||||
return ['blog/home', [
|
||||
return ['blog/index', [
|
||||
'posts' => $posts,
|
||||
'page' => $page
|
||||
]];
|
||||
|
|
@ -36,4 +28,13 @@ class BlogActions extends Actions
|
|||
'post' => $post
|
||||
]];
|
||||
}
|
||||
|
||||
public static function prepareAuthor(array $vars)
|
||||
{
|
||||
$post = $vars['post'];
|
||||
return [
|
||||
'authorName' => $post->getAuthorName(),
|
||||
'authorBioHtml' => $post->getAuthorBioHtml()
|
||||
];
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -17,12 +17,13 @@ class ContentActions extends Actions
|
|||
|
||||
public static function executeGet()
|
||||
{
|
||||
if (isset($_GET['email']) && $_GET['email'] && Session::get(Session::KEY_LIST_SUB_ERROR))
|
||||
$hasEmail = isset($_GET['email']) && $_GET['email'];
|
||||
if ($hasEmail && Session::get(Session::KEY_LIST_SUB_ERROR))
|
||||
{
|
||||
Controller::redirect('/get');
|
||||
}
|
||||
return ['page/get', [
|
||||
'isSubscribed' => $_GET['email'] || in_array(Mailchimp::LIST_GENERAL_ID, Session::get(Session::KEY_MAILCHIMP_LIST_IDS, []))
|
||||
'isSubscribed' => $hasEmail || in_array(Mailchimp::LIST_GENERAL_ID, Session::get(Session::KEY_MAILCHIMP_LIST_IDS, []))
|
||||
]];
|
||||
}
|
||||
//
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ class Blog
|
|||
public static function getPosts()
|
||||
{
|
||||
$posts = [];
|
||||
foreach(glob(ROOT_DIR.'/blog/posts/*.md') as $file)
|
||||
foreach(static::getAllPostPaths() as $file)
|
||||
{
|
||||
$posts[] = Post::fromFile($file);
|
||||
}
|
||||
|
|
@ -33,13 +33,18 @@ class Blog
|
|||
{
|
||||
if (!static::$slugMap)
|
||||
{
|
||||
foreach(glob(ROOT_DIR.'/blog/posts/*.md') as $file)
|
||||
foreach(static::getAllPostPaths() as $file)
|
||||
{
|
||||
static::$slugMap[static::getSlugFromFilename($file)] = $file;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
protected static function getAllPostPaths()
|
||||
{
|
||||
return glob(ROOT_DIR . '/view/posts/*.md');
|
||||
}
|
||||
|
||||
public static function getSlugMap()
|
||||
{
|
||||
static::initSlugMap();
|
||||
|
|
@ -19,6 +19,11 @@ class Post
|
|||
$this->contentHtml = ParsedownExtra::instance()->text(trim($markdown));
|
||||
}
|
||||
|
||||
public function getRelativeUrl()
|
||||
{
|
||||
return BlogActions::URL_STEM . '/' . $this->slug;
|
||||
}
|
||||
|
||||
public function getSlug()
|
||||
{
|
||||
return $this->slug;
|
||||
|
|
@ -57,4 +62,39 @@ class Post
|
|||
$key = array_search($this->getSlug(), $slugs);
|
||||
return $key === false || $key >= count($slugs)-1 ? null : Blog::getPost($slugs[$key+1]);
|
||||
}
|
||||
|
||||
public function getAuthorName()
|
||||
{
|
||||
switch(strtolower($this->author))
|
||||
{
|
||||
case 'jeremy':
|
||||
return 'Jeremy Kauffman';
|
||||
case 'mike':
|
||||
return 'Mike Vine';
|
||||
case 'jimmy':
|
||||
return 'Jimmy Kiselak';
|
||||
case 'jack':
|
||||
return 'Jack Robison';
|
||||
case 'lbry':
|
||||
default:
|
||||
return 'Samuel Bryan';
|
||||
}
|
||||
}
|
||||
|
||||
public function getAuthorBioHtml()
|
||||
{
|
||||
switch(strtolower($this->author))
|
||||
{
|
||||
case 'jeremy':
|
||||
return '<p>Jeremy is the creator of TopScore (usetopscore.com), LBRY (lbry.io), and that joke where the first two items in your list are serious while the third one is a run-on sentence.</p>';
|
||||
case 'mike':
|
||||
case 'jimmy':
|
||||
return '<p>' . $this->getAuthorName() . ' is one of the founding members of LBRY.</p>';
|
||||
case 'jack':
|
||||
return '<p>Jack was one of the first people to discover LBRY and took to it so fast he may understand more about it than anyone. He has Asperger\'s Syndrome and is actively involved in the autism community.</p>';
|
||||
case 'lbry':
|
||||
default:
|
||||
return '<p>Much of our writing is a collaboration between LBRY team members, so we use SamueL BRYan to share credit. Sam has become a friend... an imaginary friend... even though we\'re adults...</p>';
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -62,7 +62,7 @@ class View
|
|||
|
||||
protected static function getFullPath($template)
|
||||
{
|
||||
return ROOT_DIR . '/view/' . $template . '.php';
|
||||
return ROOT_DIR . '/view/template/' . $template . '.php';
|
||||
}
|
||||
|
||||
public static function imagePath($image)
|
||||
|
|
|
|||
|
|
@ -1,21 +0,0 @@
|
|||
<?php Response::setMetaDescription('Access information and content in ways you never dreamed possible. Earn credits for your unused bandwidth and diskspace.') ?>
|
||||
<?php echo View::render('nav/header', ['isDark' => false]) ?>
|
||||
<main>
|
||||
<div class="hero hero-quote hero-img spacer2" style="background-image: url(/img/frontdesk.jpg)">
|
||||
<div class="hero-content-wrapper">
|
||||
<div class="hero-content blog-header">
|
||||
<h1>The Front Desk</h1>
|
||||
<p>News and musings from the LBRY team.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content post-list">
|
||||
<?php foreach($posts as $post): ?>
|
||||
<div>
|
||||
<a href="/blog/<?php echo $post->getSlug() ?>"><?php echo $post->getTitle() ?></a>
|
||||
<span title="<?php echo $post->getDate()->format('F jS, Y') ?>"><?php echo $post->getDate()->format('M j') ?></span>
|
||||
</div>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
</main>
|
||||
<?php echo View::render('nav/footer') ?>
|
||||
|
|
@ -1,74 +0,0 @@
|
|||
<?php Response::setMetaDescription($post->getTitle()) ?>
|
||||
<?php echo View::render('nav/header') ?>
|
||||
<main class='blog-post'>
|
||||
|
||||
<header class="content">
|
||||
<a href="/blog"><< Return to LBRY Front Desk</a>
|
||||
</header>
|
||||
|
||||
<div class="content">
|
||||
<div class="date" title="<?php echo $post->getDate()->format('F jS, Y') ?>">
|
||||
<?php echo $post->getDate()->format('M j') ?>
|
||||
</div>
|
||||
<h1><?php echo htmlentities($post->getTitle()) ?></h1>
|
||||
<?php echo $post->getContentHtml() ?>
|
||||
</div>
|
||||
|
||||
<nav class="content prev-next row-fluid">
|
||||
<div class="prev span5">
|
||||
<?php if ($prevPost = $post->getPrevPost()): ?>
|
||||
<div class="prev-next-label">
|
||||
<a href="/blog/<?php echo $prevPost->getSlug() ?>"><< Previous</a>
|
||||
</div>
|
||||
<a class="prev-next-title" href="/blog/<?php echo $prevPost->getSlug() ?>">
|
||||
<?php echo htmlentities($prevPost->getTitle()) ?>
|
||||
</a>
|
||||
<?php endif ?>
|
||||
</div>
|
||||
<div class="next span2"></div>
|
||||
<div class="next span5">
|
||||
<?php if ($nextPost = $post->getNextPost()): ?>
|
||||
<div class="prev-next-label">
|
||||
<a href="/blog/<?php echo $nextPost->getSlug() ?>">Next >></a>
|
||||
</div>
|
||||
<a class="prev-next-title" href="/blog/<?php echo $nextPost->getSlug() ?>">
|
||||
<?php echo htmlentities($nextPost->getTitle()) ?>
|
||||
</a>
|
||||
<?php endif ?>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<section class="author">
|
||||
<div class="content">
|
||||
<em>Author</em>
|
||||
<?php switch(strtolower($post->getAuthor())):
|
||||
case 'jeremy' ?>
|
||||
<h2>Jeremy Kauffman</h2>
|
||||
<p>
|
||||
Jeremy is the creator of TopScore (usetopscore.com), LBRY (lbry.io), and that joke where the first two items in your list are serious while the third one is a run-on sentence.
|
||||
</p>
|
||||
<?php break ?>
|
||||
<?php case 'mike': ?>
|
||||
<h2>Mike Vine</h2>
|
||||
<?php break ?>
|
||||
<?php case 'jimmy': ?>
|
||||
<h2>Jimmy Kiselak</h2>
|
||||
<?php break ?>
|
||||
<?php case 'jack': ?>
|
||||
<h2>Jack Robison</h2>
|
||||
<p>
|
||||
Jack was one of the first people to discover LBRY and took to it so fast he may understand more about it than anyone. He has Asperger's Syndrome and is actively involved in the autism community.
|
||||
</p>
|
||||
<?php break ?>
|
||||
<?php case 'lbry': ?>
|
||||
<h2>Samuel Bryan</h2>
|
||||
<p>
|
||||
Much of our writing is a collaboration between LBRY team members, so we use SamueL BRYan to share credit. Sam has become a friend... an imaginary friend... even though we're adults...
|
||||
</p>
|
||||
<?php break ?>
|
||||
<?php endswitch ?>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
<?php echo View::render('nav/footer') ?>
|
||||
|
|
@ -10,7 +10,7 @@ Perhaps the most-asked question we receive is: Why have you created LBC, rather
|
|||
|
||||
There are three important reasons why we must use LBC instead of Bitcoin. Some of it is highly technical, so please bear with us as we attempt to translate into plain English.
|
||||
|
||||
**Reason #1 – Using LBC instead of Bitcoin makes verifying content ownership possible for lightweight clients.**
|
||||
### Reason #1 – Using LBC instead of Bitcoin makes verifying content ownership possible for lightweight clients.
|
||||
|
||||
In blockchain-based systems, data (in the case of Bitcoin, transactions) are grouped into multiple packages called blocks. These blocks are “chained” one after another to form the public ledger known as the blockchain. Each block starts with a block header, a comparatively tiny piece of data, which has some metadata about the block such as the time it was mined and a reference to the block that came before it. That metadata also includes a cryptographic value which can be used to prove to someone who doesn’t have (or want) the whole block, but has all of the block headers, that a given transaction was included in that block and therefore into the blockchain. This is used by so-called *lightweight clients*, which make it possible for people to use bitcoin on devices that wouldn’t be able to handle the full blockchain, like web browsers and smartphones.
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ LBC block headers contain an additional piece of information: a value which can
|
|||
|
||||
This is necessary for LBRY because unlike systems built on Bitcoin or other existing altcoins, LBRY’s naming system assigns ownership over content through an ongoing auction. Whoever pledges the most credits against a name holds it, subject to a defined window for a counter-bid. These bids are stored in a special tree-shaped data structure on the hard drives of all miners. Whenever the winning bid for a name changes, that change has an effect which spreads all the way up the tree and into the special piece of information stored in LBC block headers.
|
||||
|
||||
**Reason #2 – LBRY could easily overwhelm the maximum transaction volume allowed by Bitcoin.**
|
||||
### Reason #2 – LBRY could easily overwhelm the maximum transaction volume allowed by Bitcoin.
|
||||
|
||||
LBRY intends to thrive on microtransactions that are looking increasingly implausible with Bitcoin. By now, everyone interested in cryptocurrency is all-too-intimately familiar with the limitations of Bitcoin’s current block size. Currently, Bitcoin has a limit of one megabyte of data per block. If enough transactions happen over the network that the one-megabyte limit is reached, all additional transactions are considerably delayed. That’s why we’re currently seeing reports of transaction times in the high double-digits.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ The problem is a double bind. If the block size stays low, then transactions gri
|
|||
|
||||
If LBRY starts growing exponentially, we don’t want to worry about contributing to the delinquency of the Bitcoin blockchain by overwhelming it with microtransactions. And in the immediate future, we don’t want to see payments to artists eaten up by Bitcoin’s rising fees.
|
||||
|
||||
**Reason #3 - Decentralization and independence are good for progress.**
|
||||
### Reason #3 - Decentralization and independence are good for progress.
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -36,7 +36,7 @@ In the early days of our protocol, LBRY Inc. will be making a concerted effort t
|
|||
|
||||
Bitcoin was created as a grand experiment to demonstrate blockchain technology and liberate the world from legacy banking, but it couldn’t possibly have been designed to be all things to all applications. We believe our appcoin is the best tool to succeed at our mission of putting every film, song, book, and game ever made onto a blockchain – without trying to displace Bitcoin as a global currency.
|
||||
|
||||
**Wait! This is also relevant to your interests:**
|
||||
### Wait! This is also relevant to your interests
|
||||
|
||||
Converting from fiat money to cryptocash is hard. But converting between cryptos is super-easy, especially since the launch of [ShapeShift.io](http://www.shapeshift.io/). So LBRYians can earn LBC and quickly convert it to BTC to save or spend. And Bitcoiners can easily convert a bit of their holdings to LBC to get great content on the LBRY network.
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ date: '2016-03-21 20:06:18'
|
|||
|
||||
Understanding autism is personal for us.
|
||||
|
||||
<img src="http://i.imgur.com/gDip22e.jpg" alt="Built for Artists by Autists: LBRY Takes Autism Personally">
|
||||
|
||||
|
||||
A recent New York Times [op-ed](http://well.blogs.nytimes.com/2016/03/18/an-experimental-autism-treatment-cost-me-my-marriage/) by John Elder Robison tells the story of his life before and after taking part in a groundbreaking experiment into using an innovative electromagnetic therapy to perhaps remediate a core disability of autism. Robison, who is on the autism spectrum had a successful career and family life, but nevertheless faced personal challenges and decided to try TMS, or transcranial magnetic stimulation, to gain greater insight into the emotional cues and nonverbal communications of other people. Researchers hoped to gain better insight into how TMS might help address these challenges. Robison hopes these insights will one day form the basis of therapies, and he himself experienced great rewards - even from this early stage experiment. The treatment granted him the ability to better read and feel emotions, but it was quite a ride. His marriage fell apart, and many of his personal relationships became strained for years. Conversely, with new eyes, he formed many new relationships, he re-married, and many others relationships grew stronger.
|
||||
|
||||
236
view/posts/37-art.md
Normal file
236
view/posts/37-art.md
Normal file
|
|
@ -0,0 +1,236 @@
|
|||
---
|
||||
author: jeremy, zargham, jack
|
||||
title: Art in the Internet Age
|
||||
date: '2016-03-21 20:06:18'
|
||||
cover: /img/altamira-bison.jpg
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
In 34,000 B.C., there were cave paintings. And that’s it. When you came home from a sweltering August day of foraging along the Vézère river, the only form of non-live art or entertainment available was something like the above buffalo.
|
||||
|
||||
Today, we live in a world of near infinite choices. This is true not just for art but for all kinds of things (like potato chips). Since the era of cave art, humanity has incessantly and progressively trended towards interconnected, more efficient, and increasingly transparent markets. This undercurrent of connectedness and openness has affected everything human beings produce.
|
||||
|
||||
Nerds like us like to speculate about the end-game of this trend with others on the internet. What will society be like when we have a "Star Trek"-like capacity to instantly and freely replicate anything that exists? The term for this society is _post-scarcity_<sup>[1](#note-post-scarcity)</sup>.
|
||||
|
||||
Generally, post-scarcity is regarded as fantastical; something that will never happen in our lifetimes. Except for one area: digital goods.
|
||||
|
||||
Art in the internet age is infinitely reproducible and easily shared. This is a sea change from any prior time in history. Previously, vinyl records captured audio in physical grooves; tapes captured data on magnetic strips; compact disks held digital files read by lasers—in each of these cases physical, medium-specific hardware is required to both produce and recover the bits of data that made up the digital content.
|
||||
|
||||
Today art is just data, a string of 1s and 0s, a _number_, and we no longer need any specialized hardware to decode and enjoy digital content. We use the same technological methods to access a personal photograph a single time as we do to watch a blockbuster on Netflix.
|
||||
|
||||
This is a big step forward from the past. As production costs fall to zero, choices go up. Digital distributors provide virtually every song, film, photo or book for purchase and download to any internet enabled device. Technology has decreased the cost of production, too -- it has never been easier for aspirant artists to achieve a following through self-publishing.
|
||||
|
||||
The digitization of art has added a lot of value to both content creators and consumers, reducing costs and increasing choice. This transition is still in its infancy. With LBRY, we’re going to make it a little more mature.
|
||||
|
||||
<footer id="note-post-scarcity"><sup>1</sup> Note that post-scarcity does not eliminate the need to create _new_ goods, it just eliminates or reduces the costs of _duplicating_ goods to nothing. As long as people desire goods that did not previously exist, there will always be a market demand for creation, even in a post-scarcity world.</footer>
|
||||
|
||||
## A People’s Marketplace
|
||||
|
||||
LBRY is the first digital marketplace to be controlled by the market’s participants rather than a corporation or other 3rd-party. It is the most open, fair, and efficient marketplace for digital goods ever created, with an incentive design encouraging it to become the most complete.
|
||||
|
||||
At the highest level, LBRY does something extraordinarily simple. LBRY creates an association between a unique name and a piece of digital content, such as a movie, book, or game. This is similar to the domain name system that you are most likely using to access this very post.
|
||||
|
||||
<div class="text-center meta spacer1">
|
||||
|
||||
<div class="content-inset">A user searches and prepares to stream and the film _It’s a Wonderful Life_, located at [lbry://wonderfullife](lbry://wonderfullife), via a completely decentralized network. Try it out for yourself at [lbry.io/get](http://lbry.io/get).</div>
|
||||
|
||||
</div>
|
||||
|
||||
However, LBRY does this not through a proprietary service or network, but as a _protocol_, or a method of doing things, much like HTTP, DNS and other specifications that make up the internet itself. Just as many different domains owned by many different companies all speak a shared language, so too can any person or company speak LBRY. No special access or permission is needed.
|
||||
|
||||
LBRY differs from the status quo in three big ways:
|
||||
|
||||
1. **Coupled payment and access**. If desired, the person who publishes to [lbry://wonderfullife](lbry://wonderfullife) can charge a fee to users that view the content.
|
||||
2. **Decentralized and distributed**. Content published to LBRY is not specific to one computer or network. No one party, including us, can unilaterally remove or block content on the LBRY network. (If it worries you that LBRY could facilitate unsavory content, this is discussed in its own section.)
|
||||
3. **Domain names are controlled via ongoing auction**. This facilitates names being controlled by the publishers that value them most. These transactions take place via an electronic currency called LBRY credits, or _LBC_. This is covered in more detail, below.
|
||||
|
||||
While creating a protocol that we ourselves cannot control sounds chaotic, it is actually about establishing trust. Every other publishing system requires trusting an intermediary that can unilaterally change the rules on you. What happens when you build your business on YouTube or Amazon and they change fees? Or Apple drops your content because the Premier of China thought your comedy went to far?
|
||||
|
||||
Only LBRY consists of a known, promised set of rules that no one can unilaterally change. LBRY provides this by doing something unique: leaving the _users_ in control rather than demanding that control for itself.
|
||||
|
||||
## A Sample Use
|
||||
|
||||
Let’s look at a sample use of LBRY, Ernest releasing a film on LBRY that is later purchased and viewed by Hilary.
|
||||
|
||||
1. Ernest wants to release his comedy-horror film, _Ernie Goes To Guantanamo Bay_.
|
||||
2. The content is encrypted and sliced into many pieces. These pieces are stored by hosts.
|
||||
3. Ernest reserves [lbry://erniebythebay](lbry://erniebythebay), a name pointing to his content.
|
||||
4. When Ernest reserves the location, he also submits metadata, such as a description and thumbnail.
|
||||
5. Hillary, a user, browses the LBRY network and decides she wants to watch the film.
|
||||
6. Hillary issues a payment to Ernest for the decryption key, allowing her to watch the film.
|
||||
7. Hillary’s LBRY client collects the pieces from the hosts and reassembles them, using the key to decrypt the pieces (if necessary). This is transparent to Hillary, the film streams within a few seconds after purchase.
|
||||
|
||||
This is a lot like an interaction that can happen on many different sites on the web, except that this one happens via a network that is completely decentralized. The data and technology that makes the entire interaction possible is not reliant on nor controlled by any single entity (as it would be via YouTube, Amazon, etc.).
|
||||
|
||||
## The LBRY Network
|
||||
|
||||
To understand precisely what LBRY is and why it matters, one must understand both LBRY as a protocol and the services the protocol enables. HTTP is the protocol that makes web browsing possible, but it would be of little interest without the service of a web browser!
|
||||
|
||||
To understand LBRY, think of LBRY in terms of two layers: _protocol_ and _service._ The protocol provides a fundamental, underlying technological capability. The service layer utilizes the protocol to do something that a human being would actually find useful.
|
||||
|
||||
For a user using LBRY at the service level, the magic of what the LBRY protocol does will be largely transparent, much as a typical internet user sees nothing of how HTTP works. Via a LBRY application, a user will be able to open a familiar interface to quickly and easily discover and purchase a piece of digital content published by anyone in the world.
|
||||
|
||||
However, such an application would not be possible without the LBRY the underlying layer, the LBRY protocol.
|
||||
|
||||
### Layer 1: Protocol
|
||||
|
||||
While the protocol is one comprehensive set of rules, it is easier to understand as two parts.
|
||||
|
||||
#### Part A: The LBRY Blockchain
|
||||
|
||||
A _blockchain_, or _distributed ledger_ is the key innovation behind the Bitcoin network. Blockchains solved the very complicated technological problem of having a bunch of distributed, disparate entities all agree on a rivalrous state of affairs (like how much money they owe each other).
|
||||
|
||||
Like Bitcoin, the LBRY blockchain maintain balances -- in this case, balances of _LBC_, LBRY’s unit of credit. More importantly, the LBRY blockchain also provides a decentralized lookup and metadata storage system. The LBRY blockchain supports a specific set of commands that allows anyone to bid (in LBC) to control a LBRY _name_, which is a lot like a domain name. Whoever controls a name gets to describe what it contains, what it costs to access, who to pay, and where to find it. These names are sold in a continuous running auction. We will talk more about this system a little later on.
|
||||
|
||||
If you’re a programmer, you might recognize the LBRY blockchain as a _key-value store_. Each key, or name, corresponds to a value, or a metadata entry. Whichever party or parties bid the most LBC gets to control the metadata returned by a key lookup.
|
||||
|
||||
Here is a sample key-value entry in the LBRY blockchain. Here, wonderfullife is the key, and the rest of the description is the value.
|
||||
|
||||
<div class="code-bash">`
|
||||
|
||||
<pre style="white-space: pre-wrap;"> <span class="code-bash-kw1">wonderfullife</span> : {
|
||||
<span class="code-bash-kw2">title</span>: "It’s a Wonderful Life",
|
||||
<span class="code-bash-kw2">description</span>: "An angel helps a compassionate but despairingly frustrated businessman by showing what life would have been like if he never existed.",
|
||||
<span class="code-bash-kw2">thumbnail</span>: "http://i.imgur.com/MW45x88.jpg",
|
||||
<span class="code-bash-kw2">license</span>: "public domain",
|
||||
<span class="code-bash-kw2">price</span>: 0, <span class="code-bash-comment">//free!</span>
|
||||
<span class="code-bash-kw2">publisher</span>: "A Fan Of George Bailey", <span class="code-bash-comment">//simplification</span>
|
||||
<span class="code-bash-kw2">sources</span>: { <span class="code-bash-comment">//extensible, variable list</span>
|
||||
<span class="code-bash-kw2">lbry_hash</span> : <unique id>,
|
||||
<span class="code-bash-kw2">url</span> : <url>
|
||||
}
|
||||
}</pre>
|
||||
|
||||
`</div>
|
||||
|
||||
<div class="meta text-center content-inset">
|
||||
|
||||
A slightly simplified sample entry of metadata in the LBRY blockchain. Whichever party or parties bid the most in an ongoing auction control what a name returns.
|
||||
|
||||
</div>
|
||||
|
||||
Other than the usage of the LBRY blockchain to store names and metadata, there are only minor differences between the blockchains of LBRY and Bitcoin, and the changes are generally consensus improvements. We’ve buffed the hashing algorithm, smoothed the block reward function, increased the block size, increased the total number of credits, and prepared for offchain settlement.
|
||||
|
||||
The LBRY blockchain simply maintains LBC balances and a content namespace/catalogue. The next part, LBRYnet, specifies what to do with this data. To compare to the existing web, the blockchain is like the domain system (it maintains a listing of what is available), while the next piece makes it possible to actually fetch and pay for content.
|
||||
|
||||
<footer>If you’re a Bitcoiner wondering why we don’t use the Bitcoin blockchain, you can read a detailed answer to that question [here](https://blog.lbry.io/why-doesnt-lbry-just-use-bitcoin/).</footer>
|
||||
|
||||
#### Part B: The Data Network (LBRYNet)
|
||||
|
||||
LBRYNet is the layer that makes the LBRY blockchain useful beyond a simple payment system. It says what to do with the information available in the LBRY blockchain, how to issue payments, how to look up a content identifier, and so on.
|
||||
|
||||
To use the LBRY network, a user’s computer needs the capacity to speak LBRY. That layer is LBRYNet. Just as your computer has a library that enables it to understand HTTP, DNS, and other languages and protocols, LBRYNet is the piece of software that allows your computer to understand how to interact with the LBRY network.
|
||||
|
||||
To understand what role LBRYNet plays, let’s drill a little more into a sample user interaction. Once a user has affirmed access and purchase, such as in step 5 of our Sample Use above, the following happens:
|
||||
|
||||
1. LBRYNet issues a lookup for the name associated with the content. If the client does not have a local copy of the blockchain, this lookup is broadcast to miners or to a service provider. This lookup acquires the metadata associated with the name.
|
||||
2. LBRYNet issues any required payments, as instructed by metadata entries.
|
||||
1. If the content is set to free, nothing happens here.
|
||||
2. If the content is set to have a price in LBC, the client must issue a payment in LBC to the specified address. If the content is published encrypted, LBRYNet will not allow access until this payment has been issued.
|
||||
3. If the content is set to have another payment method, the seller must run or use a service that provides a private server enforcing payment and provisioning accessing keys.
|
||||
3. Simultaneous to #2, LBRYNet uses the metadata to download the content itself.
|
||||
1. The metadata allows chunks to be discovered and assembled in a BitTorrent-like fashion. However, unlike BitTorrent, chunks do not individually identify themselves as part of a greater whole. Chunks are just arbitrary pieces of data.
|
||||
2. If LBRYNet cannot find nodes offering chunks for free, it will offer payments for chunks to other hosts with those chunks.
|
||||
3. This payment is not done via proof-of-bandwidth, or third-party escrow. Instead, LBRYNet uses reputation, trust, and small initial payments to ensure reliable hosts.
|
||||
4. If content is not published directly to LBRY, the metadata can instruct other access methods, such as a Netflix URL. This allows us to catalogue content not yet available on LBRY as well as offer legacy and extensibility purposes.
|
||||
|
||||
### Layer 2: Services
|
||||
|
||||
Services are what actually make the LBRY protocol _useful._ While the LBRY protocol determines what is possible, it is the services that actually do things.
|
||||
|
||||
While the protocol is determined, open, and fixed, the service layer is much more flexible. It is far easier to redesign a website than it is to revise the HTTP protocol itself. The same is true here.
|
||||
|
||||
Additionally, just as in the early days of the internet the later direction of web would have been unfathomable, so too may the best uses of LBRY’s namespace or technology be undiscovered. However, here are some clear uses.
|
||||
|
||||
#### Applications and Devices
|
||||
|
||||
A LBRY application is how a user would actually have meaningful interactions with the LBRY network. A LBRY client packages the power of the LBRY protocol into a simple application that allows the user to simply search for content, pay for it when necessary, download and enjoy.
|
||||
|
||||
Additionally, a LBRY client can allow users to passively participate in the network, allowing them to automatically earn rewards in exchange for contributing bandwidth, disk space, or processing power to the overall network.
|
||||
|
||||
Applications beyond a traditional computer based browser are possible as well. A LBRY television dongle, a LBRY radio, and any number of existing content access mechanisms can be implemented via an analogous LBRY device.
|
||||
|
||||
#### Content Discovery
|
||||
|
||||
Although the namespace provided by the LBRY protocol is helpful towards discovery, much as the web would be much less useful without search engines or aggregators, LBRY needs it’s own discovery mechanisms.
|
||||
|
||||
Search features can be constructed from the catalogue of metadata provided in the blockchain as well as the content transaction history available in the blockchain or observed on the network. All of this data, along with user history, allows for the creation of content recommendation engines and advanced search features.
|
||||
|
||||
Discovery on LBRY can also take the form of featured content. Clients can utilize featured content to provide additional visibility for new content that consumers might not otherwise be looking for.
|
||||
|
||||
#### Content Distribution
|
||||
|
||||
Digital content distributors with server-client models are subject to the whims of internet service providers and hostile foreign governments. Traffic from the host servers can be throttled or halted altogether if the owners of cables and routers so choose. However, in case of the LBRY protocol content comes from anywhere and everywhere, and is therefore not so easily stifled.
|
||||
|
||||
Additionally, the market mechanisms of LBRY create a strong incentive for efficient distribution, which will save the costs of producers and ISPs alike. These properties, along with LBRY’s infringement disincentivizing properties, make LBRY an appealing technology for large existing data or content distributors.
|
||||
|
||||
#### Transaction Settlement
|
||||
|
||||
While payments can be issued directly on the LBRY blockchain, the LBRY protocol encourages a volume of transactions that will not scale without usage of offchain settlement.
|
||||
|
||||
Essentially, rather than issue a transaction to the core blockchain, transactions are issued to a 3rd-party provider. These providers have a substantial number of coins which are used to maintain balances internally and settle a smaller number of transactions to the core chain. In exchange, these providers earn a small fee, less than the fee required to issue the transaction directly to the blockchain.
|
||||
|
||||
## LBRY Credits
|
||||
|
||||
LBRY Credits, or _LBC_, are the unit of account for LBRY. Eventually 1,000,000,000 LBC will exist, according to a defined schedule over 20 years. The schedule decays exponentially, with around 100,000,000 in the first year.
|
||||
|
||||
Additionally, some credits are awarded on a fixed basis. The total break down looks like this:
|
||||
|
||||
* 10% are used to peg LBC to Bitcoin, likely via a sidechain. This will allow LBRY to leverage the security of the Bitcoin blockchain, and incentive adoption from Bitcoin users.
|
||||
* 10% for organizations, charities, and other strategic partners. Organizations the EFF, ACLU, and others that have fought for digital rights and the security and freedom of the internet.
|
||||
* 10% for adoption programs. We’ll be giving out lots of bonus credits, especially in the early days of LBRY, in order to encourage participation. We will also look to award credits broadly, ensuring the marketplace is egalitarian.
|
||||
* 10% for us. For operational costs as well as profit.
|
||||
* 60% earned by LBRY users, via mining the LBRY cryptocurrency.
|
||||
|
||||
## More on Naming
|
||||
|
||||
LBRY names are one of the most unique aspects of LBRY and one that we believe will play a big role in helping it succeed.
|
||||
|
||||
Control of a LBRY name is awarded via a _continuous running auction_ in LBC. Bids are entered into a _trustless escrow_, marking the credits as unspendable, but leaving them intact. When a user looks up a name, the name resolves to the largest bid made by a party or parties. The ability for any number of people to have a say in where a name resolves is part of what makes LBRY a system controlled by its users. As the credits are distributed primarily among users and producers, it is community itself that has ultimate controls over the catalogue of what is available.
|
||||
|
||||
Additionally, bids can also be retracted at any time, even if you’re the current winning bidder. To prevent a name from rapidly switching between multiple resolutions, the parties that have existing control of a name have a reasonable period of time to respond to counter bids before a name’s resolution switches.
|
||||
|
||||
It’s possible this system sounds like chaos to you, but we’re betting on a Nobel-prize winning result that predicts the opposite. Economist Ronald Coase theorized that in a system with low transaction cost and clear rules, property will be held by those who value it the most. Since LBRY names are the equivalent to content storefronts, we believe that LBRY names will hold the most value to rightsholders who produce content associated with a given name.
|
||||
|
||||
As names in demand on LBRY will be more expensive, the names themselves will also serve as a signal of reputation, legitimacy, and quality. If a user searches LBRY for _Spider Man_ and sees one at lbry://spiderman and one at lbry://spiderman_russhaxor, there will be little doubt that the latter is less legitimate.
|
||||
|
||||
<footer>
|
||||
|
||||
It is also worth noting that in the event that LBRY received notice that either name contained an illegitimate copy of _Spider Man_, LBRY would dutifully and quickly put that content id on a blacklist, blocking discovery or purchase via any legal services. LBRY and users of LBRY are still subject to the DMCA and other relevant laws of their respective countries.
|
||||
|
||||
</footer>
|
||||
|
||||
## Combatting The Ugly
|
||||
|
||||
As neither naïfs nor knaves, we acknowledge that LBRY can be used for bad ends. Technology is frequently this way. Encryption protects our privacy -- as well as that of terrorists. Cars allow us to travel marvelous distances -- and kill millions per year.
|
||||
|
||||
The downside to LBRY is that it can be used to exchange illegal content. However, several factors of LBRY make illicit usage less likely than it may seem at first consideration. On the whole, as with the car and encryption, the benefits of LBRY clearly outway nefarious uses.
|
||||
|
||||
To evaluate a technology’s effect, we must consider where it moves us from the current state of affairs, not judge against a Platonic ideal or past eta. In assessing LBRY, we must compare it to a world in which BitTorrent already exists and is quite popular, not the 1950s. LBRY is an improvement over BitTorrent in combatting unsavory content in at least five ways:
|
||||
|
||||
1. **More records.** LBRY contains a public ledger of transactions recording name purchases and content publishings. As many purchases make it onto the ledger as well, this means infringing actions are frequently recorded _forever,_ or are at a minimum widely observable.
|
||||
2. **Unilateral removal.** The LBRY naming system allows for quick, unilateral acquisition of infringing URIs. Once a BitTorrent magnet hash is in the wild, there is no mechanism to update or alter its resolution whatsoever. If a LBRY name is pointing to infringing content, it can be seized according to clear rules.
|
||||
3. **Blacklists**. LBRY will publish and maintain a blacklist of infringing names. All clients we release and all legal clients will have to follow our blacklist, or one like it, or face substantial penalties. Especially because…
|
||||
4. **Stiffer penalties.** Penalties for profiting off of infringement are far stronger and involve can involve jail time, while infringement without profit only results in statutory damages. This serves as a far stronger deterrent for all infringing uses than BitTorrent provides.
|
||||
5. **Expensive or impossible.** Offchain settlement will be a requirement for efficient purchases at any significant network size. Settlement providers, ourselves included, will be able to block purchases for infringing content. At significant traffic volume, if infringing content can’t be outright removed or blocked, transaction fees will make it prohibitively expensive.
|
||||
|
||||
And of course, let’s not forget that LBRY users are still subject to the DMCA and other laws governing intellectual property. Users who publishing infringing content are still subject to penalties for doing so in exactly the same way they would be via BitTorrent. LBRY only adds to the suite of options available. This makes LBRY a strict improvement over BitTorrent with regards to illegal usages, which provides none of the mechanisms listed.
|
||||
|
||||
## Our Values
|
||||
|
||||
We want to be the first digital content marketplace to:
|
||||
|
||||
1. **Treat users like adults** LBRY doesn’t play nanny. It encourages individual people to express their own preferences, rather than force our own onto them. We enable consumers to make their own choices about where and who they want to purchase digital content from.
|
||||
2. **Operate openly, inclusively, and transparently** Anyone can publish or interact with the LBRY network. No one needs permission from us or anyone else. LBRY encourages all parties to participate in the network, rather than the creation of walled gardens. LBRY is a completely open specification and all code is open source.
|
||||
3. **Prove decentralization doesn’t mean infringement** Existing decentralized publishing protocols offer no way for rightsholders to combat or capture profits from illegally shared content. LBRY’s service layer, blacklisting mechanisms, and naming system all improve the status quo.
|
||||
4. **Acknowledge modern digital realities and ethical norms** Prohibition has failed at every turn and in every iteration. Regulating human behavior only works when it aligns with moral norms that are shared by the majority of the population. If it is impossible to keep drugs out of prisons, it will never be possible to enforce copyright via analogous tactics on the infinitely less-controlled internet. Instead, focus on enticement. While legal compliance is paramount, concentrate as much as possible on making a system that relies more on giving people no excuse to do the wrong thing.
|
||||
5. **Collect no rent**. Whatever an artist or creator charges for their work should go to them. Distributing bits is exceedingly simple. There’s no need to give 45% to YouTube or 30% to Apple. Collecting no rent isn’t just a promise, it’s hard coded. The nature of LBRY means this could never be done -- by us or anyone else.
|
||||
|
||||
## TL;DR
|
||||
|
||||
Digital art is one of the first goods to evolve beyond scarcity. This evolution is changing the way content is discovered, publicized, paid for and delivered. Heretofore, the lack of transparency and monetization mechanisms in peer-to-peer sharing networks has largely enabled piracy. By equipping a peer-to-peer protocol with a digital currency and transparent decentralized ledger, the LBRY protocol opens the door to a new era of digital content distribution making peer-to-peer content distribution suitable for major publishing housing, self-publishers and everyone in between.
|
||||
|
||||
If LBRY succeeds, we will enter a world that is even more creative, connected, and conservatory. We will waste less and we make more. We will create a world where a teenager in Kenya and a reality star in Los Angeles use the same tool to search the same network and have access to the same results -- a world where information, knowledge, and imagination know no borders.
|
||||
|
||||
Build our dream with us. Download LBRY at [lbry.io/get](https://lbry.io/get).
|
||||
12
view/template/blog/author.php
Normal file
12
view/template/blog/author.php
Normal file
|
|
@ -0,0 +1,12 @@
|
|||
<section class="post-author-spotlight cover cover-dark cover-dark-grad">
|
||||
<div class="content content-dark">
|
||||
<div class="row-fluid">
|
||||
<div class="span3">(photo)</div>
|
||||
<div class="span9">
|
||||
<div class="meta">Author</div>
|
||||
<h3><?php echo $authorName ?></h3>
|
||||
<?php echo $authorBioHtml ?>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
21
view/template/blog/index.php
Normal file
21
view/template/blog/index.php
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
<?php Response::setMetaDescription('Access information and content in ways you never dreamed possible. Earn credits for your unused bandwidth and diskspace.') ?>
|
||||
<?php echo View::render('nav/header', ['isDark' => false]) ?>
|
||||
<main>
|
||||
<div class="hero hero-quote hero-img spacer2" style="background-image: url(/img/cover-team.jpg)">
|
||||
<div class="hero-content-wrapper">
|
||||
<div class="hero-content text-center">
|
||||
<h1 class="cover-title">The Front Desk</h1>
|
||||
<h2 class="cover-subtitle">News and musings from the LBRY team.</h2>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content spacer2">
|
||||
<?php foreach($posts as $post): ?>
|
||||
<div class="spacer1">
|
||||
<h3><a href="<?php echo $post->getRelativeUrl() ?>" class="link-primary"><?php echo $post->getTitle() ?></a></h3>
|
||||
<div class="meta" title="<?php echo $post->getDate()->format('F jS, Y') ?>"><?php echo $post->getDate()->format('M j, Y') ?></div>
|
||||
</div>
|
||||
<?php endforeach ?>
|
||||
</section>>
|
||||
</main>
|
||||
<?php echo View::render('nav/footer') ?>
|
||||
49
view/template/blog/post.php
Normal file
49
view/template/blog/post.php
Normal file
|
|
@ -0,0 +1,49 @@
|
|||
<?php Response::setMetaDescription($post->getTitle()) ?>
|
||||
<?php echo View::render('nav/header') ?>
|
||||
<main>
|
||||
<section class="content spacer2">
|
||||
<h1><?php echo htmlentities($post->getTitle()) ?></h1>
|
||||
<div class="meta spacer1" title="<?php echo $post->getDate()->format('F jS, Y') ?>">
|
||||
<div class="clearfix">
|
||||
<div class="pull-left spacer1"><?php echo $post->getAuthorName() ?></div>
|
||||
<div class="pull-right spacer1"><?php echo $post->getDate()->format('M j') ?></div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="post-content">
|
||||
<?php echo $post->getContentHtml() ?>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<nav class="content prev-next row-fluid">
|
||||
<div class="prev span6">
|
||||
<?php if ($prevPost = $post->getPrevPost()): ?>
|
||||
<div class="prev-next-label">
|
||||
<a href="<?php echo $prevPost->getRelativeUrl() ?>" class="link-primary">‹ Previous</a>
|
||||
</div>
|
||||
<div class="meta">
|
||||
<a href="<?php echo $prevPost->getRelativeUrl() ?>">
|
||||
<?php echo htmlentities($prevPost->getTitle()) ?>
|
||||
</a>
|
||||
</div>
|
||||
<?php endif ?>
|
||||
</div>
|
||||
<div class="next span6">
|
||||
<?php if ($nextPost = $post->getNextPost()): ?>
|
||||
<div class="prev-next-label">
|
||||
<a href="<?php echo $nextPost->getRelativeUrl() ?>" class="link-primary">Next ›</a>
|
||||
</div>
|
||||
<div class="meta">
|
||||
<a class="prev-next-title" href="<?php echo $nextPost->getRelativeUrl() ?>">
|
||||
<?php echo htmlentities($nextPost->getTitle()) ?>
|
||||
</a>
|
||||
</div>
|
||||
<?php endif ?>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<?php echo View::render('blog/author', [
|
||||
'post' => $post
|
||||
]) ?>
|
||||
|
||||
</main>
|
||||
<?php echo View::render('nav/footer') ?>
|
||||
|
|
@ -12,7 +12,7 @@
|
|||
'LBRY' ?>
|
||||
<title><?php echo $title ?></title>
|
||||
|
||||
<link href='https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,600|Raleway:300,300italic,400,600' rel='stylesheet' type='text/css'>
|
||||
<link href='https://fonts.googleapis.com/css?family=Merriweather:300,300italic,700,700italic|Raleway:400,400italic,500,500italic' rel='stylesheet' type='text/css'>
|
||||
<link href="/css/all.css" rel="stylesheet" type="text/css" media="screen,print" />
|
||||
<link rel="apple-touch-icon" sizes="60x60" href="/img/fav/apple-touch-icon-60x60.png">
|
||||
<link rel="apple-touch-icon" sizes="114x114" href="/img/fav/apple-touch-icon-114x114.png">
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
<?php define('FOOTER_RENDERED', true) ?>
|
||||
<div class="footer">
|
||||
<div class="content">
|
||||
<div class="control-group">
|
||||
<nav class="control-group">
|
||||
<div class="control-item">
|
||||
<a href="/"><?php echo __('Home') ?></a>
|
||||
</div>
|
||||
|
|
@ -12,7 +12,7 @@
|
|||
<img src="/img/Free-speech-flag.svg" alt="Free Speech Flag" height="30"/>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
<?php endif ?>
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
<?php foreach([
|
||||
// '/fund' => __('Fund'),
|
||||
'/get' => __('Get'),
|
||||
'https://blog.lbry.io' => __('News'),
|
||||
'/news' => __('News'),
|
||||
'/learn' => __('Learn')
|
||||
] as $url => $label): ?>
|
||||
<div class="control-item">
|
||||
|
|
@ -19,9 +19,9 @@
|
|||
</a>
|
||||
</div>
|
||||
<div class="fullscreen header-navigation-fullscreen">
|
||||
<div class="control-group">
|
||||
<nav class="control-group">
|
||||
<?php echo View::render('nav/globalItems') ?>
|
||||
</div>
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
<div class="cover cover-dark cover-dark-grad ">
|
||||
<div class="content content-dark spacer2">
|
||||
<div class="content content-dark">
|
||||
<div class="row-fluid">
|
||||
<div class="span6">
|
||||
<h3><?php echo __('Sounds Great. What\'s Next?') ?></h3>
|
||||
|
|
@ -48,24 +48,8 @@
|
|||
<?php if ($_SERVER['REQUEST_URI'] != '/team'): ?>
|
||||
<li>Find out about <a href="/team" class="link-primary">the team behind LBRY</a>.</li>
|
||||
<?php endif ?>
|
||||
<?php /*
|
||||
<li>Access our
|
||||
<a href="https://docs.google.com/document/u/1/d/1F2kcuWa8ccGdDZwAyPs3tddvATjN9rcq3iKkyJp9SYM/edit?usp=drive_web"
|
||||
class="link-primary">business plan</a>.
|
||||
</li>
|
||||
<li>Watch our
|
||||
<a href="https://docs.google.com/presentation/u/1/d/1zaAPzh9cqvwVD5X7Ewn7_vuBWlJcjNPIfYuUg1rVhRo/present?noreplica=1&slide=id.p"
|
||||
class="link-primary">pitch deck</a>.
|
||||
</li>*/ ?>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<?php /*
|
||||
* <div class="content text-center spacer2">
|
||||
<h3>Not Ready to Get Serious?</h3>
|
||||
<p>Join our mailing list for updates about LBRY.</p>
|
||||
|
||||
</div>
|
||||
*/ ?>
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
<p>At the highest level, LBRY does something extraordinarily simple. LBRY creates an association between a unique name and a piece of digital content, such as a movie, book, or game. This is similar to the domain name system that you are most likely using to access this very post.</p>
|
||||
|
||||
<div class="text-center meta spacer1">
|
||||
<img src="/img/lbry_UI.png"/>
|
||||
<img src="/img/lbry-ui.png"/>
|
||||
<div class="content-inset">
|
||||
A user searches and prepares to stream and the film <em>It’s a Wonderful Life</em>, located at <a href="lbry://wonderfullife">lbry://wonderfullife</a>, via a completely decentralized network. Try it out for yourself at <a href="http://lbry.io/get">lbry.io/get</a>.
|
||||
</div>
|
||||
|
|
@ -8,8 +8,8 @@
|
|||
<h1><?php echo __('What?') ?></h1>
|
||||
<div class="spacer1">
|
||||
<div class="spacer1">
|
||||
<a href="/img/lbry-win-ss-783x272.png">
|
||||
<img src="/img/lbry-win-ss-783x272.png" />
|
||||
<a href="/img/lbry-ui.png">
|
||||
<img src="/img/lbry-ui.png" alt="Screenshot of a LBRY browser"/>
|
||||
</a>
|
||||
</div>
|
||||
<p><em>Puts on jargon hat.</em></p>
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
<?php Response::setMetaDescription('Download/install the latest version of LBRY for Linux.') ?>
|
||||
<?php ob_start() ?>
|
||||
<h1>Install LBRY on Linux<span class="icon-linux"></span></h1>
|
||||
<h1>Install LBRY on Linux <span class="icon-linux"></span></h1>
|
||||
<?php echo View::render('get/alphaNotice') ?>
|
||||
<div class="meta spacer1 text-center">Choose an install option.</div>
|
||||
<div class="row-fluid">
|
||||
|
|
@ -3,55 +3,46 @@
|
|||
<?php Response::setMetaDescription('LBRY is founded by a team passionate about connecting producers and consumers and breaking down broken models. Learn more about them.') ?>
|
||||
<?php echo View::render('nav/header', ['isDark' => false]) ?>
|
||||
<main>
|
||||
<div class="content">
|
||||
<h1>About Us</h1>
|
||||
</div>
|
||||
<div class="hero hero-quote hero-img spacer2" style="background-image: url(/img/cover-team.jpg)">
|
||||
<div class="hero-content-wrapper">
|
||||
<div class="hero-content">
|
||||
<blockquote class="blockquote-large">
|
||||
<p>LBRY is so simple your Grandma can use it. I’m ready to see blockchain technology become useful for regular people.</p>
|
||||
</blockquote>
|
||||
<cite>Mike Vine <em>Technology Evangelist</em></cite>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="content photo-grid spacer2">
|
||||
<h2>The Team</h2>
|
||||
<h1>The Team</h1>
|
||||
<div class="row-fluid">
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/jeremy-644x450.jpg" alt="Jeremy Kauffman"/>
|
||||
</div>
|
||||
<h4>Jeremy Kauffman <a href="mailto:jeremy@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Executive Officer</div>
|
||||
<p>
|
||||
Jeremy knows how to build and scale a startup starting from day one. He knows how to deliver usable products and get those products in front of the right people.
|
||||
</p>
|
||||
<p>
|
||||
Jeremy is responsible for the packing, presentation, and strategy of LBRY, as well as some design aspects. He is a longtime BitTorrent community enthusiast.
|
||||
</p>
|
||||
<p>
|
||||
Jeremy founded <a href="//usetopscore.com" class="link-primary">TopScore</a>, a startup that
|
||||
processes millions of dollars monthly in event and activity registrations.
|
||||
He also attended <a href="//rpi.edu" class="link-primary">Rensselaer Polytechnic Institute</a>, where he received degrees in physics and computer science.
|
||||
</p>
|
||||
<div>
|
||||
<h4>Jeremy Kauffman <a href="mailto:jeremy@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Executive Officer</div>
|
||||
<p>
|
||||
Jeremy knows how to build and scale a startup starting from day one. He knows how to deliver usable products and get those products in front of the right people.
|
||||
</p>
|
||||
<p>
|
||||
Jeremy is responsible for the packing, presentation, and strategy of LBRY, as well as some design aspects. He is a longtime BitTorrent community enthusiast.
|
||||
</p>
|
||||
<p>
|
||||
Jeremy founded <a href="//usetopscore.com" class="link-primary">TopScore</a>, a startup that
|
||||
processes millions of dollars monthly in event and activity registrations.
|
||||
He also attended <a href="//rpi.edu" class="link-primary">Rensselaer Polytechnic Institute</a>, where he received degrees in physics and computer science.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/zargham-644x450.jpg" alt="Michael Zargham"/>
|
||||
</div>
|
||||
<h4>Michael Zargham <a href="mailto:zargham@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Technical Officer</div>
|
||||
<p>
|
||||
Michael has spent years managing, designing, and overseeing a data science team and framework used to make multi-million dollar
|
||||
purchasing decisions for a large media company. He brings knowledge of the media distribution business, software development
|
||||
expertise, business development experience, technical skill and a network of corporate contacts.
|
||||
</p>
|
||||
<p>
|
||||
Michael’s ability to rapidly adapt new skill sets makes him a technical and business pocketknife of our startup team. He has a
|
||||
PhD in systems engineering from the University of Pennsylvania, with a focus on distributed systems.
|
||||
</p>
|
||||
<div>
|
||||
<h4>Michael Zargham <a href="mailto:zargham@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Technical Officer</div>
|
||||
<p>
|
||||
Michael has spent years managing, designing, and overseeing a data science team and framework used to make multi-million dollar
|
||||
purchasing decisions for a large media company. He brings knowledge of the media distribution business, software development
|
||||
expertise, business development experience, technical skill and a network of corporate contacts.
|
||||
</p>
|
||||
<p>
|
||||
Michael’s ability to rapidly adapt new skill sets makes him a technical and business pocketknife of our startup team. He has a
|
||||
PhD in systems engineering from the University of Pennsylvania, with a focus on distributed systems.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row-fluid">
|
||||
|
|
@ -59,7 +50,8 @@
|
|||
<div class="photo-container">
|
||||
<img src="/img/josh-644x450.jpg" alt="Josh Finer"/>
|
||||
</div>
|
||||
<h4>Josh Finer <a href="mailto:josh@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div>
|
||||
<h4>Josh Finer <a href="mailto:josh@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Operations & Growth Officer</div>
|
||||
<p>
|
||||
Josh's combination of an MBA, strong analytical skills, programming skills, advertising expertise, and a perceptive insight to
|
||||
|
|
@ -68,36 +60,39 @@
|
|||
Josh has founded innovative financial companies (later acquired), run millions of dollars in Adwords campaigns, and been an early
|
||||
actor in other crypto projects. Josh's contributions to LBRY will be as diverse as his background.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/jimmy-644x450.jpg" alt="Jimmy Kiselak"/>
|
||||
</div>
|
||||
<h4>
|
||||
Jimmy Kiselak
|
||||
<a href="mailto:jimmy@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a>
|
||||
</h4>
|
||||
<div class="meta spacer1">Founder, Chief Product Officer</div>
|
||||
<p>
|
||||
Jimmy is the second member of team LBRY to graduate from Rensselaer with degrees in computer science and physics.
|
||||
After, he found himself mired in government bureaucracy, spending too much time to get too little done.
|
||||
</p>
|
||||
<p>
|
||||
Ready to work on a project he believed in, Jimmy left a national security programming job to start LBRY.
|
||||
Jimmy created the LBRY protocol and the first LBRY application.
|
||||
</p>
|
||||
<p>
|
||||
Jimmy is a Bitcoin fanatic and has been since its early days. He has long been interested in the benefits of decentralization.
|
||||
</p>
|
||||
<div>
|
||||
<h4>
|
||||
Jimmy Kiselak
|
||||
<a href="mailto:jimmy@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a>
|
||||
</h4>
|
||||
<div class="meta spacer1">Founder, Chief Product Officer</div>
|
||||
<p>
|
||||
Jimmy is the second member of team LBRY to graduate from Rensselaer with degrees in computer science and physics.
|
||||
After, he found himself mired in government bureaucracy, spending too much time to get too little done.
|
||||
</p>
|
||||
<p>
|
||||
Ready to work on a project he believed in, Jimmy left a national security programming job to start LBRY.
|
||||
Jimmy created the LBRY protocol and the first LBRY application.
|
||||
</p>
|
||||
<p>
|
||||
Jimmy is a Bitcoin fanatic and has been since its early days. He has long been interested in the benefits of decentralization.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row-fluid">
|
||||
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/mike-644x450.jpg" alt="Mike Vine"/>
|
||||
</div>
|
||||
<h4>Mike Vine <a href="mailto:mike@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div>
|
||||
<h4>Mike Vine <a href="mailto:mike@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Evangelist</div>
|
||||
<p>
|
||||
With a humble BA in Philosophy from <a href="http://tulane.edu/" class="link-primary">Tulane University</a>, Mike has
|
||||
|
|
@ -113,12 +108,14 @@
|
|||
Now, he's ready to change the world by harnessing blockchain technology.
|
||||
Mike heads up LBRY’s marketing efforts and serves as an ambassador for our platform to media, investors, and the public.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/grin-644x450.jpg" alt="Alex Grin"/>
|
||||
</div>
|
||||
<h4>Alex Grin <a href="mailto:grin@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div>
|
||||
<h4>Alex Grin <a href="mailto:grin@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Chief Infrastructure Officer</div>
|
||||
<p>
|
||||
One of Alex's job titles is Wizard, so named because he can seemingly understand and utilize
|
||||
|
|
@ -130,6 +127,7 @@
|
|||
<p>
|
||||
Alex attended RPI (receiving degrees in Computer Science and Psychology) and Stuyvesant High School.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row-fluid">
|
||||
|
|
@ -138,7 +136,8 @@
|
|||
<div class="photo-container">
|
||||
<img src="/img/jack-robison-644x450.jpg" alt="Jack Robison"/>
|
||||
</div>
|
||||
<h4>Jack Robison <a href="mailto:jack@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div>
|
||||
<h4>Jack Robison <a href="mailto:jack@lbry.io" class="link-primary"><span class="icon icon-envelope"></span></a></h4>
|
||||
<div class="meta spacer1">Founder, Core Developer</div>
|
||||
<p>
|
||||
Jack's path to developer with LBRY is fairly typical:
|
||||
|
|
@ -155,18 +154,21 @@
|
|||
Autism Talk TV, has appeared on
|
||||
<em>National Public Radio</em>, the <em>New York Times</em>, and presents around the country.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6">
|
||||
<div class="photo-container">
|
||||
<img src="/img/spooner-644x450.jpg" alt="you!"/>
|
||||
</div>
|
||||
<h4>You</h4>
|
||||
<div>
|
||||
<h4>You</h4>
|
||||
<div class="meta spacer1">Developer, Designer, Economist, Marketer, Investor, ???</div>
|
||||
<p>
|
||||
Do you think opening up information would facilitate human flourishing?
|
||||
Do you want to join a bright core of people with an obsession for upending broken systems?
|
||||
<a href="mailto:jeremy@lbry.io" class="link-primary">Say hello.</a>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<h2>Advisory Team</h2>
|
||||
|
|
@ -175,48 +177,52 @@
|
|||
<div class="photo-container">
|
||||
<img src="/img/alex-tabarrok-644x450.jpg" alt="Alex Tabarrok"/>
|
||||
</div>
|
||||
<h4>Alex Tabarrok</h4>
|
||||
<div class="meta spacer1">Economic Advisor</div>
|
||||
<p>Alex Tabarrok is Bartley J. Madden Chair in Economics at the <a href="http://mercatus.org/" class="link-primary">Mercatus Center</a>
|
||||
and a professor of economics at <a href="//gmu.edu" class="link-primary">George Mason University</a>. He specializes in intellectual property reform, the effectiveness of markets, and the justice system.
|
||||
</p>
|
||||
<p>Tabarrok is the coauthor, with Mercatus colleague Tyler Cowen, of the popular economics blog <a class="link-primary" href="http://www.marginalrevolution.com/"><em>Marginal Revolution</em></a>
|
||||
and cofounder of the online educational platform <a class="link-primary" href="http://mruniversity.com/">Marginal Revolution University</a>.
|
||||
He is the coauthor of
|
||||
<em><a href="http://www.amazon.com/Modern-Principles-Economics-Tyler-Cowen/dp/1429239972" class="link-primary">Modern Principles of Economics</a></em>,
|
||||
and author of the recent book
|
||||
<em><a href="http://www.amazon.com/Launching-The-Innovation-Renaissance-Market-ebook/dp/B006C1HX24" class="link-primary">Launching the Innovation Renaissance</em></a>.
|
||||
His articles have appeared in the<em> New York Times</em>, the<em> Washington Post</em>, the<em> Wall Street Journal</em>, and many
|
||||
other prestigious publications.
|
||||
</p>
|
||||
<p>Tabarrok received his PhD in economics from
|
||||
<a class="link-primary" href="http://en.wikipedia.org/wiki/George_Mason_University" title="George Mason University">George Mason University</a>.
|
||||
</p>
|
||||
<div>
|
||||
<h4>Alex Tabarrok</h4>
|
||||
<div class="meta spacer1">Economic Advisor</div>
|
||||
<p>Alex Tabarrok is Bartley J. Madden Chair in Economics at the <a href="http://mercatus.org/" class="link-primary">Mercatus Center</a>
|
||||
and a professor of economics at <a href="//gmu.edu" class="link-primary">George Mason University</a>. He specializes in intellectual property reform, the effectiveness of markets, and the justice system.
|
||||
</p>
|
||||
<p>Tabarrok is the coauthor, with Mercatus colleague Tyler Cowen, of the popular economics blog <a class="link-primary" href="http://www.marginalrevolution.com/"><em>Marginal Revolution</em></a>
|
||||
and cofounder of the online educational platform <a class="link-primary" href="http://mruniversity.com/">Marginal Revolution University</a>.
|
||||
He is the coauthor of
|
||||
<em><a href="http://www.amazon.com/Modern-Principles-Economics-Tyler-Cowen/dp/1429239972" class="link-primary">Modern Principles of Economics</a></em>,
|
||||
and author of the recent book
|
||||
<em><a href="http://www.amazon.com/Launching-The-Innovation-Renaissance-Market-ebook/dp/B006C1HX24" class="link-primary">Launching the Innovation Renaissance</em></a>.
|
||||
His articles have appeared in the<em> New York Times</em>, the<em> Washington Post</em>, the<em> Wall Street Journal</em>, and many
|
||||
other prestigious publications.
|
||||
</p>
|
||||
<p>Tabarrok received his PhD in economics from
|
||||
<a class="link-primary" href="http://en.wikipedia.org/wiki/George_Mason_University" title="George Mason University">George Mason University</a>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6 spacer2">
|
||||
<div class="photo-container">
|
||||
<img src="/img/stephan-644x450.jpg" alt="Stephan Kinsella"/>
|
||||
</div>
|
||||
<h4>Stephan Kinsella</h4>
|
||||
<div class="meta spacer1">Legal Advisor</div>
|
||||
<p>
|
||||
Stephan Kinsella is a registered patent attorney and has over twenty years’ experience in patent, intellectual property,
|
||||
and general commercial and corporate law. He is the founder and director of the <a href="http://c4sif.org/" class="link-primary">Center for the Study of Innovative Freedom</a>.
|
||||
Kinsella has published numerous articles and books on intellectual property law and legal topics including
|
||||
<a href="http://www.amazon.com/International-Investment-Political-Dispute-Resolution/dp/0379215225" class="link-primary">
|
||||
<em>International Investment, Political Risk, and Dispute Resolution: A Practitioner’s Guide</em>
|
||||
</a>
|
||||
and
|
||||
<a href="https://mises.org/library/against-intellectual-property-0" class="link-primary">
|
||||
<em>Against Intellectual Property</em>
|
||||
</a>.
|
||||
</p>
|
||||
<p>
|
||||
He received an LL.M. in international business law from <a href="http://www.kcl.ac.uk/" class="link-primary">King’s College London</a>, a JD from the Paul M. Hebert Law Center at
|
||||
<a href="//lsu.edu" class="link-primary">Lousiana State University</a>,
|
||||
as well as BSEE and MSEE degrees. His websites are <a href="stephankinsella.com" class="link-primary">stephankinsella.com</a>
|
||||
and <a href="kinsellalaw.com" class="link-primary">kinsellalaw.com</a>
|
||||
</p>
|
||||
<div>
|
||||
<h4>Stephan Kinsella</h4>
|
||||
<div class="meta spacer1">Legal Advisor</div>
|
||||
<p>
|
||||
Stephan Kinsella is a registered patent attorney and has over twenty years’ experience in patent, intellectual property,
|
||||
and general commercial and corporate law. He is the founder and director of the <a href="http://c4sif.org/" class="link-primary">Center for the Study of Innovative Freedom</a>.
|
||||
Kinsella has published numerous articles and books on intellectual property law and legal topics including
|
||||
<a href="http://www.amazon.com/International-Investment-Political-Dispute-Resolution/dp/0379215225" class="link-primary">
|
||||
<em>International Investment, Political Risk, and Dispute Resolution: A Practitioner’s Guide</em>
|
||||
</a>
|
||||
and
|
||||
<a href="https://mises.org/library/against-intellectual-property-0" class="link-primary">
|
||||
<em>Against Intellectual Property</em>
|
||||
</a>.
|
||||
</p>
|
||||
<p>
|
||||
He received an LL.M. in international business law from <a href="http://www.kcl.ac.uk/" class="link-primary">King’s College London</a>, a JD from the Paul M. Hebert Law Center at
|
||||
<a href="//lsu.edu" class="link-primary">Lousiana State University</a>,
|
||||
as well as BSEE and MSEE degrees. His websites are <a href="stephankinsella.com" class="link-primary">stephankinsella.com</a>
|
||||
and <a href="kinsellalaw.com" class="link-primary">kinsellalaw.com</a>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row-fluid">
|
||||
|
|
@ -224,31 +230,34 @@
|
|||
<div class="photo-container">
|
||||
<img src="/img/huemer-644x450.jpg" alt="Michael Huemer"/>
|
||||
</div>
|
||||
<h4>Michael Huemer</h4>
|
||||
<div>
|
||||
<h4>Michael Huemer</h4>
|
||||
<div class="meta spacer1">Ethical Advisor</div>
|
||||
<p>
|
||||
Michael Huemer is Professor of Philosophy and Ethics at the <a href="//www.colorado.edu/" class="link-primary">University of Colorado</a>,
|
||||
where he has taught since 1998. He has published three single-author scholarly books
|
||||
(including <em><a href="http://www.amazon.com/Ethical-Intuitionism-Michael-Huemer/dp/0230573746" class="link-primary">Ethical Intuitionism</a></em>),
|
||||
one edited anthology, and more than fifty academic articles in epistemology, ethics, political philosophy, and metaphysics.
|
||||
|
||||
</p>
|
||||
<p>
|
||||
Huemer's articles have appeared in such journals as the <em>Philosophical Review</em>, <em>Mind</em>, the <em>Journal of Philosophy</em>, <em>Ethics</em>, and others.
|
||||
His materials are used as readings in classrooms nationwide. He received a B.A. from UC Berkeley and a Ph.D. from Rutgers University.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="span6">
|
||||
<div class="photo-container">
|
||||
<img src="/img/spooner-644x450.jpg" alt="you!"/>
|
||||
</div>
|
||||
<h4>You</h4>
|
||||
<div>
|
||||
<h4>You</h4>
|
||||
<div class="meta spacer1">Technical or Media Advisor</div>
|
||||
<p>
|
||||
LBRY is seeking an extremely experienced technical advisor or advisor with a strong background in the publishing and media space.
|
||||
If you're that person or have a suggestion,
|
||||
<a href="mailto:jeremy@lbry.io?subject=Advisor" class="link-primary">let us know</a>.
|
||||
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -2,9 +2,6 @@
|
|||
<?php NavActions::setNavUri('/learn') ?>
|
||||
<?php echo View::render('nav/header', ['isDark' => false]) ?>
|
||||
<main>
|
||||
<div class="content">
|
||||
<h1>What is LBRY?</h1>
|
||||
</div>
|
||||
<div class="hero hero-pattern spacer2">
|
||||
<div class="hero-content text-center">
|
||||
<h2 class="hero-title">A revolution in accessing and publishing information.</h2>
|
||||
|
|
@ -37,8 +34,8 @@
|
|||
</div>
|
||||
</div>
|
||||
<div class="content">
|
||||
<h1>What is LBRY?</h1>
|
||||
<div class="spacer2">
|
||||
<h3>Tell Me More</h3>
|
||||
<p>LBRY allows anyone to publish content to a location like this:</p>
|
||||
<p class="text-center"><code>lbry://wonderfullife</code></p>
|
||||
<p>Others can access this resource, either for free or for credits. Let's look at an example:</p>
|
||||
|
|
@ -3,7 +3,6 @@
|
|||
<?php Response::setMetaDescription('Learn about the inspiration behind LBRY\'s revolutionary content distribution system.') ?>
|
||||
<?php echo View::render('nav/header', ['isDark' => false]) ?>
|
||||
<main>
|
||||
<div class="content"><h1>Why?</h1></div>
|
||||
<div class="hero hero-quote hero-img spacer2" style="background-image: url(/img/cover-jcole.jpg)">
|
||||
<div class="hero-content-wrapper">
|
||||
<div class="hero-content">
|
||||
|
|
@ -14,6 +13,7 @@
|
|||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="content"><h1>Why?</h1></div>
|
||||
<div class="content spacer2">
|
||||
<h3>The World We Live In</h3>
|
||||
<p>Annual internet video traffic is approximately 500 exabytes (500,000,000,000 GB)<sup><a href="http://www.cisco.com/c/en/us/solutions/collateral/service-provider/ip-ngn-ip-next-generation-network/white_paper_c11-481360.html">1</a></sup>.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 236 KiB |
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 67 KiB |
|
|
@ -10,8 +10,8 @@ html
|
|||
}
|
||||
body
|
||||
{
|
||||
font-family: $bodyFont;
|
||||
font-weight: 300;
|
||||
font-family: $font-body;
|
||||
font-weight: 400;
|
||||
line-height: 1.3333;
|
||||
min-height: 100%;
|
||||
position: relative;
|
||||
|
|
@ -37,17 +37,24 @@ code { font-family: Consolas, Menlo, Monaco, Lucida Console, Liberation Mono, De
|
|||
|
||||
h1, h2, h3, h4, h5, h6
|
||||
{
|
||||
font-family: $headerFont;
|
||||
font-weight: 300;
|
||||
font-family: $font-header;
|
||||
font-weight: 500;
|
||||
}
|
||||
h1, h2, h3
|
||||
h1, h2, h3, h4
|
||||
{
|
||||
margin-bottom: $spacing-vertical / 2; margin-top: $spacing-vertical * 1.5;
|
||||
margin-bottom: $spacing-vertical / 2;
|
||||
margin-top: $spacing-vertical / 2;
|
||||
}
|
||||
h1 { font-size: 2.4em; }
|
||||
h2 { font-size: 2.0em; }
|
||||
h3 { font-size: 1.75em; }
|
||||
h4 { font-size: 1.4em; }
|
||||
nav
|
||||
{
|
||||
font-size: 1.2em;
|
||||
font-family: $font-header;
|
||||
font-weight: 400;
|
||||
}
|
||||
h1 { font-size: 2.0em; }
|
||||
h2 { font-size: 1.75em; }
|
||||
h3 { font-size: 1.4em; }
|
||||
h4 { font-size: 1.2em; margin-bottom: $spacing-vertical / 2; }
|
||||
sup, sub {
|
||||
vertical-align: baseline;
|
||||
position: relative;
|
||||
|
|
@ -64,6 +71,7 @@ section
|
|||
}
|
||||
|
||||
.hide { display: none; }
|
||||
.spacer-half { margin-bottom: $spacing-vertical / 2; }
|
||||
.spacer1 { margin-bottom: $spacing-vertical; }
|
||||
.spacer2 { margin-bottom: $spacing-vertical * 2; }
|
||||
.text-center { text-align: center; }
|
||||
|
|
@ -74,16 +82,7 @@ section
|
|||
|
||||
.link-primary
|
||||
{
|
||||
color: $color-primary;
|
||||
text-decoration: underline;
|
||||
.icon:first-child
|
||||
{
|
||||
padding-right: 5px;
|
||||
}
|
||||
.icon:last-child
|
||||
{
|
||||
padding-left: 5px;
|
||||
}
|
||||
@include anchor($color-primary);
|
||||
}
|
||||
a:hover img
|
||||
{
|
||||
|
|
@ -123,7 +122,9 @@ a:hover img
|
|||
text-decoration: none;
|
||||
border: 0 none;
|
||||
text-align: center;
|
||||
font-weight: 400;
|
||||
font-family: $font-header;
|
||||
font-size: 1.15em;
|
||||
|
||||
}
|
||||
.btn-primary
|
||||
{
|
||||
|
|
@ -158,6 +159,11 @@ a:hover img
|
|||
@include clearfix();
|
||||
}
|
||||
|
||||
.clearfix
|
||||
{
|
||||
@include clearfix();
|
||||
}
|
||||
|
||||
.table-layout
|
||||
{
|
||||
td
|
||||
|
|
|
|||
|
|
@ -1,71 +1,28 @@
|
|||
@import "global";
|
||||
|
||||
.blog-post {
|
||||
.date {
|
||||
margin-top: $spacing-vertical * 2;
|
||||
}
|
||||
h1 {
|
||||
font-size: 2em;
|
||||
margin-top: 0 !important;
|
||||
}
|
||||
p, li {
|
||||
font-weight: 400;
|
||||
}
|
||||
img + p {
|
||||
margin-top: $spacing-vertical;
|
||||
}
|
||||
|
||||
.prev-next {
|
||||
margin-top: $spacing-vertical * 2;
|
||||
margin-bottom: $spacing-vertical * 2;
|
||||
|
||||
.prev-next-label {
|
||||
font-weight: 700;
|
||||
}
|
||||
.next {
|
||||
text-align: right;
|
||||
}
|
||||
}
|
||||
|
||||
blockquote {
|
||||
padding-left: 40px;
|
||||
border-left: solid 8px #f2f2f2;
|
||||
}
|
||||
|
||||
.author {
|
||||
background-color: #f2f2f2;
|
||||
.content {
|
||||
padding-top: $spacing-vertical * 2;
|
||||
padding-bottom: $spacing-vertical * 2;
|
||||
}
|
||||
h2 {
|
||||
font-weight: 400;
|
||||
margin-top: 0;
|
||||
text-transform: uppercase;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
.blog-header {
|
||||
font-size: 2em;
|
||||
h1 {
|
||||
font-weight: 400;
|
||||
&:after {
|
||||
clear: right;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
.post-list {
|
||||
font-family: $bodyFont;
|
||||
.prev-next {
|
||||
margin-top: $spacing-vertical * 2;
|
||||
margin-bottom: $spacing-vertical * 2;
|
||||
div {
|
||||
margin-bottom: $spacing-vertical;
|
||||
|
||||
.prev-next-label {
|
||||
font-weight: bold;
|
||||
}
|
||||
a {
|
||||
font-weight: 400;
|
||||
}
|
||||
span {
|
||||
margin-left: 10px;
|
||||
.next {
|
||||
text-align: right;
|
||||
}
|
||||
}
|
||||
|
||||
.post-content
|
||||
{
|
||||
max-width: $max-content-width - 200;
|
||||
margin-left: auto;
|
||||
margin-right: auto;
|
||||
a[href]
|
||||
{
|
||||
@include anchor($color-primary);
|
||||
}
|
||||
}
|
||||
.post-author-spotlight
|
||||
{
|
||||
h3 { text-transform: uppercase; margin-top: $spacing-vertical / 4 !important; }
|
||||
}
|
||||
|
|
@ -18,24 +18,11 @@
|
|||
{
|
||||
max-width: 1400px;
|
||||
}
|
||||
&.content-readable
|
||||
{
|
||||
max-width: $max-content-width - 200;
|
||||
p
|
||||
{
|
||||
line-height: 29px;
|
||||
}
|
||||
a[href]
|
||||
{
|
||||
color: $color-primary;
|
||||
text-decoration: underline;
|
||||
}
|
||||
}
|
||||
|
||||
padding-left: 15px;
|
||||
padding-right: 15px;
|
||||
|
||||
h1, h2, h3, h4, h5, h6
|
||||
h1, h2, h3, h4
|
||||
{
|
||||
&:not(:first-child)
|
||||
{
|
||||
|
|
@ -65,6 +52,12 @@
|
|||
}
|
||||
|
||||
.link-primary { color: $color-primary; }
|
||||
|
||||
blockquote
|
||||
{
|
||||
padding-left: 40px;
|
||||
border-left: solid 8px #f2f2f2;
|
||||
}
|
||||
}
|
||||
|
||||
p
|
||||
|
|
@ -101,10 +94,12 @@
|
|||
ul
|
||||
{
|
||||
margin-bottom: $spacing-vertical * 1.5;
|
||||
&:last-child { margin-bottom: $spacing-vertical / 2; }
|
||||
> li + li { margin-top: $spacing-vertical; }
|
||||
}
|
||||
ol {
|
||||
margin-bottom: $spacing-vertical * 1.5;
|
||||
&:last-child { margin-bottom: $spacing-vertical / 2; }
|
||||
padding-left: 2em;
|
||||
counter-reset: li-counter;
|
||||
> li {
|
||||
|
|
|
|||
|
|
@ -17,18 +17,14 @@
|
|||
.cover-full
|
||||
{
|
||||
height: 100vh;
|
||||
font-size: 1.2em;
|
||||
.cover-title, .cover-subtitle
|
||||
{
|
||||
text-shadow: 0 0 6px rgba(0,0,0,0.8);
|
||||
}
|
||||
font-size: 1.4em;
|
||||
}
|
||||
@media (max-width: $mobile-width-threshold) {
|
||||
.cover { padding: $spacing-vertical $spacing-vertical * 2 / 3; }
|
||||
.cover-title { font-size: 2.4em; margin-bottom: $spacing-vertical; }
|
||||
.cover-title { font-size: 2.8em; margin-bottom: $spacing-vertical; }
|
||||
}
|
||||
@media (min-width: $mobile-width-threshold) {
|
||||
.cover-title { font-size: 3.6em; }
|
||||
.cover-title { font-size: 4.0em; }
|
||||
}
|
||||
@media (max-width: $max-content-width) and (min-width: $mobile-width-threshold) {
|
||||
.cover { padding: $spacing-vertical * 1.5 $spacing-vertical * 2; }
|
||||
|
|
@ -77,6 +73,10 @@
|
|||
@include linear-gradient(darken($color-light-alt, 5), lighten($color-light-alt, 5));
|
||||
}
|
||||
|
||||
.cover-title, .cover-subtitle
|
||||
{
|
||||
text-shadow: 0 0 6px rgba(0,0,0,0.8);
|
||||
}
|
||||
.cover-title
|
||||
{
|
||||
line-height: 1.4;
|
||||
|
|
@ -84,5 +84,5 @@
|
|||
.cover-subtitle
|
||||
{
|
||||
margin: $spacing-vertical 0 $spacing-vertical;
|
||||
font-size: 1.1em;
|
||||
font-size: 1.2em;
|
||||
}
|
||||
|
|
@ -8,14 +8,28 @@ $color-text-dark: #000;
|
|||
$color-money: #216C2A;
|
||||
$color-meta-light: #505050;
|
||||
|
||||
$font-size: 18px;
|
||||
$font-size: 16px;
|
||||
|
||||
$mobile-width-threshold: 801px;
|
||||
$max-content-width: 1000px;
|
||||
$max-text-width: 660px;
|
||||
|
||||
$headerFont: 'Raleway', sans-serif;
|
||||
$bodyFont: 'Lato', sans-serif;
|
||||
$font-header: 'Raleway', sans-serif;
|
||||
$font-body: 'Merriweather', sans-serif;
|
||||
|
||||
@mixin anchor($color)
|
||||
{
|
||||
color: $color;
|
||||
text-decoration: underline;
|
||||
.icon:first-child
|
||||
{
|
||||
padding-right: 5px;
|
||||
}
|
||||
.icon:last-child
|
||||
{
|
||||
padding-left: 5px;
|
||||
}
|
||||
}
|
||||
|
||||
@mixin clearfix()
|
||||
{
|
||||
|
|
@ -69,6 +83,17 @@ $bodyFont: 'Lato', sans-serif;
|
|||
flex-direction: $direction;
|
||||
}
|
||||
|
||||
@mixin flex-wrap($wrap) {
|
||||
-webkit-flex-wrap: $wrap;
|
||||
flex-wrap: $wrap;
|
||||
}
|
||||
|
||||
|
||||
@mixin justify-content($location) {
|
||||
-webkit-justify-content: $location;
|
||||
justify-content: $location;
|
||||
}
|
||||
|
||||
@mixin absolute-center()
|
||||
{
|
||||
@include display-flex();
|
||||
|
|
@ -80,8 +105,7 @@ $bodyFont: 'Lato', sans-serif;
|
|||
-webkit-box-pack: center;
|
||||
-moz-box-pack: center;
|
||||
-ms-flex-pack: center;
|
||||
-webkit-justify-content: center;
|
||||
justify-content: center;
|
||||
@include justify-content(center);
|
||||
}
|
||||
|
||||
@mixin linear-gradient($from-color, $to-color) {
|
||||
|
|
|
|||
|
|
@ -57,12 +57,12 @@ $gutter_fluid: 4;
|
|||
|
||||
.column-fluid {
|
||||
@include display-flex();
|
||||
flex-wrap: wrap;
|
||||
@include flex-wrap(wrap);
|
||||
> [class*="span"] {
|
||||
@include display-flex();
|
||||
@include flex(1 0 auto);
|
||||
overflow: hidden;
|
||||
justify-content: center;
|
||||
@include justify-content(center);
|
||||
}
|
||||
}
|
||||
|
||||
|
|
@ -70,6 +70,11 @@ $gutter_fluid: 4;
|
|||
@include clearfix();
|
||||
}
|
||||
|
||||
@media (min-width: $mobile-width-threshold) {
|
||||
.pull-left { float: left; }
|
||||
.pull-right { float: right; }
|
||||
}
|
||||
|
||||
@media (max-width: $mobile-width-threshold) {
|
||||
.row-fluid, .tile-fluid, .column-fluid {
|
||||
width: 100%;
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ $color-nav-border: #ddd;
|
|||
a
|
||||
{
|
||||
&:hover { text-decoration: underline; }
|
||||
// &.nav-active { font-weight: bold; }
|
||||
&.nav-active { font-weight: bold; }
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -6,19 +6,19 @@
|
|||
color: white;
|
||||
padding-top: $spacing-vertical;
|
||||
padding-bottom: $spacing-vertical;
|
||||
font-family: $font-header;
|
||||
blockquote
|
||||
{
|
||||
font-family: $headerFont;
|
||||
border-left: 10px solid rgba(180, 180, 180, 0.3);
|
||||
padding: 0 15px;
|
||||
font-size: 1.5em;
|
||||
font-size: 1.8em;
|
||||
&.blockquote-large
|
||||
{
|
||||
max-width: 600px;
|
||||
display: block;
|
||||
margin-left: auto;
|
||||
margin-right: auto;
|
||||
font-size: 2.0em;
|
||||
font-size: 2.2em;
|
||||
}
|
||||
+ cite
|
||||
{
|
||||
|
|
@ -132,26 +132,22 @@
|
|||
}
|
||||
h3
|
||||
{
|
||||
font-size: 1.25em;
|
||||
font-size: 1.35em;
|
||||
margin-bottom: $spacing-vertical * .5;
|
||||
font-weight: bold;
|
||||
text-align: center;
|
||||
margin-top: $spacing-vertical * .5;
|
||||
}
|
||||
p
|
||||
{
|
||||
font-size: 16px;
|
||||
}
|
||||
}
|
||||
.hero-title
|
||||
{
|
||||
font-weight: bold;
|
||||
font-size: 2.0em;
|
||||
font-size: 2.2em;
|
||||
margin-bottom: $spacing-vertical * 2;
|
||||
}
|
||||
.hero-title-small
|
||||
{
|
||||
font-weight: bold;
|
||||
font-size: 1.5em;
|
||||
font-size: 1.6em;
|
||||
margin-bottom: $spacing-vertical;
|
||||
}
|
||||
|
|
@ -42,3 +42,8 @@ a
|
|||
color: inherit;
|
||||
text-decoration: none;
|
||||
}
|
||||
input, a, button, select
|
||||
{
|
||||
-webkit-appearance: none;
|
||||
border-radius: 0;
|
||||
}
|
||||
|
|
@ -27,6 +27,7 @@
|
|||
.sale-call
|
||||
{
|
||||
text-align: center;
|
||||
font-family: $font-header;
|
||||
margin-bottom: $spacing-vertical / 2;
|
||||
.sale-call-total-people
|
||||
{
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue