Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0940c6784f | ||
|
|
2530d21d9d | ||
|
|
c2e46bb10b | ||
|
|
77328449a1 | ||
|
|
60351d6a16 | ||
|
|
266d830831 | ||
|
|
80270c2e50 | ||
|
|
23ffee8dbd | ||
|
|
6485d78a04 | ||
|
|
66f0c08ec8 | ||
|
|
b181563aba | ||
|
|
4840f17f05 | ||
|
|
ed8fec9c4d | ||
|
|
f039ddf660 | ||
|
|
94e1402b7a | ||
|
|
14eb953d72 | ||
|
|
2dbfb53492 | ||
|
|
6295825f81 | ||
|
|
5659461d96 | ||
|
|
deee6623a0 | ||
|
|
5a26a43eb9 | ||
|
|
519ca5eb26 | ||
|
|
2f7aa6dc2d | ||
|
|
6a87546d8d | ||
|
|
141b20ad5d | ||
|
|
cde8adc715 | ||
|
|
9fa46b2536 | ||
|
|
b126d8579a | ||
|
|
91659a77b6 | ||
|
|
085fe86189 | ||
|
|
bb2279ba08 | ||
|
|
cc293e19bf | ||
|
|
90174c793f | ||
|
|
27f2910f7f | ||
|
|
6733cea0a2 | ||
|
|
4853adb114 | ||
|
|
af55e553ac | ||
|
|
c90459b406 | ||
|
|
16936bc759 | ||
|
|
970ec88e26 | ||
|
|
1f277c22e2 | ||
|
|
192a2e11a8 | ||
|
|
9420247ed0 | ||
|
|
86aa85aeac | ||
|
|
ad4e25db21 | ||
|
|
f95856f198 | ||
|
|
5238e52575 | ||
|
|
00fa2329ee | ||
|
|
a5c6c4da2b | ||
|
|
076962dae1 | ||
|
|
d387e259d7 | ||
|
|
cd3f0e1190 | ||
|
|
5898f6c838 | ||
|
|
4a3fabf2fd | ||
|
|
fecc4d1308 | ||
|
|
ec9825a856 | ||
|
|
d7f62b1b24 | ||
|
|
d3af4a1729 | ||
|
|
5e73137d7e | ||
|
|
1a82b1f19f | ||
|
|
2346f7e0c6 | ||
|
|
2fd620ff50 | ||
|
|
1464fb94a6 | ||
|
|
f4d6908b2c | ||
|
|
1fd49428a6 | ||
|
|
8f696da5b5 | ||
|
|
cc4e21f381 | ||
|
|
e0e4eb7104 | ||
|
|
7a42856d32 | ||
|
|
fbbba49d24 | ||
|
|
6bbb8c426b | ||
|
|
c2546a6f81 | ||
|
|
9a070c7b3f | ||
|
|
1bc15aad39 | ||
|
|
e453bca309 | ||
|
|
b2184866f2 | ||
|
|
aec94f6380 | ||
|
|
40748f7726 | ||
|
|
34277316c7 | ||
|
|
161c878d49 | ||
|
|
9fb4d0bcc3 | ||
|
|
239692e90b | ||
|
|
ce438ce16a | ||
|
|
1cb87f3b1b | ||
|
|
d7f20e6827 | ||
|
|
5e5e7d4ab7 | ||
|
|
0dfeec9e82 | ||
|
|
666ecd57ab | ||
|
|
e6255f8b2a | ||
|
|
63726f19d3 | ||
|
|
00ff968546 | ||
|
|
5d25014536 | ||
|
|
188463e86b | ||
|
|
1b043683b4 | ||
|
|
ab371f0c5e | ||
|
|
1ce00e6c12 | ||
|
|
c22487b710 | ||
|
|
33a1a91fac | ||
|
|
dba257bef8 | ||
|
|
0f821a004c | ||
|
|
70ef9ac884 | ||
|
|
aa665db0b6 | ||
|
|
0661d9b0f0 | ||
|
|
7b8a0cdc65 | ||
|
|
35243efdc8 | ||
|
|
1a29e40318 | ||
|
|
f40ce4a86c | ||
|
|
3f90ea07b4 | ||
|
|
ac37f8e49c | ||
|
|
06738ed3b1 | ||
|
|
00f7bfc251 | ||
|
|
d48aad8426 | ||
|
|
7adcd311bf | ||
|
|
2b9c406294 | ||
|
|
f172a9b139 | ||
|
|
fb98609613 | ||
|
|
e8b69b9584 | ||
|
|
0204dd043a | ||
|
|
94053443be | ||
|
|
250ab48126 | ||
|
|
08c62fa845 | ||
|
|
401887492c | ||
|
|
8bbe6e63ee | ||
|
|
67579fa537 | ||
|
|
46ccd5ffaa | ||
|
|
dd16f21da3 |
No files matched your search
@@ -5,11 +5,14 @@
|
||||
"ext-curl": "*",
|
||||
"ext-mbstring": "*",
|
||||
"ext-xml": "*",
|
||||
"ext-pdo": "*",
|
||||
"ext-pdo_mysql": "*",
|
||||
"ext-json": "*",
|
||||
"leafo/scssphp": "0.7.6",
|
||||
"erusev/parsedown": "^1.6",
|
||||
"erusev/parsedown-extra": "^0.7.1",
|
||||
"pelago/emogrifier": "^2.0",
|
||||
"mustangostang/spyc": "^0.6.2",
|
||||
"phpunit/phpunit": "^6.5"
|
||||
"paquettg/php-html-parser": "^2.1"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
name: Julie Sigwart
|
||||
role: Community Manager
|
||||
email: Julie@lbry.com
|
||||
twitter: jsigwart
|
||||
github: jsigwart
|
||||
---
|
||||
|
||||
Julie brings a unique background including a long history of software development, is a cartoonist, and is also a First Amendment champion. In 1988, the Hustler v. Falwell ruling was a major event in free speech history and has been a major influence for her. As an editorial cartoonist, she appreciates the gravity of that ruling to protect free speech, including speech that may be unpopular. In the early 2000’s, she founded Take Back the Media, a website dedicated to calling out mainstream news media for bias, omissions, and factual inaccuracies. Aside from receiving death threats (another consequence associated with free speech), Julie and Take Back The Media were sued in a SLAPP (Strategic Lawsuit Against Public Participation designed to chill free speech) for publishing contested information involving Michael Savage, Roy Masters, and Talk Radio Network. Ultimately, the lawsuit was withdrawn by the plaintiff, but it set Julie on a course to assist others who have been targeted in SLAPP suits attempting to shut down their free speech.
|
||||
|
||||
She is also a veteran of the dotcom era, including managing internet communities for Metacreations Corp, including support forums, gaming forums, and general chat support. She has also worked on and supported Metacreations Corp software titles like Kai’s Power Tips, Kai’s Power Tools, Kai’s Power Photos, and Stephen Hawking’s Life in the Universe product website.
|
||||
@@ -53,9 +53,9 @@ The LBRY Android App comes with its own wallet and is stored locally on your pho
|
||||
|
||||
If you do not opt for the [wallet sync program](https://lbry.com/faq/how-to-backup-wallet#sync), it is critical that you backup your own wallet locally or else the credits will be lost.
|
||||
|
||||
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to `Discovery`. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance and recent transactions.
|
||||
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to the Search bar. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance and recent transactions.
|
||||
|
||||

|
||||

|
||||
|
||||
### Where Do I Find My LBC Wallet Address?
|
||||
|
||||
@@ -66,52 +66,55 @@ Scroll down in the Wallet menu to find recent transactions, or click `View All`
|
||||
|
||||

|
||||
|
||||
The LBRY wallet is different from other wallets - it also stores your shared content's metadata in the form of [claims](/faq/naming) when using the [publishing features](/faq/how-to-publish).
|
||||
The LBRY wallet is different from other wallets - it also stores your shared content's metadata in the form of [claims](/faq/naming) when using the publishing features.
|
||||
|
||||
### How do I Publish content? {#publish}
|
||||
|
||||
1. Tap on the 3 horizontal bars on the upper left side of the app next to the Search bar.
|
||||
|
||||
2. Select the option for `New publish`
|
||||
|
||||

|
||||
|
||||
3. Choose the option for publishing your content either by recording a live video, taking a picture or picking a file from your gallery.
|
||||
|
||||
![Choose an option]https://spee.ch/4/chooses.png)
|
||||
|
||||
4. Enter a `Title` and `Description` for your content.
|
||||
|
||||
5. Next you can add tags to your content which will help categorize it for [discovery purposes](https://lbry.com/faq/trending). If it's intended for mature audiences, please add the pink `mature` tag. Next, determine any other tags that relate to the content you are publishing. Please be mindful of accuracy when tagging content as this is currently up to the publisher only and cannot be edited. If incorrect/inappropriate tags are used, your content may be filtered to provide a better user experience. In the future, this will be done through community voting and building a web of trust.
|
||||
|
||||

|
||||
|
||||
6. You have the option to select/create the channel you would like to publish the content under. If no channel is selected, it will be posted anonymously.
|
||||
|
||||

|
||||
|
||||
7.Under the `Price`, first, determine if you want to make your content free or set a price in LBC per view.
|
||||
|
||||
8. Type in the URL you want the content to be found under, along with a minimum of 0.00000001 LBC deposit for the upload (default amount is higher due to publishing fees). 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. Making your bid higher will result in (better discovery)[https://lbry.com/faq/trending) for your content. For more details regarding the URL or bid, check out our [naming document](/faq/naming).
|
||||
|
||||

|
||||
|
||||
|
||||
|
||||
9. Next, there is `Show extra fields` which gives you an option to select language and license. Default language is set to `English`, and the License is set to `None`. If a change is needed, click the dropdown menus and select the appropriate choice.
|
||||
|
||||
*please review our terms of service before publishing [terms of service](/termsofservice)
|
||||
|
||||
Click `Publish`.
|
||||
|
||||
The file will process in the background and will be added to the LBRY Blockchain. It is a good idea to leave LBRY open for a while after this to make sure the app is able to share your file to at least one peer on the data network. Larger files will take longer to upload depending on your network speed.
|
||||
|
||||
|
||||
Claim related [wallet transactions](/faq/transaction-types) ensure that the blockchain uniquely identifies your content and the payment/tips can be routed appropriately.
|
||||
|
||||
### How Do I Claim Weekly LBRYcast Rewards In The Android App? {#lbrycastrewards}
|
||||
### How Do I Claim Rewards In The Android App? {#rewards}
|
||||
|
||||
1. On the Discover page, Play/Download any of the first 10 videos with the badge icon on it.
|
||||
|
||||

|
||||
|
||||
2. After clicking on the video to play/download, the reward should be claimed automatically. If not, go into the Menu > Rewards and you will see the LBRY cast reward on the first. Tap the round circle to claim your reward.
|
||||
|
||||

|
||||
|
||||
To claim any other reward, you just have to click on the round circle next to the reward to claim.
|
||||
|
||||

|
||||
You'll receive daily random rewards just for watching the videos you love! All you need to do is open your LBRY app and start watching. Comeback everyday for a different reward.Incase for some reason the reward does not show up in your wallet after watching a video everyday, go to rewards and click on the daily rewards.
|
||||
|
||||
To check whether your wallet is updated, you need to swipe your screen to show the menu bar, click on Wallet and you will see your overall updated balance. Check [How to Backup Your Wallet](/faq/how-to-backup-wallet)
|
||||
|
||||
### How Do I Delete Downloaded Content In The LBRY Android App? {#deletecontents}
|
||||
|
||||
To delete any content downloaded, you first need to open the content.
|
||||
To find where the Downloaded contents are:
|
||||
|
||||
1. Swipe your phone screen from left to right to reveal the menu.
|
||||
|
||||

|
||||
|
||||
2. Tap on `My LBRY`, Depending on the contents you have downloaded/watched it should come up like this with the stats of how much
|
||||
storage the contents have consumed:
|
||||
|
||||

|
||||
|
||||
3. Tap the content you would like to delete and then once it's open, you should see a trash can icon.
|
||||
|
||||

|
||||
|
||||
Click on the bin icon and confirm deletion if you still want to delete the content.
|
||||
|
||||

|
||||
|
||||
Right after the content is deleted, you should see the same content showing on the app screen, if you click on it, it will start the download again.
|
||||
|
||||
To delete additional content, please follow the same steps until you delete all the contents you do not need on your phone. We'll be improving this to allow for easier deletion multiple content at the same time.
|
||||
|
||||
### How Do I Enable Background Media Playback? {#backgroundmediaplayback}
|
||||
|
||||
When playing anything on the LBRY android app, it will stop playing when you minimize the app or switch to another application. Since we aren't YouTube and won't make you pay for subscription to enable background media playback, you can enable this feature in the app settings.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: Has LBRY received any secret government subpoenas? Does LBRY have a warrant canary?
|
||||
category: other
|
||||
---
|
||||
Unfortunately, the nature of _secret_ subpoenas means they have to be kept secret. Fortuantely, LBRY maintains a warrant canary, viewable at:
|
||||
|
||||
[https://lbry.com/canary](https://lbry.com/canary)
|
||||
|
||||
For more on warrant canaries and how they work, check out this [Wikipedia article](https://en.wikipedia.org/wiki/Warrant_canary).
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: What is censorship resistance and how does it apply to LBRY?
|
||||
category: publisher
|
||||
order: 3
|
||||
---
|
||||
|
||||
## What is censorship-resistance?
|
||||
At the risk of tautology, censorship-resistance is the ability to resist censorship. Less tautologically, censorship-resistance is the degree to which a system is tamper proof. That is, a censorship-resistant system means a third party cannot modify or remove content created by someone else.
|
||||
|
||||
Just as nothing in the world is theft proof, nothing in the world is censorship proof. When a bank builds twenty foot walls around a vault with 3-foot-thick steel door that is monitored by security cameras, it does not do so to make theft literally impossible. It does so to make theft of the goods inside sufficiently challenging that it is extraordinarily improbable. When we speak of censorship-resistance, we speak the same as of the bank vault. A system can never be literally censorship proof, but it can be made extremely censorship resistant.
|
||||
|
||||
So when speaking of censorship resistance with regards to LBRY, we are speaking about how challenging it is to modify or remove content from the LBRY network without permission from the publisher
|
||||
|
||||
## How censorship-resistant is LBRY?
|
||||
|
||||
We believe LBRY to be the most censorship-resistant system to ever exist for the purposes of publishing digital content.
|
||||
|
||||
To understand where LBRY’s censorship resistance comes from, we need to break the problem down into two areas: data (the digital content) and metadata (information about the digital content, such as it’s title or publisher).
|
||||
|
||||
In the case of the data itself, LBRY is as or more censorship-resistant as BitTorrent or other peer-to-peer networks. Like these other networks, when you publish a file, it ends up being hosted by dozens, hundreds, or thousands of other computers, depending on its popularity. Additionally, there are economic incentives to host content that is popular but undersupplied, which means that LBRY is even better than its predecessors, which were already world leaders in the censorship-resistance department.
|
||||
|
||||
In the case of the metadata, LBRY is truly novel. Previous peer-to-peer systems had decent censorship-resistance at the data level, but never the metadata. LBRY writes it’s metadata to a public blockchain, the same technology that powers the censorship-resistant Bitcoin. Metadata in the LBRY blockchain cannot be altered without a hard-fork of the network, which is an expensive and unlikely proposition. Even if this happened, it would be possible to roll-back the system to it’s last previously good state, resulting in only a temporary rather than permanent data loss.
|
||||
|
||||
## How could LBRY be censored?
|
||||
|
||||
An internet service provider or network operator could conceivably censor traffic to the LBRY network entirely, by blocking or dropping packets that appear to be part of the LBRY protocol. However, given that this traffic is typically encrypted, consists of otherwise ordinary TCP and UDP packets, and can be headed to or from basically any address on the internet, this would be fairly challenging.
|
||||
|
||||
If a network operator did find a way to block LBRY traffic at the network level, we would work tirelessly to continue to evolve the system to make this difficult or impossible.
|
||||
|
||||
## Why does censorship-resistance matter?
|
||||
|
||||
Censorship-resistance matters because there are many people in the world who would like to stop others from speaking. This can range in scale from national governments (China, North Korea, Iran) to college campuses (Evergreen).
|
||||
|
||||
Prosperity and freedom starts with the ability for people to communicate freely with one another. The ability to censor is the ability to control the narrative and spread propaganda.
|
||||
|
||||
For the purposes of discovering truth and fighting injustice, censorship-resistance is absolutely vital.
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: How does LBRY disclose its usage of LBC?
|
||||
category: other
|
||||
---
|
||||
|
||||
LBRY issues regular reports outlining its transaction history as well as the current state of LBRY, Inc.'s balance sheet and anticipated future expenditures.
|
||||
|
||||
### How do I view the reports?
|
||||
|
||||
The reports are publicly available on the [Credit Reports page](https://lbry.com/credit-reports). When a new report is issued, we post a link to our official Twitter. They are also usually mentioned in a community email message, though not as promptly. You can join our mailing list here.
|
||||
|
||||
### When are reports issued?
|
||||
|
||||
Reports are issued every 3 months in January, April, July, and October, covering the preceding 3 full months. There is no specific day within the month that the reports are issued, though we try to get them out promptly.
|
||||
|
||||
### Are the reports financial advice? Are they legally binding?
|
||||
The reports are not official or legal financial disclosures, nor do they formally or legally bind the company in any way. They are an attempt by us to provide transparency about our usage of LBC.
|
||||
|
||||
LBRY Inc. does not commit to following predictions made in the reports and reserves full rights to change how it uses LBC at any time.
|
||||
|
||||
### What happens if the reports contain a mistake?
|
||||
If we issue a report that was factually mistaken, we will update the report with a correction. If the mistake is caught within the same month that it was issued and was not substantial, the report will be updated without a notification other than a reply to the original Tweet.
|
||||
|
||||
If an error is noticed in the report outside of the month it was issued or the error was substantial, then we will publish a blog post and a separate Tweet announcing the correction, as well as leave a note in the report itself linking to the blog post explaining the mistake.
|
||||
@@ -7,7 +7,7 @@ We are listed on several exchanges. You can buy or sell LBRY Credits at one of t
|
||||
|
||||
### Traditional Exchanges
|
||||
- [Bittrex](https://bittrex.com/Market/Index?MarketName=BTC-LBC)
|
||||
- [Poloniex](https://poloniex.com/exchange#btc_lbc)
|
||||
- [Poloniex](https://poloniex.com/exchange#btc_lbc) (Currently in maintenance, working with Poloniex team to fix)
|
||||
- [Upbit](https://upbit.com/exchange?code=CRIX.UPBIT.BTC-LBC)
|
||||
- [Instant Bitex](https://instantbitex.com)
|
||||
- [Coinspot](https://www.coinspot.com.au/buy/lbc)
|
||||
@@ -15,7 +15,7 @@ We are listed on several exchanges. You can buy or sell LBRY Credits at one of t
|
||||
|
||||
### Instant Exchanges
|
||||
- [Shapeshift](https://shapeshift.io) (Currently unavailable, ShapeShift working on it. Requires free membership account now)
|
||||
- [Changelly](https://changelly.com/exchange/BTC/LBC/1)
|
||||
- [Changelly](https://changelly.com/exchange/BTC/LBC/1) (Currently unavailable)
|
||||
- [ChangeNow](https://changenow.io/exchange?amount=1&from=btc&to=lbc)
|
||||
- [Simple Swap](https://simpleswap.io)
|
||||
- [Stealthex](https://stealthex.io/)
|
||||
|
||||
@@ -9,4 +9,7 @@ While the LBRY app is running, it communicates to the network whatever content y
|
||||
|
||||
Think of it like how torrents or any other peer-to-peer (P2P) service works. First, you download a file from the host(s) that have made it available via seeding. When the download has finished, you become a host in the network (seeder) that other people can download from.
|
||||
|
||||
### Deleting hosted content
|
||||
You can delete files from the blob folder directly, or you can also delete them from the My LBRY section of the App - both will get rid of the hosted content and you'll lose the ability to seed it anymore.
|
||||
|
||||
**Please note: Hosting fees are currently disabled on the network as we're currently working on a better way to implement the fee structure.**
|
||||
@@ -5,6 +5,8 @@ category: troubleshooting
|
||||
|
||||
In certain cases, we may ask you to send us your log file(s). The current log file is titled `lbrynet.log` (or just `lbrynet` if you have file extensions hidden) and is archived each time the files reaches 2MB. Older log files are copied to `lbrynet.log.<#>`. Typically only the lbrynet.log file is required, but we may ask for the others depending on the situation. Since each Operating System has its own set of working directories, use the below guide in order to locate the log file(s).
|
||||
|
||||
[Find my logs without opening the app](#manual)
|
||||
|
||||
**lbrynet.log files may contain your IP address. While sharing this is not inherently dangerous, if you desire maximum privacy, please mask it before posting to public websites.**
|
||||
|
||||
### Find Logs via the LBRY App
|
||||
@@ -16,24 +18,24 @@ The folder will be highlighted, so just double click to open and here you will s
|
||||
### Sending log files from Android
|
||||
Navigate to the **About** page and use the **Send Logs** button at the bottom. You can email them to [help@lbry.com](mailto:help@lbry.com)
|
||||
|
||||
### Find Logs Manually
|
||||
## Windows
|
||||
### Find Logs Manually {#manual}
|
||||
#### Windows
|
||||
1. Open File Explorer (Keyboard shortcut: Windows Key + E).
|
||||
2. Type `%localappdata%\lbry\lbrynet` (or `%appdata%\lbrynet` if you originally installed v0.14 or earlier) into the address bar and click Enter.
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## MacOS
|
||||
#### MacOS
|
||||
1. Open Finder.
|
||||
2. Click Go in the top menu and choose "Go To Folder".
|
||||
3. Type "~/Library/Application Support/LBRY" and then click go.
|
||||
4. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## Ubuntu / Linux *(Exact steps may differ slightly)*
|
||||
#### Ubuntu / Linux *(Exact steps may differ slightly)*
|
||||
1. Navigate to your home directory. Ensure hidden files and folders are shown if using a graphical file explorer.
|
||||
2. Navigate to the `.local/share/lbry/lbrynet` folder (or `~/.lbrynet` if you originally installed v0.14 or earlier).
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## Android *(Exact steps may differ slightly)*
|
||||
#### Android *(Exact steps may differ slightly)*
|
||||
1. Launch your favorite file explorer.
|
||||
2. Navigate to `Internal storage\android\data\io.lbry.browser->files\lbrynet`.
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How do I get LBRY for development?
|
||||
title: How do I install LBRY for development and contributing?
|
||||
category: powerusers
|
||||
---
|
||||
|
||||
|
||||
@@ -19,7 +19,9 @@ If you don't have LBRY yet, download it [here](/get).
|
||||
|
||||
2. Under the `Publish` section, click `Choose File`.
|
||||
|
||||
3. On your local machine, select the content you wish to upload to LBRY. LBRY accepts any HTML5 format for video streaming; the full list can be found [here](https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats). This means a web-optimized MP4 file is the best format. Other file types can also be uploaded, but won't be streamable via the LBRY app.
|
||||
3. On your local machine, select the content you wish to upload to LBRY. For video content, LBRY works best with MP4 files in H264/AAC format which support proper streaming. Besides videos, other popular formats supported are MP3s, text documents like markdown (md)/HTML, PDF, CSV, and comic books (cbr, cbz). In the future, the in app player may support additional formats.
|
||||
|
||||
Other file types can also be uploaded, but won't be streamable via the LBRY app directly. They can be opened externally for viewing.
|
||||
|
||||
4. Enter a `Title` and `Description` for your content. Click on advanced Editor if you will like to add some markdown text otherwise leave it as default and put your title and description.
|
||||
|
||||
@@ -119,7 +121,7 @@ In the future, we will add more of these types of statistics to LBRY.
|
||||
|
||||
### My video doesn't stream in the app, what's wrong?
|
||||
|
||||
The in-app video player's streaming capabilities are limited to MP4 files which are web-optimized (metadata is contained at the front of the file). If it's not web-optimized, the MP4 file will still play in the app, but the entire file will need to be downloaded first. AVI/WMV/MOV file formats are also not supported by the in-app player. They can be shared/downloaded but will need to be played externally.
|
||||
The in-app video player's streaming capability works best with the H264/AAC format, typically in a MP4 container but others like M4V will also work. Other non-streaming video types like AVI/WMV/MOV file formats are not supported by the in-app player, but they can be shared/downloaded and will play outside of the app.
|
||||
|
||||
### I shared my URL, but others can't download it. What's going on?
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: How do I remove my account?
|
||||
category: troubleshooting
|
||||
order: 5
|
||||
---
|
||||
|
||||
Account deletion is a manual process at this time. If you'd to proceed with account removal, please [email us at hello@lbry.com](mailto:hello@lbry.com). You can then uninstall your LBRY application. Any LBC and downloaded content you may have had will persist on your device, see our [directories FAQ](https://lbry.com/faq/lbry-directories) to find these locations.
|
||||
|
||||
Please note: If you have earned Rewards on your email address, we'll put your email into a dormant state and you'll never hear from us (all other data deleted). Otherwise, it will be completely removed.
|
||||
@@ -60,6 +60,9 @@ Please refer to our [publishing guide](/faq/how-to-publish) as a reference to as
|
||||
### Where can I see my Downloadeds?
|
||||
The downloaded contents can be found on the rightside of the LBRY app under Library.
|
||||
|
||||
### How can I delete my Downloads?
|
||||
The downloaded contents can be found on the rightside of the LBRY app under Library. Select the item you want to delete, and then click the trash can icon on the file page. We'll be introducing batch deletion options in the near future.
|
||||
|
||||
### Where can I see my Publishes?
|
||||
You can find published items under Publishes on the right side of the LBRY app.
|
||||

|
||||
|
||||
@@ -8,7 +8,7 @@ The very first question of newcomers is often, "How do you pronounce it?" Answer
|
||||
|
||||
"Is it an acronym?" No.
|
||||
|
||||
"Then why confuse people with the all-caps and no vowels?"
|
||||
"Then why confuse people with the all-caps and removed vowels?"
|
||||
|
||||
First and foremost, LBRY is an internet protocol, just like HTTP. Content on LBRY is served to users via "LBRY names," which look like this: lbry://itsawonderfullife. Very similar to the URL you type into your internet browser. LBRY is not just our branded name, but the character string we've chosen to lead our URIs (Uniform Resource Identifier).
|
||||
|
||||
|
||||
@@ -0,0 +1,71 @@
|
||||
---
|
||||
title: How does LBRY handle privacy? What data does LBRY collect?
|
||||
category: LBRY 101
|
||||
order: 5
|
||||
---
|
||||
|
||||
LBRY takes privacy seriously and carefully considers the data it collects.
|
||||
|
||||
|
||||
Our official privacy policy is viewable at https://lbry.com/privacypolicy. This FAQ article attempts to explain our policy in plain English, but should not be considered an official policy document.
|
||||
|
||||
LBRY collects data for a variety of reasons, including but not limited to:
|
||||
- debugging and improving the protocol
|
||||
- understanding how our users interact with our applications
|
||||
- preventing fraud in our reward programs
|
||||
- providing statistics to content creators
|
||||
|
||||
We promise to keep any collected data safe and to never share personal, private information with anyone outside of LBRY Inc.
|
||||
|
||||
Users can also [choose to use LBRY anonymously](#anonymous) however some features, like [LBRY Rewards](https://lbry.com/faq/rewards), will not be available.
|
||||
|
||||
Additionally, even when not sending data to us, using LBRY typically involves participation in the peer-to-peer LBRY network and certain information like your IP address is likely to be exposed regardless. See [below](#p2p) for more information.
|
||||
|
||||
### What type of data is collected and where?
|
||||
As a first time user of LBRY applications, you have the option of providing an email address to create a LBRY account. This allows for a richer user experience by enabling services such as [LBRY Rewards](https://lbry.com/faq/rewards), email notifications, and account synchronization (i.e. subscriptions and user preferences) across multiple devices/platforms. If you do not provide an email, any data collected cannot be associated with your identity, but may still be tied back to other system information like IP addresses.
|
||||
|
||||
See below tables for a break-down of the types of data collected and associated applications.
|
||||
|
||||
Scope of Data | Depends on| Optional | Visibility | Details
|
||||
:------------ |:------------ |:------------ |:------------ |:------------ |
|
||||
Email addresses | | Yes, if email provided | LBRY | Used to create and authenticate a LBRY account
|
||||
User preferences | Email | Yes, if email provided | LBRY | Subscriptions, tags, blocked channels, and application settings
|
||||
System information | | Yes, if Share Diagnostic Data enabled | LBRY | Operating system, application/SDK versions, and unique install identifier
|
||||
Identity verification | Email | Yes, if going through manual approval | LBRY | Phone number, credit card fingerprint (Stripe), and 3rd party services identifiers (i.e. YouTube, GitHub)
|
||||
Google Analytics | | Yes, if Share Diagnostic Data enabled | LBRY | User behavior and interactions within the applications are tracked anonymously. This is not linked to a LBRY account.
|
||||
Content access analytics | Email | Yes, if email provided | LBRY | Content views used for Rewards and internal analytics
|
||||
IP addresses | | No, use VPN to protect | Everyone | Any access to LBRY services are logged to prevent abuse and comply with legal requirements
|
||||
Blockchain metadata | Email | Yes, if email provided | LBRY| Wallet addresses and transactions related to Rewards are logged to prevent abuse and comply with tax requirements (above $600 yearly threshold)
|
||||
Blockchain transactions | | No, don’t create transactions | Everyone | Any actions taken that use LBRY credits and create a permanent transaction on the blockchain. Not linked to any Account/User data.
|
||||
|
||||
Scope of Data | LBRY Desktop App | LBRY.tv (Web) | LBRY Android App | LBRY SDK |
|
||||
:------------ |:------------ |:------------ | :-------------| :-------------|
|
||||
Email addresses | yes | yes | yes | no |
|
||||
User preferences | yes | yes | yes | no |
|
||||
System information | yes | no | yes | yes |
|
||||
Identity verification | yes | yes | yes | no |
|
||||
Google Analytics | opt-out | yes | yes | no |
|
||||
Content access analytics | yes | yes | yes | yes |
|
||||
IP addresses | yes | yes | yes | opt-out |
|
||||
Blockchain metadata | yes | yes | yes | no |
|
||||
Blockchain transactions | yes | yes | yes | yes |
|
||||
|
||||
### What’s the difference between account data and cryptocurrency wallets?
|
||||
Each installable LBRY application also contains a cryptocurrency wallet which is stored locally on the respective device. The wallet allows you to store LBRY Credits and use them to [transact (spend, publish, purchase, and tip) on the network](https://lbry.com/faq/transaction-types). The private information, which is required to perform these actions, is under the sole control of the user.
|
||||
|
||||
LBRY does provide a wallet syncing and backup mechanism to allow seamless access across multiple devices. The backup service ensures that a wallet can be retrieved by the user through their LBRY account in case they lose access to their local copy. Any storage and exchange of wallet data has end to end encryption, and the user can also provide an additional encryption password if desired.
|
||||
|
||||
### How do I use LBRY anonymously? {#anonymous}
|
||||
To use LBRY in a fully anonymous way, we recommend the LBRY Desktop application. To disable tracking features, you’ll want to disable the `Share Diagnostic Data` option from the Settings page (cog in the top right of the app). Also, you’ll want to skip providing an email and use a Virtual Private Network (VPN) to protect your IP address. This will still allow you use blockchain related features like retrieving content data, publishing, purchasing, tipping, and other transactions. Depending on VPN features and network configuration, hosting data currently may not be possible but we are looking into techniques to allow this in the future.
|
||||
|
||||
### Where is the account and analytics data stored?
|
||||
LBRY stores collected data on its own secured databases and ensures only authorized employees have access to this data. Google Analytics data is anonymized and protected by Google.
|
||||
|
||||
### What information is shared with others in the network? {#p2p}
|
||||
Similarly to other peer to peer protocols like BitTorrent, users in the network share messages (i.e. announcing content availability) and create direct connections to exchange data (i.e. downloads / uploads). While LBRY does not collect this information, other participants of the network can observe and collect the information.
|
||||
|
||||
### Can I use a VPN to use and access LBRY?
|
||||
Yes, a VPN can be used with all LBRY services. Major features will work without any problems, but VPN users may not be eligible for [LBRY Rewards](https://lbry.com/faq/rewards) in order to prevent abuse.
|
||||
|
||||
### Is any additional data collected if I participate in the YouTube Sync program?
|
||||
When authenticating into the [YouTube Sync program](https://lbry.com/youtube), you provide proof of channel ownership that allows us to link your YouTube channel to a LBRY account. Information about your account is stored and kept by LBRY, Inc.
|
||||
@@ -3,7 +3,7 @@ title: What are LBRY Rewards?
|
||||
category: getstarted
|
||||
---
|
||||
|
||||
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 3 Reward redemptions per day**.
|
||||
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 5 Reward redemptions per day**.
|
||||
|
||||

|
||||
|
||||
@@ -18,9 +18,9 @@ In order to be eligible for LBRY Rewards, users must have an approved account vi
|
||||
| **Go for a Stream** | 4 LBC | Rewarded for streaming your very first video on LBRY.
|
||||
| **Channel Surfing** | 6 LBC | A one-time reward for creating a channel on LBRY via the Publish screen.
|
||||
| **First Publish** | 10 LBC | A one-time reward for publishing your first piece of content to LBRY
|
||||
| **Daily View** | 1- 100 LBC | A random daily reward from 1 to 100 LBC, resets every 24 hours!
|
||||
| **Many Views** | 2- ???? LBC | A multi-level reward for watching videos on LBRY. See descriptions in-app for levels/details!
|
||||
| **Sub Sandwich** | 1 -2 LBC | A multi-level reward for subscribing to channels.
|
||||
| **Weekly LBRYCast** | 10 LBC | A weekly award for checking out featured content on LBRY. This content is marked with the red rocket logo and will be announced via email, recurring weekly.
|
||||
| **Welcome Back** | 6 LBC | Return to the LBRY app 24-48 hours following your first use of the app. This reward will self-destruct after that time span.
|
||||
| **Android in Beta** | 20 LBC | Limited time reward for early Android Beta testers.
|
||||
| **Upgrade** | 10 LBC | Rewarded each time the LBRY app updates versions (i.e. 0.27 to 0.28).
|
||||
|
||||
@@ -12,9 +12,9 @@ Another common cause of this issue is the lack of access to UDP port 4444. LBRY
|
||||
|
||||
1. Shutdown LBRY and lbrynet-daemon (check running processes using Task Manager on Windows or Activity Monitor on Mac OS.)
|
||||
2. Go to your [lbrynet folder](/faq/lbry-directories).
|
||||
3. If you have a `daemon_settings.yml` file, add this line to it at the end (44444 is an example, can be changed): `dht_node_port: 44444`.
|
||||
3. If you have a `daemon_settings.yml` file, add this line to it at the end (4444 is an example, can be changed): `dht_node_port: 4444`.
|
||||
4. If you don't have the `daemon_settings.yml` file, you can create one or download/copy [this sample](https://goo.gl/a5uJq5) into the `lbrynet` folder.
|
||||
5. Start LBRY and try to download a couple of items from the homepage. Be patient, if it doesn't work, leave the page and try again or a different video.
|
||||
6. Depending on your network, you may need UDP port 44444 (the new port you just set up) forwarded. Also, for file sharing to work properly, you may need TCP port 3333 open/forwarded. This can be verified by using a [port checker tool](http://www.canyouseeme.org) on port 3333. Port 44444 will fail since it's UDP.
|
||||
6. Depending on your network, you may need UDP port 4444 (the new port you just set up) forwarded. Also, for file sharing to work properly, you may need TCP port 3333 open/forwarded. This can be verified by using a [port checker tool](http://www.canyouseeme.org) on port 3333. Port 4444 will fail since it's UDP.
|
||||
|
||||
If you continue to experience issues streaming/downloading content after completing the above steps, please [reach out to us](/faq/how-to-report-bugs) for additional support.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: How do view and subscriber counts work?
|
||||
category: publisher
|
||||
order: 4
|
||||
---
|
||||
Some LBRY applications provide view and subscriber counts, like LBRY Desktop/Web.
|
||||
|
||||

|
||||
|
||||
How these numbers work is more complicated than it might appear. As a decentralized protocol, there is no single node or computer that can observe all user activity on the LBRY network.
|
||||
|
||||
Instead, view and subscriber counts are currently provided by LBRY, Inc., not the protocol itself. We aggregate data from users that participate in our rewards program and/or opt-in to sharing analytics data to provide these counts.
|
||||
|
||||
Currently, users who opt-out of analytics (more on how to use [LBRY anonymously here](https://lbry.com/faq/privacy-and-data#anonymous)) are not counted in view or subscriber figures.
|
||||
|
||||
In the future, LBRY will look to improve the accuracy of this feature as well as by adding it to the protocol itself (for example, by allowing wallet servers to share aggregated statistics and allowing subscriptions to occur via a special transaction).
|
||||
@@ -1,50 +1,91 @@
|
||||
---
|
||||
title: What is YouTube Sync?
|
||||
title: What is the LBRY YouTube Program?
|
||||
category: publisher
|
||||
order: 4
|
||||
---
|
||||
|
||||
***Service Announcement: Our queue is a bit behind at the moment, so please bear with us! You'll receive an email once your sync is complete. If you qualify for a reward (i.e., if you have over 1000 subscribers and have recently posted content), you will be able to claim this in the app. Please continue reading below...***
|
||||
LBRY offers an easy way for YouTubers to republish their content to the LBRY network, engage with LBRY users, and earn LBC. This program is available to new and existing LBRY users - installing or using our platform is not a prerequisite to syncing your channel. LBRY provides a one-click sync process that gathers your channel and video metadata (i.e. covers, thumbnails, etc), creates a channel for you on LBRY, and publishes your videos to it.
|
||||
|
||||
LBRY offers an easy way for YouTubers to sync their content to the LBRY network, engage with LBRY users, and earn LBC. This is intended for content creators that aren't quite ready to make the switch over to using the LBRY app at this time, and want us to keep their YouTube channel updated on LBRY. Not all channels qualify for the YouTube sync / rewards program, but users can always [upload the content themselves](https://lbry.com/faq/how-to-publish) through the LBRY app instead.
|
||||
To sync your existing YouTube channel to LBRY and learn more about the program, use [lbry.com/youtube](/youtube).
|
||||
|
||||
To sync your existing channel to LBRY and learn more about the program, use the [LBRY.com YouTube Sync page](/youtube).
|
||||
### What are the Steps?
|
||||
|
||||
***IMPORTANT NOTICES: You won't see your content in the LBRY app under `Publishes` nor have control of the channel until LBRY transfers control of the synced content to you. We're actively working on an automated process for this which will be ready by the end of the northern hemisphere summer. There is a manual process for creators with over 50K subscribers, please see your sync status page. Your content will be accessible through the LBRY Desktop app and [LBRY.tv](https://beta.lbry.tv) (see the links in your sync email). You also won't be able to claim the Publisher/Identity rewards in the app until the transfer is complete, though you will be able to claim your sync reward by following the instructions below.**
|
||||
There are three main steps to this program:
|
||||
|
||||
**If you want to experiment with publishing manually in the LBRY app, you can create a test channel under a different name. If you create one with the same name, there will be duplicates and we won't be merging them. You can delete the content/claim you created locally using the trash can icons on the transactions page. We will be automatically updating channel pages (i.e., cover art and descriptions) from your YouTube profile in the coming weeks. Thank you for your patience and understanding!**
|
||||
1. *[Enroll](#enroll)* - Provide authorization for us to begin syncing. After this step, you can begin claiming [rewards](#reward) (if eligible).
|
||||
|
||||
### Authenticating with your YouTube Account and Sync Details
|
||||
Authenticating your YouTube channel and other information puts your content into a queue to be automatically mirrored on the LBRY network. This serves as an alternative to re-publishing your entire channel by yourself. The content, its title and description, as well as thumbnails and other metadata, will sync to your channel name. When it is done, you will receive a notice from LBRY indicating your channel is available to view.
|
||||
2. *Sync* - During this step, we perform magic behind the scenes. It can take up to several days and [some sync limitations apply](#limits).
|
||||
|
||||
There is a size limit per video of 2GB. There is a total count limit of your most recent 1,000 videos. What this means, if that isn't clear, is that your most recent 1,000 videos that are smaller than (or equal to) 2GB in size will be synced to LBRY. **Content that's marked as potential copyright violations by YouTube also will not be synced**
|
||||
3. *[Transfer](#transfer)* - Claim ownership of your new LBRY channel. This requires receiving your LBRY wallet, so that you and only you are in control. More [below](#claim).
|
||||
|
||||
When you sync your channel, you are also eligible to receive LBRY Credits in our Partner Program based on your subscriber count. Receiving these credits is subject to a one-year agreement. The exact agreement you make when you sync can be seen [here](/faq/youtube-terms). The current rewards for syncing can be seen on the [sync page](/youtube).
|
||||
#### Enrolling {#enroll}
|
||||
|
||||
The sync process stores your wallet in a secure location, as you may not have the LBRY app installed already. If you have over 100K subs and are comfortable with [swapping out wallet files](/faq/how-to-backup-wallet), we can work with you to transfer your synced wallet as part of a manual process. Typically, we recommend waiting until we have an automated solution for transferring this data to you via the app. Please reach out to [help@lbry.com](mailto:help@lbry.com) if you have any questions about this process.
|
||||
To enroll, visit [lbry.com/youtube](/youtube).
|
||||
|
||||
### How to Receive Your LBRY Credits for Syncing
|
||||
The enrollment page will validate that you own your channel and that you agree to the terms of the LBRY YouTube program. After enrolling, we collect information about your channel (title, description, etc.) and put your content into a queue to be automatically published to the LBRY network. This means you don't have to do anything to have your entire channel backed up and permanently available via LBRY.
|
||||
|
||||
You can do this once your channel has been synced.
|
||||
When the process is complete, you will receive a notice from LBRY indicating your channel is available to view.
|
||||
|
||||
- Download the LBRY App from [/get](https://lbry.com/get)
|
||||
- Run the LBRY App
|
||||
- Make sure the email saved in the application matches the email address on your [Sync Status Page](/youtube/status) - you can update this and make sure to verify via the email you receive (the email may not update but it will link together)
|
||||
- Click on the **Rewards** option from under Account in the sidebar.
|
||||
- Scroll to the "YouTube Reward" tile and click Get XXXX LBC.
|
||||
- If you met a particular subscriber threshold (minimum 1K subs, 10 videos, and recent content), you should receive the appropriate amount of credits.
|
||||

|
||||
|
||||
### I created a channel and/or published on my LBRY app, what do I do now?
|
||||
Note that as soon as you enroll, you are eligible to receive LBRY Credits based on the terms of our program. The current rewards for participating can be seen on the [program page](/youtube). The exact agreement you make when you enroll can be seen [here](/faq/youtube-terms).
|
||||
|
||||
You can delete this channel and any content you published using the transactions page and trash can icons. Unless you plan to experiment with a different channel name in the meantime, please be patient until the channel is transferred to you (see above notice for timing information).
|
||||
#### Claiming Rewards {#reward}
|
||||
|
||||
### How do I Publish using my Channel?
|
||||
As soon as you've enrolled, you can claim your rewards.
|
||||
|
||||
You won't see your content in the LBRY app under `Publishes` nor have control of the channel until LBRY transfers control of the synced content to you. We're actively working on an automated process for this which will be ready by the end of the northern hemisphere summer. However, your content will be accessible through the LBRY Desktop app and [LBRY.tv](https://beta.lbry.tv) (see the links in your sync email). If you have over 50K subscribers and want to do this via a manual process, see the [wallet claim page](https://lbry.com/claim-wallet)
|
||||
1) Download, install and run the LBRY App from [lbry.com](https://lbry.com/get).
|
||||
2) Make sure the email saved in the application matches the email address on your [YouTube status page](/youtube/status). If it doesn't, please update it and be sure to verify it via the email you receive.
|
||||
3) Navigate to the _Rewards_ section of the app by clicking your balance in the top right.
|
||||
4) Scroll to the "YouTube Reward" tile and click Get XXXX LBC to receive the appropriate amount of credits. If your account is under review, please check back later.
|
||||
|
||||
### What's the difference between Sync and Transfer?
|
||||
#### Wallet Transfer {#transfer}
|
||||
|
||||
When a channel is synced, it means the content has been mirrored to LBRY and available on the network for anyone to view. YouTubers will get an email once this is completed. The transfer process is described in the important notice above, which is the final step of sending the channel and content to the YouTuber's wallet so they can publish/control the content. This last step is still being actively developed and we'll let you know via email once the content is ready to be transferred. Until then, you won't see the channel/content in your Publishes section, nor be able to publish as that channel outside of the YouTube sync process.
|
||||
Your _wallet_ is a special file that contains the secret keys (like a password) to your account.
|
||||
|
||||
**It is important that you have a [backup of your wallet](faq/how-to-backup-wallet) after the transfer process is initiated.** New users will have the option of doing so when they first sign into LBRY (Sync Balance setting when entering email).
|
||||
|
||||
If you're having any trouble with the sync process or receiving your credits, please contact [help@lbry.com](mailto:help@lbry.com).
|
||||
The wallet transfer step ensures you have full control of your content and channel. After completing this step, LBRY will not be able to access your funds or modify your channel/account, outside of a permission we retain to continue publishing.
|
||||
|
||||
Currently, content transfer is available in the LBRY Desktop application. Once the channel and content is transferred, you'll be able to publish, comment, and edit existing content in the LBRY app.
|
||||
|
||||
If you are signing into the LBRY app for the first time, you'll be presented with an option to claim your channel. If the channel is still queued, you'll be able to claim it from the Channels page (right hand side above Publishes) after its synced. Existing app users can also claim their channels via the Channels page. If you created any channels or published content locally before initiating this step, see the [cleanup section](#cleanup).
|
||||
|
||||

|
||||
|
||||
#### What's the exact difference between Enrolling and Transfer? {#transfer}
|
||||
|
||||
When you _enroll_, it means the content has been mirrored to LBRY and available on the network for anyone to view. You will get an email once this begins and once this is completed. The _transfer_ process is the final step that gives you actual and permanent control over your account (though LBRY will continue publishing content uploaded to YouTube directly to your account after transfer, retaining a permission to do this and only this).
|
||||
|
||||
Feature | Enroll | Transfer |
|
||||
:------------ | :-------------| :-------------|
|
||||
Your Youtube publishes will be synced | yes | yes |
|
||||
You can claim LBC rewards | yes | yes |
|
||||
You can use the app to publish to the channel and your content shows in the app | no | yes |
|
||||
You can receive LBC from tips and content payments | no | yes |
|
||||
You are responsible for keeping your wallet safe | no | yes |
|
||||
|
||||
### Limitations {#limits}
|
||||
|
||||
- There is a size limit per video of 2GB.
|
||||
- There is a total count limit of your most recent 1,000 videos.
|
||||
|
||||
Your most recent 1,000 videos that are 2GB or smaller in size will be synced to LBRY.
|
||||
|
||||
Private or unlisted videos will not be published, but everything else will.
|
||||
|
||||
### What happens if I created a channel and/or published on my LBRY app before transfer? {#cleanup}
|
||||
|
||||
If you created a channel with the same name as your YouTube channel, it is recommended you delete your locally created channel, which can be done before or after the channel transfer process. If you published any content locally, you can edit the content and use your newly transferred channel to include it, or you can simply delete the locally published content as well. Unless you plan to experiment with a different channel name in the meantime, please be patient until the channel is tranferred to you.
|
||||
|
||||
To delete the original channel, you'll need to navigate to the Wallet page (click on your balance in the top right). Next, click "Full History" and find the original channel you created. You may need to paginate in order to find it. Make sure it is the right channel to delete by clicking on the name from the history page first. Then use the trash can icon to remove it.
|
||||
|
||||
You can do the same for any content you published locally. The other option is to edit the content and select your newly tranferred channel. This will make the content appear under this channel.
|
||||
|
||||
### Why can't I Sync my Channel?
|
||||
|
||||
Not all channels may qualify for the program, but users can always [upload the content themselves](https://lbry.com/faq/how-to-publish) through a LBRY app instead. Eligibility is based on a careful determined criteria to keep spam and abuse out, but everyone else is intended to be eligible. If you were rejected and think this was an error, please [contact us](mailto:hello@lbry.com).
|
||||
|
||||
### Help Me
|
||||
|
||||
If you have questions this article did not cover, or are having any trouble with the enrollment process, transfer process, or staying calm and happy under the unrelenting pressure that is modern society, please contact [help@lbry.com](mailto:help@lbry.com).
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
author: brinck-slattery
|
||||
title: 'The Birth Of Entertainment'
|
||||
date: '2020-11-17 14:00:00'
|
||||
date: '2018-01-17 15:30:00'
|
||||
cover: 'muses.jpg'
|
||||
category: content
|
||||
---
|
||||
|
||||
@@ -6,6 +6,8 @@ cover: 'Hacktoberfest.jpg'
|
||||
category: users
|
||||
---
|
||||
|
||||
_(For CURRENT\_YEAR's Hacktoberfest announcement, please visit [lbry.com/hacktoberfest](https://lbry.com/hacktoberfest))_
|
||||
|
||||
The leaves are starting to fall, and that means it's time for Hackoberfest! Thanks to [DigitalOcean's hard work](https://hacktoberfest.digitalocean.com), newbies and seasoned open source developers alike have a unique opportunity to solve new and challenging problems and bugs all through the month of October (and earn [some recognition and a free t-shirt](https://hacktoberfest.digitalocean.com/details) in the process).
|
||||
|
||||
Open source is (literally) part of our DNA here at LBRY, and we're always happy when we get an opportunity to support our fellow open source projects. Throughout the month of October, our developers will be hosting informational sessions, meetups, and coding projects to introduce other programmers to the world of open source software and start making contributions immediately.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Blockchain Update'
|
||||
date: '2019-9-10 09:00:00'
|
||||
cover: 'blockchaintech.jpg'
|
||||
category: update
|
||||
---
|
||||
|
||||
On August 16, 2019, the LBRY chain experienced an unexpected fork between the current version of lbrycrd (v0.17.2) and previous versions. Block height of the fork: 617743. We might have favored the older build, but older versions of lbrycrd would crash when receiving data from the newer version after that block. v0.17.1 was able to proceed down its own chain, but there was little mining power behind this; the main pools were already mining with majority of hash on the correct (v0.17.2) chain.
|
||||
|
||||
This was middle of the night for most LBRY engineers, but the event was fortunately detected by a LBRY engineer three hours after the occurrence. In response to the incident, miners and other critical systems were immediately upgraded to v0.17.2. We appreciate the immediate and dedicated response from the various mining pools, exchanges, and others.
|
||||
|
||||
Version 0.17.2 replaces a large portion of the consensus-critical code path with more memory-efficient mechanisms. When this work was done, two existing issues with the takeover height computation were discovered in the older code. An effort was made to search for others through random block data generation. No other issues were found at the time, and it was hoped that there were no other lurking issues with the old code. The two known issues were maintained with workarounds in hopes that the root hash computation would match the existing versions, but it was done in a way that they would be disabled with the next hard-fork (not released yet). Details on the bugs are to be revealed after the pending hard fork occurs.
|
||||
|
||||
In block 617743, the newer code for the hash computation incorrectly decided that a certain claim required the takeover height workaround. It was a failure to completely model the previous erroneous behavior. Other blocks in the future may be affected, but the behavior will likely go undetected as most are now upgraded to the latest release. We appreciate your patience in the matter. Sincerely, blockchain@lbry.com
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
author: jeremy-kauffman
|
||||
title: 'What Is Censorship Resistance, And Why Does It Matter?'
|
||||
date: '2019-9-10 12:00:00'
|
||||
cover: 'censorship2.jpg'
|
||||
category: update
|
||||
---
|
||||
|
||||
## What is censorship-resistance?
|
||||
At the risk of tautology, censorship-resistance is the ability to resist censorship. Less tautologically, censorship-resistance is the degree to which a system is tamper proof. That is, a censorship-resistant system means a third party cannot modify or remove content created by someone else.
|
||||
|
||||
Just as nothing in the world is theft proof, nothing in the world is censorship proof. When a bank builds twenty foot walls around a vault with 3-foot-thick steel door that is monitored by security cameras, it does not do so to make theft literally impossible. It does so to make theft of the goods inside sufficiently challenging that it is extraordinarily improbable. When we speak of censorship-resistance, we speak the same as of the bank vault. A system can never be literally censorship proof, but it can be made extremely censorship resistant.
|
||||
|
||||
So when speaking of censorship resistance with regards to LBRY, we are speaking about how challenging it is to modify or remove content from the LBRY network without permission from the publisher
|
||||
|
||||
## How censorship-resistant is LBRY?
|
||||
|
||||
We believe LBRY to be the most censorship-resistant system to ever exist for the purposes of publishing digital content.
|
||||
|
||||
To understand where LBRY’s censorship resistance comes from, we need to break the problem down into two areas: data (the digital content) and metadata (information about the digital content, such as it’s title or publisher).
|
||||
|
||||
In the case of the data itself, LBRY is as or more censorship-resistant as BitTorrent or other peer-to-peer networks. Like these other networks, when you publish a file, it ends up being hosted by dozens, hundreds, or thousands of other computers, depending on its popularity. Additionally, there are economic incentives to host content that is popular but undersupplied, which means that LBRY is even better than its predecessors, which were already world leaders in the censorship-resistance department.
|
||||
|
||||
In the case of the metadata, LBRY is truly novel. Previous peer-to-peer systems had decent censorship-resistance at the data level, but never the metadata. LBRY writes it’s metadata to a public blockchain, the same technology that powers the censorship-resistant Bitcoin. Metadata in the LBRY blockchain cannot be altered without a hard-fork of the network, which is an expensive and unlikely proposition. Even if this happened, it would be possible to roll-back the system to it’s last previously good state, resulting in only a temporary rather than permanent data loss.
|
||||
|
||||
## How could LBRY be censored?
|
||||
|
||||
An internet service provider or network operator could conceivably censor traffic to the LBRY network entirely, by blocking or dropping packets that appear to be part of the LBRY protocol. However, given that this traffic is typically encrypted, consists of otherwise ordinary TCP and UDP packets, and can be headed to or from basically any address on the internet, this would be fairly challenging.
|
||||
|
||||
If a network operator did find a way to block LBRY traffic at the network level, we would work tirelessly to continue to evolve the system to make this difficult or impossible.
|
||||
|
||||
## Why does censorship-resistance matter?
|
||||
|
||||
Censorship-resistance matters because there are many people in the world who would like to stop others from speaking. This can range in scale from national governments (China, North Korea, Iran) to college campuses (Evergreen).
|
||||
|
||||
Prosperity and freedom starts with the ability for people to communicate freely with one another. The ability to censor is the ability to control the narrative and spread propaganda.
|
||||
|
||||
For the purposes of discovering truth and fighting injustice, censorship-resistance is absolutely vital.
|
||||
@@ -0,0 +1,194 @@
|
||||
---
|
||||
author: tom-zarebczan
|
||||
title: 'Development Update for August 2019'
|
||||
date: '2019-09-10 20:00:00'
|
||||
cover: 'tech-cover.jpg'
|
||||
category: community-update
|
||||
---
|
||||
Welcome to the August 2019 LBRY Development update! In this post we’ll show you what we’ve been up to since our [last update in July](https://lbry.com/news/jun-july-dev). Sit tight, there’s been lots of progress and releases, including updates from the Apps (Desktop and Mobile), SDK, and blockchain teams!
|
||||
|
||||
To read previous updates, please visit our [Development and Community Update archive](https://lbry.com/news/category/community-update).
|
||||
|
||||
If you want to see a condensed view of what we have completed recently and what’s planned for LBRY, check out our [Roadmap](https://lbry.io/roadmap).
|
||||
|
||||
First off, let’s start with some GitHub stats across all our repos (some of which are internal only to LBRY) since our last update about 40 days ago:
|
||||
36 repos were updated. 617 issues and pull requests were created, 146 were closed. 18 pull requests were merged. 30 GitHub users outside of LBRY made code contributions, including:
|
||||
- [AlessandroSpallina](https://github.com/AlessandroSpallina)
|
||||
- [Borewit](https://github.com/Borewit)
|
||||
- [btzr-io](https://github.com/btzr-io)
|
||||
- [ceoger](https://github.com/ceoger)
|
||||
- [dittaeva](https://github.com/dittaeva)
|
||||
- [eggplantbren](https://github.com/eggplantbren)
|
||||
- [nestordominguez](https://github.com/nestordominguez)
|
||||
- [vv181](https://github.com/vv181)
|
||||
- [ykris45](https://github.com/ykris45)
|
||||
- [zxawry](https://github.com/zxawry)
|
||||
|
||||
Thanks to everyone who took time out of their busy days to help LBRY out!
|
||||
|
||||
## In this report, we cover updates for
|
||||
* [Desktop App](#summary-desktop)
|
||||
* [SDK](#summary-sdk)
|
||||
* [Blockchain](#blockchain)
|
||||
* [LBRY.tv](#web)
|
||||
* [LBRY for Android](#android)
|
||||
* [Rewards](#rewards)
|
||||
* [Cross Device Syncing](#cross)
|
||||
* [YouTube Sync Transfers](#youtube)
|
||||
* [Community Block Explorer](#explorer)
|
||||
* [2019 Roadmap Progress](#roadmap)
|
||||
|
||||
### Desktop App {#summary-desktop}
|
||||
Since our last development update, the app team shipped our next named release, 0.35, under codename [Franklin](https://lbry.com/news/franklin-is-minted) as well as a few patches. Franklin enhances the app experience with a brand new [videojs-based](https://github.com/videojs/video.js) video player.
|
||||
|
||||
Other new features in Franklin include:
|
||||
- The ability to continue watching videos in pop out mode
|
||||
- Support of range requests (streaming)
|
||||
- The ability to block channels app-wide
|
||||
|
||||
The patch releases included some new features:
|
||||
- All new features added to the SDK between version 0.38.5 and 0.40, including improved wallet sync behavior, download speeds, and overall connectivity ([more details below](#summary-sdk))
|
||||
- Tipping on channel pages (which gets sent to the channel claim, as opposed to content claims on file pages)
|
||||
- Ability to set the time period for dark mode
|
||||
- Improvements to the display of URLs (now has the [canonical URL](https://lbry.tech/glossary#canonical-url) which uses both channel and claim short IDs)
|
||||
- Support for a new daily watch reward that went live on September 10th (replacing the weekly LBRYCast)
|
||||
|
||||
The patches fixed many bugs, including:
|
||||
- Issues with bid amounts required on the publish page (did not show vanity URL bids),
|
||||
- Auto-downloading subscription content
|
||||
- Search bar focus getting stuck
|
||||
- Disabling autoplay on paid content
|
||||
- DMCA blocking to include entire channels
|
||||
|
||||
We also updated our digital certificate for Windows builds which is an annual maintenance task. We'll explore a better solution for this down the road.
|
||||
|
||||

|
||||
|
||||
#### Video Player and Download Settings
|
||||
|
||||
The new video player fixes multiple bugs from previous versions: most importantly the ability to set the volume, not being able to play back certain MP4 formats, and being able to skip anywhere in the video right away thanks to range requests (versus the previous version where you had to wait for it to download). It also allows us to add two new settings for saving hosted content and files, both of which are enabled by default. Users who wish to disable either or both are now able to, but turning off content hosting hurts the LBRY network because you no longer become a seeder. For non-streamable file types like games, documents, and 3d printing files, the files will download locally, regardless.
|
||||
|
||||

|
||||
|
||||
#### Desktop Next Steps
|
||||
The app team also began development of our planned cross-device sync process (wallet + app data like tags/subscriptions/blocked channels, other settings) but we’re waiting on additional support from our SDK and API teams to finish up this feature - see the [cross device update](#sync) for more information. Continuing work on the video player, we’ll be adding features to save position and volume settings throughout the app which will also eventually be synced up.
|
||||
|
||||
We also are working on a more streamlined [sign in/out process](#login) that will be featured in-app and on lbry.tv. This will include a 1 LBC email reward for all users, including new ones, so that they can create a channel during the signup process (some users, such as those using a VPN, may not qualify). Once we get wallet sync fleshed out, this new login process will also include those options and ability to restore via email/password.
|
||||
|
||||
Another area that continues to get attention is internationalization. You may have noticed we added German as an additional language, and we’re making more changes under the hood to support a streamlined effort across all our projects. Finally, we’ll also be working on an improved balance display on the wallet page that shows how much LBC you have locked in claims/channels, supports, and tips.
|
||||
|
||||
### SDK {#summary-sdk}
|
||||
On the SDK side of the house, we’ve shipped versions 0.39, with patches, and 0.40.0 with a recent patch. You can review all the changelogs on our [GitHub releases page](https://github.com/lbryio/lbry-sdk/releases).
|
||||
|
||||
The main features include:
|
||||
- Treating multiple accounts inside a wallet to effectively be treated as one (missing a few API calls, to be completed soon)
|
||||
- ability to connect and synchronize transactions with multiple wallet servers (see screenshot below) which improves wallet sync speed and paves the way to interfacing with community wallet servers
|
||||
- Wallet server monitoring tools to include session information / logging of troublesome claim search queries
|
||||
- A key value store which will be the final location of synced LBRY data.
|
||||
- Added a new function for comments that allows channel owners to moderate comments by hiding them (to be implemented in the app in the next few months)
|
||||
|
||||
On SDK startup, we now ping all the wallet servers and select the best main one to connect to based on the peer’s location. The ability to connect/sync with multiple servers proved to be more troublesome than expected, we experienced and fixed reconnection issues which should be resolved with the [0.40.1 patch](https://github.com/lbryio/lbry-sdk/releases/tag/v0.40.1).
|
||||
|
||||

|
||||
|
||||
#### SDK Next Steps
|
||||
During testing of the [YouTube transfer](#youtube) process, we ran into a snag with how our channel import/export process was designed, especially when the channel itself is transferred from one wallet to another which prevented both sides (YouTube Sync and the Content Creator) from signing claims. Progress has been made to support a short term solution for both cases, and we expect a resolution soon. Besides this bug, we are also looking into any remaining wallet syncing / connectivity problems, one affecting content announcement, and another that may cause memory leaks on some machines. If you think your node has suffered from either, please give us a shout on [Discord](https://chat.lbry.com).
|
||||
|
||||
Finally, we’ve also been researching and have begun initial implementation of a technique called [holepunching](https://en.wikipedia.org/wiki/TCP_hole_punching), which will improve connectivity between nodes -- especially for those behind firewalls or with unusual network configurations. This may alleviate the need for port forwarding, but nodes that can do port forwarding will be encouraged to leave it on. We expect this to increase our overall network availability and performance.
|
||||
|
||||
### Blockchain {#blockchain}
|
||||
Since our last update, the blockchain team continues their work towards enabling SegWit later this year, optimizing memory usage, revamping RPC calls to include bid (which will allow us to show pending effective amounts during takeovers) and sequence (which was removed in a previous update), and enabling metadata along with supports. Support metadata will enable us to expand the support/tipping feature of LBRY, which currently only allows simple LBC transactions to occur, to include additional metadata that can be used for signing the supports to prove channel ownership and enabling use cases like commenting, rating, and subscriptions on chain. Signing of supports will finally give us the ability to link a channel back to a tip transaction, so publishers can see and verify who sent LBC (or even a support). On-chain subscriptions also help further decentralize data you can only find on our API currently, and enable a Patreon-like system where creators can release content that’s accessible only by their supportors or at various support/tip levels.
|
||||
|
||||
#### Forced Upgrade - Pre 0.17.2 Nodes Go Offline
|
||||
On August 16, 2019, the LBRY chain experienced an unexpected fork between the current version of lbrycrd (v0.17.2) and previous versions. The fork occured at block height 617743. Everything is back to normal currently on the latest release/chain, and we’ll continue to monitor the situation. If you are still running a pre 0.17.2 node, please [see below](#recover) on how to recover.
|
||||
|
||||
Read [our blog post](https://lbry.com/news/lbry-blockchain-update) for the entire executive summary of the incident.
|
||||
|
||||
#### How to Recover a Pre 0.17.2 Node {#recover}
|
||||
Please upgrade your LBRYcrd node to the latest version on our [GitHub release page](https://github.com/lbryio/lbrycrd/releases/tag/v0.17.2.1). After you’ve run it, perform the following CLI command: `lbrycrd-cli reconsiderblock b9a350fa8b4471c46cb2088927ac5e959939c815e7d98e8125f099b902e96a62` to get back up to speed. The other option would be to clear our your local data and resync from scratch.
|
||||
|
||||
### LBRY.tv {#web}
|
||||
Over the last few months, we’ve been running a view-only pilot of [beta.lbry.tv](https://beta.lbry.tv), meaning you can view free content, but many of the other features like wallets, rewards, and publishing have been disabled. We’ve also created and run stress tests on lbry.tv to make sure the web server and underlying SDK can handle thousands of concurrent users. In order to scale to even more users in the future, we will need to run multiple web and SDK servers.
|
||||
|
||||
Recently, we introduced application options on the Settings page, but none of these options persist between refreshes until we’re able to sync the settings to our interim API sync solution. Longer term, these will sync back to the wallet file once lbry.tv migrates from an account-based model to a wallet-based one that will support cross device syncing (today, syncing only works at a wallet level). The current SDK does not support multiple wallets, which is why we went with an account-based model (to at least ship a fully featured web experience without wallet sync).
|
||||
|
||||
We also added OpenGraph metadata to channels and claim links when shared on Twitter/Facebook and other sites that support it.
|
||||
|
||||

|
||||
|
||||
#### Login/Logout {#login}
|
||||
As mentioned in the [Desktop summary](#summary-desktop), we’re in the process of implementing a typical login/logout process that most users are accustomed to. This will include a 1 LBC reward for a verified email (some VPN users may not qualify) that will allow new users to create a channel as part of the process. Once lbry.tv moves to a wallet model, it will also include wallet syncing/restore options. This change will include two top menu items instead of one: wallet and balance under your LBC total, and Overview + Publish under the Account icon. Users not logged in can still enjoy free content, but won’t see any of the right sidebar options, nor be able to customize the tag list.
|
||||
|
||||

|
||||
|
||||
#### Publishing on the Web
|
||||
|
||||
Publishing from the web is a bit trickier since the lbry.tv server will need to act as an intermediary between the user and the SDK running - so it needs to be able to handle/intercept the file transfer process. This is currently a work in progress and may not be ready for the first soft launch with wallets/rewards.
|
||||
|
||||
#### LBRY.tv Launch
|
||||
|
||||
We are preparing for soft launch of LBRY.tv support with wallets and rewards. This will also include syncing tags, subscriptions, and other app settings, with wallet syncing to come at a later date (wallet notice will be shown to users with other installations). Publishing features are not too far behind, and if all goes well, we should see a full launch by the end of the month.
|
||||
|
||||
Want to be the first to know when it’s fully operational? Sign up for the mailing list at [lbry.tv](https://lbry.tv).
|
||||
|
||||
### LBRY for Android {#android}
|
||||
|
||||
Since our last update, the Android app has been playing catchup with the Desktop app’s discovery features - this includes the ability to follow tags and explore tags, create channels, and publish (and edit!) content. We’re also excited that some of the more profound performance problems with the Android app have been resolved under the hood - the latest release provides a much smoother experience navigating throughout the app. The publish process was streamlined for mobile purposes which includes automatic uploading of thumbnails. You can also tag your content, create a channel, select a URL, and adjust your default LBC bid. On another note, we have noticed some issues with syncing wallets on restore, so if you run into this, please reach out to us on [Discord](https://chat.lbry.com) - we are still investigating but this will be solved once the SDK fully supports multiple accounts.
|
||||
|
||||
#### Discovery
|
||||
The discovery process, which resembles the Desktop application, allows you to customize your followed tags which are then shown on the "Your Tags" page - this includes a drop down to change between trending/top/new, along with a top level listing of content across all your tags, plus a break down for each tag you follow with an option to view the tag page (click the arrows, or More tile). Currently we have to limit this to 5 tags (randomized between runs) which are shown on the main page due to performance issues, but you can click on the rest of your tags at the bottom of the page to see their tag pages. The subscriptions area also received a revamp - you can now see Trending/Top/New views across all your subscriptions, or you can click on a specific creator to filter. The "All Content" page enables you to explore other LBRY content not in your tags (default setting) using the same Trending/Top/New sorting options (you can also choose to limit on tags you follow which is the view you’d get to by clicking More on the top item from the "Your Tags" homepage.
|
||||
|
||||

|
||||
|
||||
#### Android Next Steps
|
||||
Next steps for Android include a richer channel process, which includes a My Channel pages and creation/editing area that will allow publishers to modify data like their title, thumbnail/cover images, bid, website, email, description, and tags. Be on the lookout for this featured in version 0.9, which will be the next named release. After this, we’ll be enabling our interim data/settings sync feature, add the ability to block channels, allow publishing of more file types (currently limited to videos/images), and the ability to save files locally.
|
||||
|
||||
### Rewards {#rewards}
|
||||
We’ve got some exciting rewards updates in progress and coming out very soon! First off, we’ll be enabling a 1 LBC reward for a majority of users so they can take advantage of the new sign up flow which creates a channel for them. We are also currently experimenting with auto-enabling rewards for users with clean IP scores using a third party IP ranking system. This process will be further optimized to prevent abuse and also to check other IP attributes like ISP/location to enable more with auto-approvals.
|
||||
|
||||
Finally, we’ve recently sent our last LBRYCast email that will be tied to a weekly featured reward - this is now moving to a daily watch reward where users will be randomly awarded between 1 and 100 LBC. We’ll send an email as soon as this is available to claim. Enjoy the LBC!
|
||||
|
||||
### Cross Device Syncing {#sync}
|
||||
As we’ve mentioned in other sections of this report, we ran into a snag with being able to implement wallet syncing if a user has multiple encrypted wallets (the sync tool is not aware of this yet) and being able to use this to sync settings back onto LBRY.tv (SDK syncing is implemented wallet wide). Since wallet syncing on LBRY.tv would require a move from an account to wallet based model (which is not yet supported), we decided on implementing a quicker API sync tool for settings + application data, so at least some data like tags and blocked channels can work cross device. This is currently in development along with the sign in/out feature and will also be supported on Desktop/Mobile.
|
||||
|
||||
The SDK already has support for a similar key value store as seen below, so once we have fully implemented multi-account awareness and multi-wallet support for lbry.tv, we can then sync up balances between all devices/wallets. We’ll still try to enable wallet sync on Desktop before it’s fully ready for all the scenarios we want to support - but we’ll have to limit it to previously un-synced users or if your balance is zero (so that we can enable the synced account, discarding the current one). So the main case we won’t be able to support right away is users who have an existing desktop wallet, and have another device that’s already synced (Desktop/Android).
|
||||
|
||||

|
||||
|
||||
### YouTube Sync Transfers {#youtube}
|
||||
During the last 2 months, the team has worked on bringing creators closer to their content and audience with a long awaited feature, currently in test phase: transferring ownership of synced content directly into creators’ app wallets and also allow new content publishing.
|
||||
|
||||
This feature is a culmination of efforts across multiple teams at LBRY:
|
||||
The SDK team was responsible for exposing the necessary tools to export and update channels and streams, the Backend team was responsible for exposing the endpoints necessary to initiate and pursue the process, the App team had to interface with such endpoints and last but not least, the YouTube sync team had to ensure the integrity of each channel before transferring everything to the creator.
|
||||
|
||||
The result is pretty fascinating and closes the last loop in the sync process: YouTube creators can click a single button in the app, immediately gain access to publish new content via their channel, and their wallet will soon be populated with all their content and channel claims, including all their tips being re-supported on their channel. We’re all super excited for this one!
|
||||
|
||||
### Community Block Explorer {#explorer}
|
||||
A community member by the name of [Alessandro Spallina](https://github.com/AlessandroSpallina) became interested in the LBRY ecosystem and wanted to implement a more modern and fully featured block explorer that exposes important metrics of the LBRY blockchain. You can check out his [GitHub issue](https://github.com/lbryio/block-explorer/issues/67) outlining what he plans on developing or you can go straight to the explorer prototype at [lbryexplorer.tech](https://lbryexplorer.tech/) to give it a shot We’d appreciate any feedback on the GitHub issue and current prototype - you can leave a comment on GitHub or reach out on [Discord](https://chat.lbry.com) #dev channel by tagging @SK3LA.
|
||||
|
||||

|
||||
|
||||
### 2019 Roadmap {#roadmap}
|
||||
We’ve successfully accomplished a number of roadmap items fully, while others are partially complete and ongoing efforts. See our [previous development report](https://lbry.com/news/jun-july-dev) on updates for completed ones.
|
||||
|
||||
Partially completed/still in progress are:
|
||||
* **Commenting** - moderation features are in progress
|
||||
* **Creator Features** - granular account balances in process
|
||||
* **Creator Partnerships** - no update since last month - in progress and will be announced later this year
|
||||
* **LBRY on the Web** - account features which are set to go live this month.
|
||||
* **Multi-Device Experience** - app settings/data syncing in progress, wallet sync to come soon after.
|
||||
* **Internationalization** - ongoing internationalization enhancements are in progress on Desktop.
|
||||
* **Protocol Performance** - improved download performance in 0.39 releases. Holepunching research in progress.
|
||||
|
||||
# Limited Reward Code!
|
||||
We’ve got a special bonus for readers of this update, enjoy some LBC via this code (while supplies last!): `dev-update-aug-jkala`
|
||||
|
||||
# Want to Develop on the LBRY ecosystem?
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [contributing guide](https://lbry.tech/contribute) and our [LBRY App specific contributing document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Make sure you have turned on the Developer option in your email preferences (see app overview page), or sign up at [lbry.tech](https://lbry.tech). We also have a [LBRY Discourse Forum](https://discourse.lbry.io) where developers can interact with the team and ask questions across all our different projects.
|
||||
|
||||
If you aren’t part of our Discord community yet, [join us](https://chat.lbry.com) 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. Also follow us on [Twitter](https://twitter.com/lbryio), [Facebook](https://facebook.com/lbryio), [Reddit](https://www.reddit.com/r/lbry), [BitcoinTalk](https://bitcointalk.org/index.php?topic=5116826.new#new), and [Telegram](https//t.me/lbryofficial).
|
||||
|
||||
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?
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
author: brinck-slattery
|
||||
title: 'LBRY Butterfly Flits Onto The Scene'
|
||||
date: '2019-09-26 08:00:00'
|
||||
cover: 'Butterfly.jpg'
|
||||
category: news
|
||||
---
|
||||
# LBRY Butterfly is LIVE in the Google Play store!
|
||||

|
||||
## The first in a series of updates that will be rolling out over the next few months, Butterfly has some amazing features that you've all been asking for, and a few you haven't!
|
||||
Wondering what's in the box?
|
||||
* **A new channel page.** This page will help publishers manage their content.
|
||||
* **Thumbnail selection for published content.**
|
||||
* **Universal Publishing.** You can publish ANY kind of file form your mobile device.
|
||||
* **USD Pricing.** To allow creators to give people purchasing their content a better idea of what they're spending in dollars.
|
||||
* **Synchronized tags and subscriptions across devices.** We're still overhauling the whole LBRY ecosystem, but when universal log-in is ready, our Android app will be too!
|
||||
* **LBRY SDK 0.40.1** for improved stability and performance.
|
||||
* **And much, much more!**
|
||||
|
||||
## On top of all that, you can now earn DAILY REWARDS just for watching your favorite stuff on LBRY!
|
||||
|
||||
And as a gift to our biggest fans, we've included a special reward code for the first 100 users to get to it! Enter **android-b-919** in your app to get the reward.
|
||||
|
||||
So open your app now to upgrade - and if you haven’t installed it yet, what are you waiting for? [Click here to get it now](https://play.google.com/store/apps/details?id=io.lbry.browser&hl=en_US), or open your app to upgrade!
|
||||
@@ -0,0 +1,176 @@
|
||||
---
|
||||
author: julie-sigwart
|
||||
title: 'September 2019 LBRY Community Report'
|
||||
date: '2019-09-26 13:00:00'
|
||||
cover: 'leaves.jpg'
|
||||
category: community-update
|
||||
---
|
||||
|
||||
# Welcome to the September 2019 LBRY Community update!
|
||||
|
||||
If you aren’t part of our Discord community yet, [join us](https://chat.lbry.com) anytime and say hello! Our community allows LBRYians to interact with the team directly and for us to engage users and grow the LBRY platform. If you don't already, follow us on [Twitter](https://twitter.com/lbryio), [Facebook](https://facebook.com/lbryio), [Reddit](https://www.reddit.com/r/lbry), and [Telegram](https://t.me/lbryofficial).
|
||||
|
||||
## In This Update: {#updates}
|
||||
* [What's new at LBRY?](#news)
|
||||
* [LBRY.tv is nearly here](#web)
|
||||
* [LBRY Android Butterfly Released](#android)
|
||||
* [New Daily Rewards!](#rewards)
|
||||
* [Hacktoberfest](#hacktoberfest)
|
||||
* [We're looking to create new hives!](#new)
|
||||
* [Hive Updates](#hives)
|
||||
* [LBRY App in More Languages](#i18n)
|
||||
* [Community Block Explorer](#explorer)
|
||||
* [Yummy Dessert!](#dessert)
|
||||
|
||||
### What's New at LBRY? {#news}
|
||||
|
||||
#### LBRY Desktop, Android, and Web App Software
|
||||
|
||||
Since our last update, progress has been made on a number of our Roadmap items, including:
|
||||
|
||||
* Software app for Android, desktop, and the web. the app team shipped our next named release, 0.35, under codename Franklin as well as a few patches. Franklin enhances the app experience with a brand new videojs-based video player.
|
||||
|
||||
* Other new features in Franklin include:
|
||||
- The ability to continue watching videos in pop out mode
|
||||
- Support of range requests (streaming)
|
||||
- The ability to block channels app-wide
|
||||
|
||||

|
||||
|
||||
#### Video Player and Download Settings
|
||||
|
||||
The new video player fixes a number of bugs and includes new features like volume control, ability to play more video codecs, and you can also skip anywhere in the video instantly.
|
||||
|
||||
Did you say you don't want to download every video? We heard your feedback! There are two new settings for saving hosted content and files. Users who wish to disable either or both can do so.
|
||||
|
||||

|
||||
|
||||
#### LBRY.tv {#web}
|
||||
|
||||
Over the last few months, we’ve been running a view-only pilot of [beta.lbry.tv](https://beta.lbry.tv), meaning you can view free content, but many of the other features like wallets, rewards, and publishing have been disabled.
|
||||
|
||||
We also added some tags so when you share a LBRY file on social media such as Twitter or Facebook, you will see a preview and description of the actual content instead of a generic LBRY image.
|
||||
|
||||

|
||||
|
||||
#### LBRY for Android {#android}
|
||||
|
||||
Announcing the release of Butterfly! Since our last update, the Android app has been playing catchup with the Desktop app’s discovery features - this includes the ability to follow tags and explore tags, create channels, and publish (and edit!) content. We’re also excited that some of the more profound performance problems with the Android app have been resolved. The publish process now includes automatic uploading of thumbnails, and you can also tag your content, create a channel, select a URL, and adjust your default LBC bid.
|
||||
|
||||
All of the [details of the latest release are here.](https://lbry.com/news/butterfly-flits-onto-the-scene)
|
||||
|
||||
#### New Daily Rewards! {#rewards}
|
||||
|
||||
Weekly rewards tied to the LBRYCast email have gone away, but now you can earn even more LBC with the new daily watch rewards! Each day you watch a video, you'll receive a random award of between 1 and 100 LBC. Enjoy!
|
||||
|
||||
### Hacktoberfest is Here! {#hacktoberfest}
|
||||
|
||||
As an Open Source company, LBRY is excited to participate in Hacktoberfest again this year! Submit Pull Requests to our Github project repos to earn a brand new limited-edition collectible LBRY Hacktoberfest t-shirt and other swag.
|
||||
|
||||
The details will be [posted here](https://lbry.com/hacktoberfest) as they are available, including requirements to earn swag and other activities we'll be hosting in October.
|
||||
|
||||

|
||||
|
||||
### We're recruiting for existing and new hives! {#new}
|
||||
|
||||
The LBRY Swarm is a community program to promote awareness, use, and development of the LBRY protocol and network. We believe in empowering people across the globe to be able to promote and monetize their content and regain control from corporate-controlled centralized platforms.
|
||||
|
||||
We need your help to grow the Swarm program. There are a number of potential hive focus areas, and we're interested in new hives or for existing hives to curate content in these areas:
|
||||
|
||||
* Fine Art
|
||||
* Photography
|
||||
* Fan Art (think DeviantArt)
|
||||
* Science topics
|
||||
* Craft How-tos
|
||||
* Life Hacks/How-tos
|
||||
* News
|
||||
* Free Speech
|
||||
* Activism
|
||||
* Environment
|
||||
* Arabic
|
||||
* French
|
||||
* Gaming
|
||||
|
||||
If you’re interested in finding out more about the Swarm program, how to start a hive, or join one, [please check out this link.](https://docs.google.com/forms/d/e/1FAIpQLSfDabPptaLx7TI7DeT_dAOZgeulSRD1A-VnYYypbuc_r4wlhA/viewform?usp=sf_link)
|
||||
|
||||
We have a new Discord home for the Swarm, and you [can join here and ask us questions about the program or find an interesting hive!](https://invite.lbry.org)
|
||||
|
||||
### Selected Hive Updates {#hives}
|
||||
|
||||
#### Open Source LBRY
|
||||
|
||||
Open Source LBRY has been focused on uploading all of Project Gutenberg to LBRY. There are a total of over 60,000 books in the project, and you can see works from [Project Gutenberg channel here.](lbry://@Gutenberg#a)
|
||||
|
||||

|
||||
|
||||
#### LBRY India - Blockchain Youth at LPU
|
||||
|
||||
LBRY India hive attended this event, and Clement was featured and spoke about LBRY as an emerging blockchain technology and the opportunities for young adults to get involved! We're excited to see Clement's involvement as Blockchain Youth develops into its own organization.
|
||||
|
||||

|
||||
_Clement tells the audience about LBRY and blockchain opportunities_
|
||||
|
||||

|
||||
_There was a fantastic turnout for the event_
|
||||
|
||||

|
||||
_A LBRY user talks about how she uses LBRY to host her content_
|
||||
|
||||
#### LBRY.social
|
||||
|
||||
This hive has been working on many different objectives, including a weblog. Here is an [excellent case study](https://lbry.social/blog/using-lbry-well/) they've written about Turkish creator Efe Aydal and his success on the LBRY platform.
|
||||
|
||||
Dr. Brendon Brewer has been working with Mark Firth to create a visualization of LBRY statistics. Take a look here to see their progress: https://lbry.social/lbrynomics/
|
||||
|
||||
[Brendon Brewer LBRYnomics](https://www.brendonbrewer.com/lbrynomics/)
|
||||
|
||||
#### China Hive
|
||||
|
||||
The China Hive is attending the Blockchain World Forum Conference, October 24-25 in Shenzhen, through a grant from the LBRY fund. The website for [the conference is here.](http://sz.thebwf.com/)
|
||||
|
||||
#### New LBRY Uganda Hive!
|
||||
|
||||
We're excited to have our first hive in Africa!
|
||||
|
||||
Our Uganda community held their first LBRY meetup. We love to see LBRY, open source, and blockchain technologies spread worldwide.
|
||||
|
||||

|
||||

|
||||
|
||||
LBRY Uganda has even created special t-shirts for their members.
|
||||
|
||||

|
||||
|
||||
#### Noob Team Hive
|
||||
|
||||
Noob Team Hive is always coming up with imaginative ideas! Most recently, they created an activity easy enough for any skill level to participate. They love our LBRY mascot, Yerbil the Gerbil, and have created fan art variations:
|
||||
|
||||

|
||||
|
||||
### LBRY App Language Translations {#i18n}
|
||||
|
||||
We have internationalized the LBRY App! We have added new languages like Bahasa Indonesia, Polish and German, and we will soon have many others. If you're interested in adding a language or helping translate please contact [Julie.](mailto:julie@lbry.com)
|
||||
|
||||
### Community Block Explorer {#explorer}
|
||||
|
||||
A community member by the name of [Alessandro Spallina](https://github.com/AlessandroSpallina) became interested in the LBRY ecosystem and wanted to implement a more modern and fully featured block explorer that exposes important metrics of the LBRY blockchain.
|
||||
|
||||
You can check out his [GitHub issue](https://github.com/lbryio/block-explorer/issues/67) outlining what he plans on developing or you can go straight to the explorer prototype at [lbryexplorer.tech](https://lbryexplorer.tech/) to give it a shot.
|
||||
|
||||
He’d appreciate any feedback on the GitHub issue and current prototype - you can leave a comment on GitHub or reach out on [Discord](https://chat.lbry.com) #dev channel by tagging @SK3LA.
|
||||
|
||||

|
||||
|
||||
### Since you've read this far here's your dessert! 🍦 {#dessert}
|
||||
|
||||
We appreciate your attention and now we have a little dessert for you. Enter `lbry-ice-cream` in the desktop app and get a few sprinkles of LBCs!
|
||||
|
||||
## Want to Develop on the LBRY Ecosystem?
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [contributing guide](https://lbry.tech/contribute) and our [LBRY App specific contributing document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Make sure you have turned on the Developer option in your email preferences (see app overview page), or sign up at [lbry.tech](https://lbry.tech). We also have a [LBRY Discourse Forum](https://discourse.lbry.io) where developers can interact with the team and ask questions across all our different projects.
|
||||
|
||||
If you aren’t part of our Discord community yet, [join us](https://chat.lbry.com) anytime and say hello!
|
||||
|
||||
[Back to **Community Updates**](#updates)
|
||||
|
||||
Thanks for supporting LBRY - stay tuned for more news and updates! And if you haven’t downloaded the [LBRY app](https://lbry.com/get?auto=1) yet, what are you waiting for?
|
||||
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
author: jeremy-kauffman
|
||||
title: 'Hacktoberfest 2019!'
|
||||
date: '2019-10-01 11:37:00'
|
||||
cover: 'Hacktoberfest.jpg'
|
||||
og: 'https://spee.ch/@lbryblog:e/hacktoberfest2019.png'
|
||||
category: developers
|
||||
---
|
||||
|
||||
It's fall and...
|
||||
|
||||
*Hoot hoot!*
|
||||
|
||||
Do you hear that? Is it an owl?
|
||||
|
||||
Actually, it’s people expressing their excitement about this year’s Hacktoberfest!
|
||||
|
||||
Every October, LBRY and many other open-source companies make a special effort to welcome new contributors. Throughout the month, we’ll be guiding new contributors, hosting information sessions and events, and giving out some sweet swag and rewards to those who participate.
|
||||
|
||||

|
||||
|
||||
## How To Participate
|
||||
|
||||
If you’re a developer that is comfortable working in Python, C++, JavaScript, or HTML/CSS, there’s plenty to be done from big to small.
|
||||
|
||||
If you are a capable reader (and if you’re a developer, we cannot recommend this skill strongly enough), our [contributor’s guide](https://lbry.tech/contribute) outlines existing LBRY repos, languages, and how to get started.
|
||||
|
||||
For Hacktoberfest specifically, we’ve focused on making sure there are newcomer-friendly issues for the following repos:
|
||||
|
||||
| Repo | Language | Description | Hacktoberfest Issues
|
||||
--- | --- | --- | ---
|
||||
| [lbrycrd](https://github.com/lbryio/lbrycrd) | C++ | The LBRY blockchain daemon. | [Issues](https://github.com/lbryio/lbrycrd/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
|
||||
| [lbry-sdk](https://github.com/lbryio/lbry-sdk) | Python | The SDK used by most LBRY apps, includes SPV wallet, data network, and more. | [Issues](https://github.com/lbryio/lbry-sdk/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
|
||||
| [lbry-desktop](https://github.com/lbryio/lbry-desktop) | JavaScript (React) | The official desktop client and soon-to-be lbry.tv frontend. | [Issues](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
|
||||
| [lbry-android](https://github.com/lbryio/lbry-android) | JavaScript (React) | The official Android browser. | [Issues](https://github.com/lbryio/lbry-android/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
|
||||
|
||||
|
||||
All of the above repos have user-friendly READMEs to get up and running because around here we’ve got [standards](https://lbry.tech/resources/repository-standards). And if you’re looking for some personal help, you can [join our chat](https://chat.lbry.com/), post on [our forum](http://forum.lbry.tech/), or join a [live session](#events).
|
||||
|
||||
Note: the chat link goes to LBRY’s main public chat. Post a message in binary* to let everyone know you are a developer and you will be whisked away to secret lairs.
|
||||
|
||||
*You don’t have to do this and as far as I know no one ever has, but it would presumably work.
|
||||
|
||||
## Swagtoberfest and Token Giveaways
|
||||
|
||||
Anyone who makes any contribution at all, even a one line typo fix, will receive a LBRY sticker.
|
||||
|
||||
Anyone who contributes anything of any substance* will receive a sticker, LBRY t-shirt, and more.
|
||||
|
||||
And as always, anyone who contributes will receive LBC as [appreciation](https://lbry.com/faq/appreciation).
|
||||
|
||||
Additionally, this month only, every contributor, new or returning, will receive a 10,000 LBC bonus for their first PR of this month.
|
||||
|
||||
T-shirts and stickers will be the above Hacktoberfest image.
|
||||
|
||||
*We’re going to be very inclusive as counting PRs as substantive, but due to some people making drive-by PRs to earn shirts, we’ve introduced this additional qualifier.
|
||||
|
||||
## <a name="events"></a>Events
|
||||
|
||||
This year, we’ll be hosting several live video sessions.
|
||||
|
||||
If you want to live help with screen sharing and extended demos, you can join these sessions during the hours listed. A LBRY developer will be there, waiting, lurking, and just when you least expect it… will answer your questions politely and promptly.
|
||||
|
||||
Video sessions will happen on the following dates and times:
|
||||
|
||||
- Thursday, October 3rd, 18:00-22:00 UTC
|
||||
- Sunday, October 13th, 15:00-19:00 UTC
|
||||
- Tuesday, October 22nd, 20:00-24:00 UTC
|
||||
|
||||
For all sessions, visit [lbry.com/doitlive](https://lbry.com/doitlive). This link may not function until shortly before each event.
|
||||
|
||||
## Developer Credits Program
|
||||
|
||||
New developers with valid GitHub accounts can receive 100 LBC for testing and getting started. You can claim that [here](https://lbry.tech/developer-program).
|
||||
|
Before Width: | Height: | Size: 1.2 MiB |
@@ -32,8 +32,11 @@ class Controller
|
||||
unset($viewParameters[View::LAYOUT_PARAMS]);
|
||||
|
||||
$content = View::render($viewTemplate, $viewParameters + ['fullPage' => true]);
|
||||
|
||||
Response::setContent($layout ? View::render('layout/basic', ['content' => $content] + $layoutParams) : $content);
|
||||
if ($layout) {
|
||||
$content = View::render('layout/basic', ['content' => $content] + $layoutParams);
|
||||
}
|
||||
$content = View::safeExternalLinks($content, Request::getHost());
|
||||
Response::setContent($content);
|
||||
}
|
||||
|
||||
Response::setDefaultSecurityHeaders();
|
||||
@@ -135,10 +138,15 @@ class Controller
|
||||
$router->get('/verify/{token}', 'AcquisitionActions::executeVerify');
|
||||
$router->get('/verify', 'AcquisitionActions::executeAutoVerify');
|
||||
|
||||
$router->get('/follow/{claim}', 'AcquisitionActions::executeFollowCampaign');
|
||||
|
||||
$router->get('/i18n/get/{project}/{resource}/{language}.json', 'i18nActions::executeServeTranslationFile');
|
||||
|
||||
$router->get('/news/category/{category}', 'ContentActions::executePostCategoryFilter');
|
||||
|
||||
$router->post('/set-culture', 'i18nActions::setCulture');
|
||||
$router->post('/i18n/set-culture', 'i18nActions::setCulture');
|
||||
|
||||
$router->get('/snapshot/{type}', 'DownloadActions::executeDownloadSnapshot');
|
||||
|
||||
$permanentRedirectsPath = ROOT_DIR . '/data/redirect/permanent.yaml';
|
||||
$tempRedirectsPath = ROOT_DIR . '/data/redirect/temporary.yaml';
|
||||
@@ -168,7 +176,7 @@ class Controller
|
||||
return static::redirect('/' . strtolower($slug), 301);
|
||||
}
|
||||
if (View::exists('page/' . $slug)) {
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
return ['page/' . $slug, []];
|
||||
} else {
|
||||
return NavActions::execute404();
|
||||
|
||||
@@ -16,11 +16,18 @@ class Session
|
||||
{
|
||||
ini_set('session.cookie_secure', IS_PRODUCTION); // send cookie over ssl only
|
||||
ini_set('session.cookie_httponly', true); // no js access to cookies
|
||||
|
||||
session_start();
|
||||
|
||||
/*
|
||||
* session_start automatically adds headers because lolphp, let's remove them and handle it ourselves
|
||||
*/
|
||||
header_remove('cache-control');
|
||||
header_remove('pragma');
|
||||
header_remove('expires');
|
||||
|
||||
if (!static::get('secure_and_httponly_set')) {
|
||||
session_regenerate_id(); // ensure that old cookies get new settings
|
||||
session_regenerate_id(); // ensure that old cookies get new settings
|
||||
}
|
||||
static::set('secure_and_httponly_set', true);
|
||||
|
||||
|
||||
@@ -2,6 +2,24 @@
|
||||
|
||||
class AcquisitionActions extends Actions
|
||||
{
|
||||
public static function executeFollowCampaign(string $claimName)
|
||||
{
|
||||
$claim = ChainQuery::findChannelClaim($claimName);
|
||||
|
||||
if (!$claim || !$claim['source_url']) {
|
||||
Controller::redirect('/');
|
||||
}
|
||||
|
||||
$title = $claim['title'] ?: $claim['name'];
|
||||
$coverUrl = $claim['source_url'];
|
||||
return ['acquisition/follow_campaign', [
|
||||
'claim' => $claim,
|
||||
'claimCount' => ChainQuery::countClaimsInChannel($claim['claim_id']),
|
||||
'title' => $title,
|
||||
'coverUrl' => $coverUrl,
|
||||
]];
|
||||
}
|
||||
|
||||
public static function executeYouTube(string $version = '')
|
||||
{
|
||||
$errorMessage = Request::getParam('error_message', '');
|
||||
@@ -18,16 +36,19 @@ class AcquisitionActions extends Actions
|
||||
|
||||
public static function executeVerify(string $token)
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
return ['acquisition/verify', ['token' => $token]];
|
||||
}
|
||||
|
||||
public static function executeAutoVerify()
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
return ['acquisition/auto-verify'];
|
||||
}
|
||||
|
||||
public static function executeYoutubeToken()
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
$channelName = Request::encodeStringFromUser($_POST['desired_lbry_channel_name']);
|
||||
$immediateSync = (boolean)$_POST['immediate_sync'];
|
||||
|
||||
@@ -47,6 +68,7 @@ class AcquisitionActions extends Actions
|
||||
|
||||
public static function executeYoutubeStatus(string $token)
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
$data = LBRY::statusYoutube($token);
|
||||
|
||||
if (!$data['success']) {
|
||||
|
||||
@@ -28,27 +28,27 @@ class ContentActions extends Actions
|
||||
|
||||
public static function executeHome(): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
return ['page/home'];
|
||||
}
|
||||
|
||||
//
|
||||
public static function executeOrg(): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
return ['page/org'];
|
||||
}
|
||||
|
||||
public static function executeTv(): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
return ['page/tv'];
|
||||
}
|
||||
//
|
||||
|
||||
public static function executeNews(string $slug = null): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
if (!$slug || $slug == static::SLUG_RSS) {
|
||||
$posts = array_filter(
|
||||
@@ -90,7 +90,7 @@ class ContentActions extends Actions
|
||||
|
||||
public static function executeFaq(string $slug = null): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
if (!$slug) {
|
||||
$allPosts = Post::find(static::VIEW_FOLDER_FAQ, Post::SORT_ORD_ASC);
|
||||
@@ -139,7 +139,7 @@ class ContentActions extends Actions
|
||||
|
||||
public static function executeCreditReports(string $year = null, string $month = null): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
$posts = Post::find(static::VIEW_FOLDER_CREDIT_REPORTS);
|
||||
|
||||
@@ -150,7 +150,7 @@ class ContentActions extends Actions
|
||||
|
||||
public static function executeCreditReport(string $year = null, string $quarter = null): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
try {
|
||||
$post = Post::load(static::SLUG_CREDIT_REPORTS . '/' . $year . '-Q' . $quarter);
|
||||
@@ -172,7 +172,7 @@ class ContentActions extends Actions
|
||||
|
||||
public static function executeBounty(string $slug = null): array
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
|
||||
|
||||
@@ -276,7 +276,7 @@ class ContentActions extends Actions
|
||||
//
|
||||
// $zip->close();
|
||||
//
|
||||
// Response::enableHttpCache();
|
||||
// Response::enablePublicImmutableCache();
|
||||
// Response::setDownloadHttpHeaders($zipFileName, 'application/zip', filesize($zipPath));
|
||||
//
|
||||
// return ['internal/zip', [
|
||||
@@ -320,7 +320,7 @@ class ContentActions extends Actions
|
||||
}
|
||||
public static function executePostCategoryFilter(string $category)
|
||||
{
|
||||
Response::enableHttpCache();
|
||||
Response::enablePublicImmutableCache();
|
||||
|
||||
$filter_post = [];
|
||||
|
||||
|
||||
@@ -15,6 +15,23 @@ class DownloadActions extends Actions
|
||||
return Controller::redirect(GitHub::getRepoReleaseUrl($repo, OS::getOsForExtension($ext), $allowPrerelease) ?: '/get', 302);
|
||||
}
|
||||
|
||||
public static function executeDownloadSnapshot(string $type)
|
||||
{
|
||||
if (!in_array($type, ['blockchain', 'wallet'])) {
|
||||
return ['page/404'];
|
||||
}
|
||||
|
||||
$bucketName = "snapshots.lbry.com";
|
||||
$bucket = S3::getBucket($bucketName, "$type/");
|
||||
|
||||
if (!count($bucket)) {
|
||||
return ['page/404'];
|
||||
}
|
||||
|
||||
krsort($bucket);
|
||||
|
||||
return Controller::redirect("https://$bucketName/" . array_keys($bucket)[0], 302);
|
||||
}
|
||||
/*
|
||||
* this is a quick fix to add android, prob not proper design
|
||||
*/
|
||||
|
||||
@@ -51,6 +51,7 @@ class MailActions extends Actions
|
||||
|
||||
public static function executeUnsubscribe(string $email)
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
$decodedEmail = Encoding::base64DecodeUrlsafe(urldecode($email));
|
||||
if (!$decodedEmail) {
|
||||
return ['mail/unsubscribe', ['error' => 'Invalid unsubscribe link']];
|
||||
@@ -62,6 +63,7 @@ class MailActions extends Actions
|
||||
|
||||
public static function editEmailSettings(string $token)
|
||||
{
|
||||
Response::disableHttpCache();
|
||||
list($status, $headers, $response) = LBRY::emailStatus($token);
|
||||
if ($status == 403) {
|
||||
//Catch 403 to return elegant error message.
|
||||
@@ -78,45 +80,19 @@ class MailActions extends Actions
|
||||
|
||||
public static function prepareSettingsFormPartial(array $vars)
|
||||
{
|
||||
return $vars + [
|
||||
'tagMetadata' => [
|
||||
'3d-printing' => [
|
||||
'label' => '3D Printing',
|
||||
'description' => 'Receive updates, tips, and new content suggestions related to 3D Printing.'
|
||||
],
|
||||
'android' => [
|
||||
'label' => 'Android',
|
||||
'description' => 'Be an Android beta tester, earn LBC, and receive notification when the app goes live!'
|
||||
],
|
||||
'college' => [
|
||||
'label' => 'University',
|
||||
'description' => 'LBRY has special programs and opportunities for people in school.'
|
||||
],
|
||||
'creator' => [
|
||||
'label' => 'Creator',
|
||||
'description' => 'Get the most out of the stuff you create with tips and feedback from LBRY.'
|
||||
],
|
||||
'consumer' => [
|
||||
'label' => 'Content Lover',
|
||||
'description' => 'Learn how to get the most out of LBRY as someone who just wants to find cool stuff.'
|
||||
],
|
||||
'developer' => [
|
||||
'label' => 'Developer',
|
||||
'description' => 'Receive technical updates and other news intended for those who are familiar with software engineering.'
|
||||
],
|
||||
'ios' => [
|
||||
'label' => 'iPhone',
|
||||
'description' => 'Be an iOS alpha tester, earn LBC, and receive notification when the app goes live!'
|
||||
],
|
||||
'reward' => [
|
||||
'label' => 'Rewards',
|
||||
'description' => 'Receive emails about the latest rewards that are available to LBRY users.'
|
||||
],
|
||||
'subscription' => [
|
||||
'label' => 'Subscriptions',
|
||||
'description' => 'Stay up to date on the latest content from your favorite creators.'
|
||||
],
|
||||
]
|
||||
$tags = LBRY::listTags($vars['token']);
|
||||
$tagMetadata = [];
|
||||
$specialDisplayNames = [
|
||||
'ios' => 'iOS'
|
||||
];
|
||||
foreach($tags as $tag) {
|
||||
if ($tag['is_user_addable']) {
|
||||
$tagMetadata[$tag['name']] = [
|
||||
'label' => $specialDisplayNames[$tag['name']] ?? ucwords(str_replace(['-', '_'], ' ', $tag['name'])),
|
||||
'description' => $tag['description']
|
||||
];
|
||||
}
|
||||
}
|
||||
return $vars + ['tagMetadata' => $tagMetadata];
|
||||
}
|
||||
}
|
||||
@@ -22,4 +22,26 @@ class i18nActions extends Actions
|
||||
|
||||
return Controller::redirect(Request::getReferrer());
|
||||
}
|
||||
|
||||
public static function executeServeTranslationFile(string $project, string $resource, string $language)
|
||||
{
|
||||
if (!Transifex::isConfigured()) {
|
||||
throw new Exception('Please set Config::TRANSIFEX_API_KEY in your configuration.');
|
||||
}
|
||||
|
||||
$usecache = !Request::getParam('nocache');
|
||||
$json = Transifex::getTranslationResourceFile($project, $resource, $language, $usecache);
|
||||
|
||||
if (!$json) {
|
||||
return NavActions::execute404();
|
||||
}
|
||||
|
||||
Response::setHeader(Response::HEADER_CROSS_ORIGIN, "*");
|
||||
|
||||
if ($usecache) {
|
||||
Response::enablePublicMutableCache(md5(json_encode($json)));
|
||||
}
|
||||
|
||||
return View::renderJson($json);
|
||||
}
|
||||
}
|
||||
@@ -1,6 +1,9 @@
|
||||
<?php
|
||||
|
||||
$config = [];
|
||||
// $config[Config::CHAINQUERY_DSN] = '';
|
||||
// $config[Config::CHAINQUERY_USERNAME] = '';
|
||||
// $config[Config::CHAINQUERY_PASSWORD] = '';
|
||||
// $config[Config::GITHUB_KEY] = '';
|
||||
// $config[Config::GITHUB_APP_CLIENT_ID] = ''; //optional, increases API rate limit
|
||||
// $config[Config::GITHUB_APP_CLIENT_SECRET] = '';
|
||||
@@ -9,4 +12,5 @@ $config = [];
|
||||
// $config[Config::MAILCHIMP_KEY] = '';
|
||||
// $config[Config::AWS_LOG_ACCESS_KEY] = '';
|
||||
// $config[Config::AWS_LOG_SECRET_KEY] = '';
|
||||
// $config[Config::TRANSIFEX_API_KEY] = '';
|
||||
return $config;
|
||||
@@ -17,6 +17,7 @@
|
||||
/faq/claimtrie-implementation: https://lbry.tech/resources/lbry-claimtrie
|
||||
/faq/proof-algorithm: https://lbry.tech/resources/pow
|
||||
/faq/regtest-setup-guide: https://lbry.tech/resources/regtest-setup
|
||||
/faq/bounty https://lbry.com/faq/how-to-get-lbry-command-line
|
||||
|
||||
# FAQ
|
||||
/faq/tips: /faq/appreciation
|
||||
@@ -54,6 +55,7 @@
|
||||
/nothing-here: /news
|
||||
/There: /news
|
||||
/youtube/cdSSo: /news
|
||||
/news/hacktoberfest: /hacktoberfest
|
||||
/news/$1.2b-market-cap-we-dont-care: /news/1.2b-market-cap-we-dont-care
|
||||
/news/boom: /news/boombust
|
||||
/news/tag/freedom-of-information: /news/crypto-freedom
|
||||
@@ -111,4 +113,8 @@
|
||||
/feedback: /learn
|
||||
/press-kit.zip: /press-kit
|
||||
/news/tag/events: /roadmap
|
||||
/privacy: /privacypolicy
|
||||
# /publish: /youtube
|
||||
|
||||
# Images
|
||||
/img/lbry-ui.png: /img/og-image.png
|
||||
@@ -5,6 +5,7 @@
|
||||
/swarm: https://docs.google.com/document/d/1W4chXeUvF4I9T3lVyyeZ-N1SUuyoMrp_QH_ITA9BrZ4/edit#
|
||||
/deck.pdf: "https://www.dropbox.com/s/0xj4vgucsbi8rtv/lbry-deck.pdf?dl=1"
|
||||
/LBRY-deck.pdf: "https://www.dropbox.com/s/0xj4vgucsbi8rtv/lbry-deck.pdf?dl=1"
|
||||
/hacktoberfest: /news/hacktoberfest-2019
|
||||
/security: /faq/security
|
||||
/youtubers: "https://traction.lbry.io/public/question/8dfc23e2-71e7-44cb-9740-0aec18d1da73"
|
||||
/support: /faq/support
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
<?php
|
||||
|
||||
|
||||
class ChainQuery
|
||||
{
|
||||
protected static $pdo = null;
|
||||
|
||||
public static function getInstance()
|
||||
{
|
||||
if (!static::$pdo) {
|
||||
static::$pdo = new PDO(Config::get(Config::CHAINQUERY_DSN),
|
||||
Config::get(Config::CHAINQUERY_USERNAME), Config::get(Config::CHAINQUERY_PASSWORD));
|
||||
}
|
||||
return static::$pdo;
|
||||
}
|
||||
|
||||
public static function findChannelClaim($claimName)
|
||||
{
|
||||
$claimName = '@' . trim($claimName, '@');
|
||||
$stmt = static::getInstance()->prepare("SELECT * FROM claim c WHERE c.name = ? AND c.bid_state = ?");
|
||||
$stmt->execute([$claimName, "controlling"]);
|
||||
return $stmt->fetch();
|
||||
}
|
||||
|
||||
public static function countClaimsInChannel($claimId)
|
||||
{
|
||||
$stmt = static::getInstance()->prepare("SELECT COUNT(*) FROM claim c WHERE c.publisher_id = ?");
|
||||
$stmt->execute([$claimId]);
|
||||
$result = $stmt->fetch();
|
||||
return $result[0] ?? 0;
|
||||
}
|
||||
}
|
||||
@@ -3,6 +3,8 @@
|
||||
|
||||
class LBRY
|
||||
{
|
||||
const DEFAULT_TIMEOUT = 10;
|
||||
|
||||
public static function getApiUrl($endpoint)
|
||||
{
|
||||
if (!strlen(Config::get(Config::LBRY_API_SERVER)) > 0) {
|
||||
@@ -21,39 +23,40 @@ class LBRY
|
||||
return $response['data']['lbc_usd'] ?? 0;
|
||||
}
|
||||
|
||||
public static function listTags($authToken)
|
||||
{
|
||||
$response = Curl::get(static::getApiUrl('/tag/list'), ['auth_token' => $authToken], ['json_response' => true]);
|
||||
return $response['data'] ?? [];
|
||||
}
|
||||
|
||||
public static function subscribe($email, $tag = null)
|
||||
{
|
||||
return Curl::post(static::getApiUrl('/list/subscribe'), array_filter([
|
||||
'email' => $email,
|
||||
'tag' => $tag,
|
||||
]), ['json_response' => true]);
|
||||
}
|
||||
|
||||
public static function editEmailSettings($token, $email, $isPrimary =null, $isEnabled = null)
|
||||
{
|
||||
return Curl::post(static::getApiUrl('/user_email/edit'), ['auth_token' => $token], ['email' => $email], ['is_primary' => $isPrimary], ['is_enabled' => $isEnabled]);
|
||||
]), ['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
|
||||
public static function emailStatus($token)
|
||||
{
|
||||
list($status, $headers, $body) = Curl::doCurl(Curl::POST, static::getApiUrl('/user_email/status'), ['auth_token' => $token], ['json_response' => true]);
|
||||
list($status, $headers, $body) = Curl::doCurl(
|
||||
Curl::POST,
|
||||
static::getApiUrl('/user_email/status'),
|
||||
['auth_token' => $token],
|
||||
['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]
|
||||
);
|
||||
return array($status,$headers,$body);
|
||||
}
|
||||
|
||||
public static function applyTags($type, $token, $tags)
|
||||
{
|
||||
return Curl::post(static::getApiUrl('/user_tag/edit'), ['auth_token' => $token], [$type => $tags]);
|
||||
}
|
||||
|
||||
public static function unsubscribe($email)
|
||||
{
|
||||
return Curl::post(static::getApiUrl('/user/unsubscribe'), ['email' => $email], ['json_response' => true]);
|
||||
return Curl::post(static::getApiUrl('/user/unsubscribe'), ['email' => $email], ['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
|
||||
public static function connectYoutube($channel_name, $immediateSync = false)
|
||||
{
|
||||
// Uncomment next line for production and comment other return
|
||||
return Curl::post(static::getApiUrl('/yt/new'), [ 'desired_lbry_channel_name' => $channel_name, 'immediate_sync' => $immediateSync, 'type' => 'sync' ], [ 'json_response' => true ]);
|
||||
return Curl::post(static::getApiUrl('/yt/new'), [ 'desired_lbry_channel_name' => $channel_name, 'immediate_sync' => $immediateSync, 'type' => 'sync' ], [ 'json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT ]);
|
||||
|
||||
// Uncomment next line for development and comment other return (this also requires the testnet API)
|
||||
// return Curl::post(static::getApiUrl('/yt/new'), [
|
||||
@@ -69,12 +72,12 @@ class LBRY
|
||||
// Check the sync status
|
||||
public static function statusYoutube($status_token)
|
||||
{
|
||||
return Curl::get(static::getApiUrl('/yt/status'), ['status_token' => $status_token], ['json_response' => true]);
|
||||
return Curl::get(static::getApiUrl('/yt/status'), ['status_token' => $status_token], ['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
|
||||
public static function youtubeReward()
|
||||
{
|
||||
return CurlWithCache::post(static::getApiUrl('/yt/rewards'), [], ['cache' => 3600, 'json_response' => true]);
|
||||
return CurlWithCache::post(static::getApiUrl('/yt/rewards'), [], ['cache' => 3600, 'json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
|
||||
public static function editYouTube($status_token, $channel_name, $email, $sync_consent)
|
||||
@@ -97,13 +100,13 @@ class LBRY
|
||||
$postParams['new_preferred_channel'] = $channel_name;
|
||||
}
|
||||
|
||||
return Curl::post(static::getApiUrl("/yt/update"), $postParams, ['json_response' => true]);
|
||||
return Curl::post(static::getApiUrl("/yt/update"), $postParams, ['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
|
||||
public static function logWebVisitor($site, $visitorID, $IPAddress)
|
||||
{
|
||||
if (IS_PRODUCTION) {
|
||||
return Curl::post(static::getApiUrl("/visitor/new"), ['site' => $site, 'visitor_id' => $visitorID, 'ip_address' => $IPAddress], ['json_response' => true]);
|
||||
return Curl::post(static::getApiUrl("/visitor/new"), ['site' => $site, 'visitor_id' => $visitorID, 'ip_address' => $IPAddress], ['json_response' => true, 'timeout' => static::DEFAULT_TIMEOUT]);
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,18 @@
|
||||
<?php
|
||||
|
||||
|
||||
class Transifex
|
||||
{
|
||||
public static function isConfigured() {
|
||||
return (boolean)Config::get(Config::TRANSIFEX_API_KEY);
|
||||
}
|
||||
|
||||
public static function getTranslationResourceFile($project, $resource, $language, $cache = true)
|
||||
{
|
||||
$url = "https://www.transifex.com/api/2/project/$project/resource/$resource/translation/$language?file=1";
|
||||
return json_decode(CurlWithCache::get($url, [], [
|
||||
'password' => 'api:' . Config::get(Config::TRANSIFEX_API_KEY),
|
||||
'cache' => $cache ? 1000 * 60 * 60 * 8 : false
|
||||
]), true);
|
||||
}
|
||||
}
|
||||
@@ -6,12 +6,16 @@ class Config
|
||||
|
||||
//Constant to help with managing strings
|
||||
const IS_PROD = "is_prod";
|
||||
const CHAINQUERY_DSN = 'chainquery_dsn';
|
||||
const CHAINQUERY_USERNAME = 'chainquery_username';
|
||||
const CHAINQUERY_PASSWORD = 'chainquery_password';
|
||||
const GITHUB_KEY = "github_key";
|
||||
const GITHUB_APP_CLIENT_ID = "github_app_client_id";
|
||||
const GITHUB_APP_CLIENT_SECRET = "github_app_client_secret";
|
||||
const GITHUB_PERSONAL_AUTH_TOKEN = 'github_personal_auth_token';
|
||||
const LBRY_API_SERVER = "lbry_api_server";
|
||||
const MAILCHIMP_KEY = "mailchimp_key";
|
||||
const TRANSIFEX_API_KEY = 'transifex_api_key';
|
||||
const AWS_LOG_ACCESS_KEY = "aws_log_access_key";
|
||||
const AWS_LOG_SECRET_KEY = "aws_log_secret_key";
|
||||
const MAILGUN_API_KEY = "mailgun_api_key";
|
||||
|
||||
@@ -20,7 +20,7 @@ class OS
|
||||
'Android',
|
||||
'icon-android',
|
||||
false,
|
||||
false,
|
||||
"Android",
|
||||
"<span class='icon-android icon-fw'></span> Android"
|
||||
];
|
||||
|
||||
@@ -30,7 +30,7 @@ class OS
|
||||
'iOS',
|
||||
'icon-mobile',
|
||||
false,
|
||||
false,
|
||||
"iOS",
|
||||
"<span class='icon-ios icon-fw'></span> iOS"
|
||||
];
|
||||
|
||||
|
||||
@@ -309,6 +309,11 @@ class Post
|
||||
{
|
||||
$urls = [];
|
||||
|
||||
$metadata = $this->getMetadata();
|
||||
if (isset($metadata['og']) && $metadata['og']) {
|
||||
$urls[] = $metadata['og'];
|
||||
}
|
||||
|
||||
$cover = $this->getCover();
|
||||
if ($cover) {
|
||||
$urls[] = 'https://' . Request::getHost() . '/img/blog-covers/' . $cover;
|
||||
@@ -321,7 +326,7 @@ class Post
|
||||
$urls = array_merge($urls, $matches[1]);
|
||||
}
|
||||
|
||||
return $urls;
|
||||
return array_unique($urls);
|
||||
}
|
||||
|
||||
protected function markdownToText($markdown)
|
||||
|
||||
@@ -6,7 +6,6 @@ class Response
|
||||
const HEADER_LOCATION = 'Location';
|
||||
|
||||
const HEADER_CACHE_CONTROL = 'Cache-Control';
|
||||
const HEADER_LAST_MODIFIED = 'Last-Modified';
|
||||
const HEADER_ETAG = 'Etag';
|
||||
|
||||
const HEADER_CONTENT_TYPE = 'Content-Type';
|
||||
@@ -26,11 +25,12 @@ class Response
|
||||
],
|
||||
'css' => ['/css/all.css']
|
||||
];
|
||||
protected static $headers = [];
|
||||
protected static $headers = [
|
||||
'Cache-Control' => 'private, no-cache'
|
||||
];
|
||||
protected static $headersSent = false;
|
||||
protected static $content = '';
|
||||
protected static $contentSent = false;
|
||||
protected static $isHeadersOnly = false;
|
||||
protected static $gzipResponseContent = true;
|
||||
protected static $metaImages = [];
|
||||
protected static $facebookAnalyticsType = "PageView";
|
||||
@@ -71,7 +71,7 @@ class Response
|
||||
|
||||
public static function getMetaTitle()
|
||||
{
|
||||
return static::$metaTitle;
|
||||
return trim(static::$metaTitle);
|
||||
}
|
||||
|
||||
public static function guessMetaTitle($content)
|
||||
@@ -82,11 +82,11 @@ class Response
|
||||
if ($headerValue == '1' || !$title) {
|
||||
$title = $titleMatches[2][$matchIndex];
|
||||
if ($headerValue == '1') {
|
||||
return $title;
|
||||
return trim($title);
|
||||
}
|
||||
}
|
||||
}
|
||||
return $title;
|
||||
return trim($title);
|
||||
}
|
||||
|
||||
public static function getJsCalls()
|
||||
@@ -144,8 +144,21 @@ class Response
|
||||
|
||||
public static function send()
|
||||
{
|
||||
$status = static::getHeader(static::HEADER_STATUS);
|
||||
$sendContent = true;
|
||||
if ((!$status || $status === 200) &&
|
||||
static::getHeader(static::HEADER_ETAG) &&
|
||||
Request::getHttpHeader('If-None-Match', null) === static::getHeader(static::HEADER_ETAG)
|
||||
) {
|
||||
static::setHeader(static::HEADER_STATUS, 304);
|
||||
$sendContent = false;
|
||||
}
|
||||
|
||||
static::sendHeaders();
|
||||
static::sendContent();
|
||||
|
||||
if ($sendContent) {
|
||||
static::sendContent();
|
||||
}
|
||||
}
|
||||
|
||||
public static function setContent(string $content)
|
||||
@@ -164,18 +177,11 @@ class Response
|
||||
throw new LogicException('Content has already been sent. It cannot be sent twice');
|
||||
}
|
||||
|
||||
if (!static::$isHeadersOnly) {
|
||||
echo static::$content;
|
||||
}
|
||||
echo static::$content;
|
||||
|
||||
static::$contentSent = true;
|
||||
}
|
||||
|
||||
public static function setIsHeadersOnly(bool $isHeadersOnly = true)
|
||||
{
|
||||
static::$isHeadersOnly = $isHeadersOnly;
|
||||
}
|
||||
|
||||
public static function setDownloadHttpHeaders($name, $type = null, $size = null, $noSniff = true)
|
||||
{
|
||||
static::setBinaryHttpHeaders($type, $size, $noSniff);
|
||||
@@ -192,35 +198,23 @@ class Response
|
||||
]));
|
||||
}
|
||||
|
||||
public static function setContentEtag()
|
||||
//public immutable cache = hard-caching (no server checks) until time limit passes
|
||||
public static function enablePublicImmutableCache(int $seconds = 300)
|
||||
{
|
||||
static::setHeader(static::HEADER_ETAG, md5(static::getContent()));
|
||||
static::setHeader(static::HEADER_CACHE_CONTROL, 'public, max-age=' . $seconds);
|
||||
}
|
||||
|
||||
public static function enableHttpCache(int $seconds = 300)
|
||||
//public mutable cache = soft-caching (requires at least one round trip for headers) as long as etag identifier matches
|
||||
public static function enablePublicMutableCache(string $etag)
|
||||
{
|
||||
static::addCacheControlHeader('max-age', $seconds);
|
||||
static::setHeader('Pragma', 'public');
|
||||
static::setHeader(static::HEADER_CACHE_CONTROL, 'public');
|
||||
static::setHeader(static::HEADER_ETAG, $etag);
|
||||
}
|
||||
|
||||
public static function addCacheControlHeader(string $name, $value = null)
|
||||
//always reload and re-execute this resource, disable any local or intermediary caching
|
||||
public static function disableHttpCache()
|
||||
{
|
||||
$cacheControl = static::getHeader(static::HEADER_CACHE_CONTROL);
|
||||
$currentHeaders = [];
|
||||
if ($cacheControl) {
|
||||
foreach (preg_split('/\s*,\s*/', $cacheControl) as $tmp) {
|
||||
$tmp = explode('=', $tmp);
|
||||
$currentHeaders[$tmp[0]] = $tmp[1] ?? null;
|
||||
}
|
||||
}
|
||||
$currentHeaders[strtr(strtolower($name), '_', '-')] = $value;
|
||||
|
||||
$headers = [];
|
||||
foreach ($currentHeaders as $key => $currentVal) {
|
||||
$headers[] = $key . ($currentVal !== null ? '=' . $currentVal : '');
|
||||
}
|
||||
|
||||
static::setHeader(static::HEADER_CACHE_CONTROL, implode(', ', $headers));
|
||||
static::setHeader(static::HEADER_CACHE_CONTROL, 'private, no-cache, no-store');
|
||||
}
|
||||
|
||||
public static function setHeader($name, $value)
|
||||
|
||||
@@ -176,4 +176,34 @@ class View
|
||||
Response::setHeader(Response::HEADER_CONTENT_TYPE, 'application/json');
|
||||
return ['internal/json', ['json' => $data, '_no_layout' => true]];
|
||||
}
|
||||
|
||||
public static function safeExternalLinks(string $html, string $domain): string
|
||||
{
|
||||
//temporarily disable this as it is breaking JS
|
||||
return $html;
|
||||
|
||||
$dom = new PHPHtmlParser\Dom();
|
||||
$dom->load($html, ['cleanupInput' => false, 'removeDoubleSpace' => false, 'removeSmartyScripts' => false]);
|
||||
|
||||
foreach ($dom->find('body a') as $link) {
|
||||
if ($link->getAttribute('href') && static::isLinkExternal($link->getAttribute('href'), $domain)) {
|
||||
$link->setAttribute('rel', "noopener noreferrer");
|
||||
}
|
||||
}
|
||||
return $dom->root->outerHtml();
|
||||
}
|
||||
|
||||
public static function isLinkExternal(string $url, string $domain): bool
|
||||
{
|
||||
$components = parse_url(strtolower($url));
|
||||
$domain = strtolower($domain);
|
||||
|
||||
return $url
|
||||
&&
|
||||
!empty($components['host']) // relative urls are not external
|
||||
&&
|
||||
$components['host'] !== $domain
|
||||
&&
|
||||
mb_substr($components['host'], -mb_strlen('.' . $domain)) !== '.' . $domain;
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,84 @@
|
||||
<?php Response::setMetaDescription('Watch ' . $title . ' on a platform that shares your values.') ?>
|
||||
<?php Response::setMetaTitle($title . ' on LBRY') ?>
|
||||
<main class="ancillary">
|
||||
<section class="hero hero--half-height" style="background-image: url(<?php echo $coverUrl ?>)">
|
||||
<div class="inner-wrap inner-wrap--center-hero">
|
||||
<h1>Watch <?php echo $title ?></h1>
|
||||
<h3>On a platform that shares your values.</h3>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inline-image-and-text">
|
||||
<img
|
||||
alt="cctv camera"
|
||||
class="inline-image"
|
||||
src="/img/icon--cctv.svg"
|
||||
/>
|
||||
|
||||
<p>Predatory platforms like Facebook and YouTube abuse users, censor creators, enforce rules arbitrarily, and spy on everything you do.</p>
|
||||
</div>
|
||||
<div class="inline-image-and-text">
|
||||
<p>LBRY is a user-controlled, open-source platform that stands for user freedom and personal choice. It has <em><?php echo $claimCount ?> videos from <?php echo $claim['name'] ?></em>.</p>
|
||||
<img
|
||||
alt="smile icon"
|
||||
class="inline-image"
|
||||
src="/img/icon--smile.svg"
|
||||
/>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<h3>Step 1: Download LBRY</h3>
|
||||
<p>LBRY is an open-source application available on Windows, macOS, Linux, and Android, with iOS coming soon.</p>
|
||||
<br/>
|
||||
<div class="align-text--center">
|
||||
<?php echo View::render('download/_downloadButton', ['buttonStyle' => 'primary'])?>
|
||||
<a href="/get?showall=1" class="button--link">show all platforms</a>
|
||||
</div>
|
||||
<br/>
|
||||
</div>
|
||||
</section>
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<h3>Step 2: Search and Follow <?php echo $claim['name'] ?></h3>
|
||||
<p>Type <?php echo $claim['name'] ?> in the search bar and then click Follow.</p>
|
||||
<div class="align-text--center" style="margin-top: 1rem; margin-bottom: 1rem;">
|
||||
<img src="https://spee.ch/e/follow-1.gif" alt="How to follow <?php echo $claim['name'] ?> on LBRY" />
|
||||
</div>
|
||||
<p>If you provide your email address, you'll be notified about every new video.</p>
|
||||
</div>
|
||||
<br/>
|
||||
</section>
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<h3>Step 3 (Optional): Support <?php echo $claim['name'] ?></h3>
|
||||
<p>Use the Tip button to support <?php echo $claim['name'] ?> and help others discover this content.</p>
|
||||
<p>If you verify your account, you'll receive free credits that you can send to <?php echo $claim['name'] ?> or other creators.</p>
|
||||
<small><em>Having trouble?</em> Read <a href="/faq/rewards">the rewards FAQ</a> for help.</small>
|
||||
<div class="align-text--center" style="margin-top: 1rem; margin-bottom: 1rem;">
|
||||
<img src="https://spee.ch/9/follow-tip.png" alt="How to support <?php echo $claim['name'] ?> on LBRY" />
|
||||
</div>
|
||||
</div>
|
||||
<br/>
|
||||
</section>
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<h3>Step 4: Enjoy Peace of Mind</h3>
|
||||
<p>When you watch <?php echo $title ?> on LBRY, you're watching via a platform that is open-source, user-controlled, and censorship-resistant.</p>
|
||||
<p>Unlike other platforms, it is <em>literally impossible</em> for LBRY to put it's thumb on the scales.</p>
|
||||
<p>So what are you waiting for? Try LBRY today!</p>
|
||||
<br/>
|
||||
<div class="align-text--center">
|
||||
<?php echo View::render('download/_downloadButton', ['buttonStyle' => 'primary'])?>
|
||||
<a href="/get?showall=1" class="button--link">show all platforms</a>
|
||||
</div>
|
||||
<br/>
|
||||
<div>
|
||||
<small>Not enough details for you? Read the <a href="/what">manifesto</a> or the <a href="//lbry.tech">docs</a>.</small>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
@@ -54,8 +54,7 @@
|
||||
|
||||
<p hidden id="lbry_error" class="error-block">YouTube channel name is either not valid (only letters, numbers and - allowed, no spaces) or your input is blank</p>
|
||||
|
||||
<h2>Connect with your fans while earning money and rewards</h2>
|
||||
|
||||
<h2>Connect with your fans while earning rewards</h2>
|
||||
<form id="youtube_claim" method="post" action="/youtube/token">
|
||||
<p hidden id="sync-status" class="sync-status"></p>
|
||||
|
||||
@@ -224,13 +223,13 @@
|
||||
|
||||
<div class="v-card">
|
||||
<figure>
|
||||
<img alt="Rob Smith, Head of Product Growth" src="https://spee.ch/7/rob-smith1.png"/>
|
||||
<img alt="Brinck Slattery, Director of Communications" src="https://spee.ch/@Memes:26/brinck-slattery1.png"/>
|
||||
</figure>
|
||||
|
||||
<info>
|
||||
<h3>Rob Smith</h3>
|
||||
<p>Head of Product Growth</p>
|
||||
<a href="mailto:rob@lbry.com?subject=YouTube+Freedom">Contact</a>
|
||||
<h3>Brinck Slattery</h3>
|
||||
<p>Director of Communications</p>
|
||||
<a href="mailto:brinck@lbry.com?subject=YouTube+Freedom">Contact</a>
|
||||
</info>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -8,6 +8,7 @@
|
||||
<?php $statusData = $status_token['data'] ?>
|
||||
<?php $isSyncAgreed = in_array($statusData['status'], ["failed", "finalized", "pendingemail", "queued", "synced", "syncing"]) ?>
|
||||
<?php $isRewardClaimed = $statusData['redeemed_reward'] > 0 ?>
|
||||
<?php $isTransferred = $statusData['transferred'] ?>
|
||||
|
||||
<?php if (IS_PRODUCTION): ?>
|
||||
<?php js_start() ?>
|
||||
@@ -57,8 +58,8 @@
|
||||
|
||||
<li class="<?php echo $isRewardClaimed && $isSyncAgreed ? "" : "disabled" ?>">
|
||||
<span><?php echo $isRewardClaimed ? "✓" : "·" ?></span>
|
||||
<p>Claim your credits</p>
|
||||
<p <?php echo ($isRewardClaimed === false && $isSyncAgreed === true) ? "" : "hidden" ?>>(to get your credits, <a href="/get">download the app</a> and <a href="/faq/youtube">follow these instructions</a>)</p>
|
||||
<p>Transfer your content and redeem Rewards</p>
|
||||
<p <?php echo ($isSyncAgreed === true && ($isRewardClaimed === false || $isTransferred === false)) ? "" : "hidden" ?>>(<a href="/get">Download the app</a> and <a href="/faq/youtube">follow these instructions</a>)</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -196,7 +197,7 @@
|
||||
|
||||
<br/><br/>
|
||||
|
||||
<p>If you have an existing LBRY wallet please <a href="/claim-wallet" title="YouTube Sync Transfer Request">fill out this form</a>. This is still a manual process.</p>
|
||||
<p>Once your content is synced on LBRY, we can transfer control directly to your LBRY account. Please see the <a href="/faq/youtube" title="YouTube FAQ">YouTube FAQ</a> for more details.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
@@ -1,6 +1,6 @@
|
||||
<?php Response::setMetaDescription(__('description.no-os')) ?>
|
||||
<?php Response::setMetaTitle(__('global.get')) ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/lbry-ui.png') ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/og-image.png') ?>
|
||||
|
||||
<main class="ancillary">
|
||||
<section class="hero hero--half-height">
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
<?php Response::setMetaDescription(__('description.get')) ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/lbry-ui.png') ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/og-image.png') ?>
|
||||
<?php NavActions::setNavUri('/get') ?>
|
||||
|
||||
<main class="ancillary">
|
||||
<section class="hero hero--half-height">
|
||||
<div class="inner-wrap inner-wrap--center-hero">
|
||||
<h1>
|
||||
<?php echo __('download.for-os2', ['%os%' => OS::OS_DETAIL($os)[5]]) ?>
|
||||
<?php echo __('download.for-os2', ['%os%' => OS::OS_DETAIL($os)[4]]) ?>
|
||||
</h1>
|
||||
</div>
|
||||
</section>
|
||||
@@ -47,10 +47,10 @@
|
||||
loop
|
||||
poster="https://spee.ch/f/2019-08-lbry-interface-poster.jpg"
|
||||
playsinline
|
||||
style="display: block; margin-right: auto; margin-left: auto; max-width: 500px; "
|
||||
style="display: block; margin-right: auto; margin-left: auto; max-width: 700px; "
|
||||
>
|
||||
<source src="https://spee.ch/a/2019-08-lbry-interface-webm.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/4/2019-08-lbry-interface.mp4" type="video/mp4"/>
|
||||
<source src="https://spee.ch/b/2019-09-lbry-interface-webm-2.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/0/2019-09-lbry-interface-mp4-2.mp4" type="video/mp4"/>
|
||||
</video>
|
||||
<?php endif ?>
|
||||
|
||||
|
||||
@@ -6,6 +6,7 @@
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, target-densitydpi=device-dpi"/>
|
||||
|
||||
<?php $title = Response::getMetaTitle() ?: Response::guessMetaTitle($content) ?>
|
||||
<?php $images = Response::getMetaImages() ?>
|
||||
<?php $title = $title ?
|
||||
$title . (strpos($title, 'LBRY') === false ? ' - LBRY' : '') :
|
||||
'LBRY' ?>
|
||||
@@ -39,35 +40,41 @@
|
||||
<link rel="alternate" type="application/rss+xml" title="LBRY News" href="<?php echo ContentActions::URL_NEWS . '/' . ContentActions::SLUG_RSS ?>"/>
|
||||
<?php endif ?>
|
||||
|
||||
<meta property="og:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php foreach ($images as $image): ?>
|
||||
<meta property="og:image" content="<?php echo $image ?>"/>
|
||||
<?php endforeach ?>
|
||||
<meta property="og:site_name" content="LBRY"/>
|
||||
<meta property="og:title" content="<?php echo $title ?>"/>
|
||||
<meta property="og:type" content="article"/>
|
||||
|
||||
<meta name="description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<meta name="msapplication-TileColor" content="#155B4A"/>
|
||||
<meta name="msapplication-TileImage" content="/img/fav/mstile-144x144.png"/>
|
||||
<meta name="theme-color" content="#155B4A"/>
|
||||
|
||||
<meta name="twitter:card" content="app"/>
|
||||
<meta name="twitter:site" content="@LBRYio"/>
|
||||
<meta name="twitter:description" content="Meet LBRY, a content sharing and publishing platform that is decentralized and owned by its users."/>
|
||||
<meta name="twitter:app:country" content="US"/>
|
||||
<meta name="twitter:app:name:googleplay" content="LBRY beta"/>
|
||||
<meta name="twitter:app:id:googleplay" content="io.lbry.browser"/>
|
||||
<meta name="twitter:app:url:googleplay" content="https://play.google.com/store/apps/details?id=io.lbry.browser"/>
|
||||
<meta name="twitter:site" content="@lbryio"/>
|
||||
<meta name="twitter:creator" content="@lbryio"/>
|
||||
<meta name="twitter:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<meta name="twitter:title" content="<?php echo $title ?>" />
|
||||
<?php if ($images): ?>
|
||||
<?php $url = reset($images) ?>
|
||||
<meta name="twitter:image" content="<?php echo $url ?>" />
|
||||
<?php endif ?>
|
||||
|
||||
<?php if (in_array($_SERVER['REQUEST_URI'], ['/', '/android', '/get'])): ?>
|
||||
<meta name="twitter:card" content="app"/>
|
||||
<meta name="twitter:app:country" content="US"/>
|
||||
<meta name="twitter:app:name:googleplay" content="LBRY beta"/>
|
||||
<meta name="twitter:app:id:googleplay" content="io.lbry.browser"/>
|
||||
<meta name="twitter:app:url:googleplay" content="https://play.google.com/store/apps/details?id=io.lbry.browser"/>
|
||||
<?php else: ?>
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<?php endif ?>
|
||||
|
||||
<!-- Twitter Card data -->
|
||||
<meta name="twitter:site" content="@lbryio">
|
||||
<meta name="twitter:creator" content="@lbryio">
|
||||
|
||||
<meta property="fb:app_id" content="1673146449633983"/>
|
||||
|
||||
<!-- Open Graph data -->
|
||||
<meta property="og:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php foreach (Response::getMetaImages() as $image): ?>
|
||||
<meta property="og:image" content="<?php echo $image ?>"/>
|
||||
<meta property="og:image:height" content="1125"/>
|
||||
<meta property="og:image:width" content="2000"/>
|
||||
<?php endforeach ?>
|
||||
<meta property="og:site_name" content="LBRY"/>
|
||||
<meta property="og:title" content="<?php echo $title ?>"/>
|
||||
<meta property="og:type" content="article"/>
|
||||
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
|
||||
<base target="_parent"/>
|
||||
|
||||
@@ -11,49 +11,55 @@
|
||||
<div class="notice notice-error spacer1"><?php echo $error ?></div>
|
||||
<?php else: ?>
|
||||
<form id="<?php echo $formId ?>" novalidate style="display: none">
|
||||
<section class="email-section" style="position: relative;">
|
||||
<section class="email-section">
|
||||
<div style="min-height: 33px"> <?php //hack fix to prevent jumping ?>
|
||||
<div class="notice notice-error hide spacer-half"></div>
|
||||
<div class="notice notice-success hide spacer-half">Your email preferences have been updated.</div>
|
||||
</div>
|
||||
<h4><?php echo count($emails) > 1 ? 'Receiving Addresses' : 'Do You Want To Receive Mail?' ?></h4>
|
||||
<?php if (count($emails) > 1): ?>
|
||||
<div class="meta spacer-half">Uncheck all boxes if you want to receive no future messages.</div>
|
||||
<?php endif ?>
|
||||
|
||||
<div class="notice notice-error hide spacer-half"></div>
|
||||
<div class="notice notice-success hide spacer-half">Your email preferences have been updated.</div>
|
||||
|
||||
<?php $emailIndex = 0 ?>
|
||||
|
||||
<?php foreach ($emails as $email => $enabled): ?>
|
||||
<?php $emailId = 'email_' . (++$emailIndex) ?>
|
||||
<checkbox-element>
|
||||
<input id="<?php echo $emailId ?>" name="<?php echo $emailId ?>" type="checkbox"<?php echo $enabled ? " checked" : "" ?> value="<?php echo urlencode($email) ?>"/>
|
||||
<label for="<?php echo $emailId ?>"><?php echo $email ?></label>
|
||||
<label for="<?php echo $emailId ?>"><?php echo count($emails) > 1 ? $email : __('Yes') . ' (' . $email . ')' ?></label>
|
||||
<checkbox-toggle/>
|
||||
</checkbox-element>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
|
||||
<section class="tag-section spacer1" style="position: relative;">
|
||||
<section class="tag-section spacer1">
|
||||
<div style="min-height: 33px"> <?php //hack fix to prevent jumping ?>
|
||||
<div class="notice notice-error hide spacer-half"></div>
|
||||
<div class="notice notice-success hide spacer-half">Your email preferences have been updated.</div>
|
||||
</div>
|
||||
<h4>Fine-tune your Mail</h4>
|
||||
<div class="notice notice-error hide spacer-half"></div>
|
||||
<div class="notice notice-success hide spacer-half">Your email preferences have been updated.</div>
|
||||
|
||||
<?php $tagIndex = 0 ?>
|
||||
<?php foreach ($tags as $tag => $enabled): ?>
|
||||
<?php if (!isset($tagMetadata[$tag])) {
|
||||
continue;
|
||||
} //fix/kill this?>
|
||||
<?php if (!isset($tagMetadata[$tag])) continue; ?>
|
||||
<?php $tagId = 'tag_' . (++$tagIndex) ?>
|
||||
<checkbox-element>
|
||||
<input id="<?php echo $tagId ?>" name="<?php echo $tagId ?>" type="checkbox"<?php echo $enabled ? " checked" : "" ?> value="<?php echo urlencode($tag) ?>"/>
|
||||
<label for="<?php echo $tagId ?>">
|
||||
<?php echo isset($tagMetadata[$tag]['label']) ? $tagMetadata[$tag]['label'] : $tag ?>
|
||||
<?php if (isset($tagMetadata[$tag]['description'])): ?>
|
||||
<span class="meta">· <?php echo $tagMetadata[$tag]['description'] ?></small>
|
||||
<?php endif ?>
|
||||
</label>
|
||||
<checkbox-toggle/>
|
||||
</checkbox-element>
|
||||
<div>
|
||||
<checkbox-element>
|
||||
<input id="<?php echo $tagId ?>" name="<?php echo $tagId ?>" type="checkbox"<?php echo $enabled ? " checked" : "" ?> value="<?php echo urlencode($tag) ?>"/>
|
||||
<label for="<?php echo $tagId ?>">
|
||||
<?php echo isset($tagMetadata[$tag]['label']) ? $tagMetadata[$tag]['label'] : $tag ?>
|
||||
<?php if (isset($tagMetadata[$tag]['description'])): ?>
|
||||
<span class="meta">· <?php echo $tagMetadata[$tag]['description'] ?></span>
|
||||
<?php endif ?>
|
||||
</label>
|
||||
<checkbox-toggle/>
|
||||
</checkbox-element>
|
||||
</div>
|
||||
<?php endforeach ?>
|
||||
<?php if ($tagIndex === 0): ?>
|
||||
<div class="notice notice-error"><?php echo __('Something went wrong. Please email help@lbry.com') ?></div>
|
||||
<?php endif ?>
|
||||
</section>
|
||||
</form>
|
||||
<?php endif ?>
|
||||
@@ -10,7 +10,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<?php echo View::render('mail/_settingsForm', [
|
||||
'tags' => $tags,
|
||||
'emails' => $emails,
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<?php if ($confirmSuccess ?? false): ?>
|
||||
<?php if (IS_PRODUCTION): ?>
|
||||
<?php js_start() ?>
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<?php if ($error ?? false): ?>
|
||||
<div class="notice notice-error spacer1"><?php echo $error ?></div>
|
||||
<?php else: ?>
|
||||
|
||||
@@ -33,6 +33,7 @@
|
||||
<li><a href="mailto:hello@lbry.com" title="Send us an email!">hello@lbry.com</a></li>
|
||||
<li><a href="/contact" title="Send us an email!">Contact</a></li>
|
||||
<li><a href="/privacypolicy" title="View our Privacy Policy">Privacy</a></li>
|
||||
<li><a href="/termsofservice" title="Terms of Service">TOS</a></li>
|
||||
<li><a href="/faq" title="Frequently Asked Questions about LBRY">FAQ</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
</div>
|
||||
<?php /*
|
||||
<div class="control-item no-label-desktop">
|
||||
<form action="/set-culture" method="POST">
|
||||
<form action="/i18n/set-culture" method="POST">
|
||||
<select id="language-dropdown" name="culture">
|
||||
<?php foreach ($cultures as $culture): ?>
|
||||
<option value="<?php echo $culture ?>" <?php echo $culture == $selectedCulture ? 'selected="selected"' : '' ?>>
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<p>Through June 1st, 2019, LBRY has received:</p>
|
||||
<p>Through October 1st, 2019, LBRY has received:</p>
|
||||
|
||||
<ul>
|
||||
<li>Zero National Security Letters</li>
|
||||
|
||||
@@ -21,8 +21,8 @@
|
||||
poster="https://spee.ch/f/2019-08-lbry-interface-poster.jpg"
|
||||
playsinline
|
||||
>
|
||||
<source src="https://spee.ch/a/2019-08-lbry-interface-webm.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/4/2019-08-lbry-interface.mp4" type="video/mp4"/>
|
||||
<source src="https://spee.ch/b/2019-09-lbry-interface-webm-2.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/0/2019-09-lbry-interface-mp4-2.mp4" type="video/mp4"/>
|
||||
</video>
|
||||
</a>
|
||||
</figure>
|
||||
|
||||
@@ -83,7 +83,8 @@
|
||||
<p>Occasionally, at our discretion, we may include or offer third-party products or services on our website. These third-party sites have separate and independent privacy policies. We therefore have no responsibility or liability for the content and activities of these linked sites. Nonetheless, we seek to protect the integrity of our site and welcome any feedback about these sites.</p>
|
||||
|
||||
<p><strong>Google</strong></p>
|
||||
|
||||
<p> As part of LBRY Creator Verification, we will only use read-only access to verify the ownership of YouTube channels and will not transfer this data to others unless doing so is necessary to comply with applicable law, or as part of a merger, acquisition, or sale of assets.<p>
|
||||
|
||||
<p>Google's advertising requirements can be summed up by Google's Advertising Principles. They are put in place to provide a positive experience for users. <code>https://support.google.com/adwordspolicy/answer/1316548?hl=en</code></p>
|
||||
|
||||
<p>We use Google AdSense Advertising on our website.</p>
|
||||
@@ -211,7 +212,7 @@
|
||||
<p>
|
||||
</blockquote>
|
||||
|
||||
<small>Last edited on 2018-04-28</small>
|
||||
<small>Last edited on 2019-19-09</small>
|
||||
<br/><br/><br/>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
<h2>Technical</h2>
|
||||
</div>
|
||||
|
||||
<?php foreach (['jack-robison', 'lex-berezhny', 'akinwale-ariwodola', 'antoniyshumanov', 'andrey', 'sean-yesmunt', 'niko-storni', 'paul-webb', 'mark-beamer'] as $bioSlug): ?>
|
||||
<?php foreach (['jack-robison', 'lex-berezhny', 'akinwale-ariwodola', 'antoniyshumanov', 'andrey', 'sean-yesmunt', 'niko-storni', 'mark-beamer'] as $bioSlug): ?>
|
||||
<?php echo View::render('content/_bio', ['person' => $bioSlug]) ?>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
@@ -35,7 +35,7 @@
|
||||
<h2>Business</h2>
|
||||
</div>
|
||||
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery'] as $bioSlug): ?>
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery', 'julie-sigwart'] as $bioSlug): ?>
|
||||
<?php echo View::render('content/_bio', ['person' => $bioSlug]) ?>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
|
||||
@@ -11,15 +11,199 @@
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<p><strong>This page is a stub. A full acknowledgement is coming soon.</strong></p>
|
||||
<p>In the interim, by publishing to LBRY, you affirm and acknowledge that:</p>
|
||||
<p><strong>Last Updated: April 2019</strong></p>
|
||||
|
||||
<p><strong>PLEASE READ THESE TERMS OF SERVICE CAREFULLY. NOTE THAT SECTION 16 CONTAINS A BINDING ARBITRATION CLAUSE AND CLASS ACTION WAIVER, WHICH AFFECT YOUR LEGAL RIGHTS. IF YOU DO NOT AGREE TO THESE TERMS OF SERVICE, DO NOT ACCESS OR USE THE SERVICES.</strong></p>
|
||||
|
||||
<p>By clicking to agree to these Terms of Service (<strong>“Terms”</strong>) when running/installing our software, publishing content to LBRY, or by otherwise accessing or using the network [via proxy or direct], mobile applications and online services (collectively, our <strong>“Services”</strong>) of LBRY Inc. (<strong>“Company,” “we,” or “us”</strong>), you agree to be bound by these Terms. If you do not agree to these Terms, you may not access or use the Services for any purpose. Please refer to our Privacy Policy https://lbry.com/privacypolicy for information about how we collect, use and disclose information about you.</p>
|
||||
|
||||
<p>You and the Company agree as follows:</p>
|
||||
|
||||
<h3 id="toc_0">1. Overview of LBRY and the Services</h3>
|
||||
|
||||
<p><strong>“LBRY”</strong> is a decentralized, consensus-driven protocol that enables the publication and viewing of information, videos, music, data and other materials (<strong>“Content”</strong>). Content is distributed to LBRY by publishers and is stored in fragmented shards via a distributed network of third-party devices (<strong>“Hosts”</strong>) that utilize LBRY. LBRY also allows publishers to bid on and reserve names (<strong>“Names”</strong>), which can be used as a unique identifier for Content. Please consult lbry.tech to learn more about the technical architecture of LBRY. </p>
|
||||
|
||||
<p>The Services provide an interface for you to interact with LBRY, including to publish, access, or host Content through LBRY. The LBRY protocol is not owned, operated, or maintained by us. We have no responsibility or liability for LBRY, and the Company has no ability to control third parties’ use of LBRY. We are not able to delete or remove Content that has been published through LBRY and that may be accessible via the Services. </p>
|
||||
|
||||
<h3 id="toc_1">2. Eligibility</h3>
|
||||
|
||||
<p>You must be at least 13 years of age to access or use our Services. If you are under 18 years of age (or the age of legal majority where you live), you may only access or use our Services under the supervision of a parent or legal guardian who agrees to be bound by these Terms. If you are a parent or legal guardian of a user under the age of 18 (or the age of legal majority), you will be fully responsible for the acts or omissions of such user in connection with our Services. If you are accessing or using our Services on behalf of another person or entity, you represent that you are authorized to accept these Terms on that person or entity’s behalf and that the person or entity agrees to be responsible to us if you or the other person or entity violates these Terms.</p>
|
||||
|
||||
<h3 id="toc_2">3. Publishing Content</h3>
|
||||
|
||||
<p>This section applies if you use the Services to publish Content through LBRY. </p>
|
||||
|
||||
<p>a) You will make available via the Services a clear and accurate description of Content you publish, and provide the Content in accordance with any descriptions or representations you make available about the Content. You are solely responsible for resolving any disputes with users of your Content, including any chargebacks or refunds, and for any and all injuries, illnesses, damages, claims, liabilities and costs that are caused in whole or in part by you or your Content. Publishing to a blockchain is permanent. We cannot remove published content from the blockchain itself, although we can block content accessed via our app or other services on top of the blockchain.</p>
|
||||
|
||||
<p>b) LBRY enables publishers to offer Content for sale to other users by setting contract terms within the metadata of the Content. Company, in its sole discretion, may from time to time impose limits on the ability to sell Content via the Services. Upon the purchase of Content, you and the purchaser of your Content will enter into a separate agreement, pursuant to which that purchaser agrees to pay the specified fees for the Content and you agree to enable access to your Content. You are solely responsible for providing refunds as required to comply with applicable law. You are responsible for determining what, if any, taxes apply to your sale of Content, including, for example, sales, use, value added, and similar taxes. It is also your responsibility to withhold, collect, report and remit the correct taxes to the appropriate tax authorities. The Company is not responsible for withholding, collecting, reporting, or remitting any sales, use, value added, or similar tax arising from any transaction completed via the Services.</p>
|
||||
|
||||
<p>c) The Company is not a party to and has no responsibility or liability with respect to any communications, transactions, interactions, disputes or any relations whatsoever between you and any users of the Content. We will not be responsible for any loss, misuse, or deletion of Content or any failure of any Content to be encrypted, stored or distributed.. You are solely responsible for your use of the Services, including for configurations that you deem appropriate to determine access to your Content by other users in a manner that meets your expectations. You are solely responsible for backing up any Content. We are not responsible for any user’s access to your Content or any user’s misuse or redistribution of Content. </p>
|
||||
|
||||
<p>d) You will not use the Services to reserve a Name that infringes any patent, trademark, trade secret, copyright or other intellectual or proprietary right of any party.</p>
|
||||
|
||||
<p>e) We make no representations or warranties regarding the suitability of the Services for the distribution and publishing of any particular types of data. By posting any Content or reserving a Name, you represent and warrant that you have the lawful right, including all necessary intellectual property rights, to distribute and reproduce such Content or use such Name for any purpose, commercial or otherwise. You will provide all notices to, and obtain any consents from third parties as required by applicable law in connection with the distribution and publishing of Content via the Services. </p>
|
||||
|
||||
<p>f) You will not use the Services to distribute or publish Content that:</p>
|
||||
|
||||
<ul>
|
||||
<li>is unlawful, for example, copyrighted works, underage sexual content, revenge pornography, or any other content illegal under US or state law.<br></li>
|
||||
<li>would constitute, encourage or provide instructions for a criminal offense, violate the rights of any party, or that would otherwise create liability or violate any applicable local, state, national or international law;</li>
|
||||
<li>infringes any patent, trademark, trade secret, copyright or other intellectual or proprietary right of any party;</li>
|
||||
<li>impersonates any person or entity or otherwise misrepresents your affiliation with a person or entity;</li>
|
||||
<li>contains sensitive personal information, including “protected health information,” as defined under HIPAA and its implementing rules; “cardholder data,” as defined by the PCI DSS; “personal information” of a “child” as such terms are defined under the Children’s Online Privacy Protection Act and its implementing rules; or personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation;</li>
|
||||
<li>contains viruses, corrupted data or other harmful, disruptive or destructive files; UNLESS CLEARLY LABELED AS SUCH</li>
|
||||
<li>in the sole judgment of the Company, is objectionable or which restricts or inhibits any other person from using or enjoying LBRY or the Services, or which may expose the Company or its users to any harm or liability of any type.</li>
|
||||
<li>USD equivalent of LBRY Credits [LBC] is determined by 3rd party markets such as Bittrex and Poloniex, not LBRY INC.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="toc_3">4. Accessing Content</h3>
|
||||
|
||||
<p>This section applies if you use the Services to access Content that has been stored through LBRY.</p>
|
||||
|
||||
<p>a) In using our Services, you may view or otherwise interact with Content provided by publishers. Your dealings or correspondence with any publisher of Content are solely between you and that publisher. The Company is not responsible or liable for any damage or loss of any sort caused, or alleged to be caused, by or in connection with any such dealings, including the delivery, quality, safety, legality or any other aspect of any Content that you may access using our Services.</p>
|
||||
|
||||
<p>b) In certain instances, your access to Content may be subject to sale terms set forth in the metadata of the Content. Company, in its sole discretion, may from time to time impose limits on the ability to purchase Content via the Services. Upon your access of any purchased Content, you and the publisher will enter into a separate agreement, pursuant to which you agree to pay the specified fees for the Content and the publisher agrees to make such Content available to you. THE COMPANY DOES NOT HAVE THE POWER OR RESPONSIBILITY TO PROVIDE ANY REFUNDS. You agree to look solely to the publisher to resolve any disputes regarding Content, and that publishers are solely responsible for providing any refunds.</p>
|
||||
|
||||
<p>c) All payments for content will be made using LBC and occur on the LBRY blockchain. Purchaser is buying the right to access content for personal non-commercial use unless content creator provides a license for commercial use or remixing.</p>
|
||||
|
||||
<h3 id="toc_4">5. Hosting Content</h3>
|
||||
|
||||
<p>This section applies to you if you host any Content via LBRY using the Services. The Services allow Hosts to make available storage space (<strong>“Space”</strong>) on the Host’s device for the storage of Content published through LBRY
|
||||
By making available Space on your device, you authorize any user of our Services to: (i) store Content published through LBRY onto your device; and (ii) access such Content from your device at any time. </p>
|
||||
|
||||
<p>a) You represent and warrant that (i) you own or control your device, and have the right to provide the Space on your device pursuant to these Terms; and (ii) you will not breach any agreement to which you are a party in connection with your performance under these Terms, including any agreement you have with a third-party Internet service provider. </p>
|
||||
|
||||
<p>b) By allowing Space to be utilized to store Content distributed through LBRY, you understand that your device may be impacted due to the additional constraints being placed on it by the processing of Content. In particular, your device may not operate as quickly as it would without making Space available for others to utilize. </p>
|
||||
|
||||
<p>c) You will not: (i) reverse engineer any aspect of the Content stored on your device or do anything that might discover the contents or origin of the Content; (ii) attempt to bypass or circumvent measures employed to prevent or limit access to the Content, including attempting to defeat any encryption; or (iii) attempt to interfere with the storage or transmission of Content.</p>
|
||||
|
||||
<h3 id="toc_5">6. General Conduct Restrictions</h3>
|
||||
|
||||
<p>You are solely responsible for your conduct while using the Services. You will comply with all applicable laws and third-party agreements to which you are bound. Further, you will not do any of the following in connection with the Services or any other users: </p>
|
||||
|
||||
<p>a) Use the Services in any manner that could interfere with, disrupt, negatively affect or inhibit other users from fully enjoying the Services or that could damage, disable, overburden or impair the functioning of the Services in any manner;</p>
|
||||
|
||||
<p>b) Impersonate or distribute Content on behalf or any person or entity or otherwise misrepresent your affiliation with a person or entity;</p>
|
||||
|
||||
<p>c) Cheat or utilize unauthorized exploits in connection with the Services; </p>
|
||||
|
||||
<p>d) Stalk, intimidate, threaten, or otherwise harass or cause discomfort to other users; </p>
|
||||
|
||||
<p>e) Send, distribute or post spam, unsolicited or bulk commercial electronic communications, chain letters, or pyramid schemes;</p>
|
||||
|
||||
<p>f) Harvest or otherwise collect information about users, including email addresses, without their consent;</p>
|
||||
|
||||
<p>g) Use the Services for any illegal or unauthorized purpose or engage in, encourage, or promote any illegal activity, or any activity that violates these Terms; </p>
|
||||
|
||||
<p>h) Use the Services to distribute Content that you do not have the lawful right to distribute or reproduce; or</p>
|
||||
|
||||
<p>i) Circumvent or attempt to circumvent any filtering, security measures or other features we may from time to time adopt to protect the Company, the Services, its users or third parties.</p>
|
||||
|
||||
<p>The Company does not endorse or adopt any Content and you acknowledge and agree that the Company will have no responsibility for any Content, including without limitation, material that may be misleading, incomplete, erroneous, offensive, indecent or otherwise objectionable. Enforcement of the Content rules set forth in these Terms is solely at our discretion, and subject to our technical capabilities. Failure to enforce such rules in some instances does not constitute a waiver of our right to enforce such rules in other instances. In addition, these rules do not create any private right of action on the part of any third party or any reasonable expectation that the Services will not link to any Content that is prohibited by such rules. </p>
|
||||
|
||||
<h3 id="toc_6">7. Limited License; Copyright and Trademark</h3>
|
||||
|
||||
<p>Our Services and the text, graphics, images, photographs, illustrations, trademarks, trade names, service marks, logos, slogans and other content contained therein (collectively, the <strong>“Company Marks”</strong>) are owned by Company and its licensors and are protected under both United States and foreign laws, and may not be copied, imitated or used, in whole or in part, without our or the applicable licensor’s prior written permission. You may not use any metatags or other “hidden text” utilizing any Company Marks without our prior written permission. Further, you may not use, frame or utilize framing techniques to enclose any Company Mark, the content of any text or the layout or design of any page or form contained on a page, on the Services without the Company’s express written consent.</p>
|
||||
|
||||
<h3 id="toc_7">8. Open Source Software</h3>
|
||||
|
||||
<p>a) We may, from time to time, release the source code for certain of the software that supports our Services. You agree to be bound by, and comply with, any license agreement that applies to this open source software. You will not indicate that you are associated with Company in connection with any of your modifications or distributions of this open source software. </p>
|
||||
|
||||
<p>b) The source code we release in connection with open source software is not part of the Services, and your use of that source code without interacting with our Services is not subject to these Terms. For clarity, though, when we host any software and enable you to access and use such software as a service through our Services, then these Terms will apply to such access and use. </p>
|
||||
|
||||
<h3 id="toc_8">9. Feedback</h3>
|
||||
|
||||
<p>Any questions, comments, suggestions, ideas, original or creative materials or other information you submit about the Company or our products or Services (collectively, <strong>“Feedback”</strong>), is non-confidential and will become the sole property of the Company. We will own exclusive rights, including, without limitation, all intellectual property rights, in and to Feedback and will be entitled to the unrestricted use and dissemination of Feedback for any purpose, commercial or otherwise, without acknowledgment or compensation to you.</p>
|
||||
|
||||
<h3 id="toc_9">10. Copyright Complaints</h3>
|
||||
|
||||
<p>We have a policy of limiting access to our Services and terminating the accounts of users who infringe the intellectual property rights of others. If you believe that anything on our Services infringes any copyright that you own or control, you may notify the Company’s Designated Agent as follows:</p>
|
||||
|
||||
<p>Designated Agent: LBRY INC <br />
|
||||
Address: 99 Hanover St, Manchester, NH 03101<br />
|
||||
Telephone Number: 907-318-5956<br />
|
||||
Fax Number: 801-327-6808</p>
|
||||
|
||||
<p>E-Mail Address: hello@lbry.com</p>
|
||||
|
||||
<p>Please see 17 U.S.C. §512(c)(3) for the requirements of a proper notification. Also, please note that if you knowingly misrepresent that any activity or material on our Services is infringing, you may be liable to the Company for certain costs and damages.</p>
|
||||
|
||||
<h3 id="toc_10">11. Indemnification</h3>
|
||||
|
||||
<p>To the fullest extent permitted by applicable law, you will indemnify, defend, and hold harmless the Company and our officers, directors, agents, partners and employees (individually and collectively, the <strong>“Company Parties”</strong>) from and against any loss, liability, claim, demand, damages, expenses or costs (including attorney’s fees) (<strong>“Claims”</strong>) arising out of or related to (a) your access to or use of our Services; (b) your Content or any Name that you have reserved; (c) your violation of these Terms; or (d) your violation, misappropriation or infringement of any rights of another (including intellectual property rights or privacy rights). You agree to promptly notify Company Parties of any third party Claims, cooperate with Company Parties in defending such Claims and pay all fees, costs and expenses associated with defending such Claims (including, but not limited to, attorneys' fees). You also agree that the Company Parties will have control of the defense or settlement of any third party Claims. This indemnity is in addition to, and not in lieu of, any other indemnities set forth in a written agreement between you and the Company or the other Company Parties.</p>
|
||||
|
||||
<h3 id="toc_11">12. Disclaimers</h3>
|
||||
|
||||
<p><strong>Your use of our Services is at your sole risk. Our Services are provided “as is” and “as available” without warranties of any kind, either express or implied, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. In addition, the Company does not represent or warrant that our Services are accurate, complete, reliable, current or error-free. While the Company attempts to make your access to and use of our Services safe, we cannot and do not represent or warrant that our Services or servers are free of viruses or other harmful components. You assume the entire risk as to the quality and performance of the Services.</strong></p>
|
||||
|
||||
<h3 id="toc_12">13. Limitation of Liability</h3>
|
||||
|
||||
<p><strong>The Company and the other Company Parties will not be liable to you under any theory of liability—whether based in contract, tort, negligence, strict liability, warranty, or otherwise—for any indirect, consequential, exemplary, incidental, special or punitive damages or lost profits, even if the Company or the other Company Parties have been advised of the possibility of such damages.</strong></p>
|
||||
|
||||
<p><strong>The total liability of the Company and the other Company Parties, for any claim arising out of or relating to these Terms or our Services, regardless of the form of the action, is limited to the greater of any amount paid, if any, by you to access or use our Services or $100 USD.</strong></p>
|
||||
|
||||
<p><strong>The limitations set forth in this section will not limit or exclude liability for the gross negligence, fraud or intentional misconduct of the Company or other Company Parties or for any other matters in which liability cannot be excluded or limited under applicable law. Additionally, some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations or exclusions may not apply to you.</strong></p>
|
||||
|
||||
<h3 id="toc_13">14. Release</h3>
|
||||
|
||||
<p>To the fullest extent permitted by applicable law, you release the Company and the other Company Parties from responsibility, liability, claims, demands and damages (actual and consequential) of every kind and nature, known and unknown (including, but not limited to, claims of negligence), arising out of or related to disputes between users and the acts or omissions of third parties. <strong>You expressly waive any rights you may have under California Civil Code § 1542 as well as any other statute or common law principles that would otherwise limit the coverage of this release to include only those claims which you may know or suspect to exist in your favor at the time of agreeing to this release.</strong></p>
|
||||
|
||||
<h3 id="toc_14">15. Dispute Resolution; Arbitration</h3>
|
||||
|
||||
<p><strong>Please read the following section carefully because it requires you to arbitrate certain disputes and claims with the Company and limits the manner in which you can seek relief from us.</strong></p>
|
||||
|
||||
<h3 id="toc_15">16.1. Binding Arbitration</h3>
|
||||
|
||||
<p>Except for any disputes, claims, suits, actions, causes of action, demands or proceedings (collectively, <strong>“Disputes”</strong>) in which either party seeks to bring an individual action in small claims court or seeks injunctive or other equitable relief for the alleged unlawful use of intellectual property, including, without limitation, copyrights, trademarks, trade names, logos, trade secrets or patents, you and the Company (a) waive your and the Company’s respective rights to have any and all Disputes arising from or related to these Terms or the Services resolved in a court, and (b) waive your and the Company’s respective rights to a jury trial. Instead, you and the Company will arbitrate Disputes through binding arbitration (which is the referral of a Dispute to one or more persons charged with reviewing the Dispute and making a final and binding determination to resolve it instead of having the Dispute decided by a judge or jury in court).</p>
|
||||
|
||||
<h3 id="toc_16">16.2. No Class Arbitrations, Class Actions or Representative Actions</h3>
|
||||
|
||||
<p>Any Dispute arising out of or related to these Terms or the Services is personal to you and the Company and will be resolved solely through individual arbitration and will not be brought as a class arbitration, class action or any other type of representative proceeding. There will be no class arbitration or arbitration in which an individual attempts to resolve a Dispute as a representative of another individual or group of individuals. Further, a Dispute cannot be brought as a class or other type of representative action, whether within or outside of arbitration, or on behalf of any other individual or group of individuals.</p>
|
||||
|
||||
<h3 id="toc_17">16.3. Federal Arbitration Act</h3>
|
||||
|
||||
<p>These Terms affect interstate commerce and the enforceability of this Section 16 will be both substantively and procedurally governed by and construed and enforced in accordance with the Federal Arbitration Act, 9 U.S.C. § 1 et seq. (the <strong>“FAA”</strong>), to the maximum extent permitted by applicable law.</p>
|
||||
|
||||
<h3 id="toc_18">16.4. Notice; Informal Dispute Resolution</h3>
|
||||
|
||||
<p>Each party will notify the other party in writing of any arbitrable or small claims Dispute within thirty (30) days of the date it arises, so that the parties can attempt in good faith to resolve the Dispute informally. Notice to the Company will be sent by e-mail to the Company at hello@lbry.com Notice to you will be by email to the then-current email address in your Account. Your notice must include (a) your name, postal address, email address and telephone number, (b) a description in reasonable detail of the nature or basis of the Dispute, and (c) the specific relief that you are seeking. If you and the Company cannot agree how to resolve the Dispute within thirty (30) days after the date notice is received by the applicable party, then either you or the Company may, as appropriate and in accordance with this Section 16, commence an arbitration proceeding or, to the extent specifically provided for in Section 16.1, file a claim in court. </p>
|
||||
|
||||
<h3 id="toc_19">16.5. Process</h3>
|
||||
|
||||
<p>Any arbitration will occur in New Castle County, Delaware. Arbitration will be conducted confidentially by a single arbitrator in accordance with the rules of the Judicial Arbitration and Mediation Services (<strong>“JAMS”</strong>), which are hereby incorporated by reference. The state and federal courts located in New Castle County, Delaware will have exclusive jurisdiction over any appeals and the enforcement of an arbitration award. You may also litigate a Dispute in the small claims court located in the county where you reside if the Dispute meets the requirements to be heard in small claims court. </p>
|
||||
|
||||
<h3 id="toc_20">16.6. Authority of Arbitrator</h3>
|
||||
|
||||
<p>As limited by the FAA, these Terms and the applicable JAMS rules, the arbitrator will have (a) the exclusive authority and jurisdiction to make all procedural and substantive decisions regarding a Dispute, including the determination of whether a Dispute is arbitrable, and (b) the authority to grant any remedy that would otherwise be available in court; provided, however, that the arbitrator does not have the authority to conduct a class arbitration or a representative action, which is prohibited by these Terms. The arbitrator may only conduct an individual arbitration and may not consolidate more than one individual’s claims, preside over any type of class or representative proceeding or preside over any proceeding involving more than one individual.</p>
|
||||
|
||||
<h3 id="toc_21">16.7. Rules of JAMS</h3>
|
||||
|
||||
<p>The rules of JAMS and additional information about JAMS are available on the <a href="http://www.jamsadr.com/">JAMS website.</a> By agreeing to be bound by these Terms, you either (a) acknowledge and agree that you have read and understand the rules of JAMS, or (b) waive your opportunity to read the rules of JAMS and any claim that the rules of JAMS are unfair or should not apply for any reason.</p>
|
||||
|
||||
<h3 id="toc_22">17. Governing Law and Venue</h3>
|
||||
|
||||
<p>These Terms and your access to and use of the Services will be governed by and construed and enforced in accordance with the laws of the State of Delaware, without regard to conflict of law rules or principles (whether of the State of Delaware or any other jurisdiction) that would cause the application of the laws of any other jurisdiction. Any Dispute between the parties arising out of or relating to these Terms that is not subject to arbitration or cannot be heard in small claims court will be resolved in the state or federal courts of the State of Delaware and the United States, respectively, sitting in New Castle County, Delaware. </p>
|
||||
|
||||
<h3 id="toc_23">18. Severability</h3>
|
||||
|
||||
<p>If any term, clause or provision of these Terms is held invalid or unenforceable, then that term, clause or provision will be severable from these Terms and will not affect the validity or enforceability of any remaining part of that term, clause or provision, or any other term, clause or provision of these Terms.</p>
|
||||
|
||||
<h3 id="toc_24">19. Termination or Suspension</h3>
|
||||
|
||||
<p>Notwithstanding anything contained in these Terms, we reserve the right, without notice and in our sole discretion, to terminate this agreement or suspend your right to access the Services. You may terminate this agreement without notice by discontinuing use of the Services. All rights and licenses granted to you under these Terms will immediately be revoked upon our termination of the agreement or our suspension of your access to the Services. We make no representations that termination or suspension of the Services will prevent the spread or distribution of published Content through LBRY.</p>
|
||||
|
||||
<h3 id="toc_25">20. Amendment</h3>
|
||||
|
||||
<p>We reserve the right to change these Terms from time to time upon notice to you. If we make changes to these Terms, we will provide notice of such changes by posting the revised Terms to the Services and updating the “Last Updated” date at the top of these Terms. In some cases, we may provide additional notice to you, such as via our Services or to an email address associated with your Account. Your continued use of the Services following our provision of any such notice will confirm your acceptance of the revised Terms. If you do not agree to the modified Terms, you must stop using the Services. </p>
|
||||
|
||||
<h3 id="toc_26">21. Survival</h3>
|
||||
|
||||
<p>The following sections will survive the expiration or termination of these Terms: all defined terms and Sections 12 - 18, 21 and 22.</p>
|
||||
|
||||
<h3 id="toc_27">22. Miscellaneous</h3>
|
||||
|
||||
<p>These Terms constitutes the entire agreement between you and the Company relating to your access to and use of the Services. We may assign our rights and obligations under these Terms. Under no circumstances may you assign your rights and obligations under these Terms, including in the event of change of control or by operation of law, without our prior written consent. The failure of the Company to exercise or enforce any right or provision of these Terms will not operate as a waiver of such right or provision. We will not be liable for any delay or failure to perform any obligation under these Terms where the delay or failure results from any cause beyond our reasonable control. Except as otherwise provided in herein, the agreement is intended solely for the benefit of the parties and are not intended to confer third-party beneficiary rights upon any other person or entity.</p>
|
||||
|
||||
<ul>
|
||||
<li>You have the right to publish what you are publishing.</li>
|
||||
<li>You are publishing to a decentralized, distributed network that is not controlled by LBRY, Inc.</li>
|
||||
<li>LBRY, Inc. offers no guarantees of any kind with regards to its protocol, applications, or services, including with regard to the security or availability of your content.</li>
|
||||
<li>You absolve LBRY, Inc. of any and all obligations it is legal for you to surrender.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
@@ -1,3 +1,12 @@
|
||||
<head>
|
||||
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
|
||||
<script>
|
||||
(adsbygoogle = window.adsbygoogle || []).push({
|
||||
google_ad_client: "ca-pub-7620985872686147",
|
||||
enable_page_level_ads: true
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
<main class="soon">
|
||||
<section>
|
||||
<h1><strong>lbry.tv</strong> is coming soon</h1>
|
||||
|
||||
|
After Width: | Height: | Size: 177 KiB |
|
After Width: | Height: | Size: 82 KiB |
|
After Width: | Height: | Size: 88 KiB |
|
After Width: | Height: | Size: 420 KiB |
|
Before Width: | Height: | Size: 656 KiB After Width: | Height: | Size: 175 KiB |
@@ -9,13 +9,9 @@
|
||||
}
|
||||
|
||||
.notice {
|
||||
top: -0.5rem; right: 0;
|
||||
|
||||
border: 1px solid var(--lbry-gray-1);
|
||||
font-size: 0.8rem;
|
||||
// margin-bottom: 0.5rem;
|
||||
padding: 0.5rem 0.75rem;
|
||||
position: absolute;
|
||||
|
||||
[href] {
|
||||
text-decoration: underline;
|
||||
|
||||
@@ -110,7 +110,7 @@
|
||||
}
|
||||
|
||||
position: relative;
|
||||
width: 450px;
|
||||
width: 520px;
|
||||
}
|
||||
|
||||
img {
|
||||
|
||||