LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-08-31 01:11:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

more edits

Browse source
This commit is contained in:
Thomas Zarebczan 2018-12-18 18:59:23 -05:00 • committed by GitHub
parent 223986092d
commit 5593c3165d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/news/195-nov-dec-update.md
View file

@ -84,14 +84,14 @@ If you have a Ledger hardware wallet, you can now store your LBC on it! This doe
![hw](https://spee.ch/@lbry:3f/ledger.jpg)
### LBRY Streaming {#stream}
One negative aspect of LBRY we hear about often is the need to download content in order to view it. We’re taking the initial steps to improve this experience by creating a new API that allows for streaming of blob data directly to a web server, where our apps can listen and render videos from. You can check out the [initial spec on GitHub](https://github.com/lbryio/lbry/issues/1634) for details. The first iteration will still require the file to be downloaded locally, but will allow the App team to integrate a new video player that’s capable of reading data at certain chunks of the file. After this is fully tested and working, we’ll be moving to a streaming only solution for files types that support it (mainly video/audio and images). Other files will still need to be downloaded locally, but we’ll also be including disk management settings to help users allocate how much data they want LBRY to store.
One negative aspect of LBRY we hear about is the need to download content in order to view it. We’re taking the initial steps to improve this experience by creating a new API that allows for streaming of blob data directly to a web server, where our apps can listen and render content from. You can check out the [initial spec on GitHub](https://github.com/lbryio/lbry/issues/1634) for details. The first iteration will still require the file to be downloaded locally, but will allow the App team to integrate a new video player that’s capable of reading data at certain chunks of the file. After this is fully tested and working, we’ll be moving to a streaming only solution for files types that support it (mainly video/audio and images). Other files will still need to be downloaded locally, but we’ll also be including disk management settings to help users allocate how much data they want LBRY to store.
### SDK Progress {#sdk}
The SDK team is thrilled to have its months long of development and testing come into fruition with the 0.30.1 release shipped with the LBRY Desktop and Android apps! This was a complex release because it includes a brand new wallet, written from scratch in accordance with industry standards, an upgrade to Python 3.7.1, and a custom UPNP module to replace MiniUPNP (which was a pain to build on Windows). The new wallet includes a migration to process existing wallets, including making a backup first! It inspects the old wallet for all receiving and change addresses, populates them in a new database/syncing transaction data, and migrates the format to a simpler file that doesn’t include all transaction data bloating older wallets.
The SDK team is thrilled to have its months long of development and testing come into fruition with the 0.30.1 SDK release that shipped with the LBRY Desktop and Android apps! This was a complex release because it includes a brand new wallet, written from scratch in accordance with industry best practices, an upgrade to Python 3.7.1, and a custom UPNP module to replace MiniUPNP (which was a pain to build on Windows) to help users host data. The new wallet includes a migration to process existing wallets, including making a backup first! It inspects the old wallet for all receiving and change addresses, populates them in a new database/syncing transaction data, and migrates the format to a simpler file that doesn’t include all transaction data that would bloat the previous wallet format.
The wallet is much smarter, more efficient, and better at reconnecting during server or internet problems. It will look ahead when new addresses are created, subscribing to those transactions, enabling cross device syncing. This is a feature we plan to roll out slowly over the next few months. If you have multiple LBRY installations today, you can try this out by copying the default_wallet file from one device to the other. As transactions occur on one device, they’ll be synced automatically on the other (and vice versa). This still does not include the ability to sync channels. We’re still looking for the best way to proceed with this in the future. Currently channels are created with a key outside of the seed, and thus can’t be re-created automatically on the other wallet.
The next steps for the SDK team is to refactor more of the code using asyncio, which will offer even better performance throughout various SDK functions and lessen race condition possibilities. Users will mainly see improved publishing speeds for larger files and download speeds (both when looking up peers on the DHT network and when combining blob files into their output files).
The next steps for the team is to refactor more of the code using asyncio, which will offer even better performance throughout various SDK functions and lessen race condition possibilities. Users will mainly see improved publishing speeds for larger files and download speeds (both when looking up peers on the DHT network and when combining blob files into their output files).
![sync](https://spee.ch/@lbry:3f/syncing.jpg)
@ -102,13 +102,13 @@ The blockchain team released a couple of updates to the full blockchain client,
We are in the process of planning what’s in store for the LBRY ecosystem for 2019, so stay tuned on our Discord/Social media pages for updates. Some areas we plan to tackle include cross device syncing (wallets, subscriptions, purchases, history), LBC<>USD on/off ramps, community metadata overlays (tags, categories, etc), comments, creator features, internationalization, and using the power of community swarms to increase LBRY adoption.
# 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). We also recently launched our [LBRY Discourse Forum](https://discourse.lbry.io) where developers can interact with the team and ask questions across all our different projects.
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? A great place to start is [lbry,tech](https://lbry.tech) to learn more about what makes LBRY work under the hood. 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). We also recently launched our [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.io) anytime and say hello! For a short time, Santa Yerbil will be visiting our Discord to give lots of presents!
![santa](https://spee.ch/@lbrynews:0/santa-yrbl.jpg)
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), [Instagram](https://www.instagram.com/lbryio), and [Telegram](https//t.m/lbryofficial).
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), [Instagram](https://www.instagram.com/lbryio), and [Telegram](https//t.me/lbryofficial).
[Back to **top**](#dev-updates)