Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
759559b2eb |
No files matched your search
+2
-4
@@ -5,13 +5,11 @@
|
||||
"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"
|
||||
"mustangostang/spyc": "^0.6.2",
|
||||
"phpunit/phpunit": "^6.5"
|
||||
}
|
||||
}
|
||||
Generated
+1554
-35
File diff suppressed because it is too large.
Load diff
@@ -1,9 +0,0 @@
|
||||
---
|
||||
name: Julie Sigwart
|
||||
role: Community Manager
|
||||
email: Julie@lbry.com
|
||||
---
|
||||
|
||||
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 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.
|
||||
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.
|
||||
|
||||

|
||||

|
||||
|
||||
### Where Do I Find My LBC Wallet Address?
|
||||
|
||||
@@ -66,55 +66,52 @@ 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.
|
||||
|
||||
### 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.
|
||||
|
||||
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).
|
||||
|
||||
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 Rewards In The Android App? {#rewards}
|
||||
### How Do I Claim Weekly LBRYcast Rewards In The Android App? {#lbrycastrewards}
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||

|
||||
|
||||
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.
|
||||
|
||||
File renamed without changes.
@@ -1,36 +0,0 @@
|
||||
---
|
||||
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.
|
||||
@@ -1,24 +0,0 @@
|
||||
---
|
||||
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.
|
||||
@@ -9,7 +9,4 @@ 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,8 +5,6 @@ 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
|
||||
@@ -18,24 +16,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 {#manual}
|
||||
#### Windows
|
||||
### Find Logs Manually
|
||||
## 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 install LBRY for development and contributing?
|
||||
title: How do I get LBRY for development?
|
||||
category: powerusers
|
||||
---
|
||||
|
||||
|
||||
@@ -60,9 +60,6 @@ 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 removed vowels?"
|
||||
"Then why confuse people with the all-caps and no 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).
|
||||
|
||||
|
||||
@@ -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 5 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 3 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 (4444 is an example, can be changed): `dht_node_port: 4444`.
|
||||
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`.
|
||||
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 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.
|
||||
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.
|
||||
|
||||
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.
|
||||
+3
-10
@@ -4,15 +4,15 @@ category: publisher
|
||||
order: 4
|
||||
---
|
||||
|
||||
***Service Announcement: We're close to having an automated transfer process where creators will claim their channels with the Desktop app. If you'd like to request a manual transfer sooner, please see https://lbry.com/claim-wallet***
|
||||
***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 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 channel to LBRY and learn more about the program, use the [LBRY.com YouTube Sync page](/youtube).
|
||||
|
||||
***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 September (we missed our original Summer estimate due unforeseen bugs). You can request at manual process at https://lbry.com/claim-wallet which requires some technical knowledge. 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 are able to claim your Sync Reward immeadiately if you qualify (min 1K subs).**
|
||||
***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.**
|
||||
|
||||
**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. Thank you for your patience and understanding!**
|
||||
**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!**
|
||||
|
||||
### 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.
|
||||
@@ -46,12 +46,5 @@ You won't see your content in the LBRY app under `Publishes` nor have control of
|
||||
|
||||
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.
|
||||
|
||||
Feature | Sync | Transfer |
|
||||
:------------ | :-------------| :-------------|
|
||||
Your Youtube publishes will be synced | :heavy_check_mark: | :heavy_check_mark: |
|
||||
You have access to content and channel LBC from tips | :x: | :heavy_check_mark: |
|
||||
Your content shows up in the app under your Publishes | :x: | :heavy_check_mark: |
|
||||
You are responsible for keeping your wallet safe | :x: | :heavy_check_mark: |
|
||||
You can use the app to publish to the channel | :x: | :heavy_check_mark: |
|
||||
|
||||
If you're having any trouble with the sync process or receiving your credits, please contact [help@lbry.com](mailto:help@lbry.com).
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
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
|
||||
@@ -1,38 +0,0 @@
|
||||
---
|
||||
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.
|
||||
@@ -1,194 +0,0 @@
|
||||
---
|
||||
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 [Allesandro 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?
|
||||
|
||||
@@ -135,15 +135,10 @@ 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('/i18n/set-culture', 'i18nActions::setCulture');
|
||||
|
||||
$router->get('/snapshot/{type}', 'DownloadActions::executeDownloadSnapshot');
|
||||
$router->post('/set-culture', 'i18nActions::setCulture');
|
||||
|
||||
$permanentRedirectsPath = ROOT_DIR . '/data/redirect/permanent.yaml';
|
||||
$tempRedirectsPath = ROOT_DIR . '/data/redirect/temporary.yaml';
|
||||
|
||||
@@ -2,24 +2,6 @@
|
||||
|
||||
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', '');
|
||||
|
||||
@@ -15,23 +15,6 @@ 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("http://$bucketName/" . array_keys($bucket)[0], 302);
|
||||
}
|
||||
/*
|
||||
* this is a quick fix to add android, prob not proper design
|
||||
*/
|
||||
|
||||
@@ -22,18 +22,4 @@ 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.');
|
||||
}
|
||||
|
||||
$json = Transifex::getTranslationResourceFile($project, $resource, $language);
|
||||
|
||||
Response::setHeader(Response::HEADER_CROSS_ORIGIN, "*");
|
||||
Response::setHeader(Response::HEADER_ETAG, md5($json));
|
||||
|
||||
return View::renderJson($json);
|
||||
}
|
||||
}
|
||||
@@ -1,9 +1,6 @@
|
||||
<?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] = '';
|
||||
@@ -12,5 +9,4 @@ $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,7 +17,6 @@
|
||||
/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
|
||||
@@ -113,6 +112,3 @@
|
||||
/press-kit.zip: /press-kit
|
||||
/news/tag/events: /roadmap
|
||||
# /publish: /youtube
|
||||
|
||||
# Images
|
||||
/img/lbry-ui.png: /img/og-image.png
|
||||
Vendored
-32
@@ -1,32 +0,0 @@
|
||||
<?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;
|
||||
}
|
||||
}
|
||||
Vendored
-18
@@ -1,18 +0,0 @@
|
||||
<?php
|
||||
|
||||
|
||||
class Transifex
|
||||
{
|
||||
public static function isConfigured() {
|
||||
return (boolean)Config::get(Config::TRANSIFEX_API_KEY);
|
||||
}
|
||||
|
||||
public static function getTranslationResourceFile($project, $resource, $language)
|
||||
{
|
||||
$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' => 1000 * 60 * 60 * 8
|
||||
]), true);
|
||||
}
|
||||
}
|
||||
@@ -6,16 +6,12 @@ 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";
|
||||
|
||||
@@ -192,6 +192,11 @@ class Response
|
||||
]));
|
||||
}
|
||||
|
||||
public static function setContentEtag()
|
||||
{
|
||||
static::setHeader(static::HEADER_ETAG, md5(static::getContent()));
|
||||
}
|
||||
|
||||
public static function enableHttpCache(int $seconds = 300)
|
||||
{
|
||||
static::addCacheControlHeader('max-age', $seconds);
|
||||
|
||||
@@ -1,84 +0,0 @@
|
||||
<?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>
|
||||
@@ -224,13 +224,13 @@
|
||||
|
||||
<div class="v-card">
|
||||
<figure>
|
||||
<img alt="Brinck Slattery, Director of Communications" src="https://spee.ch/@Memes:26/brinck-slattery1.png"/>
|
||||
<img alt="Rob Smith, Head of Product Growth" src="https://spee.ch/7/rob-smith1.png"/>
|
||||
</figure>
|
||||
|
||||
<info>
|
||||
<h3>Brinck Slattery</h3>
|
||||
<p>Director of Communications</p>
|
||||
<a href="mailto:brinck@lbry.com?subject=YouTube+Freedom">Contact</a>
|
||||
<h3>Rob Smith</h3>
|
||||
<p>Head of Product Growth</p>
|
||||
<a href="mailto:rob@lbry.com?subject=YouTube+Freedom">Contact</a>
|
||||
</info>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
<?php Response::setMetaDescription(__('description.no-os')) ?>
|
||||
<?php Response::setMetaTitle(__('global.get')) ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/og-image.png') ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/lbry-ui.png') ?>
|
||||
|
||||
<main class="ancillary">
|
||||
<section class="hero hero--half-height">
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<?php Response::setMetaDescription(__('description.get')) ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/og-image.png') ?>
|
||||
<?php Response::addMetaImage(Request::getHostAndProto() . '/img/lbry-ui.png') ?>
|
||||
<?php NavActions::setNavUri('/get') ?>
|
||||
|
||||
<main class="ancillary">
|
||||
@@ -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: 700px; "
|
||||
style="display: block; margin-right: auto; margin-left: auto; max-width: 500px; "
|
||||
>
|
||||
<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"/>
|
||||
<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"/>
|
||||
</video>
|
||||
<?php endif ?>
|
||||
|
||||
|
||||
@@ -39,42 +39,38 @@
|
||||
<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 (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 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:site" content="@lbryio"/>
|
||||
<meta name="twitter:creator" content="@lbryio"/>
|
||||
<meta name="twitter:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php if (Response::getMetaImages()): ?>
|
||||
<?php $url = reset(Response::getMetaImages()) ?>
|
||||
<meta name="twitter:image" content="<?php echo $url ?>" />
|
||||
<?php endif ?>
|
||||
<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."/>
|
||||
|
||||
<?php if (in_array($_SERVER['REQUEST_URI'], ['/', '/android', '/get'])): ?>
|
||||
<meta name="twitter:card" content="app"/>
|
||||
<?php if ($_SERVER['REQUEST_URI'] === '/' || $_SERVER['REQUEST_URI'] === '/android' || $_SERVER['REQUEST_URI'] === '/get'): ?>
|
||||
<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"/>
|
||||
|
||||
@@ -10,7 +10,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<div class="inner-wrap">
|
||||
<?php echo View::render('mail/_settingsForm', [
|
||||
'tags' => $tags,
|
||||
'emails' => $emails,
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<div class="inner-wrap">
|
||||
<?php if ($confirmSuccess ?? false): ?>
|
||||
<?php if (IS_PRODUCTION): ?>
|
||||
<?php js_start() ?>
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<div class="inner-wrap">
|
||||
<?php if ($error ?? false): ?>
|
||||
<div class="notice notice-error spacer1"><?php echo $error ?></div>
|
||||
<?php else: ?>
|
||||
|
||||
@@ -33,7 +33,6 @@
|
||||
<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="/i18n/set-culture" method="POST">
|
||||
<form action="/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 October 1st, 2019, LBRY has received:</p>
|
||||
<p>Through June 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/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"/>
|
||||
<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"/>
|
||||
</video>
|
||||
</a>
|
||||
</figure>
|
||||
|
||||
@@ -35,7 +35,7 @@
|
||||
<h2>Business</h2>
|
||||
</div>
|
||||
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery', 'julie-sigwart'] as $bioSlug): ?>
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery'] as $bioSlug): ?>
|
||||
<?php echo View::render('content/_bio', ['person' => $bioSlug]) ?>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
|
||||
@@ -11,199 +11,15 @@
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<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>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 82 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 420 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 175 KiB After Width: | Height: | Size: 656 KiB |
@@ -110,7 +110,7 @@
|
||||
}
|
||||
|
||||
position: relative;
|
||||
width: 520px;
|
||||
width: 450px;
|
||||
}
|
||||
|
||||
img {
|
||||
|
||||
Reference in new issue
Block a user