LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-09-03 02:35:11 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

edits

Browse source
This commit is contained in:
Thomas Zarebczan 2019-09-10 12:24:33 -04:00 • committed by GitHub
parent 63726f19d3
commit e6255f8b2a
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/219-aug-dev.md
View file

@ -45,7 +45,7 @@ The new video player fixes multiple bugs from previous versions: most important
![download](https://spee.ch/9/download-settings.png)
#### Desktop Next Steps
The app team also began development of our 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 [#sync] for more information - we will be syncing app data/preferences before moving onto the wallet portion. Continuing work on the video player, we’ll be adding features to save position and volume settings throughout the app.
The app team also began development of our 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(we will be syncing app data/preferences before moving onto the wallet portion). Continuing work on the video player, we’ll be adding features to save position and volume settings throughout the app.
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, i.e. ones over 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.
@ -54,17 +54,17 @@ Another area to continue getting additional attention is internationalization. Y
### 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, and a key value store which will be the final location of synced LBRY data. On startup, we also ping all the wallet servers and select the best main one to connect to based on the peer’s location. We also 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). The ability to connect/sync with multiple servers proved to be more troublesome than expected because we experienced and then fixed sync and reconnection issues which should be resolved with the [0.40.1 patch](https://github.com/lbryio/lbry-sdk/releases/tag/v0.40.1).
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, and a key value store which will be the final location of synced LBRY data. On startup, we also ping all the wallet servers and select the best main one to connect to based on the peer’s location. We also 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). 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).
![settings and wallet sync](https://spee.ch/8/sdk-settings.png)
#### SDK Next Steps
During testing of the [YouTube transfer](#youtube) process, we ran into a snag with our how 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).
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 began initial implementation of a technique called holepunching, which will improve connectivity between nodes -- especially for those behind firewalls and atypical 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 LBRY blockchain continues their work towards being able to enable SegWit later this year, optimizing memory usage, revamping RPC calls to include bid (allow us to show pending effective amounts during takeovers) and sequence (which was removed in a previous update), and enabling metadata along with claims 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 fine on our API currently, and enable a Patreon like system where creators can release content that’s accessible only by their supports / at various support/tip levels.
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 (allow us to show pending effective amounts during takeovers) and sequence (which was removed in a previous update), and enabling metadata along with claims 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 fine on our API currently, and enable a Patreon like system where creators can release content that’s accessible only by their supports / 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. 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. Everything is back to normal currently on the latest release/chain, and we’ll continue to monitor. If you are still running a pre 0.17.2 node, please delete local
@ -113,7 +113,7 @@ We’ve got some exciting rewards updates in progress and coming out very soon!
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 Update {#cross}
### Cross Device Syncing Update {#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 accounts 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, discard 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).