Compare commits
59
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
733b667275 | ||
|
|
20ebf24a44 | ||
|
|
c9cfc8baa3 | ||
|
|
b26ee5df30 | ||
|
|
bf25e7ebae | ||
|
|
e82da29618 | ||
|
|
4a3fabf2fd | ||
|
|
fecc4d1308 | ||
|
|
d7f62b1b24 | ||
|
|
d3af4a1729 | ||
|
|
5e73137d7e | ||
|
|
1a82b1f19f | ||
|
|
2346f7e0c6 | ||
|
|
2fd620ff50 | ||
|
|
1464fb94a6 | ||
|
|
f4d6908b2c | ||
|
|
1fd49428a6 | ||
|
|
8f696da5b5 | ||
|
|
cc4e21f381 | ||
|
|
e0e4eb7104 | ||
|
|
7a42856d32 | ||
|
|
fbbba49d24 | ||
|
|
6bbb8c426b | ||
|
|
c2546a6f81 | ||
|
|
9a070c7b3f | ||
|
|
1bc15aad39 | ||
|
|
e453bca309 | ||
|
|
b2184866f2 | ||
|
|
aec94f6380 | ||
|
|
40748f7726 | ||
|
|
34277316c7 | ||
|
|
161c878d49 | ||
|
|
9fb4d0bcc3 | ||
|
|
239692e90b | ||
|
|
ce438ce16a | ||
|
|
1cb87f3b1b | ||
|
|
d7f20e6827 | ||
|
|
5e5e7d4ab7 | ||
|
|
0dfeec9e82 | ||
|
|
666ecd57ab | ||
|
|
e6255f8b2a | ||
|
|
63726f19d3 | ||
|
|
00ff968546 | ||
|
|
5d25014536 | ||
|
|
188463e86b | ||
|
|
1b043683b4 | ||
|
|
ab371f0c5e | ||
|
|
1ce00e6c12 | ||
|
|
c22487b710 | ||
|
|
33a1a91fac | ||
|
|
dba257bef8 | ||
|
|
0f821a004c | ||
|
|
70ef9ac884 | ||
|
|
aa665db0b6 | ||
|
|
0661d9b0f0 | ||
|
|
7b8a0cdc65 | ||
|
|
35243efdc8 | ||
|
|
1a29e40318 | ||
|
|
f40ce4a86c |
No files matched your search
@@ -7,6 +7,7 @@
|
||||
"ext-xml": "*",
|
||||
"ext-pdo": "*",
|
||||
"ext-pdo_mysql": "*",
|
||||
"ext-json": "*",
|
||||
"leafo/scssphp": "0.7.6",
|
||||
"erusev/parsedown": "^1.6",
|
||||
"erusev/parsedown-extra": "^0.7.1",
|
||||
|
||||
Generated
+19
-18
@@ -4,7 +4,7 @@
|
||||
"Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
|
||||
"This file is @generated automatically"
|
||||
],
|
||||
"content-hash": "de5f8449179c92b9416b62185db66c94",
|
||||
"content-hash": "4df89eeabf27a1fde648e75d29109826",
|
||||
"packages": [
|
||||
{
|
||||
"name": "erusev/parsedown",
|
||||
@@ -200,16 +200,16 @@
|
||||
},
|
||||
{
|
||||
"name": "pelago/emogrifier",
|
||||
"version": "v2.1.1",
|
||||
"version": "v2.2.0",
|
||||
"source": {
|
||||
"type": "git",
|
||||
"url": "https://github.com/MyIntervals/emogrifier.git",
|
||||
"reference": "8ee7fb5ad772915451ed3415c1992bd3697d4983"
|
||||
"reference": "2472bc1c3a2dee8915ecc2256139c6100024332f"
|
||||
},
|
||||
"dist": {
|
||||
"type": "zip",
|
||||
"url": "https://api.github.com/repos/MyIntervals/emogrifier/zipball/8ee7fb5ad772915451ed3415c1992bd3697d4983",
|
||||
"reference": "8ee7fb5ad772915451ed3415c1992bd3697d4983",
|
||||
"url": "https://api.github.com/repos/MyIntervals/emogrifier/zipball/2472bc1c3a2dee8915ecc2256139c6100024332f",
|
||||
"reference": "2472bc1c3a2dee8915ecc2256139c6100024332f",
|
||||
"shasum": ""
|
||||
},
|
||||
"require": {
|
||||
@@ -227,7 +227,7 @@
|
||||
"type": "library",
|
||||
"extra": {
|
||||
"branch-alias": {
|
||||
"dev-master": "2.1.x-dev"
|
||||
"dev-master": "3.0.x-dev"
|
||||
}
|
||||
},
|
||||
"autoload": {
|
||||
@@ -240,16 +240,6 @@
|
||||
"MIT"
|
||||
],
|
||||
"authors": [
|
||||
{
|
||||
"name": "John Reeve",
|
||||
"email": "jreeve@pelagodesign.com"
|
||||
},
|
||||
{
|
||||
"name": "Cameron Brooks"
|
||||
},
|
||||
{
|
||||
"name": "Jaime Prado"
|
||||
},
|
||||
{
|
||||
"name": "Oliver Klee",
|
||||
"email": "github@oliverklee.de"
|
||||
@@ -258,9 +248,19 @@
|
||||
"name": "Zoli Szabó",
|
||||
"email": "zoli.szabo+github@gmail.com"
|
||||
},
|
||||
{
|
||||
"name": "John Reeve",
|
||||
"email": "jreeve@pelagodesign.com"
|
||||
},
|
||||
{
|
||||
"name": "Jake Hotson",
|
||||
"email": "jake@qzdesign.co.uk"
|
||||
},
|
||||
{
|
||||
"name": "Cameron Brooks"
|
||||
},
|
||||
{
|
||||
"name": "Jaime Prado"
|
||||
}
|
||||
],
|
||||
"description": "Converts CSS styles into inline style attributes in your HTML code",
|
||||
@@ -270,7 +270,7 @@
|
||||
"email",
|
||||
"pre-processing"
|
||||
],
|
||||
"time": "2018-12-10T10:36:30+00:00"
|
||||
"time": "2019-09-04T16:07:59+00:00"
|
||||
},
|
||||
{
|
||||
"name": "symfony/css-selector",
|
||||
@@ -338,7 +338,8 @@
|
||||
"ext-mbstring": "*",
|
||||
"ext-xml": "*",
|
||||
"ext-pdo": "*",
|
||||
"ext-pdo_mysql": "*"
|
||||
"ext-pdo_mysql": "*",
|
||||
"ext-json": "*"
|
||||
},
|
||||
"platform-dev": []
|
||||
}
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
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.
|
||||
File renamed without changes.
@@ -53,9 +53,9 @@ The LBRY Android App comes with its own wallet and is stored locally on your pho
|
||||
|
||||
If you do not opt for the [wallet sync program](https://lbry.com/faq/how-to-backup-wallet#sync), it is critical that you backup your own wallet locally or else the credits will be lost.
|
||||
|
||||
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to `Discovery`. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance and recent transactions.
|
||||
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to the Search bar. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance and recent transactions.
|
||||
|
||||

|
||||

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

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

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

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

|
||||
|
||||
7.Under the `Price`, first, determine if you want to make your content free or set a price in LBC per view.
|
||||
|
||||
8. Type in the URL you want the content to be found under, along with a minimum of 0.00000001 LBC deposit for the upload (default amount is higher due to publishing fees). If you are trying to outbid a user-friendly/common URL, the system will suggest a minimum bid to take over the content at that vanity URL. There may be a delay for this takeover. Making your bid higher will result in (better discovery)[https://lbry.com/faq/trending) for your content. For more details regarding the URL or bid, check out our [naming document](/faq/naming).
|
||||
|
||||

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

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

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

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

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

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

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

|
||||
|
||||
Right after the content is deleted, you should see the same content showing on the app screen, if you click on it, it will start the download again.
|
||||
|
||||
To delete additional content, please follow the same steps until you delete all the contents you do not need on your phone. We'll be improving this to allow for easier deletion multiple content at the same time.
|
||||
|
||||
### How Do I Enable Background Media Playback? {#backgroundmediaplayback}
|
||||
|
||||
When playing anything on the LBRY android app, it will stop playing when you minimize the app or switch to another application. Since we aren't YouTube and won't make you pay for subscription to enable background media playback, you can enable this feature in the app settings.
|
||||
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: What is censorship resistance and how does it apply to LBRY?
|
||||
category: publisher
|
||||
order: 3
|
||||
---
|
||||
|
||||
## What is censorship-resistance?
|
||||
At the risk of tautology, censorship-resistance is the ability to resist censorship. Less tautologically, censorship-resistance is the degree to which a system is tamper proof. That is, a censorship-resistant system means a third party cannot modify or remove content created by someone else.
|
||||
|
||||
Just as nothing in the world is theft proof, nothing in the world is censorship proof. When a bank builds twenty foot walls around a vault with 3-foot-thick steel door that is monitored by security cameras, it does not do so to make theft literally impossible. It does so to make theft of the goods inside sufficiently challenging that it is extraordinarily improbable. When we speak of censorship-resistance, we speak the same as of the bank vault. A system can never be literally censorship proof, but it can be made extremely censorship resistant.
|
||||
|
||||
So when speaking of censorship resistance with regards to LBRY, we are speaking about how challenging it is to modify or remove content from the LBRY network without permission from the publisher
|
||||
|
||||
## How censorship-resistant is LBRY?
|
||||
|
||||
We believe LBRY to be the most censorship-resistant system to ever exist for the purposes of publishing digital content.
|
||||
|
||||
To understand where LBRY’s censorship resistance comes from, we need to break the problem down into two areas: data (the digital content) and metadata (information about the digital content, such as it’s title or publisher).
|
||||
|
||||
In the case of the data itself, LBRY is as or more censorship-resistant as BitTorrent or other peer-to-peer networks. Like these other networks, when you publish a file, it ends up being hosted by dozens, hundreds, or thousands of other computers, depending on its popularity. Additionally, there are economic incentives to host content that is popular but undersupplied, which means that LBRY is even better than its predecessors, which were already world leaders in the censorship-resistance department.
|
||||
|
||||
In the case of the metadata, LBRY is truly novel. Previous peer-to-peer systems had decent censorship-resistance at the data level, but never the metadata. LBRY writes it’s metadata to a public blockchain, the same technology that powers the censorship-resistant Bitcoin. Metadata in the LBRY blockchain cannot be altered without a hard-fork of the network, which is an expensive and unlikely proposition. Even if this happened, it would be possible to roll-back the system to it’s last previously good state, resulting in only a temporary rather than permanent data loss.
|
||||
|
||||
## How could LBRY be censored?
|
||||
|
||||
An internet service provider or network operator could conceivably censor traffic to the LBRY network entirely, by blocking or dropping packets that appear to be part of the LBRY protocol. However, given that this traffic is typically encrypted, consists of otherwise ordinary TCP and UDP packets, and can be headed to or from basically any address on the internet, this would be fairly challenging.
|
||||
|
||||
If a network operator did find a way to block LBRY traffic at the network level, we would work tirelessly to continue to evolve the system to make this difficult or impossible.
|
||||
|
||||
## Why does censorship-resistance matter?
|
||||
|
||||
Censorship-resistance matters because there are many people in the world who would like to stop others from speaking. This can range in scale from national governments (China, North Korea, Iran) to college campuses (Evergreen).
|
||||
|
||||
Prosperity and freedom starts with the ability for people to communicate freely with one another. The ability to censor is the ability to control the narrative and spread propaganda.
|
||||
|
||||
For the purposes of discovering truth and fighting injustice, censorship-resistance is absolutely vital.
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Claiming LBRY Rewards
|
||||
category: tutorial
|
||||
order: 1
|
||||
---
|
||||
|
||||
Did you know you can earn LBC through the LBRY Rewards program just for watching sweet content and doing other simple actions? If not, today is your lucky day.
|
||||
|
||||

|
||||
|
||||
_On the left, navigating to Rewards in LBRY Desktop and lbry.tv. On the right, navigating to Rewards on LBRY Android._
|
||||
|
||||
You can find the rewards section under the Account menu > Rewards. On Android, click or slide out the menu, and then select Rewards. [Click here to navigate directly to your app](https://open.lbry.com/?rewards).
|
||||
|
||||
In addition to the one time rewards, we have a daily reward for watching content you love on LBRY - so make sure to check back often to keep earning!
|
||||
|
||||
LBC rewards can be used to buy content on the LBRY network, to support your favorite creators, or to publish yourself. Tipping creators also helps creators become discovered on LBRY by boosting their relevance in results.
|
||||
|
||||

|
||||
|
||||
You may need to complete account verification to participate in the rewards program. See our [Rewards](https://lbry.com/faq/rewards) for more information and details about what rewards are available.
|
||||
|
||||
### More Tutorials
|
||||
|
||||
If you’d like to learn more about how to get the most out of LBRY, check out our [other tutorials](https://lbry.com/faq?category=tutorial) or [Frequently Asked Questions](https://lbry.com/faq).
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: How does LBRY disclose its usage of LBC?
|
||||
category: other
|
||||
---
|
||||
|
||||
LBRY issues regular reports outlining its transaction history as well as the current state of LBRY, Inc.'s balance sheet and anticipated future expenditures.
|
||||
|
||||
### How do I view the reports?
|
||||
|
||||
The reports are publicly available on the [Credit Reports page](https://lbry.com/credit-reports). When a new report is issued, we post a link to our official Twitter. They are also usually mentioned in a community email message, though not as promptly. You can join our mailing list here.
|
||||
|
||||
### When are reports issued?
|
||||
|
||||
Reports are issued every 3 months in January, April, July, and October, covering the preceding 3 full months. There is no specific day within the month that the reports are issued, though we try to get them out promptly.
|
||||
|
||||
### Are the reports financial advice? Are they legally binding?
|
||||
The reports are not official or legal financial disclosures, nor do they formally or legally bind the company in any way. They are an attempt by us to provide transparency about our usage of LBC.
|
||||
|
||||
LBRY Inc. does not commit to following predictions made in the reports and reserves full rights to change how it uses LBC at any time.
|
||||
|
||||
### What happens if the reports contain a mistake?
|
||||
If we issue a report that was factually mistaken, we will update the report with a correction. If the mistake is caught within the same month that it was issued and was not substantial, the report will be updated without a notification other than a reply to the original Tweet.
|
||||
|
||||
If an error is noticed in the report outside of the month it was issued or the error was substantial, then we will publish a blog post and a separate Tweet announcing the correction, as well as leave a note in the report itself linking to the blog post explaining the mistake.
|
||||
@@ -7,7 +7,7 @@ We are listed on several exchanges. You can buy or sell LBRY Credits at one of t
|
||||
|
||||
### Traditional Exchanges
|
||||
- [Bittrex](https://bittrex.com/Market/Index?MarketName=BTC-LBC)
|
||||
- [Poloniex](https://poloniex.com/exchange#btc_lbc)
|
||||
- [Poloniex](https://poloniex.com/exchange#btc_lbc) (Currently in maintenance, working with Poloniex team to fix)
|
||||
- [Upbit](https://upbit.com/exchange?code=CRIX.UPBIT.BTC-LBC)
|
||||
- [Instant Bitex](https://instantbitex.com)
|
||||
- [Coinspot](https://www.coinspot.com.au/buy/lbc)
|
||||
@@ -15,7 +15,7 @@ We are listed on several exchanges. You can buy or sell LBRY Credits at one of t
|
||||
|
||||
### Instant Exchanges
|
||||
- [Shapeshift](https://shapeshift.io) (Currently unavailable, ShapeShift working on it. Requires free membership account now)
|
||||
- [Changelly](https://changelly.com/exchange/BTC/LBC/1)
|
||||
- [Changelly](https://changelly.com/exchange/BTC/LBC/1) (Currently unavailable)
|
||||
- [ChangeNow](https://changenow.io/exchange?amount=1&from=btc&to=lbc)
|
||||
- [Simple Swap](https://simpleswap.io)
|
||||
- [Stealthex](https://stealthex.io/)
|
||||
|
||||
@@ -9,4 +9,7 @@ While the LBRY app is running, it communicates to the network whatever content y
|
||||
|
||||
Think of it like how torrents or any other peer-to-peer (P2P) service works. First, you download a file from the host(s) that have made it available via seeding. When the download has finished, you become a host in the network (seeder) that other people can download from.
|
||||
|
||||
### Deleting hosted content
|
||||
You can delete files from the blob folder directly, or you can also delete them from the My LBRY section of the App - both will get rid of the hosted content and you'll lose the ability to seed it anymore.
|
||||
|
||||
**Please note: Hosting fees are currently disabled on the network as we're currently working on a better way to implement the fee structure.**
|
||||
@@ -5,6 +5,8 @@ category: troubleshooting
|
||||
|
||||
In certain cases, we may ask you to send us your log file(s). The current log file is titled `lbrynet.log` (or just `lbrynet` if you have file extensions hidden) and is archived each time the files reaches 2MB. Older log files are copied to `lbrynet.log.<#>`. Typically only the lbrynet.log file is required, but we may ask for the others depending on the situation. Since each Operating System has its own set of working directories, use the below guide in order to locate the log file(s).
|
||||
|
||||
[Find my logs without opening the app](#manual)
|
||||
|
||||
**lbrynet.log files may contain your IP address. While sharing this is not inherently dangerous, if you desire maximum privacy, please mask it before posting to public websites.**
|
||||
|
||||
### Find Logs via the LBRY App
|
||||
@@ -16,24 +18,24 @@ The folder will be highlighted, so just double click to open and here you will s
|
||||
### Sending log files from Android
|
||||
Navigate to the **About** page and use the **Send Logs** button at the bottom. You can email them to [help@lbry.com](mailto:help@lbry.com)
|
||||
|
||||
### Find Logs Manually
|
||||
## Windows
|
||||
### Find Logs Manually {#manual}
|
||||
#### Windows
|
||||
1. Open File Explorer (Keyboard shortcut: Windows Key + E).
|
||||
2. Type `%localappdata%\lbry\lbrynet` (or `%appdata%\lbrynet` if you originally installed v0.14 or earlier) into the address bar and click Enter.
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## MacOS
|
||||
#### MacOS
|
||||
1. Open Finder.
|
||||
2. Click Go in the top menu and choose "Go To Folder".
|
||||
3. Type "~/Library/Application Support/LBRY" and then click go.
|
||||
4. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## Ubuntu / Linux *(Exact steps may differ slightly)*
|
||||
#### Ubuntu / Linux *(Exact steps may differ slightly)*
|
||||
1. Navigate to your home directory. Ensure hidden files and folders are shown if using a graphical file explorer.
|
||||
2. Navigate to the `.local/share/lbry/lbrynet` folder (or `~/.lbrynet` if you originally installed v0.14 or earlier).
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
|
||||
## Android *(Exact steps may differ slightly)*
|
||||
#### Android *(Exact steps may differ slightly)*
|
||||
1. Launch your favorite file explorer.
|
||||
2. Navigate to `Internal storage\android\data\io.lbry.browser->files\lbrynet`.
|
||||
3. Here you will see the `lbrynet.log` file and any archives.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How do I get LBRY for development?
|
||||
title: How do I install LBRY for development and contributing?
|
||||
category: powerusers
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: Publishing Quickstart
|
||||
category: tutorial
|
||||
order: 3
|
||||
---
|
||||
|
||||
Publishing to LBRY allows anyone else in the world to access your content. You can publish any type of digital file to LBRY. Publishing requires a small amount of LBC, but almost all of this is returned if you decide to later unpublish. We'll cover that later. For now, get those [cat videos](https://beta.lbry.tv/cats:cb) ready!
|
||||
|
||||
This tutorial is meant to provide a quick overview. Our [Publishing FAQ](/faq/how-to-publish) covers publishing in even more detail.
|
||||
|
||||
We'll start with publishing on LBRY Desktop and lbry.tv. Scroll down or [click here](#android) for Android instructions.
|
||||
|
||||
### Publishing on Desktop and lbry.tv
|
||||
1. Click the **Publish** option from the Account drop down. You can also click **New Publish** from the Publishes page (right hand side).
|
||||
1. Select the file you want to publish by clicking **Choose File**. 
|
||||
1. Fill in details for the content you are uploading, including the title, tags, and description.
|
||||
1. For your video thumbnail, you can upload a thumbnail image or take one directly from your video. 
|
||||
1. For the channel section, you can choose to publish anonymously, select an existing channel, or create a new one.
|
||||

|
||||
1. Set a price for your content, if desired.
|
||||
1. Adjust the auto-suggested lbry:// URL and bid, if desired. ([learn more](/faq/naming) about how this works)
|
||||
1. Click **Publish** to submit your upload to the LBRY network! Please leave your app open so that the file can be properly seeded to the network.
|
||||
|
||||
Congratulations on publishing your first piece of content! Have any questions? Please see our [detailed Publishing FAQ](/faq/how-to-publish).
|
||||
|
||||
### Publishing on Android
|
||||
1. Select the **New Publish** option from the left hand menu.
|
||||
1. Select from: record a new video, snap a photo, select a file manually, or click an item from the recent videos/GIFs list.
|
||||
1. Fill in details for the content you are uploading, including the title, tags, and description.
|
||||
1. For the channel section, you can choose to publish anonymously, select an existing channel, or create a new one.
|
||||
1. You can adjust the auto-suggested lbry:// URL and bid as needed ([learn more](/faq/naming) and have the option of setting a price for your content.
|
||||
1. Set a price for your content, if desired.
|
||||
1. Adjust the auto-suggested lbry:// URL and bid, if desired. ([learn more](/faq/naming) about how this works)
|
||||
1. click **Publish** to submit your upload to the LBRY network!
|
||||
|
||||
Congratulations on publishing your first piece of content! Have any questions? Please see our [detailed Android FAQ](/faq/android-basics).
|
||||
|
||||

|
||||
|
||||
### More Tutorials
|
||||
|
||||
If you’d like to learn more about how to get the most out of LBRY, check out our [other tutorials](https://lbry.com/faq?category=tutorial) or [Frequently Asked Questions](https://lbry.com/faq).
|
||||
@@ -3,24 +3,24 @@ title: What are LBRY Rewards?
|
||||
category: getstarted
|
||||
---
|
||||
|
||||
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 3 Reward redemptions per day**.
|
||||
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 5 Reward redemptions per day**.
|
||||
|
||||

|
||||
|
||||
### Rewards Approval requirements
|
||||
### Rewards Approval Requirements
|
||||
|
||||
In order to be eligible for LBRY Rewards, users must have an approved account via [phone number](/faq/phone) or [credit card](/faq/identity-requirements) (there's also a manual approval method on [Discord](https://chat.lbry.com)). If users choose not to become approved for rewards, LBRY works with full functionality, but they will not be able to earn any free credits from LBRY. **Rewards will only be granted on a 1 account per household basis and LBRY reserves the right to revoke Rewards privileges on any account if abuse is suspected or if VPN/shared connections are used.**
|
||||
|
||||
### List of the current LBRY Rewards
|
||||
### List of Current LBRY Rewards
|
||||
| Reward | Amount | Description |
|
||||
--- | --- | ---
|
||||
| **Your First Nickel** | 6 LBC | A one-time welcome gift for learning the basics of the application & wallet. Including the purchase of paid content.
|
||||
| **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).
|
||||
@@ -32,12 +32,13 @@ Rewards are added to your LBC wallet balance as they are completed. All the rewa
|
||||
|
||||
If you are new to Publishing, check out [our guide](/faq/how-to-publish).
|
||||
|
||||
### Custom reward codes {#reward-code}
|
||||
### Custom Reward Codes {#reward-code}
|
||||
|
||||
Custom reward codes can be claimed via the [Rewards](https://open.lbry.com/?rewards) page in the LBRY app. You may have been given a reward code via email, social media or you stumbled upon it somewhere - whichever way, you can claim it for LBC today! It's simple, just hit `Enter Code`, type it in and press `Redeem`.
|
||||
|
||||

|
||||
|
||||
|
||||
### Having Trouble?
|
||||
|
||||
If you have any questions or problems with receiving the Rewards, feel free to [reach out to us](/faq/support).
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Searching for Content
|
||||
category: tutorial
|
||||
order: 2
|
||||
---
|
||||
|
||||
Searching for content on the LBRY Desktop and Android apps is easy. We'll start with lbry.tv and Desktop first, then cover [Android below](#android).
|
||||
|
||||
### Searching on Desktop and lbry.tv
|
||||
|
||||
Click your cursor into the top bar, and enter a search term. Typically, you'll see at least 3 items at the top:
|
||||
1. **Search** - Default if enter is clicked. This is your typical search option, will return all results matching it.
|
||||
2. **Exact URL** - Select this to navigate directly to the content published at `lbry://comics`
|
||||
3. **Tag** - Select this to navigate to the tag page to browse all content tagged `comics`
|
||||
|
||||

|
||||
|
||||
After performing a search, you'll have access to additional filter to help narrow down the results.
|
||||
- Filtering to _files_ will return content published according to the selected file types.
|
||||
- Filtering to _channels_ will return only channel results.
|
||||
|
||||

|
||||
|
||||
### Searching on Android {#android}
|
||||
|
||||
Select the top bar and begin typing. Once you pause or click enter, the search results will appear. Currently there are no filtering options on this platform.
|
||||
|
||||

|
||||
|
||||
### More Tutorials
|
||||
|
||||
If you’d like to learn more about how to get the most out of LBRY, check out our [other tutorials](https://lbry.com/faq?category=tutorial) or [Frequently Asked Questions](https://lbry.com/faq).
|
||||
@@ -12,9 +12,9 @@ Another common cause of this issue is the lack of access to UDP port 4444. LBRY
|
||||
|
||||
1. Shutdown LBRY and lbrynet-daemon (check running processes using Task Manager on Windows or Activity Monitor on Mac OS.)
|
||||
2. Go to your [lbrynet folder](/faq/lbry-directories).
|
||||
3. If you have a `daemon_settings.yml` file, add this line to it at the end (44444 is an example, can be changed): `dht_node_port: 44444`.
|
||||
3. If you have a `daemon_settings.yml` file, add this line to it at the end (4444 is an example, can be changed): `dht_node_port: 4444`.
|
||||
4. If you don't have the `daemon_settings.yml` file, you can create one or download/copy [this sample](https://goo.gl/a5uJq5) into the `lbrynet` folder.
|
||||
5. Start LBRY and try to download a couple of items from the homepage. Be patient, if it doesn't work, leave the page and try again or a different video.
|
||||
6. Depending on your network, you may need UDP port 44444 (the new port you just set up) forwarded. Also, for file sharing to work properly, you may need TCP port 3333 open/forwarded. This can be verified by using a [port checker tool](http://www.canyouseeme.org) on port 3333. Port 44444 will fail since it's UDP.
|
||||
6. Depending on your network, you may need UDP port 4444 (the new port you just set up) forwarded. Also, for file sharing to work properly, you may need TCP port 3333 open/forwarded. This can be verified by using a [port checker tool](http://www.canyouseeme.org) on port 3333. Port 4444 will fail since it's UDP.
|
||||
|
||||
If you continue to experience issues streaming/downloading content after completing the above steps, please [reach out to us](/faq/how-to-report-bugs) for additional support.
|
||||
+11
-4
@@ -4,15 +4,15 @@ category: publisher
|
||||
order: 4
|
||||
---
|
||||
|
||||
***Service Announcement: Our queue is a bit behind at the moment, so please bear with us! You'll receive an email once your sync is complete. If you qualify for a reward (i.e., if you have over 1000 subscribers and have recently posted content), you will be able to claim this in the app. Please continue reading below...***
|
||||
***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***
|
||||
|
||||
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 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.**
|
||||
***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).**
|
||||
|
||||
**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!**
|
||||
**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!**
|
||||
|
||||
### 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.
|
||||
@@ -42,9 +42,16 @@ You can delete this channel and any content you published using the transactions
|
||||
|
||||
You won't see your content in the LBRY app under `Publishes` nor have control of the channel until LBRY transfers control of the synced content to you. We're actively working on an automated process for this which will be ready by the end of the northern hemisphere summer. However, your content will be accessible through the LBRY Desktop app and [LBRY.tv](https://beta.lbry.tv) (see the links in your sync email). If you have over 50K subscribers and want to do this via a manual process, see the [wallet claim page](https://lbry.com/claim-wallet)
|
||||
|
||||
### What's the difference between Sync and Transfer?
|
||||
### What's the difference between Sync and Transfer? {#transfer}
|
||||
|
||||
When a channel is synced, it means the content has been mirrored to LBRY and available on the network for anyone to view. YouTubers will get an email once this is completed. The transfer process is described in the important notice above, which is the final step of sending the channel and content to the YouTuber's wallet so they can publish/control the content. This last step is still being actively developed and we'll let you know via email once the content is ready to be transferred. Until then, you won't see the channel/content in your Publishes section, nor be able to publish as that channel outside of the YouTube sync process.
|
||||
|
||||
Feature | Sync | Transfer |
|
||||
:------------ | :-------------| :-------------|
|
||||
Your Youtube publishes will be synced | yes | yes |
|
||||
You have access to content and channel LBC from tips | no | yes |
|
||||
Your content shows up in the app under your Publishes | no | yes |
|
||||
You are responsible for keeping your wallet safe | no | yes |
|
||||
You can use the app to publish to the channel | no | yes |
|
||||
|
||||
If you're having any trouble with the sync process or receiving your credits, please contact [help@lbry.com](mailto:help@lbry.com).
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
author: brinck-slattery
|
||||
title: 'The Birth Of Entertainment'
|
||||
date: '2020-11-17 14:00:00'
|
||||
date: '2018-01-17 15:30:00'
|
||||
cover: 'muses.jpg'
|
||||
category: content
|
||||
---
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
author: samuel-lbryian
|
||||
title: 'LBRY Blockchain Update'
|
||||
date: '2019-9-10 09:00:00'
|
||||
cover: 'blockchaintech.jpg'
|
||||
category: update
|
||||
---
|
||||
|
||||
On August 16, 2019, the LBRY chain experienced an unexpected fork between the current version of lbrycrd (v0.17.2) and previous versions. Block height of the fork: 617743. We might have favored the older build, but older versions of lbrycrd would crash when receiving data from the newer version after that block. v0.17.1 was able to proceed down its own chain, but there was little mining power behind this; the main pools were already mining with majority of hash on the correct (v0.17.2) chain.
|
||||
|
||||
This was middle of the night for most LBRY engineers, but the event was fortunately detected by a LBRY engineer three hours after the occurrence. In response to the incident, miners and other critical systems were immediately upgraded to v0.17.2. We appreciate the immediate and dedicated response from the various mining pools, exchanges, and others.
|
||||
|
||||
Version 0.17.2 replaces a large portion of the consensus-critical code path with more memory-efficient mechanisms. When this work was done, two existing issues with the takeover height computation were discovered in the older code. An effort was made to search for others through random block data generation. No other issues were found at the time, and it was hoped that there were no other lurking issues with the old code. The two known issues were maintained with workarounds in hopes that the root hash computation would match the existing versions, but it was done in a way that they would be disabled with the next hard-fork (not released yet). Details on the bugs are to be revealed after the pending hard fork occurs.
|
||||
|
||||
In block 617743, the newer code for the hash computation incorrectly decided that a certain claim required the takeover height workaround. It was a failure to completely model the previous erroneous behavior. Other blocks in the future may be affected, but the behavior will likely go undetected as most are now upgraded to the latest release. We appreciate your patience in the matter. Sincerely, blockchain@lbry.com
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
author: jeremy-kauffman
|
||||
title: 'What Is Censorship Resistance, And Why Does It Matter?'
|
||||
date: '2019-9-10 12:00:00'
|
||||
cover: 'censorship2.jpg'
|
||||
category: update
|
||||
---
|
||||
|
||||
## What is censorship-resistance?
|
||||
At the risk of tautology, censorship-resistance is the ability to resist censorship. Less tautologically, censorship-resistance is the degree to which a system is tamper proof. That is, a censorship-resistant system means a third party cannot modify or remove content created by someone else.
|
||||
|
||||
Just as nothing in the world is theft proof, nothing in the world is censorship proof. When a bank builds twenty foot walls around a vault with 3-foot-thick steel door that is monitored by security cameras, it does not do so to make theft literally impossible. It does so to make theft of the goods inside sufficiently challenging that it is extraordinarily improbable. When we speak of censorship-resistance, we speak the same as of the bank vault. A system can never be literally censorship proof, but it can be made extremely censorship resistant.
|
||||
|
||||
So when speaking of censorship resistance with regards to LBRY, we are speaking about how challenging it is to modify or remove content from the LBRY network without permission from the publisher
|
||||
|
||||
## How censorship-resistant is LBRY?
|
||||
|
||||
We believe LBRY to be the most censorship-resistant system to ever exist for the purposes of publishing digital content.
|
||||
|
||||
To understand where LBRY’s censorship resistance comes from, we need to break the problem down into two areas: data (the digital content) and metadata (information about the digital content, such as it’s title or publisher).
|
||||
|
||||
In the case of the data itself, LBRY is as or more censorship-resistant as BitTorrent or other peer-to-peer networks. Like these other networks, when you publish a file, it ends up being hosted by dozens, hundreds, or thousands of other computers, depending on its popularity. Additionally, there are economic incentives to host content that is popular but undersupplied, which means that LBRY is even better than its predecessors, which were already world leaders in the censorship-resistance department.
|
||||
|
||||
In the case of the metadata, LBRY is truly novel. Previous peer-to-peer systems had decent censorship-resistance at the data level, but never the metadata. LBRY writes it’s metadata to a public blockchain, the same technology that powers the censorship-resistant Bitcoin. Metadata in the LBRY blockchain cannot be altered without a hard-fork of the network, which is an expensive and unlikely proposition. Even if this happened, it would be possible to roll-back the system to it’s last previously good state, resulting in only a temporary rather than permanent data loss.
|
||||
|
||||
## How could LBRY be censored?
|
||||
|
||||
An internet service provider or network operator could conceivably censor traffic to the LBRY network entirely, by blocking or dropping packets that appear to be part of the LBRY protocol. However, given that this traffic is typically encrypted, consists of otherwise ordinary TCP and UDP packets, and can be headed to or from basically any address on the internet, this would be fairly challenging.
|
||||
|
||||
If a network operator did find a way to block LBRY traffic at the network level, we would work tirelessly to continue to evolve the system to make this difficult or impossible.
|
||||
|
||||
## Why does censorship-resistance matter?
|
||||
|
||||
Censorship-resistance matters because there are many people in the world who would like to stop others from speaking. This can range in scale from national governments (China, North Korea, Iran) to college campuses (Evergreen).
|
||||
|
||||
Prosperity and freedom starts with the ability for people to communicate freely with one another. The ability to censor is the ability to control the narrative and spread propaganda.
|
||||
|
||||
For the purposes of discovering truth and fighting injustice, censorship-resistance is absolutely vital.
|
||||
@@ -0,0 +1,194 @@
|
||||
---
|
||||
author: tom-zarebczan
|
||||
title: 'Development Update for August 2019'
|
||||
date: '2019-09-10 20:00:00'
|
||||
cover: 'tech-cover.jpg'
|
||||
category: community-update
|
||||
---
|
||||
Welcome to the August 2019 LBRY Development update! In this post we’ll show you what we’ve been up to since our [last update in July](https://lbry.com/news/jun-july-dev). Sit tight, there’s been lots of progress and releases, including updates from the Apps (Desktop and Mobile), SDK, and blockchain teams!
|
||||
|
||||
To read previous updates, please visit our [Development and Community Update archive](https://lbry.com/news/category/community-update).
|
||||
|
||||
If you want to see a condensed view of what we have completed recently and what’s planned for LBRY, check out our [Roadmap](https://lbry.io/roadmap).
|
||||
|
||||
First off, let’s start with some GitHub stats across all our repos (some of which are internal only to LBRY) since our last update about 40 days ago:
|
||||
36 repos were updated. 617 issues and pull requests were created, 146 were closed. 18 pull requests were merged. 30 GitHub users outside of LBRY made code contributions, including:
|
||||
- [AlessandroSpallina](https://github.com/AlessandroSpallina)
|
||||
- [Borewit](https://github.com/Borewit)
|
||||
- [btzr-io](https://github.com/btzr-io)
|
||||
- [ceoger](https://github.com/ceoger)
|
||||
- [dittaeva](https://github.com/dittaeva)
|
||||
- [eggplantbren](https://github.com/eggplantbren)
|
||||
- [nestordominguez](https://github.com/nestordominguez)
|
||||
- [vv181](https://github.com/vv181)
|
||||
- [ykris45](https://github.com/ykris45)
|
||||
- [zxawry](https://github.com/zxawry)
|
||||
|
||||
Thanks to everyone who took time out of their busy days to help LBRY out!
|
||||
|
||||
## In this report, we cover updates for
|
||||
* [Desktop App](#summary-desktop)
|
||||
* [SDK](#summary-sdk)
|
||||
* [Blockchain](#blockchain)
|
||||
* [LBRY.tv](#web)
|
||||
* [LBRY for Android](#android)
|
||||
* [Rewards](#rewards)
|
||||
* [Cross Device Syncing](#cross)
|
||||
* [YouTube Sync Transfers](#youtube)
|
||||
* [Community Block Explorer](#explorer)
|
||||
* [2019 Roadmap Progress](#roadmap)
|
||||
|
||||
### Desktop App {#summary-desktop}
|
||||
Since our last development update, the app team shipped our next named release, 0.35, under codename [Franklin](https://lbry.com/news/franklin-is-minted) as well as a few patches. Franklin enhances the app experience with a brand new [videojs-based](https://github.com/videojs/video.js) video player.
|
||||
|
||||
Other new features in Franklin include:
|
||||
- The ability to continue watching videos in pop out mode
|
||||
- Support of range requests (streaming)
|
||||
- The ability to block channels app-wide
|
||||
|
||||
The patch releases included some new features:
|
||||
- All new features added to the SDK between version 0.38.5 and 0.40, including improved wallet sync behavior, download speeds, and overall connectivity ([more details below](#summary-sdk))
|
||||
- Tipping on channel pages (which gets sent to the channel claim, as opposed to content claims on file pages)
|
||||
- Ability to set the time period for dark mode
|
||||
- Improvements to the display of URLs (now has the [canonical URL](https://lbry.tech/glossary#canonical-url) which uses both channel and claim short IDs)
|
||||
- Support for a new daily watch reward that went live on September 10th (replacing the weekly LBRYCast)
|
||||
|
||||
The patches fixed many bugs, including:
|
||||
- Issues with bid amounts required on the publish page (did not show vanity URL bids),
|
||||
- Auto-downloading subscription content
|
||||
- Search bar focus getting stuck
|
||||
- Disabling autoplay on paid content
|
||||
- DMCA blocking to include entire channels
|
||||
|
||||
We also updated our digital certificate for Windows builds which is an annual maintenance task. We'll explore a better solution for this down the road.
|
||||
|
||||

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

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

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

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

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

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

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

|
||||
|
||||
### 2019 Roadmap {#roadmap}
|
||||
We’ve successfully accomplished a number of roadmap items fully, while others are partially complete and ongoing efforts. See our [previous development report](https://lbry.com/news/jun-july-dev) on updates for completed ones.
|
||||
|
||||
Partially completed/still in progress are:
|
||||
* **Commenting** - moderation features are in progress
|
||||
* **Creator Features** - granular account balances in process
|
||||
* **Creator Partnerships** - no update since last month - in progress and will be announced later this year
|
||||
* **LBRY on the Web** - account features which are set to go live this month.
|
||||
* **Multi-Device Experience** - app settings/data syncing in progress, wallet sync to come soon after.
|
||||
* **Internationalization** - ongoing internationalization enhancements are in progress on Desktop.
|
||||
* **Protocol Performance** - improved download performance in 0.39 releases. Holepunching research in progress.
|
||||
|
||||
# Limited Reward Code!
|
||||
We’ve got a special bonus for readers of this update, enjoy some LBC via this code (while supplies last!): `dev-update-aug-jkala`
|
||||
|
||||
# Want to Develop on the LBRY ecosystem?
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a developer and want to find out more? Check out our [contributing guide](https://lbry.tech/contribute) and our [LBRY App specific contributing document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Make sure you have turned on the Developer option in your email preferences (see app overview page), or sign up at [lbry.tech](https://lbry.tech). We also have a [LBRY Discourse Forum](https://discourse.lbry.io) where developers can interact with the team and ask questions across all our different projects.
|
||||
|
||||
If you aren’t part of our Discord community yet, [join us](https://chat.lbry.com) anytime and say hello!
|
||||
|
||||
Our community allows LBRYians to interact with the team directly and for us to engage users in order to grow the LBRY platform. Also follow us on [Twitter](https://twitter.com/lbryio), [Facebook](https://facebook.com/lbryio), [Reddit](https://www.reddit.com/r/lbry), [BitcoinTalk](https://bitcointalk.org/index.php?topic=5116826.new#new), and [Telegram](https//t.me/lbryofficial).
|
||||
|
||||
Thanks for supporting LBRY - stay tuned for more news and updates! And if you haven’t downloaded the [LBRY app](https://lbry.io/get?auto=1) yet, what are you waiting for?
|
||||
|
||||
@@ -137,10 +137,13 @@ class Controller
|
||||
|
||||
$router->get('/follow/{claim}', 'AcquisitionActions::executeFollowCampaign');
|
||||
|
||||
$router->get('/i18n/get/{project}/{resource}/{language}.json', 'i18nActions::executeServeTranslationFile');
|
||||
|
||||
$router->get('/news/category/{category}', 'ContentActions::executePostCategoryFilter');
|
||||
|
||||
$router->post('/set-culture', 'i18nActions::setCulture');
|
||||
$router->post('/i18n/set-culture', 'i18nActions::setCulture');
|
||||
|
||||
$router->get('/snapshot/{type}', 'DownloadActions::executeDownloadSnapshot');
|
||||
|
||||
$permanentRedirectsPath = ROOT_DIR . '/data/redirect/permanent.yaml';
|
||||
$tempRedirectsPath = ROOT_DIR . '/data/redirect/temporary.yaml';
|
||||
|
||||
@@ -98,6 +98,7 @@ class ContentActions extends Actions
|
||||
$allCategories = [
|
||||
'LBRY 101' => 'Intro to LBRY',
|
||||
'getstarted' => 'Getting Started',
|
||||
'tutorial' => 'LBRY Tutorials',
|
||||
'publisher' => 'Publishers and Creators',
|
||||
'troubleshooting' => 'Help and Troubleshooting',
|
||||
'powerusers' => 'LBRY for Power Users',
|
||||
|
||||
@@ -15,6 +15,23 @@ class DownloadActions extends Actions
|
||||
return Controller::redirect(GitHub::getRepoReleaseUrl($repo, OS::getOsForExtension($ext), $allowPrerelease) ?: '/get', 302);
|
||||
}
|
||||
|
||||
public static function executeDownloadSnapshot(string $type)
|
||||
{
|
||||
if (!in_array($type, ['blockchain', 'wallet'])) {
|
||||
return ['page/404'];
|
||||
}
|
||||
|
||||
$bucketName = "snapshots.lbry.com";
|
||||
$bucket = S3::getBucket($bucketName, "$type/");
|
||||
|
||||
if (!count($bucket)) {
|
||||
return ['page/404'];
|
||||
}
|
||||
|
||||
krsort($bucket);
|
||||
|
||||
return Controller::redirect("http://$bucketName/" . array_keys($bucket)[0], 302);
|
||||
}
|
||||
/*
|
||||
* this is a quick fix to add android, prob not proper design
|
||||
*/
|
||||
|
||||
@@ -22,4 +22,18 @@ 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);
|
||||
}
|
||||
}
|
||||
@@ -12,4 +12,5 @@ $config = [];
|
||||
// $config[Config::MAILCHIMP_KEY] = '';
|
||||
// $config[Config::AWS_LOG_ACCESS_KEY] = '';
|
||||
// $config[Config::AWS_LOG_SECRET_KEY] = '';
|
||||
// $config[Config::TRANSIFEX_API_KEY] = '';
|
||||
return $config;
|
||||
@@ -17,6 +17,7 @@
|
||||
/faq/claimtrie-implementation: https://lbry.tech/resources/lbry-claimtrie
|
||||
/faq/proof-algorithm: https://lbry.tech/resources/pow
|
||||
/faq/regtest-setup-guide: https://lbry.tech/resources/regtest-setup
|
||||
/faq/bounty https://lbry.com/faq/how-to-get-lbry-command-line
|
||||
|
||||
# FAQ
|
||||
/faq/tips: /faq/appreciation
|
||||
|
||||
Vendored
+18
@@ -0,0 +1,18 @@
|
||||
<?php
|
||||
|
||||
|
||||
class Transifex
|
||||
{
|
||||
public static function isConfigured() {
|
||||
return (boolean)Config::get(Config::TRANSIFEX_API_KEY);
|
||||
}
|
||||
|
||||
public static function getTranslationResourceFile($project, $resource, $language)
|
||||
{
|
||||
$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);
|
||||
}
|
||||
}
|
||||
@@ -15,6 +15,7 @@ class Config
|
||||
const GITHUB_PERSONAL_AUTH_TOKEN = 'github_personal_auth_token';
|
||||
const LBRY_API_SERVER = "lbry_api_server";
|
||||
const MAILCHIMP_KEY = "mailchimp_key";
|
||||
const TRANSIFEX_API_KEY = 'transifex_api_key';
|
||||
const AWS_LOG_ACCESS_KEY = "aws_log_access_key";
|
||||
const AWS_LOG_SECRET_KEY = "aws_log_secret_key";
|
||||
const MAILGUN_API_KEY = "mailgun_api_key";
|
||||
|
||||
@@ -20,7 +20,7 @@ class OS
|
||||
'Android',
|
||||
'icon-android',
|
||||
false,
|
||||
false,
|
||||
"Android",
|
||||
"<span class='icon-android icon-fw'></span> Android"
|
||||
];
|
||||
|
||||
@@ -30,7 +30,7 @@ class OS
|
||||
'iOS',
|
||||
'icon-mobile',
|
||||
false,
|
||||
false,
|
||||
"iOS",
|
||||
"<span class='icon-ios icon-fw'></span> iOS"
|
||||
];
|
||||
|
||||
|
||||
@@ -71,7 +71,7 @@ class Response
|
||||
|
||||
public static function getMetaTitle()
|
||||
{
|
||||
return static::$metaTitle;
|
||||
return trim(static::$metaTitle);
|
||||
}
|
||||
|
||||
public static function guessMetaTitle($content)
|
||||
@@ -82,11 +82,11 @@ class Response
|
||||
if ($headerValue == '1' || !$title) {
|
||||
$title = $titleMatches[2][$matchIndex];
|
||||
if ($headerValue == '1') {
|
||||
return $title;
|
||||
return trim($title);
|
||||
}
|
||||
}
|
||||
}
|
||||
return $title;
|
||||
return trim($title);
|
||||
}
|
||||
|
||||
public static function getJsCalls()
|
||||
@@ -192,11 +192,6 @@ 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);
|
||||
|
||||
@@ -224,7 +224,7 @@
|
||||
|
||||
<div class="v-card">
|
||||
<figure>
|
||||
<img alt="Rob Smith, Head of Product Growth" src="https://spee.ch/7/rob-smith1.png"/>
|
||||
<img alt="Brinck Slattery, Director of Communications" src="https://spee.ch/@Memes:26/brinck-slattery1.png"/>
|
||||
</figure>
|
||||
|
||||
<info>
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
<section class="hero hero--half-height">
|
||||
<div class="inner-wrap inner-wrap--center-hero">
|
||||
<h1>
|
||||
<?php echo __('download.for-os2', ['%os%' => OS::OS_DETAIL($os)[5]]) ?>
|
||||
<?php echo __('download.for-os2', ['%os%' => OS::OS_DETAIL($os)[4]]) ?>
|
||||
</h1>
|
||||
</div>
|
||||
</section>
|
||||
@@ -49,8 +49,8 @@
|
||||
playsinline
|
||||
style="display: block; margin-right: auto; margin-left: auto; max-width: 700px; "
|
||||
>
|
||||
<source src="https://spee.ch/a/2019-08-lbry-interface-webm.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/4/2019-08-lbry-interface.mp4" type="video/mp4"/>
|
||||
<source src="https://spee.ch/b/2019-09-lbry-interface-webm-2.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/0/2019-09-lbry-interface-mp4-2.mp4" type="video/mp4"/>
|
||||
</video>
|
||||
<?php endif ?>
|
||||
|
||||
|
||||
@@ -6,6 +6,7 @@
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, target-densitydpi=device-dpi"/>
|
||||
|
||||
<?php $title = Response::getMetaTitle() ?: Response::guessMetaTitle($content) ?>
|
||||
<?php $images = Response::getMetaImages() ?>
|
||||
<?php $title = $title ?
|
||||
$title . (strpos($title, 'LBRY') === false ? ' - LBRY' : '') :
|
||||
'LBRY' ?>
|
||||
@@ -39,38 +40,42 @@
|
||||
<link rel="alternate" type="application/rss+xml" title="LBRY News" href="<?php echo ContentActions::URL_NEWS . '/' . ContentActions::SLUG_RSS ?>"/>
|
||||
<?php endif ?>
|
||||
|
||||
<meta property="og:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php foreach ($images as $image): ?>
|
||||
<meta property="og:image" content="<?php echo $image ?>"/>
|
||||
<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:card" content="app"/>
|
||||
<meta name="twitter:site" content="@LBRYio"/>
|
||||
<meta name="twitter:site" content="@lbryio"/>
|
||||
<meta name="twitter:creator" content="@lbryio"/>
|
||||
<meta name="twitter:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php if ($images): ?>
|
||||
<?php $url = reset($images) ?>
|
||||
<meta name="twitter:image" content="<?php echo $url ?>" />
|
||||
<?php endif ?>
|
||||
|
||||
<?php if ($_SERVER['REQUEST_URI'] === '/' || $_SERVER['REQUEST_URI'] === '/android' || $_SERVER['REQUEST_URI'] === '/get'): ?>
|
||||
<?php if (in_array($_SERVER['REQUEST_URI'], ['/', '/android', '/get'])): ?>
|
||||
<meta name="twitter:card" content="app"/>
|
||||
<meta name="twitter:app:country" content="US"/>
|
||||
<meta name="twitter:app:name:googleplay" content="LBRY beta"/>
|
||||
<meta name="twitter:app:id:googleplay" content="io.lbry.browser"/>
|
||||
<meta name="twitter:app:url:googleplay" content="https://play.google.com/store/apps/details?id=io.lbry.browser"/>
|
||||
<?php else: ?>
|
||||
<meta name=”twitter:card” content=”summary_large_image”>
|
||||
<?php endif ?>
|
||||
|
||||
<!-- Twitter Card data -->
|
||||
<meta name="twitter:site" content="@lbryio">
|
||||
<meta name="twitter:creator" content="@lbryio">
|
||||
|
||||
<meta property="fb:app_id" content="1673146449633983"/>
|
||||
|
||||
<!-- Open Graph data -->
|
||||
<meta property="og:description" content="<?php echo Response::getMetaDescription() ?>"/>
|
||||
<?php foreach (Response::getMetaImages() as $image): ?>
|
||||
<meta property="og:image" content="<?php echo $image ?>"/>
|
||||
<meta property="og:image:height" content="1125"/>
|
||||
<meta property="og:image:width" content="2000"/>
|
||||
<?php endforeach ?>
|
||||
<meta property="og:site_name" content="LBRY"/>
|
||||
<meta property="og:title" content="<?php echo $title ?>"/>
|
||||
<meta property="og:type" content="article"/>
|
||||
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
|
||||
<base target="_parent"/>
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<?php if ($confirmSuccess ?? false): ?>
|
||||
<?php if (IS_PRODUCTION): ?>
|
||||
<?php js_start() ?>
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<div class="inner-wrap" style="position: relative;">
|
||||
<?php if ($error ?? false): ?>
|
||||
<div class="notice notice-error spacer1"><?php echo $error ?></div>
|
||||
<?php else: ?>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
</div>
|
||||
<?php /*
|
||||
<div class="control-item no-label-desktop">
|
||||
<form action="/set-culture" method="POST">
|
||||
<form action="/i18n/set-culture" method="POST">
|
||||
<select id="language-dropdown" name="culture">
|
||||
<?php foreach ($cultures as $culture): ?>
|
||||
<option value="<?php echo $culture ?>" <?php echo $culture == $selectedCulture ? 'selected="selected"' : '' ?>>
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
|
||||
<section>
|
||||
<div class="inner-wrap">
|
||||
<p>Through September 1st, 2019, LBRY has received:</p>
|
||||
<p>Through October 1st, 2019, LBRY has received:</p>
|
||||
|
||||
<ul>
|
||||
<li>Zero National Security Letters</li>
|
||||
|
||||
@@ -21,8 +21,8 @@
|
||||
poster="https://spee.ch/f/2019-08-lbry-interface-poster.jpg"
|
||||
playsinline
|
||||
>
|
||||
<source src="https://spee.ch/a/2019-08-lbry-interface-webm.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/4/2019-08-lbry-interface.mp4" type="video/mp4"/>
|
||||
<source src="https://spee.ch/b/2019-09-lbry-interface-webm-2.webm" type="video/webm"/>
|
||||
<source src="https://spee.ch/0/2019-09-lbry-interface-mp4-2.mp4" type="video/mp4"/>
|
||||
</video>
|
||||
</a>
|
||||
</figure>
|
||||
|
||||
@@ -35,7 +35,7 @@
|
||||
<h2>Business</h2>
|
||||
</div>
|
||||
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery'] as $bioSlug): ?>
|
||||
<?php foreach (['josh-finer', 'tom-zarebczan', 'brinck-slattery', 'julie-sigwart'] as $bioSlug): ?>
|
||||
<?php echo View::render('content/_bio', ['person' => $bioSlug]) ?>
|
||||
<?php endforeach ?>
|
||||
</section>
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 420 KiB |
Reference in new issue
Block a user