Compare commits

...
25 Commits
Author SHA1 Message Date
Thomas Zarebczan b585e8b9ac updates 2019-09-26 10:38:14 -04:00
Thomas Zarebczan 456c5abd6d Create privacy-and-data.md 2019-09-19 12:41:18 -04:00
Jeremy Kauffman d7f62b1b24 Revert "pull tag data from api.lbry.com (#1097)"
This reverts commit 5e73137d7e.
2019-09-18 14:51:57 -04:00
AlessandroSpallina d3af4a1729 fix typo (#1119) 2019-09-18 11:53:27 -04:00
Jeremy Kauffman 5e73137d7e pull tag data from api.lbry.com (#1097) 2019-09-18 11:37:26 -04:00
Thomas Zarebczan 1a82b1f19f fix date 2019-09-17 15:25:17 -04:00
Thomas Zarebczan 2346f7e0c6 Update exchanges.md 2019-09-17 09:04:37 -04:00
Thomas Zarebczan 2fd620ff50 add anchor, fix checkboxes 2019-09-16 14:15:23 -04:00
jessopb 1464fb94a6 Update youtube.md 2019-09-16 12:40:44 -04:00
Thomas Zarebczan f4d6908b2c add link to top 2019-09-16 11:20:38 -04:00
Thomas Zarebczan 1fd49428a6 heading size 2019-09-13 18:47:57 -04:00
Thomas Zarebczan 8f696da5b5 add anchor 2019-09-13 18:47:06 -04:00
Thomas Zarebczan cc4e21f381 Update host-content.md 2019-09-13 17:48:06 -04:00
Alex Grintsvayg e0e4eb7104 newest snapshot first 2019-09-13 17:02:54 -04:00
Alex Grintsvayg 7a42856d32 add snapshot redirect 2019-09-13 15:07:46 -04:00
Thomas Zarebczan fbbba49d24 Update rewards.md 2019-09-13 09:05:57 -04:00
Jeremy Kauffman 6bbb8c426b fix typo 2019-09-12 18:02:55 -04:00
Jeremy Kauffman c2546a6f81 fix typo 2019-09-12 17:59:09 -04:00
Jeremy Kauffman 9a070c7b3f cache i18n strings 2019-09-12 17:48:28 -04:00
Niko 1bc15aad39 fix port typo 2019-09-12 23:44:21 +02:00
Jeremy Kauffman e453bca309 allow i18n file loading from any origin 2019-09-12 17:41:40 -04:00
Jeremy Kauffman b2184866f2 add multiple twitter card types 2019-09-12 12:55:24 -04:00
Jeremy Kauffman aec94f6380 add twitter:image metadata 2019-09-12 12:47:48 -04:00
Thomas Zarebczan 40748f7726 capitalization 2019-09-11 17:17:34 -04:00
Thomas Zarebczan 34277316c7 remove bounty FAQ, redirects (#1117)
* archive bounty faq

will re-direct, check if we have a faq leading to lbry.tech/contribute

* Update how-to-get-lbry-command-line.md

* Update permanent.yaml
2019-09-11 15:58:08 -04:00
17 changed files with 162 additions and 55 deletions

No files matched your search

File renamed without changes.
+2 -2
View File
@@ -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/)
+3
View File
@@ -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.**
+7 -5
View File
@@ -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 -1
View File
@@ -1,5 +1,5 @@
---
title: How do I get LBRY for development?
title: How do I install LBRY for development and contributing?
category: powerusers
---
+71
View File
@@ -0,0 +1,71 @@
---
title: How does LBRY handle privacy? What data does LBRY collect?
category: LBRY 101
order: 5
---
LBRY takes privacy seriously and carefully considers the data it collects.
Our official privacy policy is viewable at https://lbry.com/privacypolicy. This FAQ article attempts to explain our policy in plain English, but should not be considered an official policy document.
LBRY collects data for a variety of reasons, including but not limited to:
- debugging and improving the protocol
- understanding how our users interact with our applications
- preventing fraud in our reward programs
- providing statistics to content creators
We promise to keep any collected data safe and to never share personal, private information with anyone outside of LBRY Inc.
Users can also [choose to use LBRY anonymously](#anonymous) however some features, like [LBRY Rewards](https://lbry.com/faq/rewards), will not be available.
Additionally, even when not sending data to us, using LBRY typically involves participation in the peer-to-peer LBRY network and certain information like your IP address is likely to be exposed regardless. See [below](#p2p) for more information.
### What type of data is collected and where?
As a first time user of LBRY applications, you have the option of providing an email address to create a LBRY account. This allows for a richer user experience by enabling services such as [LBRY Rewards](https://lbry.com/faq/rewards), email notifications, and account synchronization (i.e. subscriptions and user preferences) across multiple devices/platforms. If you do not provide an email, any data collected cannot be associated with your identity, but may still be tied back to other system information like IP addresses.
See below tables for a break-down of the types of data collected and associated applications.
Scope of Data | Depends on| Optional | Visibility | Details
:------------ |:------------ |:------------ |:------------ |:------------ |
Email addresses | | Yes, if email provided | LBRY | Used to create and authenticate a LBRY account
User preferences | Email | Yes, if email provided | LBRY | Subscriptions, tags, blocked channels, and application settings
System information | | Yes, if Share Diagnostic Data enabled | LBRY | Operating system, application/SDK versions, and unique install identifier
Identity verification | Email | Yes, if going through manual approval | LBRY | Phone number, credit card fingerprint (Stripe), and 3rd party services identifiers (i.e. YouTube, GitHub)
Google Analytics | | Yes, if Share Diagnostic Data enabled | LBRY | User behavior and interactions within the applications are tracked anonymously. This is not linked to a LBRY account.
Content access analytics | Email | Yes, if email provided | LBRY | Content views used for Rewards and internal analytics
IP addresses | | No, use VPN to protect | Everyone | Any access to LBRY services are logged to prevent abuse and comply with legal requirements
Blockchain metadata | Email | Yes, if email provided | LBRY| Wallet addresses and transactions related to Rewards are logged to prevent abuse and comply with tax requirements (above $600 yearly threshold)
Blockchain transactions | | No, don’t create transactions | Everyone | Any actions taken that use LBRY credits and create a permanent transaction on the blockchain. Not linked to any Account/User data.
Scope of Data | LBRY Desktop App | LBRY.tv (Web) | LBRY Android App | LBRY SDK |
:------------ |:------------ |:------------ | :-------------| :-------------|
Email addresses | yes | yes | yes | no |
User preferences | yes | yes | yes | no |
System information | yes | no | yes | yes |
Identity verification | yes | yes | yes | no |
Google Analytics | opt-out | yes | yes | no |
Content access analytics | yes | yes | yes | yes |
IP addresses | yes | yes | yes | opt-out |
Blockchain metadata | yes | yes | yes | no |
Blockchain transactions | yes | yes | yes | yes |
### What’s the difference between account data and cryptocurrency wallets?
Each installable LBRY application also contains a cryptocurrency wallet which is stored locally on the respective device. The wallet allows you to store LBRY Credits and use them to [transact (spend, publish, purchase, and tip) on the network](https://lbry.com/faq/transaction-types). The private information, which is required to perform these actions, is under the sole control of the user.
LBRY does provide a wallet syncing and backup mechanism to allow seamless access across multiple devices. The backup service ensures that a wallet can be retrieved by the user through their LBRY account in case they lose access to their local copy. Any storage and exchange of wallet data has end to end encryption, and the user can also provide an additional encryption password if desired.
### How do I use LBRY anonymously?
To use LBRY in a fully anonymous way, we recommend the LBRY Desktop application. To disable tracking features, you’ll want to disable the `Share Diagnostic Data` option from the Settings page (cog in the top right of the app). Also, you’ll want to skip providing an email and use a Virtual Private Network (VPN) to protect your IP address. This will still allow you use blockchain related features like retrieving content data, publishing, purchasing, tipping, and other transactions. Depending on VPN features and network configuration, hosting data currently may not be possible but we are looking into techniques to allow this in the future.
### Where is the account and analytics data stored?
LBRY stores collected data on its own secured databases and ensures only authorized employees have access to this data. Google Analytics data is anonymized and protected by Google.
### What information is shared with others in the network? {#p2p}
Similarly to other peer to peer protocols like BitTorrent, users in the network share messages (i.e. announcing content availability) and create direct connections to exchange data (i.e. downloads / uploads). While LBRY does not collect this information, other participants of the network can observe and collect the information.
### Can I use a VPN to use and access LBRY?
Yes, a VPN can be used with all LBRY services. Major features will work without any problems, but VPN users may not be eligible for [LBRY Rewards](https://lbry.com/faq/rewards) in order to prevent abuse.
### Is any additional data collected if I participate in the YouTube Sync program?
When authenticating into the [YouTube Sync program](https://lbry.com/youtube), you provide proof of channel ownership that allows us to link your YouTube channel to a LBRY account. Information about your account is stored and kept by LBRY, Inc.
+2 -2
View File
@@ -3,7 +3,7 @@ title: What are LBRY Rewards?
category: getstarted
---
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 3 Reward redemptions per day**.
To provide a rich user experience and to [distribute](/faq/credit-policy) LBRY Credits (LBC) into the hands of new and returning users, LBRY created a Rewards system where credits are earned by completing tasks throughout the application. Rewards are given to promote application testing, learning certain in-app skills, building the LBRY economy through purchasing and publishing content, and as a small "thank you" gift for being part of a revolutionary digital media platform. For qualified users, Rewards are issued automatically by the LBRY app into each users' [LBRY wallet](/faq/how-to-backup-wallet). **Note: There is a limit of 5 Reward redemptions per day**.
![rewardslist](https://spee.ch/@clem:0/rewardslist.png)
@@ -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).
+2 -2
View File
@@ -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.
+8 -1
View File
@@ -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
---
+18 -18
View File
@@ -12,7 +12,7 @@ To read previous updates, please visit our [Development and Community Update arc
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 were created, 146 were closed. 18 pull requests were merged. 30 GitHub users outside of LBRY made code contributions, including:
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)
@@ -42,22 +42,22 @@ Thanks to everyone who took time out of their busy days to help LBRY out!
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 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)
- 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
- 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.
@@ -81,11 +81,11 @@ Another area that continues to get attention is internationalization. You may ha
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)
- 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)
- 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).
@@ -164,7 +164,7 @@ The SDK team was responsible for exposing the necessary tools to export and upda
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.
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.
![explorer](https://spee.ch/f/explorer-new.png)
+2
View File
@@ -143,6 +143,8 @@ class Controller
$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';
@@ -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
*/
+7 -2
View File
@@ -26,9 +26,14 @@ class i18nActions extends Actions
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.');
throw new Exception('Please set Config::TRANSIFEX_API_KEY in your configuration.');
}
return View::renderJson(Transifex::getTranslationResourceFile($project, $resource, $language));
$json = Transifex::getTranslationResourceFile($project, $resource, $language);
Response::setHeader(Response::HEADER_CROSS_ORIGIN, "*");
Response::setHeader(Response::HEADER_ETAG, md5($json));
return View::renderJson($json);
}
}
+1
View File
@@ -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
-5
View File
@@ -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);
+20 -16
View File
@@ -39,38 +39,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 (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: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 (Response::getMetaImages()): ?>
<?php $url = reset(Response::getMetaImages()) ?>
<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"/>