mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-08-23 17:47:26 +00:00
Merge branch 'master' into youtube-onboarding-final
This commit is contained in:
Niko Storni
Niko Storni
commit
c4f8fef151
109 changed files with 649 additions and 189 deletions
29
INSTALL.md
Normal file
29
INSTALL.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
# Installation
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To run this project, you'll need to have either PHP7 or Docker installed, and be using either macOS or Linux.
|
||||
|
||||
## Running Locally
|
||||
|
||||
- Install PHP7
|
||||
- Checkout the project
|
||||
- Run `./dev.sh` from the project root
|
||||
- Access [localhost:8000](http://localhost:8000) in your browser
|
||||
|
||||
## Running via Docker
|
||||
|
||||
- Install Docker
|
||||
- Checkout the project
|
||||
- Run `./docker.sh` from the project root
|
||||
- Access [localhost:8000](http://localhost:8000) in your browser
|
||||
|
||||
## Verifying Install
|
||||
|
||||
If `localhost:8000` returns the lbry.io website, it's running correctly.
|
||||
|
||||
## Additional Notes
|
||||
|
||||
- Both the `dev.sh` and `docker.sh` scripts will initialise a configuration based on `data/config.php.example` if `data/config.php` does not exist.
|
||||
- Some pages and interactions rely on API keys that will not be available to you in your install.
|
||||
- To run remotely, simply install PHP and configure Apache or your server of choice to serve `web/index.php`.
|
||||
2
LICENSE
2
LICENSE
|
|
@ -1,6 +1,6 @@
|
|||
The MIT License (MIT)
|
||||
|
||||
Copyright (c) 2015-2016 LBRY Inc
|
||||
Copyright (c) 2015-2018 LBRY Inc
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the
|
||||
"Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish,
|
||||
|
|
|
|||
37
README.md
37
README.md
|
|
@ -1,25 +1,32 @@
|
|||
# lbry.io
|
||||
|
||||
The [lbry.io](https://lbry.io) website.
|
||||
The [lbry.io](https://lbry.io) website. This website uses barebones PHP along with Javascript and SCSS.
|
||||
|
||||
## Running lbry.io
|
||||
|
||||
|
||||
It's very easy to have lbry.io running locally:
|
||||
## Installation
|
||||
|
||||
- Install PHP7
|
||||
- Checkout the project
|
||||
- Run `./dev.sh` from the project root
|
||||
- Access [localhost:8000](http://localhost:8000) in your browser
|
||||
Please see [INSTALL](INSTALL.md) for comprehensive, easy-to-follow instructions on running this project.
|
||||
|
||||
You can also run the development server using docker:
|
||||
## Usage
|
||||
|
||||
- Install Docker
|
||||
- Checkout the project
|
||||
- Run `./docker.sh` from the project root
|
||||
- Access [localhost:8000](http://localhost:8000) in your browser
|
||||
Unless you are planning to contribute to the lbry.io website, this project serves little independent purpose.
|
||||
|
||||
Both the `dev.sh` and `docker.sh` scripts will initialise a configuration based on `data/config.php.example` if `data/config.php` does not exist.
|
||||
To access a local copy of lbry.io, follow [INSTALL](INSTALL.md) and then access `localhost:8000` in your browser.
|
||||
|
||||
To run remotely, simply install PHP and configure Apache or your server of choice to serve `web/index.php`.
|
||||
## License
|
||||
|
||||
Note that some pages and interactions rely on API keys that will not be available to you in your install.
|
||||
This project is MIT licensed. For the full license, see [LICENSE](LICENSE).
|
||||
|
||||
## Contributing
|
||||
|
||||
Contributions to this project are welcome, encouraged, and compensated. For more details, see [CONTRIBUTING](https://lbry.io/faq/contributing).
|
||||
|
||||
## Contact
|
||||
|
||||
The primary contact for this project is Jeremy Kauffman (jeremy@lbry.io).
|
||||
|
||||
## Additional Info and Links
|
||||
|
||||
- [https://lbry.io](https://lbry.io) - The live LBRY website
|
||||
- [https://chat.lbry.io](https://chat.lbry.io) - A chat room for the LBRY community
|
||||
|
|
|
|||
|
|
@ -8,6 +8,6 @@ github: kauffj
|
|||
|
||||
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.
|
||||
|
||||
Jeremy is responsible for the packing, presentation, and strategy of LBRY, as well as some design aspects. He is a longtime supporter of decentralized technology and freedom of information.
|
||||
Jeremy created LBRY because he fell in love with the idea of shared, global content registry that is owned and controlled by no one. Unsurprisingly, he is a longtime supporter of decentralized technology and freedom of information.
|
||||
|
||||
Jeremy founded [TopScore](//usetopscore.com), a startup that processes millions of dollars monthly in event and activity registrations. He also attended [Rensselaer Polytechnic Institute](//rpi.edu), where he received degrees in physics and computer science.
|
||||
Prior to LBRY, Jeremy founded [TopScore](//usetopscore.com), a startup that processes millions of dollars monthly in event and activity registrations. He attended [Rensselaer Polytechnic Institute](//rpi.edu), where he received degrees in physics and computer science.
|
||||
|
|
|
|||
10
content/bio/lex-berezhny.md
Normal file
10
content/bio/lex-berezhny.md
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
name: Lex Berezhny
|
||||
role: Protocol Developer
|
||||
email: lex@lbry.io
|
||||
twitter: eukreign
|
||||
github: eukreign
|
||||
---
|
||||
Lex learned to write Python in High School, not far from where the language was first created, and even participated in some of the first Python user groups hosted by Guido, himself. In 2000, still a very young man, Lex gave his first public talk, titled “Yorktown High School Becomes a Python Workshop” at the International Python Conference. Needless to say, Lex and Python go way back.
|
||||
|
||||
Lex spends his time on the full stack of LBRY backends, such as the wallet, protocol, and blockchain, and is currently wading deep into the improvement of test coverage and performance of various LBRY components. If you want to trade notes on Dart, and dish on a possible ideal use case for Dart at LBRY, Lex wants to hear from you!
|
||||
18
content/bounty/twitter-tipbot.md
Normal file
18
content/bounty/twitter-tipbot.md
Normal file
|
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
category: code
|
||||
title: Twitter Tip Bot
|
||||
award: 300
|
||||
status: available
|
||||
date: '2018-02-13'
|
||||
---
|
||||
|
||||
This bounty is to create a tipbot that can be used to send/receive LBRY Credits(LBC) on Twitter.
|
||||
|
||||
References to other LBRY tipbots:
|
||||
[Reddit tipbot](https://github.com/lbryio/lbry-social-tipbot)
|
||||
[Discord tipbot](https://github.com/lbryio/lbry-tipbot)
|
||||
|
||||
Possible starting point:
|
||||
https://github.com/Crowndev/Twitter-Tip
|
||||
|
||||
Please initiate a pull request on GitHub to receive this bounty.
|
||||
42
content/faq/acceptable-use-policy.md
Normal file
42
content/faq/acceptable-use-policy.md
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
* We want it to be very easy for anyone creating content or services on the LBRY network to use the official name and logo.
|
||||
* We want to be clear about how and when you can use the LBRY name and logo, as well as providing examples of uses that are not acceptable.
|
||||
* We want to make it difficult for anyone to use the LBRY name or logo to confuse or defraud people.
|
||||
|
||||
### 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 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.
|
||||
|
||||
### Examples Of Acceptable Uses
|
||||
|
||||
* Create brand new content. Entertain, educate, get famous, or change the world.
|
||||
* Build a service based on LBRY. Help make the internet a better, freer place!
|
||||
* Staying within the bounds of Fair Use, sample, derive, criticize, or otherwise use someone else's copyright work to make something new.
|
||||
|
||||
### Examples of Unacceptable Uses
|
||||
|
||||
* Creating any service that uses LBRY and presenting it as 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 content that is itself a crime.
|
||||
|
||||
### LBRY Service Trademark Usage Policy
|
||||
|
||||
As a statement of principle, you are encouraged to associate your project, product, service, domain, or company name with LBRY, so long as you're a credit to the community.
|
||||
|
||||
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.
|
||||
|
|
@ -6,7 +6,5 @@ category: other
|
|||
Yep. You can see it at [https://explorer.lbry.io](https://explorer.lbry.io).
|
||||
|
||||
If the enslaved squirrels that run our primary explorer are sleeping, try
|
||||
[https://lbrypool.com/explorer/LBC](https://lbrypool.com/explorer/LBC)
|
||||
|
||||
[https://lbry.block.ng/](https://lbry.block.ng/)
|
||||
|
||||
[http://yiimp.eu/explorer/LBC](http://yiimp.eu/explorer/LBC)
|
||||
|
|
|
|||
|
|
@ -38,9 +38,7 @@ This section describes how bids are processed by the ClaimTrie in order to deter
|
|||
|
||||
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.
|
||||
|
||||
* If the bid with the greatest amount does not have the same claimID as the bid which was ‘controlling’ prior to including the current block, change the delay for the name as of the current block to 0, redetermine which bids and supports should be active, and then perform the previous calculation again.
|
||||
|
||||
* At this point, the bid calculated to have the greatest amount behind it is the ‘controlling’ bid as of this block
|
||||
5. *Spent*: A transaction has been included in the blockchain which spends the TXout which contains the bid. Must be in the ‘accepted’ state.
|
||||
6. *Expired*: All bids ‘expire’ regardless of what state they are in when the current block height exceeds the height of the block at which the bid was accepted plus 52416 blocks, or 91 days ( currently this is set to 262974 blocks, or 456 days, which will be fixed in a future hard fork ). Updated claims will restart the expiration timer at the block height of the update.
|
||||
|
|
|
|||
40
content/faq/content.md
Normal file
40
content/faq/content.md
Normal file
|
|
@ -0,0 +1,40 @@
|
|||
---
|
||||
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.
|
||||
|
||||
###What content can I legally upload to LBRY?
|
||||
|
||||
You may upload content you created or own that does not infringe on the rights of others or is illegal, or other content you have permission to upload. This includes Public Domain content, Creative Commons or Open Source content shared according to the license requirements, and Copyrighted content where you have permission from the owner.
|
||||
|
||||
###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.
|
||||
|
||||
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.
|
||||
|
||||
LBRY Inc., makes no guarantee your content will be hosted on the network. The peer-to-peer network relies on hosts to seed content. If no user continues to host data - including you, it will not continue to be available on the network.
|
||||
|
||||
###Someone uploaded my content to LBRY without permission. How do I remove it?
|
||||
|
||||
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.
|
||||
|
||||
###What do I do if I see content that’s illegal or infringing in the LBRY App?
|
||||
|
||||
Please follow the FAQ above for reporting infringing content, and LBRY staff will review your report and take any appropriate action.
|
||||
|
||||
###What is a DMCA request or takedown notice?
|
||||
|
||||
The Digital Millennium Copyright Act (DMCA) is United States Copyright Law written to protect digital content against illegal use. When an owner finds their content used on the Internet without their permission, they can file a DMCA request with the website, app, or Internet Service Provider illegally hosting their content, asking for it to be removed.
|
||||
|
||||
###How does LBRY respond to a DMCA request or takedown notice?
|
||||
|
||||
LBRY, Inc. will block access to content deemed infringing in the LBRY App when it receives a valid DMCA request from the content owner.
|
||||
|
||||
###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.
|
||||
|
|
@ -8,9 +8,12 @@ Currently, there are a couple ways to obtain LBRY Credits, or LBC for short.
|
|||
|
||||
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).
|
||||
1. You can earn LBC for helping with tasks. Talk to us on [Discord Chat](https://chat.lbry.io/) if
|
||||
1. LBRY users can convert cryptoassets into LBC using [ShapeShift](https://lbry.io/faq/shapeshift) within the [LBRY app](https://lbry.io/get?auto=1)
|
||||
1. You can earn LBC for helping with tasks. Talk to us on [Discord Chat](https://chat.lbry.io/) if
|
||||
you're interested in additional testing or helping the community.
|
||||
1. [Contributing](https://lbry.io/faq/contributing) to the project as a developer/engineer.
|
||||
1. Research and complete LBRY [bounties](https://lbry.io/bounty)
|
||||
1. Buy them: see [Exchanges](/faq/exchanges)
|
||||
1. Mine them: see [Mining](/faq/mining-credits).
|
||||
1. [Publish](https://lbry.io/faq/how-to-publish) content: when you publish your own content to the LBRY network, you can sell it for LBC at the price of your choice.
|
||||
|
||||
|
|
|
|||
|
|
@ -48,8 +48,7 @@ If you don't have LBRY yet, download it [here](https://lbry.io/get).
|
|||
6. You have an option to select/create the channel you would like to publish the channel under. If one isn't selected, it will be posted anonymously.
|
||||
|
||||
|
||||
7. Type in the URL you want the content to be found under along with a minimum of 0.01 LBC minimum deposit for the upload (current limit, may change in future). If you are trying to outbid a user friendly/common URL, the system will suggest a minimum bid to take over the content at that vanity URL. There may be a delay for this takeover, check out the `#content` channel on our [Discord chat](https://chat.lbry.io) to see this information (search for your URL). For more details regarding the URL or bid, check out our [naming document](https://lbry.io/faq/naming).
|
||||
|
||||
7. Type in the URL you want the content to be found under along with a minimum of 0.0001 LBC deposit for the upload (current limit, may change in future). If you are trying to outbid a user friendly/common URL, the system will suggest a minimum bid to take over the content at that vanity URL. There may be a delay for this takeover, check out the `#content` channel on our [Discord chat](https://chat.lbry.io) to see this information (search for your URL). For more details regarding the URL or bid, check out our [naming document](https://lbry.io/faq/naming).
|
||||
|
||||
8. Read and agree to the terms of service.
|
||||
9. Click `Publish`.
|
||||
|
|
@ -58,10 +57,16 @@ If you don't have LBRY yet, download it [here](https://lbry.io/get).
|
|||
### How do I delete my content and reclaim my deposit?
|
||||
|
||||
1. Click on the folder icon in the top right of the LBRY app.
|
||||
|
||||
2. Click on the `Published` tab.
|
||||
3. Select the content you want to remove from LBRY
|
||||
4. Click `Remove`. If you don't see the remove button, try downloading the content locally again.
|
||||
5. There will be two options. `Abandon the claim for this URI` and `Delete this file from my computer`. Select the option that applies. Abandoning your claim will release the LBC back into your wallet (99% of the time you want to select this). **Warning: Deleting content is permanent. Please make sure this is what you want to do before confirming the deletion.**
|
||||
|
||||
5. There will be two options. `Abandon the claim for this URI` and `Delete this file from my computer`. Select the option that applies. Abandoning your claim will release the LBC back into your wallet (99% of the time you want to select this).
|
||||
|
||||
|
||||
**Warning: Deleting content is permanent. Please make sure this is what you want to do before confirming the deletion.**
|
||||
|
||||
6. Click `Remove`. If you abandoned your claim, you should see the deposit back in your balance shortly.
|
||||
|
||||
### How do I edit my existing Published content?
|
||||
|
|
|
|||
71
content/faq/lbry-basics.md
Normal file
71
content/faq/lbry-basics.md
Normal file
|
|
@ -0,0 +1,71 @@
|
|||
---
|
||||
title: LBRY App Basics
|
||||
category: getstarted
|
||||
order: 1
|
||||
---
|
||||
|
||||
The LBRY App allows you to view free and paid content, upload your digital media for free or at a set price, tip your favorite creators, send/receive LBRY Credits(LBC) and earn credits through LBRY Rewards. The app runs on top of the [LBRY protocol](https://lbry.io/faq/what-is-lbry) which is a peer to peer, decentralized file sharing and payment network secured by blockchain technology.
|
||||
|
||||
The purpose of this FAQ is to answer questions about some of the basic functionality available in the LBRY App. Please see our [other FAQ entries](https://lbry.io/faq) for additional information.
|
||||
|
||||
### What is the purpose of having my email connected to LBRY?
|
||||
Emails are collected to authenticate and [uniquely identify](https://lbry.io/faq/identity-requirements) users so that they can be eligible for [LBRY Rewards](#rewards) and to stay up to date on the latest LBRY happenings. No other data is stored with your email login. All other data, including your [wallet](#wallet), [downloads](#data) and published content are stored locally on your computer. You can find your connected email by going to Settings (gear icon in the top right) > Help > Connected email.
|
||||
|
||||
### How do I change my LBRY connected email?
|
||||
If you ever need to change your LBRY email address or sign out, please see [this guide](https://lbry.io/faq/how-to-change-email). If you sign into a new email and need to transfer your verification status, you'll need to [reach out to us](mailto:help@lbryio) in order to link your accounts. Please do not verify again to obtain rewards on a 2nd account, your Rewards account may be disabled for abuse.
|
||||
|
||||
### What if I want to run LBRY on multiple computers or on different Windows accounts?
|
||||
If you want to run the LBRY app on multiple PCs or Windows users, you can either choose not to sign in on the other computers/accounts or use a different email address for each. These additional accounts will not be eligible for LBRY Rewards as they are only allowed on a one account per household basis. If you log into a 2nd PC with the same email, the original PC will be signed out. Changing accounts back and forth on the same PC/user account will cause them to be merged.
|
||||
|
||||
### What are LBRY Rewards? {#rewards}
|
||||
[LBRY Rewards](https://lbry.io/faq/rewards) are used to distribute LBRY Credits(LBC) to new and existing users by allowing them to explore app functions and complete tasks which generate LBC as an award. In order to be eligible for Rewards, you need to [verify your identity](https://lbry.io/faq/identity-requirements) which uniquely identifies you as a LBRY user.
|
||||
|
||||
### What is a wallet and how do I find it? {#wallet}
|
||||
A wallet is a secure, digital wallet used to store, send and receive cryptocurrencies like LBRY Credits(LBC). The LBRY App comes with its own wallet and is stored locally on your computer and nowhere else! **It is critical that you [backup your wallet data](https://lbry.io/faq/backup) in case you lose access to your PC or need to [migrate](https://lbry.io/faq/backup-data) to a new one.**
|
||||
|
||||
In the app, you can find your wallet in the top-right hand corner, next to the bank icon. Clicking it will bring you to the wallet overview page which shows your balance, available Rewards and recent transactions.
|
||||
|
||||
|
||||
The LBRY wallet is different from other cryptocurrencies because it also stores your shared content's metadata in the form of [claims](https://lbry.io/faq/naming) when using the [publishing features]((https://lbry.io/faq/how-to-publish). Claim related [wallet transactions](https://lbry.io/faq/transaction-types) ensure that the blockchain uniquely identifies your content and the payment/tips can be routed appropriately.
|
||||
|
||||
### Where do I find my LBC wallet address?
|
||||
You can find your address by first clicking on the bank icon in the top right, then navigating to the Send/Receive tab. Your wallet holds multiple receiving addresses and new ones can be generated by clicking "Get New Address". Your wallet balance is the sum total of all the LBC available in each of your addresses.
|
||||
|
||||
|
||||
### Where can I get more LBRY Credits?
|
||||
The LBRY App is also integrated with [ShapeShift](https://lbry.io/faq/shapeshift) on the Get Credits tab of the wallet which allows you to convert cryptocurrencies into LBC or you can also [trade for LBC on exchanges](https://lbry.io/faq/exchanges).
|
||||
|
||||
### Where is all my LBRY App data stored? {#data}
|
||||
Please see the [LBRY directories FAQ page](https://lbry.io/faq/lbry-directories) for more information on where LBRY data is stored. Besides the internal LBRY data, you can also configure your LBRY download directory via the option at the top of the Settings page (gear icon in the top right).
|
||||
|
||||
### Why is content downloaded to my PC even when I stream?
|
||||
LBRY is a decentralized peer to peer protocol, meaning there are no big servers storing all the files (like YouTube), but instead, data is stored on each participant's computer (similar to BitTorrent). When you stream or download, LBRY will store the content in encrypted chunks called [blobs files](https://lbry.io/faq/lbry-directories) and seed it to the entire network so others can also download from you. It will also store the completed file in your downloads folder. Currently, there is no way to stop sharing or to store data temporarily, but you can always delete any files you don't want to seed from the LBRY App Downloads area.
|
||||
|
||||
### I want to share my content, where do I start? {#publish}
|
||||
Please refer to our [publishing guide](https://lbry.io/faq/how-to-publish) as a reference to assist you through the publishing process.
|
||||
|
||||
### Where can I see my Downloaded and Published items?
|
||||
Click the folder icon next to the Publish button to view downloaded files. Click the Published tab to view your published content.
|
||||
|
||||
### How do I know if I'm sharing content and helping the LBRY network properly?
|
||||
The easiest way to confirm that you are sharing correctly is to determine if the port used for seeding, 3333, is open to the rest of the LBRY network. To do so, type 3333 into [this port checking tool](http://www.canyouseeme.org) and check the result. It if shows Open, you are all set. If it shows closed, you may need to check your router settings for uPnP options (set to enable) or forward ports 3333 TCP and 4444 UDP to your local computer running LBRY. Firewall and NAT settings may also affect the availability of this port.
|
||||
|
||||
### How can I search for content on LBRY?
|
||||
Searching in LBRY is as easy as typing your search term(s) into the address bar at the top and waiting for the results to return (**don't click Enter!**). Clicking the Enter key will skip the search function and go directly to the URL typed - this is only helpful if you know the exact URL you are trying to view. We are still in the process of optimizing the search results, please bear with us if you are having trouble finding something!
|
||||
|
||||
|
||||
### How can I subscribe and view my favorite channels?
|
||||
If you navigate to a channel page (LBRY URLs with an @ symbol in the front), you will see a **Subscribe @** button that manages your subscription. To view all your subscribed channels on one page, click the Subscriptions tab from the home page or the **@** symbol next to the LBRY address bar.
|
||||
|
||||
|
||||
### Content consistently fails to stream or download, what can I do?
|
||||
Please see our [streaming guide](https://lbry.io/faq/unable-to-stream) if you consistently cannot download or stream content on LBRY.
|
||||
|
||||
### Some files don't open in the LBRY app, what's going on?
|
||||
Currently, the LBRY in-app player supports MP4 videos, mp3s, images, GIFs, HTML and text files. Even though it doesn't support other formats within the app, the files can be externally opened by clicking the **Open** button or navigating to the file by clicking the **Downloaded to** file path on the content page.
|
||||
|
||||
### How do I begin troubleshooting problems myself?
|
||||
Please see [this guide](https://lbry.io/faq/how-to-find-lbry-log-file) on how to find your LBRY log files. These may provide you additional information to troubleshoot issues or to provide to the [support team](https://lbry.io/faq/support).
|
||||
|
||||
### I need additional help with the LBRY app, where can find it? {#support}
|
||||
Please check our [other FAQ entries](https://lbry.io/faq) for more information. We are always here to help as well, feel free to [reach out to us](https://lbry.io/faq/support).
|
||||
|
|
@ -8,14 +8,14 @@ Depending on which OS and wallet you use, LBRY files may be stored in several pl
|
|||
## Windows
|
||||
|
||||
- `C:\Program Files (x86)\LBRY` - LBRY application itself
|
||||
- `C:\Users\%USER%\AppData\Local\lbry\lbrynet` or `%localappdata%\lbry\lbrynet` - Daemon configuration and blobs
|
||||
- `C:\Users\%USER%\AppData\Local\lbry\lbrynet` or `%localappdata%\lbry\lbrynet` - Daemon configuration and encrypted blob files
|
||||
- `C:\Users\%USER%\AppData\Local\lbry\lbryum` or `%localappdata%\lbry\lbryum` - Wallet and blockchain headers
|
||||
|
||||
*\*If you originally installed v0.14 and below, the lbrynet and lbryum directories will be in `%appdata%`*
|
||||
|
||||
## MacOS
|
||||
|
||||
- `~/Library/Application Support/LBRY` - LBRY application and data files
|
||||
- `~/Library/Application Support/LBRY` - LBRY application, daemon configuration and encrypted blob files
|
||||
- `~/.lbryum` - Wallet and blockchain headers
|
||||
- `~/.lbrycrd` - Location for [lbrycrdd](https://lbry.io/faq/standalone-wallet) full blockchain data (separate install)
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ Depending on which OS and wallet you use, LBRY files may be stored in several pl
|
|||
## Linux
|
||||
|
||||
- `/opt/LBRY` - LBRY application itself
|
||||
- `~/.local/share/lbry/lbrynet` - Daemon configuration and blobs
|
||||
- `~/.local/share/lbry/lbrynet` - Daemon configuration and encrypted blob files
|
||||
- `~/.local/share/lbry/lbryum` - Wallet and blockchain headers
|
||||
- `~/.lbrycrd` - Location for [lbrycrdd](https://lbry.io/faq/standalone-wallet) full blockchain data (separate install)
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ category: mining
|
|||
Library Credits (LBC) are mined over a 20-year Proof of Work period.
|
||||
Block rewards increase every 100 blocks by 1LBC, peak at 500, and decline slowly.
|
||||
|
||||
LBRY mining is dominated by the GPU market and we don't see CPU mining as economically viable at this point. If you still want to CPU mine to help the network, see instructions below.
|
||||
LBRY mining is dominated by the GPU and FPGA market and we don't see CPU mining as economically viable at this point. If you still want to CPU mine to help the network, see instructions below.
|
||||
|
||||
For GPU mining, please see our list of [pools](https://lbry.io/faq/mining-pools). Each pool has a slightly different setup so please check their Getting Started page. We can also provide mining assistance via the #mining channel on [Discord Chat](https://chat.lbry.io).
|
||||
**Note:** Sgminer is for AMD GPU Cards and CCminer is for Nvidia GPU Cards
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ Absolutely. Here are some links to the pools. Each pool will have instructions o
|
|||
While we try to work with reliable pool operators, LBRY does not officially run or endorse any one pool.
|
||||
|
||||
- [LBRY Community Pool](http://lbrypool.com)
|
||||
- [YIIMP](http://yiimp.ccminer.org)
|
||||
- [Pool.MN](https://pool.mn/lbry/index.php?page=gettingstarted)
|
||||
- [SuprNova](https://lbry.suprnova.cc/index.php?page=gettingstarted)
|
||||
- [CoinMine](https://www2.coinmine.pl/lbc/index.php?page=gettingstarted)
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Unfortunately, when you try to give stuff away for free, people will abuse it.
|
|||
Phone number verification provides another method for LBRY users to participate in the [rewards](https://lbry.io/faq/rewards) program.
|
||||
|
||||
### What if my phone number isn't working?
|
||||
In order to combat abuse, certain prepaid services, Google Voice and other VOIP will be blocked for phone verification. If you are using one of these and having trouble, please see one of the [other verification methods](https://lbry.io/faq/identity-requirements).
|
||||
Certain regions, prepaid services and VOIP will be blocked from phone verifications in order to combat abuse,. If you are having trouble with getting a phone number accepted, please see one of the [other verification methods](https://lbry.io/faq/identity-requirements).
|
||||
|
||||
### What if the LBRY app says my phone number already exists?
|
||||
This usually means that there is another LBRY account/email address that's already associated with that number. If you are changing email addresses and need to link your accounts or you believe this is an error, please [reach out to us](mailto:help@lbry.io).
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ To provide a rich user experience and to [distribute](https://lbry.io/faq/credit
|
|||
|
||||
### Verification requirements
|
||||
|
||||
In order to be eligible for LBRY Rewards, users must have a [verified account](https://lbry.io/faq/identity-requirements). If users choose not to verify themselves, LBRY works with full functionality but they will not be able to earn any free credits from LBRY. **Rewards will only be granted on a 1 account per household basis and LBRY reserves the right to revoke Rewards privileges on any account if abuse is suspected or if VPN is used.**
|
||||
In order to be eligible for LBRY Rewards, users must have a [verified account](https://lbry.io/faq/identity-requirements). If users choose not to verify themselves, LBRY works with full functionality but they will not be able to earn any free credits from LBRY. **Rewards will only be granted on a 1 account per household basis and LBRY reserves the right to revoke Rewards privileges on any account if abuse is suspected or if VPN/shared connections are used.**
|
||||
|
||||
### List of the current LBRY Rewards
|
||||
| Reward | Amount | Description |
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ category: troubleshooting
|
|||
order: 1
|
||||
---
|
||||
|
||||
Proper network connectivity, visibility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer one-on-one [troubleshooting](https://lbry.io/faq/how-to-report-bugs).
|
||||
Proper network connectivity, visibility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer [one-on-one troubleshooting](https://lbry.io/faq/how-to-report-bugs).
|
||||
|
||||
The first area to check for start-up issues is the [LBRY log file](https://lbry.io/faq/how-to-find-lbry-log-file). Except in extreme cases, a log file should be generated by the daemon startup process and will usually reveal clues on where to find problems.
|
||||
|
||||
|
|
@ -25,23 +25,22 @@ LBRY operates on a couple different ports and if there are conflicts/firewall ru
|
|||
### LBRY used to work previously but now it won't start
|
||||
First and foremost, please ensure you are on the [latest version](https://lbry.io/get) of LBRY. Reinstalling the latest version may alleviate some start-up issues. Before installing, either make sure no LBRY/lbrynet processes or simply reboot your computer.
|
||||
|
||||
- On Windows, you may receive an error titled `Uncaught Exception - Error: Object has been destroyed...` which prevents you from starting LBRY. This usually means LBRY.exe or lbrynet-daemon.exe is already running in the background. Check the task manager, kill the process(es) and start LBRY again. Please see this [GitHub issue](https://github.com/lbryio/lbry-app/issues/353) for more details.
|
||||
- On Windows, you may receive an error titled `Uncaught Exception - Error spawn...ENOENT` which usually means LBRY can't find the daemon exe file. Please see this [GitHub issue](https://github.com/lbryio/lbry-app/issues/396) for more details. The workaround is to rerun the [latest](https://lbry.io/get) LBRY installation file.
|
||||
- On Windows, if you get stuck on the "Starting daemon" green screen, the lbrynet-daemon file may be missing. The workaround is to rerun the [latest](https://lbry.io/get) LBRY installation file and try again.
|
||||
- On older MAC installations, you may run into an issue with the daemon shutting down immediately. Please see [this GitHub issue](https://github.com/lbryio/lbry-app/issues/291) for troubleshooting.
|
||||
- Other typical startup troubleshooting would be to ensure that LBRY or lbrynet-daemon is not already running in the background. If the processes cannot be killed, a restart of your computer may be required.
|
||||
|
||||
### Known startup issues and workarounds
|
||||
#### Stuck at blockchain sync {#sync}
|
||||
If you are stuck on the blockchain sync step or it shows a block count that doesn't decrease, you may need to clear your your blockchain cache. To do so, Shut LBRY down completely (check for running LBRY/lbrynet-daemon processes), delete the `blockchain_headers` file in the [lbryum folder](https://lbry.io/faq/lbry-directories) and then start LBRY again.
|
||||
If you are stuck on the blockchain sync step or it shows a block count that doesn't decrease, you may need to clear your your blockchain cache. To do so, Shut LBRY down completely by closing it from the system tray(check for running LBRY/lbrynet-daemon processes), delete the `blockchain_headers` file in the [lbryum folder](https://lbry.io/faq/lbry-directories) and then start LBRY again.
|
||||
#### Linux auth_token requirements
|
||||
Currently, LBRY requires an authorization token to be generated using the [keytar](https://github.com/atom/node-keytar) libraries. Please ensure libsecret and keytar are installed. On some distributions, LBRY won't run unless gnome keyring is also installed/operational. See [GitHub issue](https://github.com/lbryio/lbry-app/issues/386) for more information. If you get a GLIBCXX_3.4.2 error, please see [this issue](https://github.com/lbryio/lbry-app/issues/423#issuecomment-327519486).
|
||||
#### Windows user path has non-ASCII characters
|
||||
Currently, the LBRY app may fail to start because it does not support non-ASCII / non-English letters in the c:\Users\<username> directory where it tries to create your LBRY wallet, downloads and application data. As a workaround, you can manually set these directories in the `daemon_settings.yml` file. If this file does not exist in your [lbrynet folder](https://lbry.io/faq/lbry-directories), you can create one or you can use [this sample](https://goo.gl/opybNE).
|
||||
Currently, the LBRY app may fail to start because it does not support non-ASCII / non-English letters in the c:\Users\<username> directory where it tries to create your LBRY wallet, downloads and application data. As a workaround, you can manually set these directories in the `daemon_settings.yml` file within the [lbrynet folder](https://lbry.io/faq/lbry-directories). If this file does not exist in your [lbrynet folder](https://lbry.io/faq/lbry-directories), you can create one or you can use [this sample](https://goo.gl/opybNE).
|
||||
|
||||
This will setup your directories as follows or you can create/edit the file to configure your own paths (but again, don't use any folders with non-ASCII letters):
|
||||
This will configure your directories to the folders below or you can create/edit the file to configure your own paths (but again, don't use any folders with non-ASCII letters):
|
||||
```
|
||||
{data_dir: 'c:\lbry\lbrynet',
|
||||
lbryum_wallet_dir: 'c:\lbry\lbryum',
|
||||
download_directory: 'c:\lbry\Downloads'}
|
||||
```
|
||||
After you are done inserting or editing the `daemon_settings.yml` configuration file, try running LBRY again. The settings file has to stay in the original location and LBRY will create the new folders/data in the specified directories. `lbrynet`/`lbryum` folders should be copied there if you are migrating from a previous install. If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support.
|
||||
After you are done inserting/editing the `daemon_settings.yml` configuration file, try running LBRY again. The settings file has to stay in the original location and LBRY will create the new folders/data in the specified directories. `lbrynet`/`lbryum` folders should be copied there if you are migrating from a previous install. If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support.
|
||||
|
|
|
|||
|
|
@ -3,22 +3,27 @@ title: What is LBRY exactly – is it a protocol, an app, a website, a company?
|
|||
category: LBRY 101
|
||||
order: 1
|
||||
---
|
||||
LBRY is many components working together. For most users, it will just be a place where they can find great videos, music, ebooks, and more. A vast digital library available on all of your devices.
|
||||
For most users, LBRY will be a place where they can find great videos, music, ebooks, and more. A vast digital library available on all of your devices. But LBRY is many components working together.
|
||||
|
||||
But behind that experience is an ecosystem that can be hard to understand at first – especially because we tend to refer to all the pieces and the system-as-a-whole as “LBRY”. (We’re working on clearing that up.)
|
||||
LBRY is first and foremost a new *protocol* that allows anyone to build apps that interact with digital content on the LBRY network. Apps built on the protocol allow creators to upload their work to the LBRY network of hosts (like BitTorrent), and set a price per stream or download (like iTunes) or give it away for free (like YouTube without ads).
|
||||
|
||||
It might be easier to start with what LBRY is not: it is not just another corporate media service like YouTube or iTunes or Spotify. It is first and foremost a new *protocol* that allows artists to upload their content to a network of hosts (like BitTorrent) and set a price per stream or download (like iTunes) or give it away for free (like YouTube without ads). What makes this all possible is the blockchain technology developed by the founder of Bitcoin. Do you have to understand any of this to use and enjoy LBRY? No. Does it still matter to users? Yes!
|
||||
What makes this all possible is the blockchain technology developed by the creator of Bitcoin. Do you have to understand any of this to use and enjoy LBRY? No. Does it still matter to users? Yes!
|
||||
|
||||
Gmail has built an extremely popular email service on top of the near-universal *SMTP protocol* that everyone uses to exchange emails. Anyone sending email with SMTP can communicate with Gmail addresses, no matter what email platform they use (Yahoo!, AOL, iCloud, etc.). Google can’t interfere with someone emailing from a @yahoo.com address to an @aol.com address – and users are free to switch between services at any time, taking their emails with them. Users have a lot of power in open protocols that is often taken for granted.
|
||||
## Why Build A Protocol?
|
||||
Building [protocols, not platforms](https://lbry.io/news/blockchain-is-love-blockchain-is-life), is the future of the free, open internet. Almost every tech giant today is a centralized service that sells users’ personal information and attention to advertisers. They spend a lot of money chasing their product (your personal information and time/attention), but at the end of the day, offer it up for free in exchange for access to the platform.
|
||||
|
||||
Compare this to a proprietary, centrally controlled service like Facebook Messenger. If you conduct all of your social communications via Messenger, you’re stuck in that environment – you cannot move your messages or contacts over to Google Chat or Skype. And if Facebook changes the way Messenger functions by censoring conversations or sharing your information with advertisers or governments, tough luck.
|
||||
We think users should own their content (and their privacy) instead of handing it over to a corporate giant and their advertising buddies. If you think we’re being paranoid, there are dozens of examples of [companies abusing users](https://lbry.io/news/why-do-tech-giants-abuse-their-users) and acting against their interests. It’s not paranoia if they’re actually out to get you.
|
||||
|
||||
Even platforms that are ostensibly designed with the user’s control and privacy in mind are susceptible to corruption if they are centrally controlled. WhatsApp comes to mind. WhatsApp built a huge global user base claiming to put users above advertisers. Then Facebook bought it. Now users may well have their personal phone numbers and metadata mined for Facebook’s advertising algorithms.
|
||||
## Open Source and Community Driven
|
||||
The LBRY project is more than just a new protocol. It is also a company, *LBRY Inc.*, which is developing a *LBRY app* to allow users to easily interact with the protocol.
|
||||
|
||||
There is no such risk of top-down corruption with the LBRY protocol. Content uploaded to the decentralized LBRY network remains publicly accessible so long as the community finds it valuable and continues to host it.
|
||||
Not only is [our app](https://lbry.io/get?auto=1) completely open-source, but others are welcome to create competing apps that also use the LBRY protocol. For a content creator, your uploaded content will be available to all of these apps at the same time.
|
||||
|
||||
Now, the LBRY project is more than just a revolutionary new protocol. It is also a company, *LBRY Inc.*, which is developing a *LBRY app* to allow users to easily interact with the protocol. So it’s as if Google had developed the email protocol, released it to the world for free, and then built Gmail to help people make use of it. Not only is our app completely open-source, but others are welcome to create competing apps that also use the LBRY protocol. For a content creator, your uploaded content will be available to all of these apps at the same time.
|
||||
LBRY is challenging the centralized, corporate model from the ground up. Everything we’ve built is open-source, decentralized, and belongs to the community using it.
|
||||
|
||||
Do you see the difference here? YouTube can afford to push around its creators and users because they’ve created tremendous lock-in. LBRY is challenging this model from the ground-up. Everything we’ve built is open-source, decentralized, and belongs to the community using it. LBRY Inc. could go bankrupt tomorrow and the LBRY protocol will live on. Can YouTube say that?
|
||||
<h3 style="text-align: center;" markdown="1">I’d Buy That For A Dollar!</h3>
|
||||
<video width="100%" controls src="https://spee.ch/c/Id-Buy-That-for-a-Dollar.mp4"/></video>
|
||||
|
||||
[Download the LBRY App Now](https://lbry.io/get)
|
||||
Well you’re in luck, because you can [download the LBRY app](https://lbry.io/get?auto=1) for free and build LBRY with us today - try it out and let us know what you think!
|
||||
|
||||
[Download the LBRY App Now](https://lbry.io/get?auto=1)
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: 5 Questions About LBRY
|
|||
date: '2015-07-01 13:09:20'
|
||||
---
|
||||
|
||||
As I recently traveled across Europe, and ultimately to [PorcFest](www.porcfest.com), I took time to talk to talk to entrepreneurs, technologists, and libertarians about [LBRY](https://lbry.io).
|
||||
As I recently traveled across Europe, and ultimately to [PorcFest](http://www.porcfest.com), I took time to talk to talk to entrepreneurs, technologists, and libertarians about [LBRY](https://lbry.io).
|
||||
For the mutualistic education of myself and others, below are the questions and answers to five frequently asked questions.
|
||||
|
||||
## Five Questions
|
||||
|
|
@ -16,7 +16,7 @@ As we recently Tweeted, we're extremely close to releasing a POC client:
|
|||
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">LBRY's doors are locked, but gaze through the glass and one behold's the hazy form of a proof-of-concept <a href="http://t.co/93ViBCx72g">pic.twitter.com/93ViBCx72g</a></p>— LBRY (@LBRYio) <a href="https://twitter.com/LBRYio/status/616333374878281728">July 1, 2015</a></blockquote>
|
||||
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||||
|
||||
To make sure you hear as soon as it is available, [join our mailing list](https://lbry.io/list/subscribe) or [follow us](https://twitter.com/lbry_io) on Twitter.
|
||||
To make sure you hear as soon as it is available, [join our mailing list](https://lbry.io/list/subscribe) or [follow us](https://twitter.com/lbryio) on Twitter.
|
||||
|
||||
|
||||
### 2. What happens if someone uploads infringing content to LBRY?
|
||||
|
|
@ -53,7 +53,7 @@ We will also be releasing the source of LBRY so that others may stand upon us.
|
|||
### 4. What's the difference between LBRY and MaidSafe (or X)?
|
||||
|
||||
There are several attempts to build a decentralized computing platform. LBRY is not one of them; it exists only for information.
|
||||
Products that subsume the information problem, such as [MaidSafe](www.maidsafe.com) or [Ethereum](www.ethereum.org), will crumble
|
||||
Products that subsume the information problem, such as [MaidSafe](https://www.maidsafe.net) or [Ethereum](https://www.ethereum.org), will crumble
|
||||
under their own weight at the worst and not approach LBRY's performance at their best. Building an information delivery network
|
||||
inside of a larger decentralized platform is guaranteed at a fundamental level to result in worse performance, greater expense,
|
||||
or both.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Coinomi Wallet Integration'
|
||||
date: '2017-06-02 00:14:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -22,10 +22,8 @@ A commenter on his Biblical series summarized his channel best:
|
|||
└📁 Bad Videos
|
||||
└⚠️ This folder is empty
|
||||
|
||||
Check out some of the best lectures on LBRY at:
|
||||
Check out some of the [best lectures on LBRY](https://open.lbry.io/%40JordanBPeterson).
|
||||
|
||||
- lbry://@JordanBPeterson
|
||||
You can learn more about Dr. Peterson, and [order his newest book](https://jordanbpeterson.com/12-rules-for-life/), here on his [website](https://jordanbpeterson.com/).
|
||||
|
||||
You can learn more about Dr. Peterson, and [pre-order his next book](https://jordanbpeterson.com/12-rules-for-life/), here on his [website](https://jordanbpeterson.com/).
|
||||
|
||||
**Not on LBRY yet?** [Get an invite here](https://lbry.io/get). Know the meaning of life? Email reilly@lbry.io because he’s desperate to know. Or sync your channel at: https://api.lbry.io/yt/connect?type=sync
|
||||
**Not on LBRY yet?** [Download it here](https://lbry.io/get). Know the meaning of life? Email reilly@lbry.io because he’s desperate to know. Or sync your channel at: https://api.lbry.io/yt/connect?type=sync
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Latest LBRY App Adds Tipping, Themes, and More'
|
||||
date: '2017-09-21 10:30:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY v0.17 Has What You’ve Been Searching For'
|
||||
date: '2017-10-12 16:00:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: "LBRY Gets Content Creators Out of Precarious Position - Daily Decrypt's Amanda B. Johnson"
|
||||
date: '2015-10-26 15:10:51'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY v0.18 is Trending Towards Greatness'
|
||||
date: '2017-11-13 14:25:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Howl With Us'
|
||||
date: '2017-11-24 00:20:30'
|
||||
cover: ''
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'It's A Very Special Holiday Special Movie Night'
|
||||
date: '2017-12-10 00:16:00'
|
||||
cover:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY v0.19 Is Shifting Into High Gear'
|
||||
date: '2017-12-11 12:45:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Development and Community Update'
|
||||
date: '2017-12-12 5:00:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Stop Net Banality'
|
||||
date: '2017-12-14 12:30:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Digging Into LBRY: Our Inspiration & The Future of Content'
|
||||
date: '2015-11-05 21:08:22'
|
||||
---
|
||||
|
|
|
|||
17
content/news/160-srodalmenara.md
Normal file
17
content/news/160-srodalmenara.md
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
author: reilly-smith
|
||||
title: 'Rock softly and carry a big guitar'
|
||||
date: '2018-02-08 00:20:00'
|
||||
cover: 'srod-banner.png'
|
||||
---
|
||||
Music. Metal. Mattlestar M’lactica.
|
||||
|
||||
What do you get when you mash Spanish, Celtic, and Islander blood into a metal rock stew? The answer is simple: [Srod Almenara](https://open.lbry.io/%40srodalmenara)
|
||||
|
||||
<video width="100%" controls poster="http://berk.ninja/thumbnails/eNpdks5RALU" src="https://spee.ch/65a20aaa01bf7a8f6e99c69e0c536a3359536a34/star-wars-rogue-one-trailer-theme-cover.mp4"/></video>
|
||||
|
||||
From metal and progressive rock originals to the best geek covers this side of Jakku, it’s with warm welcome we re-introduce the music scene on LBRY with wailing chords.
|
||||
|
||||
Subscribe to @srodalmenara or share his songs the *safe* way [via Spee.ch](https://spee.ch/@srodalmenara).
|
||||
|
||||
**[Download LBRY today](https://lbry.io/get)**. Is your favorite channel not on LBRY? Help us feature what you want to see! Email [reilly@lbry.io](mailto:reilly@lbry.io) to make it happen. Or sync your own channel at: https://lbry.io/youtube
|
||||
19
content/news/161-nickatnyte.md
Normal file
19
content/news/161-nickatnyte.md
Normal file
|
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
author: reilly-smith
|
||||
title: 'Clash Cash'
|
||||
date: '2018-02-22 00:20:00'
|
||||
cover: 'nickatnyte-banner.jpg'
|
||||
---
|
||||
Are casual mobile games *really* casual?
|
||||
|
||||
[@nickatnyte](https://open.lbry.io/%40nickatnyte) will reframe how seriously you can take the Clash series.
|
||||
|
||||
<video width="100%" controls poster="http://berk.ninja/thumbnails/TW-sWnxiHrs" src="https://spee.ch/37763ba30c3714491816fec88ff208c3fc42ea00/boosted-troops-loot-clash-of-clans.mp4"/></video>
|
||||
|
||||
A long time Clash series veteran [@nickatnyte](https://open.lbry.io/%40nickatnyte) (and more at [@nickatnyte2](https://open.lbry.io/%40nickatnyte2)) Nick Nyte and his guests dive deeper into the casual/mobile genre than you ever thought possible, digging out every last bit of strategy there is to glean.
|
||||
|
||||
He’s also a popular Fortnite streamer if action games are more your style. Either way, Nick’s knowledge and charisma make long streams fly by in an instant.
|
||||
|
||||
Subscribe to @nickatenyte for the newest Clash strategies and welcome him to LBRY with LBC tips galore.
|
||||
|
||||
**[Download LBRY today](https://lbry.io/get)**. Is your favorite channel not on LBRY? Help us feature what you want to see! Email [reilly@lbry.io](mailto:reilly@lbry.io) to make it happen. Or sync your own channel at: https://lbry.io/youtube
|
||||
17
content/news/162-colinslaststand.md
Normal file
17
content/news/162-colinslaststand.md
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
author: reilly-smith
|
||||
title: 'The Stand'
|
||||
date: '2018-03-01 00:20:00'
|
||||
cover: 'cls-banner-2.jpg'
|
||||
---
|
||||
This week, I’d like to reintroduce one of my personalities on LBRY.
|
||||
|
||||
You caught Mr. Moriarty’s show Sidequest [in January](https://lbry.io/news/sidequest). Now it’s time for the main course.
|
||||
|
||||
<video width="100%" controls poster="http://berk.ninja/thumbnails/2pI5sJU3lVI" src="https://spee.ch/9fcd6b485e8088908d84cd2f4c042ab7ce21a47f/the-coming-and-going-of-the-wild-west.mp4"/></video>
|
||||
|
||||
The prolific [Colin Moriarty](https://open.lbry.io/%40ColinsLastStand) (CLS, Sidequest, as well as podcast series Fireside Chats and now Knockback) has continued to forge his own path in games and news media with his own blend of political opinion, games criticism, and a wit that kills fluff pieces on site. He’s as no-nonsense as they come. Long form interviews, short form reviews, and video essays on what Trump, Oprah, and reactionary thought means for America, you’ll find no shortage of content from this IGN editor-turned-content-maverick.
|
||||
|
||||
Become a subscriber to [Colin’s Patreon here](https://www.patreon.com/colinslaststand/posts).
|
||||
|
||||
**[Download LBRY today](https://lbry.io/get)**. Is your favorite channel not on LBRY? Help us feature what you want to see! Email reilly@lbry.io to make it happen. Or sync your own channel at: https://lbry.io/youtube
|
||||
126
content/news/163-lbry-development-community-update-Feb-2018.md
Normal file
126
content/news/163-lbry-development-community-update-Feb-2018.md
Normal file
|
|
@ -0,0 +1,126 @@
|
|||
---
|
||||
author: tom-zarebczan
|
||||
title: 'Development and Community Update February 2018'
|
||||
date: '2018-03-01 18:00:00'
|
||||
cover: 'wooden-letters-banner.jpg'
|
||||
---
|
||||
In December, we published the [first ever LBRY Development and Community update](https://lbry.io/news/lbry-development-community-update-1) and followed up with another for [January 2018](https://lbry.io/news/lbry-development-community-update-jan-2018) - be sure to check both out if you missed them! We will continue these updates at the beginning of each month to keep each and every LBRYian up to date on our quest to revolutionize content discovery, sharing and monetization!
|
||||
|
||||
Please take a moment to read our [Looking Back and Moving Forward: LBRY in 2017/2018](https://lbry.io/news/lbry-in-2017-2018) blog post and check out our [roadmap](https://lbry.io/roadmap).
|
||||
|
||||
Before diving in, we want to let everyone know that we’ll be hosting a **live Ask me Anything event** with our CEO Jeremy Kauffman next **Friday (3/9) at 5:30PM ET** on Twitter and Reddit. This will be the first live stream from our office, so please bear with us through any technical difficulties. Join us on the [LBRY subreddit](https://www.reddit.com/r/lbry/) and use #lbryAMA on [Twitter](https://twitter.com/LBRYio), and bring some friends who have burning questions about LBRY!
|
||||
|
||||
To skip the tech stuff and see what’s happened and what’s next in the LBRY community, click the link below. Otherwise, read on!
|
||||
|
||||
[Skip to **Community Happenings**](#com-updates)
|
||||
|
||||
# Development Updates {#dev-updates}
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://lbry.tech which will also include a StackExchange like forum for Q&A/troubleshooting.
|
||||
|
||||
### App and Protocol Summary
|
||||
As you may know from our previous updates, the LBRY app is undergoing a redesign which is taking up a large chunk of the team’s time but the app team is aiming to release a patch to version 0.20 which brings a few bug fixes, an updated LBRY protocol version and possibly a new feature or two (spee.ch thumbnail uploads from within the app, automated subscription downloads).
|
||||
|
||||
On the app side, bug fixes will include: 1) the sorting of published claims, 2) video player issues where content does not play on first attempt, 3) app state will be saved when closing LBRY to tray, 4) disabling of drag and drop of files into the app, 5) poor error messages when publishing and 6) start time of night mode.
|
||||
|
||||
The 0.19 LBRY protocol update is in the final stages of testing and will also include many bug fixes and enhancements. See a full changelog of the [current release candidate](https://github.com/lbryio/lbry/releases/tag/v0.19.0rc37) for details. Some of the highlights are: 1) better tracking of edited claims for both publishers and downloaders, 2) ability to automatically renew expiring claims, 3) ability to update claims if your current LBC balance doesn’t cover the claim amount (it will use the claim amount in the calculation), 4) ability to re-download content at updated claims, 5) improved startup performance, 6) a single database for claim and file information, 7) transaction list to include abandon claim information and 8) smarter wallet address reuse and fixing bugs where addresses were created incorrectly.
|
||||
|
||||
After this round of protocol enhancements, the team will be focusing on improving resolve(process by which claims are looked up on the blockchain) and download performance, availability in the LBRY Peer to Peer layer and blockchain sync optimizations.
|
||||
|
||||
Stay tuned for an updated version of the LBRY app next week! In the meantime, you can download the current version [here](https://lbry.io/get?auto=1) if you don’t have it installed already!
|
||||
|
||||
### App Redesign
|
||||
The LBRY App redesign continues to make great progress you can follow along on [GitHub](https://github.com/lbryio/lbry-app/issues/848) for the latest status and updates. The latest focus has been on refactoring the inner workings of the Publish page into a more optimized version using the React framework. We also have a community member, @btzr, who is helping out in migrating the dark theme into the new design.
|
||||
|
||||
Want to explore a web based prototype of the new LBRY app design? Head over to [https://design.lbry.io](https://design.lbry.io) to get a preview of what’s to come. This page works best on a Desktop but may display correctly in landscape mode on mobile. *Please note: some of the design features like notifications and commenting are still experimental and most likely will not roll out with the first iteration of the re-design as they require additional support from the protocol to work properly.*
|
||||
|
||||
|
||||
|
||||
### Subscription Enhancements in Progress
|
||||
A new round of enhancements to the Subscription feature are being developed. The goal is to increase interactivity, engagement and notification for users who subscribe to channels on LBRY. This will include an option to automatically download new content as it is added to a channel as well as notification features within the app and email. Have questions or comments, drop us a line on the [GitHub issue](https://github.com/lbryio/lbry-app/issues/994).
|
||||
|
||||
### LBRY Mobile for Android
|
||||
LBRY recently worked with a user interface designer who came up with a very nice and simple design prototype, check out video below for a preview. The process of incorporating this prototype into React Native code is underway. To solve delays deploying the app changes, we had to come up with a way to build the UI and daemon separately, such that the React Native app can be reloaded without having to rebuild the daemon each time (slow!). This enables testing the UI changes relatively quickly against any stable or development build of the daemon. There is a good chance that we will have a basic working mobile Android app in a few weeks!
|
||||
|
||||
<video width="100%" controls src="https://spee.ch/b/android-prototype.mp4"/></video>
|
||||
|
||||
### spee.ch Update
|
||||
Spee.ch is now using React! As spee.ch began to grow, we soon realized that in order to provide a robust front end experience we would need more flexibility in the way we build that experience. With that goal in mind, we spent the past few weeks converting the front end code from static handlebars templates to a full fledged React app. This will allow us to do a lot more with efficiently reusing components, building more robust tools for users, and hopefully makes the code base more accessible to community developers who are already using the popular React framework. As part of this transition, we also converted some of the back end code to perform server side rendering and updated the api endpoints.
|
||||
|
||||
### Automated Testing and Coding Tests
|
||||
As part of our push for improving scaling and overall performance, reliability and availability of the LBRY protocol we've been putting a lot of effort into increasing code coverage (lines of code covered by automated tests) and the sophistication of our integration testing. For example, improve the distributed file sharing protocol we created network models with simulated adverse conditions and then analyzed how LBRY DHT responds to these conditions. Many bugs have been fixed and improvements developed as a result of this work; the best part is that we're doing this in an automated fashion so we'll know instantly when any regressions happen and fix them before deploying new code. Unit testing for blockchain, wallet and other common use cases has also been expanding.
|
||||
|
||||
|
||||
|
||||
# Community Happenings {#com-updates}
|
||||
If you aren’t part of our Discord community yet, [join us](https://chat.lbry.io) anytime and say hello! Our community allows LBRYians to interact with the team directly and for us to engage users in order to grow the LBRY platform.
|
||||
|
||||
### LBRY Team Expands - Protocol Developer!
|
||||
Great news, our [team](https://lbry.io/team) is expanding! We’ve recently hired an additional LBRY protocol developer who will be helping Jack and Kay on improving functionality and performance in LBRY’s core component. We are excited to have Lex on board! Welcome him to the team by saying hello to @eukreign on [Discord](https://chat.lbry.io).
|
||||
|
||||
|
||||
|
||||
### LBRY Merchandise Store
|
||||
On Valentine’s day, LBRY officially launched its at-cost merchandise store through [Apex Apparel](https://apexapparel.shop/collections/lbry) on Discord chat where five lucky community members were sent free merch during an initial giveaway contest. The link was later shared on Reddit and Social media where a few fans have already shared their swag photos. Special thanks to community member @TheSethser for helping us get this project off the ground and for the awesome design work!
|
||||
|
||||
We will tip LBC if you tag us on Twitter or Facebook with a picture of you rocking LBRY swag. Please upload to [spee.ch](https://spee.ch/) and share the post on [Discord](https://chat.lbry.io) or [Reddit](http://reddit.com/r/lbry) to claim your reward. Thanks for your support in spreading LBRY love!
|
||||
|
||||
|
||||
|
||||
### Blockchain Security and Economics
|
||||
Over the last few months, we’ve noticed that the LBRY mining hash rate has gone up significantly due to the manufacturing of FPGA (specialized mining hardware) and we’ve noticed our [community](https://github.com/lbryio/lbrycrd/issues/85) has their concerns about centralization as well. We will be addressing the general blockchain security and economics discussion with a blog post that explains our take and potential solutions.
|
||||
|
||||
### Youtube Sync Site Almost Ready!
|
||||
Our revamped YouTube sync page (replacing [this one](https://lbry.io/youtube)) is almost ready to go live! This program will begin to target YouTubers more aggressively with the goal of having them sync their content to the LBRY network. The new process will allow them to claim their channel directly on the LBRY network during signup, detail the monthly LBC incentive based on subscriber counts and provide a sync status view so they monitor the sync progress. Stay tuned for updates!
|
||||
|
||||
|
||||
|
||||
### LBRY Social Media Updates
|
||||
We’ve surpassed 15k followers on [Facebook](https://www.facebook.com/lbryio) and 30k followers on [Twitter](https://twitter.com/lbryio) - as our audience keeps growing, there will be more opportunities than ever for new users to discover LBRY. We also want our community to be an integral part of our social presence - if you haven’t yet, join our [Discord](https://chat.lbry.io), and feel free to throw out any suggestions for posts, articles, or individuals you think we should reach out to!
|
||||
|
||||
### Twitter LBC Tip Bot
|
||||
We have opened up a bounty for a [Twitter Tip Bot](https://lbry.io/bounty/twitter-tipbot) to expand our ability to distribute LBC to our Twitter followers. This will accompany our Discord and Reddit tip bots which are powerful tools used by ourselves and our community to reward LBRYians for their contributions, testing and feedback. It will work by tagging the tipbot user in Twitter replies/messages with keywords such as “tip”, “balance”, “withdraw”, “deposit” - very similar to our other tip bots. A community member is very close to getting a tipbot working and you can follow [@LBC_TipBot](https://twitter.com/@LBC_TipBot) for updates.
|
||||
|
||||
### BitcoinTalk Official and Moderated Thread
|
||||
We are in the beginning stages of gathering information to create a new and official LBRY Bitcointalk thread. There is an [unofficial one](https://bitcointalk.org/index.php?topic=1541268.new#new) out in the wild currently, but it was not started by LBRY Inc, nor is it moderated. The goal is to serve the Crypto community with another medium of discussion and collaboration. It will be a moderated thread which will have specific rules against the typical hyping / pump market talk as this type of banter is not something LBRY participates in, nor does it help the project mature.
|
||||
|
||||
### Favorite Creators Contest in Discord
|
||||
Head over to our #favoritecreators channel on [Discord](https://chat.lbry.io) to vote on the submitted entries. The winning creator will be offered 10K LBC to sync their content to LBRY! It’s not too late to enter a suggestion either. This experimental contest will run until 3/9/2018.
|
||||
|
||||
|
||||
|
||||
### New Bounties Channel on Discord
|
||||
Check out our new #bounties channel on [Discord](https://chat.lbry.io). This is the place to go to find occasional mini-tasks to earn LBC as well as any questions you may have about LBRY bounties. Types of mini-tasks may include research, marketing tasks, and testing.
|
||||
|
||||
### Meetups and College Campus Initiatives
|
||||
LBRY has officially launched their Meetups and College programs! We are [looking for ambassadors](https://lbry.io/meet) to spread the word on college campuses and at live meetups! If you’d like to bring LBRY to your group, we’ll help you with resources, swag, and LBC for your members!
|
||||
|
||||
|
||||
|
||||
### LBRY.Community Contest Winners
|
||||
The [LBRY.Community contest](https://lbry.community/category/votable-contest-entries/) from January wrapped up and the [winners](https://lbry.community/contest-winners-january-2018/) were first announced and tipped on our Discord channel, congrats to all the winners! All entrants were given LBC Credits as a participation bonus and LBRY.Community is also giving out stickers and handbags to all participants and judges. Thanks again to @rouse and @coolguy3289 for coordinating! The next phase of LBRY.Community’s plans are being discussed with our team.
|
||||
|
||||
### New and updated LBRY FAQ Articles
|
||||
We recently revamped and simplified our [“What is LBRY?”](https://lbry.io/faq/what-is-lbry) FAQ so it’s a tad easier to digest for first time LBRY users.
|
||||
|
||||
The new [LBRY Basics](https://lbry.io/faq/lbry-basics) FAQ entry which will provide first-time (and existing) LBRY app users a better understanding of the various components within the app. It also explains what LBRY accounts are used for and stresses that all LBRY data, including your wallet where credits are stored, is only available on your computer and should be [backed up](https://lbry.io/faq/how-to-backup-wallet) accordingly.
|
||||
|
||||
We’ve also added FAQs which detail LBRY’s [content policy](https://lbry.io/faq/content) and [acceptable use policy](https://lbry.io/faq/acceptable-use-policy). Thanks to @julie for her hard work on these!
|
||||
|
||||
Have an idea for a FAQ or want to help us improve the current ones, check out the code on our [GitHub page](https://github.com/lbryio/lbry.io/tree/master/content/faq) for the lbry.io website.
|
||||
|
||||
### Spee.ch Biz Dev
|
||||
LBRY is actively looking for file sharing websites which could potentially build upon spee.ch’s codebase or be developed alongside it. We have reached out to numerous candidates, held introductory meetings and will continue to research additional potential partnerships. We are looking for developers who share a vision that is culturally aligned with ours: supporting free speech and decentralized technology. Are you interested or know anyone that is? Feel free to reach out to Bill (@billbit on Discord) or via [email](mailto:bill@lbry.io).
|
||||
|
||||
We are also actively looking for communities or websites that could make use of spee.ch’s image sharing features. This includes researching plugins to applications like Wordpress that would make such an integration easier for users.
|
||||
|
||||
### Babson College Update
|
||||
On February 22, LBRY CEO Jeremy Kauffman and Growth Director Natalie Mitchell gave a business focused presentation on LBRY and blockchain technology to a group of college students in Professor [Steven Gordon](http://www.babson.edu/Academics/faculty/profiles/Pages/gordon-steven.aspx)’s class at Babson College, a business school in Massachusetts. Natalie shared this feedback with the team:
|
||||
|
||||
"The presentation was really fantastic - which is to say, it turned into a conversation with the students, as well as some Babson faculty who were in attendance. All in attendance kept the very thoughtful questions flowing, which always makes for a fun time if you're the presenters! I'm happy to say that our time there sparked conversations with a few very bright minds who are interested in participating in our fledgling internship program, so that felt like a definite win.
|
||||
|
||||
The take-away, for me, was clear: Students of business/economics are taking note of what is happening in the blockchain space, and they want to be a part of it. Higher education is following suit, moving quickly to offer coursework to prepare future business leaders for the work of further progressing the decentralized business model. It is an understatement to say that this is an exciting time to be working in tech. I can't wait to see what these students, and others, will end up contributing to the space."
|
||||
|
||||
[Back to **Development Updates**](#dev-updates)
|
||||
|
||||
Thanks for supporting LBRY - stay tuned for more news and updates! And if you haven’t downloaded the [LBRY app](https://lbry.io/get?auto=1) yet, what are you waiting for?
|
||||
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: It’s Time To Liberate Anne Frank’s Diary
|
||||
date: '2015-11-18 14:27:39'
|
||||
cover: 'anne-frank-diary.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Free LBRY Credits: Come and Get ‘Em!'
|
||||
date: '2015-11-24 19:43:59'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Open a Valve to Gush Classic Movies
|
||||
date: '2015-12-02 19:04:36'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: GMU Economist Alex Tabarrok Joins LBRY
|
||||
date: '2015-12-07 17:33:37'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Web 3.0 with Albert K Lu: Movies, Songs, and Books with No Gatekeepers (Sorry iTunes)'
|
||||
date: '2015-12-09 16:38:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'BraveNewCoin Compares LBRY to Alexandria: Who Will Be the First to Supplant BitTorrent?'
|
||||
date: '2015-12-17 21:55:57'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: LBRY Blockchain App Can Now Tell Right From Wrong
|
||||
date: '2015-12-30 14:59:29'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Jack Robison Escaped 60 Years in Prison; Now He’s Revolutionizing the Internet
|
||||
date: '2015-12-31 17:10:59'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: LBRY Means Business With Addition of Josh Finer, MBA
|
||||
date: '2016-01-06 15:11:11'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY App Sneak Peak + Big Questions Answered - LBRY on #Blocktalk Last Night'
|
||||
date: '2016-01-15 19:17:12'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Try LBRY's Graphical Interface On OS X El Capitan
|
||||
date: '2016-01-23 00:15:31'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Wikimedia Forced to Remove Anne Frank's Diary
|
||||
date: '2016-02-12 19:21:53'
|
||||
cover: 'anne-frank-2.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'If LBRY Succeeds, Humanity Wins: LBRY CEO on Lions of Liberty Podcast'
|
||||
date: '2016-02-17 17:45:37'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: LBRY Exposes Itself to World; Adds Mad Scientist to Team
|
||||
date: '2016-03-02 18:12:13'
|
||||
cover: 'zargham-joins.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Why Doesn’t LBRY Just Use Bitcoin?
|
||||
date: '2016-03-17 13:31:10'
|
||||
cover: 'why-not-bitcoin2.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Built for Artists by Autists: LBRY Takes Autism Personally'
|
||||
date: '2016-03-21 20:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Information Gatekeepers Make Our Culture Sick'
|
||||
date: '2016-04-26 10:06:18'
|
||||
cover: 'gatekeepers.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: Bandcamp Is Cool & Growing – But They Still Take 15%
|
||||
date: '2016-05-06 12:11:11'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Tipping In LBC'
|
||||
date: '2016-05-12 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Apple Lost My Music!'
|
||||
date: '2016-05-20 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'BitTorrent’s New Streaming Service: Close but No Cigar'
|
||||
date: '2016-05-25 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'New Core Teammate Is An Ultimate Wizard: Meet Grin'
|
||||
date: '2016-06-07 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY’s Content Curator Is An Indie Kid Who Will Show You What’s Good'
|
||||
date: '2016-06-21 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Come and Get ‘Em! LBRY Credits Now Available to Mine'
|
||||
date: '2016-06-29 00:09:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'History Is Made - First Public Film Screenings via Blockchain at PorcFest XIII'
|
||||
date: '2016-06-30 00:09:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Beta Goes Live! A Declaration of Independence from Big Media'
|
||||
date: '2016-07-04 00:00:01'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Credits Listed on First Exchange! Liquidity Ensues!'
|
||||
date: '2016-07-06 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'The Mysterious 100K LBC Transaction: Revealed!'
|
||||
date: '2016-07-11 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Launch A Disaster'
|
||||
date: '2016-07-20 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Walking a Day in Venezuelan Shoes'
|
||||
date: '2016-07-26 00:09:18'
|
||||
cover: 'venezuela.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'You Can Now Publish on LBRY (& Earn $1,000)'
|
||||
date: '2016-08-04 00:09:00'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'ShapeShift Adds LBRY Credits! Instant Conversion to Bitcoin, Ethereum, and More'
|
||||
date: '2016-08-08 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Brings You the Fight of the Century'
|
||||
date: '2016-08-10 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Adult Swim's Million Dollar Extreme Joins LBRY'
|
||||
date: '2016-08-11 00:06:18'
|
||||
cover: 'mde.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Be Like Boba Fett – Earn Bounties for Helping LBRY Grow'
|
||||
date: '2016-08-18 00:06:18'
|
||||
cover: 'boba-fett.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Re-Weighting Massive Beta Waiting List'
|
||||
date: '2016-08-22 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'UI & Publishing Tools Upgrade with Reflector'
|
||||
date: '2016-08-25 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Kinda Sketchy, Totally Legit'
|
||||
date: '2016-08-26 00:06:18'
|
||||
cover: 'heckbendercover.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'NSFW: LBRY Bares All (Then Quickly Covers Up)'
|
||||
date: '2016-08-29 00:06:18'
|
||||
cover: 'nude.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Content Without Borders'
|
||||
date: '2016-08-31 00:06:18'
|
||||
cover: 'berlinwall.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: '#NewKidsOnTheBlockchain Thursday: Indie Rockers from Ukraine & Classical Singing de la Spain'
|
||||
date: '2016-09-01 00:06:18'
|
||||
cover: 'joaquin-pixan2.jpg'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: '$500K in VC Funds from Pillar et al'
|
||||
date: '2016-09-07 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY’s New Media Advisor: An Artist, A Businessman, A Gentleman'
|
||||
date: '2016-09-20 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Credit Policy and 3rd Quarter Credit Report'
|
||||
date: '2016-10-05 00:06:18'
|
||||
cover: 'lbry-3d-1000.png'
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
author: lbry
|
||||
author: samuel-lbryian
|
||||
title: 'Meet the Least Interesting Guy on the LBRY Team'
|
||||
date: '2016-10-10 00:06:18'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -138,6 +138,7 @@ class Controller
|
|||
'/art' => '/what',
|
||||
'/why' => '/learn',
|
||||
'/feedback' => '/learn',
|
||||
'/joinus' => '/join-us',
|
||||
'/faq/when-referral-payouts' => '/faq/referrals',
|
||||
'/faq/why-care-about-lbry' => '/get',
|
||||
'/news/meet-the-lbry-founders' => '/team',
|
||||
|
|
|
|||
|
|
@ -20,6 +20,7 @@ description:
|
|||
home: Meet LBRY, a content sharing and publishing platform that is decentralized and owned by its users.
|
||||
join: Follow along and receive updates about LBRY via email.
|
||||
learn: Learn more about LBRY, the technology that puts you back in control of the internet.
|
||||
meetup: LBRY is looking for ambassadors to spread the word to College campuses and Meetup groups worldwide!
|
||||
news: Access information and content in ways you never dreamed possible. Earn credits for your unused bandwidth and diskspace.
|
||||
no-os: Download or install the latest version of LBRY.
|
||||
press: LBRY Press Kit. Information and media for those who want to report on LBRY.
|
||||
|
|
@ -84,6 +85,7 @@ learn:
|
|||
explorer: Block Explorer
|
||||
how: Learn how LBRY will forever improve how we create and share with one another.
|
||||
join: Join Us
|
||||
contact: Contact Us
|
||||
nerd: Nerd Out
|
||||
rebels: Learn more about the relentless rebels changing the internet.
|
||||
team: About The Team
|
||||
|
|
@ -247,7 +249,7 @@ title:
|
|||
publish: Publish
|
||||
refer: Share and Earn
|
||||
what: "Art in the Internet Age: An Introduction to LBRY"
|
||||
meetup: Let LBRY Join Your Group
|
||||
meetup: Have LBRY Join Your Next Meetup!
|
||||
roadmap:
|
||||
title: LBRY Roadmap
|
||||
description: See past and future progress on development of LBRY, the world's first user-controlled digital marketplace.
|
||||
|
|
|
|||
8
dev.sh
8
dev.sh
|
|
@ -1,5 +1,7 @@
|
|||
#!/bin/bash
|
||||
|
||||
PHPBIN=php7.0
|
||||
|
||||
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
|
||||
|
||||
|
||||
|
|
@ -7,4 +9,8 @@ if [ ! -e "data/config.php" ]; then
|
|||
cp "$DIR/data/config.php.example" "$DIR/data/config.php"
|
||||
fi
|
||||
|
||||
php --server localhost:8000 --docroot "$DIR/web" "$DIR/web/index.php"
|
||||
if ! which $PHPBIN 2>/dev/null; then
|
||||
PHPBIN=php
|
||||
fi
|
||||
|
||||
$PHPBIN --server localhost:8000 --docroot "$DIR/web" "$DIR/web/index.php"
|
||||
|
|
|
|||
|
|
@ -13,4 +13,4 @@ docker run --rm -it --name "dev.lbry.io" \
|
|||
-p "127.0.0.1:8000:8000" \
|
||||
-u "$(id -u):$(id -g)" \
|
||||
php:7-alpine \
|
||||
php --server "0.0.0.0:8000" --docroot "web/" "index.php"
|
||||
php --server "0.0.0.0:8000" --docroot "web/" "web/index.php"
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ class Response
|
|||
$jsCalls = [],
|
||||
$assets = [
|
||||
'js' => [
|
||||
'/js/jquery-2.1.3.min.js',
|
||||
'/js/jquery-3.3.1.min.js',
|
||||
'/js/global.js'
|
||||
],
|
||||
'css' => ['/css/all.css']
|
||||
|
|
@ -32,7 +32,8 @@ class Response
|
|||
$contentSent = false,
|
||||
$isHeadersOnly = false,
|
||||
$gzipResponseContent = true,
|
||||
$metaImages = [];
|
||||
$metaImages = [],
|
||||
$facebookAnalyticsType = "PageView";
|
||||
|
||||
public static function setMetaDescription($description)
|
||||
{
|
||||
|
|
@ -365,6 +366,14 @@ class Response
|
|||
return $statusTexts[$code] ?? null;
|
||||
}
|
||||
|
||||
public static function setFacebookPixelAnalyticsType($type){
|
||||
static::$facebookAnalyticsType = $type;
|
||||
}
|
||||
|
||||
public static function getFacebookPixelAnalyticsType(){
|
||||
return static::$facebookAnalyticsType;
|
||||
}
|
||||
|
||||
protected static function normalizeHeaderName($name): string
|
||||
{
|
||||
return preg_replace_callback(
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@
|
|||
<h3 class="cover-title cover-title-tile cover-title-flat">I Have Questions</h3>
|
||||
<p>
|
||||
Have a big audience? Let Reilly know how we can support you
|
||||
by <a class="link-primary" href=mailto:reilly@lbry.io?subject=YouTube+Freedom">emailing him directly</a>.
|
||||
by <a class="link-primary" href=mailto:reilly@lbry.io?subject=YouTube+Freedom>emailing him directly</a>.
|
||||
</p>
|
||||
<form action="/youtube/sub" method="POST" class="spacer2">
|
||||
<?php echo View::render('form/_formRow', [
|
||||
|
|
@ -86,7 +86,7 @@
|
|||
]) ?>
|
||||
<input type="submit" value="Let's Talk" class="btn-primary">
|
||||
</form>
|
||||
<?php echo View::render('content/_bio', ['person' => 'reilly-smith-youtube']) ?>
|
||||
<?php echo View::render('content/_bio', ['person' => 'reilly-smith']) ?>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -145,7 +145,8 @@ $reward = LBRY::youtubeReward();
|
|||
<div class="inner">
|
||||
<div class="content">
|
||||
<h1>LBRY Credits and Your Channel</h1>
|
||||
<p>Be compensated for your value to your audience and the network, not what advertisers think you're worth.</p>
|
||||
<p>After you sync, receive LBRY Credits every month for one year based on your current subscriber count.</p>
|
||||
<p>The more you give to the network, the more it gives back.</p>
|
||||
<div class="price">
|
||||
<h3>Partner Programs</h3>
|
||||
<p>LBC <span class="current-value">(0.3267 USD)</span></p>
|
||||
|
|
|
|||
|
|
@ -16,18 +16,10 @@ h.end=i=function(){s.className=s.className.replace(RegExp(' ?'+y),'')};
|
|||
ga('require', 'GTM-NT8579P');
|
||||
ga('send', 'pageview');
|
||||
|
||||
<?php //we load fb sdk elsewhere, events loaded below (do we need both??) ?>
|
||||
!function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window,document,'script', 'https://connect.facebook.net/en_US/fbevents.js');
|
||||
|
||||
!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
|
||||
n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
|
||||
n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
|
||||
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
|
||||
document,'script','//connect.facebook.net/en_US/fbevents.js');
|
||||
|
||||
fbq('init', '1618717031725766');
|
||||
fbq('track', 'PageView');
|
||||
|
||||
<?php //and now everyone knows what happens on our website except us ?>
|
||||
fbq('init', '1618717031725766');
|
||||
fbq('track', '<?php echo Response::getFacebookPixelAnalyticsType() ?>');
|
||||
|
||||
</script>
|
||||
<?php else: ?>
|
||||
|
|
|
|||
3
view/template/mail/_contact-us.php
Normal file
3
view/template/mail/_contact-us.php
Normal file
|
|
@ -0,0 +1,3 @@
|
|||
<div class="spacer1">
|
||||
<a href="mailto:hello@lbry.io" class="link-primary"><span class="icon icon-envelope"></span><span class="btn-label">hello@lbry.io</span></a>
|
||||
</div>
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
<?php $error = $error ?? null ?>
|
||||
<?php $tag = $tag ?? null ?>
|
||||
<?php $largeInput = $largeInput ?? false ?>
|
||||
<form action="/list/subscribe" method="POST" novalidate>
|
||||
<form id="mail_form" action="/list/subscribe" method="POST" novalidate>
|
||||
|
||||
<?php if ($error): ?>
|
||||
<div class="notice notice-error spacer1"><?php echo $error ?></div>
|
||||
|
|
@ -19,5 +19,10 @@
|
|||
<?php if (!($hideDisclaimer ?? false)): ?>
|
||||
<div class="meta">{{email.disclaimer}}</div>
|
||||
<?php endif ?>
|
||||
<?php js_start() ?>
|
||||
$("#mail_form").submit(function() {
|
||||
fbq('track', 'Lead');
|
||||
});
|
||||
<?php js_end() ?>
|
||||
</div>
|
||||
</form>
|
||||
|
|
@ -8,19 +8,19 @@
|
|||
</div>
|
||||
<?php endforeach ?>
|
||||
<div class="control-item no-label-desktop">
|
||||
<a href="https://twitter.com/lbryio"><span class="btn-label">Twitter</span> <span class="icon-fw icon-twitter"></span></a>
|
||||
<a href="https://twitter.com/lbryio" target="_blank"><span class="btn-label">Twitter</span> <span class="icon-fw icon-twitter"></span></a>
|
||||
</div>
|
||||
<div class="control-item no-label-desktop">
|
||||
<a href="https://www.facebook.com/lbryio"><span class="btn-label">Facebook</span> <span class="icon-fw icon-facebook"></span></a>
|
||||
<a href="https://www.facebook.com/lbryio" target="_blank"><span class="btn-label">Facebook</span> <span class="icon-fw icon-facebook"></span></a>
|
||||
</div>
|
||||
<div class="control-item no-label-desktop">
|
||||
<a href="https://reddit.com/r/lbry"><span class="btn-label">Reddit</span> <span class="icon-fw icon-reddit"></span> </a>
|
||||
<a href="https://reddit.com/r/lbry" target="_blank"><span class="btn-label">Reddit</span> <span class="icon-fw icon-reddit"></span> </a>
|
||||
</div>
|
||||
<div class="control-item no-label-desktop">
|
||||
<a href="https://chat.lbry.io"><span class="btn-label">Discord</span><span class="icon-fw icon-comments"></span></a>
|
||||
<a href="https://chat.lbry.io" target="_blank"><span class="btn-label">Discord</span><span class="icon-fw icon-comments"></span></a>
|
||||
</div>
|
||||
<div class="control-item no-label-desktop">
|
||||
<a href="https://github.com/lbryio"><span class="btn-label">GitHub</span><span class="icon-github icon-fw"></span></a>
|
||||
<a href="https://github.com/lbryio" target="_blank"><span class="btn-label">GitHub</span><span class="icon-github icon-fw"></span></a>
|
||||
</div>
|
||||
<?php /*
|
||||
<div class="control-item no-label-desktop">
|
||||
|
|
|
|||
|
|
@ -15,9 +15,10 @@
|
|||
</table>
|
||||
<ul>
|
||||
<li><a href="/list/subscribe" class="link-primary"><?php echo __('email.subscribe') ?></a>.</li>
|
||||
<li>Join us on <a href="https://twitter.com/lbryio" class="link-primary"><span class="btn-label">Twitter</span><span class="icon icon-twitter"></span></a>,
|
||||
<a href="https://facebook.com/lbryio" class="link-primary"><span class="btn-label">Facebook</span><span class="icon icon-facebook"></span></a>,
|
||||
or <a href="https://reddit.com/r/lbry" class="link-primary"><span class="btn-label">Reddit</span><span class="icon icon-reddit"></span></a>.</li>
|
||||
<li>Join us on <a href="https://twitter.com/lbryio" target="_blank" class="link-primary"><span class="btn-label">Twitter</span><span class="icon icon-twitter"></span></a>,
|
||||
<a href="https://facebook.com/lbryio" target="_blank" class="link-primary"><span class="btn-label">Facebook</span><span class="icon icon-facebook"></span></a>,
|
||||
<a href="https://reddit.com/r/lbry" target="_blank" class="link-primary"><span class="btn-label">Reddit</span><span class="icon icon-reddit"></span></a>,
|
||||
<a href="https://chat.lbry.io" target="_blank" class="link-primary"><span class="btn-label">Discord</span><span class="icon-comments icon-fw"></span></a>.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="span6">
|
||||
|
|
@ -32,6 +33,9 @@
|
|||
<?php if (strpos(Request::getRelativeUri(), ContentActions::URL_NEWS) === false): ?>
|
||||
<li>Check out the latest <a href="/news" class="link-primary">news</a>.</li>
|
||||
<?php endif ?>
|
||||
<?php if (Request::getRelativeUri()!= '/faq'): ?>
|
||||
<li>Read our <a href="/faq" class="link-primary">Frequently Asked Questions</a>.</li>
|
||||
<?php endif ?>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
<?php Response::setMetaTitle(__('title.meetup')) ?>
|
||||
<?php echo View::render('nav/_header', ['isDark' => true, 'isAbsolute' => true]) ?>
|
||||
<main>
|
||||
<div class="cover cover-dark cover-center cover-full cover--dark-overlay" style="background-color:rgb(74, 175, 152)">
|
||||
<div class="cover cover-dark cover-center cover-full cover--dark-overlay" style="background-image: url(/img/table2.jpg)">
|
||||
<div class="content content-dark text-center">
|
||||
<h1 class="cover-title cover-title-tile cover-item--outline">
|
||||
Wanna Meet Up?
|
||||
|
|
|
|||
|
|
@ -70,35 +70,36 @@
|
|||
|
||||
|
||||
<h2 id="positions">Positions</h2>
|
||||
<em>If a position is marked paused, you are still welcome to contact us. For blockchain, protocol, and application engineers, we will be hiring regularly throughout 2018.</em>
|
||||
<div>
|
||||
<h3 id="blockchain-engineer">Blockchain Engineer <span class="badge badge-primary">Active</span></h3>
|
||||
<p>
|
||||
This position involves working directly on the LBRY <a href="https://github.com/lbryio/lbrycrd">blockchain</a>, written in C++.
|
||||
</p>
|
||||
<p>
|
||||
Competence with cryptography, security, and networks is mandatory. Experience with blockchain is beneficial but not required.
|
||||
</p>
|
||||
<p>
|
||||
Blockchain work is like being a goalkeeper: good work goes under-appreciated, but mistakes are catastrophic. You must be the kind of masochist that enjoys this.
|
||||
</p>
|
||||
<h3 id="protocol-engineer">Protocol Engineers <span class="badge badge-info">Paused</span></h3>
|
||||
<p>
|
||||
The LBRY protocol consists of a <a href="https://lbry.io/api">set of APIs</a> provided via a daemon. This daemon is comprised of several sub-components, and interacts with the blockchain, wallet, and other remote daemons that constitute the LBRY data network.
|
||||
</p>
|
||||
<p>
|
||||
The LBRY <a href="https://github.com/lbryio/lbry">daemon</a> and <a href="https://github.com/lbryio/lbryum">wallet</a> are both written in Python, but maybe you're the one to rewrite them in Go (we're kidding) (probably).
|
||||
</p>
|
||||
<p>Competence with security, operating systems, and networks is mandatory. Experience with peer-to-peer technology is beneficial but not required.</p>
|
||||
|
||||
<h3 id="blockchain-engineer">Blockchain Engineer</h3>
|
||||
<p>
|
||||
This position involves working directly on the LBRY <a href="https://github.com/lbryio/lbrycrd">blockchain</a>, written in C++.
|
||||
</p>
|
||||
<p>
|
||||
Competence with cryptography, security, and networks is mandatory. Experience with blockchain is beneficial but not required.
|
||||
</p>
|
||||
<p>
|
||||
Blockchain work is like being a goalkeeper: good work goes under-appreciated, but mistakes are catastrophic. You must be the kind of masochist that enjoys this.
|
||||
</p>
|
||||
<h3 id="protocol-engineer">Protocol Engineers</h3>
|
||||
<p>
|
||||
The LBRY protocol consists of a <a href="https://lbry.io/api">set of APIs</a> provided via a daemon. This daemon is comprised of several sub-components, and interacts with the blockchain, wallet, and other remote daemons that constitute the LBRY data network.
|
||||
</p>
|
||||
<p>
|
||||
The LBRY <a href="https://github.com/lbryio/lbry">daemon</a> and <a href="https://github.com/lbryio/lbryum">wallet</a> are both written in Python, but maybe you're the one to rewrite them in Go (we're kidding) (probably).
|
||||
</p>
|
||||
<p>Competence with security, operating systems, and networks is mandatory. Experience with peer-to-peer technology is beneficial but not required.</p>
|
||||
|
||||
<h3 id="web-developer">Web Developer</h3>
|
||||
<p>
|
||||
We're seeking someone to manage <a href="https://github.com/lbryio/lbry.io">this very website</a>, as well as other LBRY web properties and projects.
|
||||
</p>
|
||||
<p>
|
||||
This position involves both design and programming elements and is good for someone with a mix of creativity and logic.
|
||||
The LBRY website currently uses a moderate amount of PHP, but you be the product owner and have full control over the implementation.
|
||||
</p>
|
||||
|
||||
<h3 id="web-developer">Web Developer <span class="badge badge-info">Paused</span></h3>
|
||||
<p>
|
||||
We're seeking someone to manage <a href="https://github.com/lbryio/lbry.io">this very website</a>, as well as other LBRY web properties and projects.
|
||||
</p>
|
||||
<p>
|
||||
This position involves both design and programming elements and is good for someone with a mix of creativity and logic.
|
||||
The LBRY website currently uses a moderate amount of PHP, but you be the product owner and have full control over the implementation.
|
||||
</p>
|
||||
</div>
|
||||
<h2 id="applying">Applying</h2>
|
||||
<h4 id="how-to-apply">How To Apply</h4>
|
||||
<p>
|
||||
|
|
@ -135,7 +136,7 @@
|
|||
<tr>
|
||||
<td><a href="https://github.com/lbryio/lbry-app">lbry-app</a></td>
|
||||
<td>Application or UX Engineer</td>
|
||||
<td><a href="https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issues</a> <em>(coming 1/17)</em></td>
|
||||
<td><a href="https://github.com/lbryio/lbry-app/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issues</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="https://github.com/lbryio/lbrycrd">lbrycrd</a></td>
|
||||
|
|
|
|||
|
|
@ -57,8 +57,11 @@
|
|||
<div class="content content-dark content-tile">
|
||||
<h3>{{learn.join}}</h3>
|
||||
<?php echo View::render('social/_list') ?>
|
||||
<h3>{{learn.contact}}</h3>
|
||||
<?php echo View::render('mail/_contact-us') ?>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</main>
|
||||
|
||||
</main>
|
||||
<?php echo View::render('nav/_footer') ?>
|
||||
|
|
|
|||
34
view/template/page/meet.php
Normal file
34
view/template/page/meet.php
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
<?php Response::setMetaDescription(__('description.meetup')) ?>
|
||||
<?php Response::setMetaTitle(__('title.meetup')) ?>
|
||||
<?php echo View::render('nav/_header', ['isDark' => true, 'isAbsolute' => true]) ?>
|
||||
<main>
|
||||
<div class="cover cover-dark cover-center cover-full cover--dark-overlay" style="background-image: url(/img/table2.jpg)">
|
||||
<div class="content content-dark text-center">
|
||||
<h1 class="cover-title cover-title-tile cover-item--outline">
|
||||
Wanna Meet Up?
|
||||
</h1>
|
||||
<h3 class="cover-item--outline">
|
||||
LBRY is looking for ambassadors to spread the word to College campuses and Meetup groups worldwide!
|
||||
</h3>
|
||||
<div class="spacer1">
|
||||
<a href="#about" class="btn-primary btn-large">Tell Me More!</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="cover cover-light" id="about">
|
||||
<div class="content content-light content-readable">
|
||||
<h3>Interested in bringing LBRY to your local college campus or Meetup group?</h3>
|
||||
<p> We're looking for folks to demonstrate our platform and latest technologies. What's in it for you? We'll provide you with LBRY credits for your group, LBRY swag, and presentation resources.</p>
|
||||
<h3>Okay. How do I get involved?</h3>
|
||||
<p>Enter your email below and we'll tell you more.</p>
|
||||
<?php echo View::render('mail/_subscribeForm', [
|
||||
'tag' => 'meetup',
|
||||
'submitLabel' => 'Sign me up',
|
||||
'hideDisclaimer' => true,
|
||||
'largeInput' => true,
|
||||
'btnClass' => 'btn-alt btn-large',
|
||||
]) ?>
|
||||
</div>
|
||||
</div>
|
||||
</main>
|
||||
<?php echo View::render('nav/_footer') ?>
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue