mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-08-31 09:21:26 +00:00
Graydon
Thomas Zarebczan
parent
d7e702ae22
commit
9bd3c7eea6
4 changed files with 33 additions and 33 deletions
|
|
@ -5,7 +5,7 @@ date: '2018-04-03 18:00:00'
|
|||
cover: 'droid1.jpg'
|
||||
---
|
||||
|
||||
Back in December, we published the [first ever LBRY Development and Community update](https://lbry.io/news/lbry-development-community-update-1) and followed up with another for [January 2018](https://lbry.io/news/lbry-development-community-update-jan-2018) and [February 2018](https://lbry.io/news/lbry-development-community-update-feb-2018) - be sure to check them all out if you missed it! We will continue these updates at the beginning of each month to keep each and every LBRYian up to date on our quest to revolutionize content discovery, sharing and monetization!
|
||||
Back in December, we published the [first ever LBRY Development and Community update](https://lbry.io/news/lbry-development-community-update-1) and followed up with another for [January 2018](https://lbry.io/news/lbry-development-community-update-jan-2018) and [February 2018](https://lbry.io/news/lbry-development-community-update-feb-2018) - be sure to check them all out if you missed it! We will continue posting these updates at the beginning of each month to keep each and every LBRYian up to date on our quest to revolutionize content discovery, sharing and monetization!
|
||||
|
||||
If you haven’t already, please take a moment to read our [Looking Back and Moving Forward: LBRY in 2017/2018](https://lbry.io/news/lbry-in-2017-2018) blog post and check out our [roadmap](https://lbry.io/roadmap).
|
||||
|
||||
|
|
@ -14,12 +14,12 @@ To skip the tech stuff and see what’s happened and what’s next in the LBRY c
|
|||
[Skip to **Community Happenings**](#com-updates)
|
||||
|
||||
# Development Updates {#dev-updates}
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://lbry.tech, which is not live yet, but you can check out our progress on [GitHub](https://github.com/lbryio/lbry.tech).
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. Our plan is to create a technical reference site which will be developer focused at https://LBRY.tech, which is not live yet, but you can check out our progress on [GitHub](https://github.com/lbryio/lbry.tech).
|
||||
|
||||
### App and Protocol Summary
|
||||
We know it's been a long wait, but we're very happy with our latest app release. And the wait will be worth it when you experience the improved LBRY daemon - it's the first major protocol update since last November, and it's a big step in the right direction. You can read about specific enhancements in the changelogs ([0.19.0](https://github.com/lbryio/lbry/releases/tag/v0.19.0) and [0.19.1](https://github.com/lbryio/lbry/releases/tag/v0.19.1)) but in general we’ve noticed improvements in network availability and streaming speed (time from when play is clicked to when the download starts).
|
||||
|
||||
On top of that, it brought some much needed bug fixes, wallet encryption capabilities, ability to redownload content on updated claims and updating claims with large LBC deposits (now it uses the current bid, previously you had to have the balance in your wallet to cover it). The next steps for the protocol are to significantly improve network data announcement times, speed up startup times and rewrite of client/server side wallet functionality.
|
||||
On top of that, it brought some much needed bug fixes, wallet encryption capabilities, ability to redownload content on updated claims and updating claims with large LBC deposits (now it uses the current bid, previously you had to have the balance in your wallet to cover it). The next steps for the protocol are to significantly improve network data announcement times, speed up startup times and rewrite client/server side wallet functionality.
|
||||
|
||||
|
||||
On the app side, the main feature was subscription enhancements which enabled in-app notifications (including alerts for new content on channels that users are subscribed to) and auto download for channels that users subscribe to. The update also improves search results (see section below for details), allows YouTubers to earn [Sync Rewards](https://lbry.io/youtube), saves the app state when closing to tray, and lets users export transactions to CSV. Bug fixes included correct sorting of published content, allowing lbry:// links to be opened when the app was closed on OSX and fixing them on Linux, fixing night mode start time and bringing Windows notifications back into a working state.
|
||||
|
|
@ -47,7 +47,7 @@ The LBRY app redesign has been merged into the master branch and is available to
|
|||
|
||||
|
||||
### Subscription Next Steps
|
||||
Channel subscriptions give users a reason to return to the LBRY app on a daily or weekly basis, so we will continue to focus development effort in this area. The next steps include global and per subscribed content auto download settings, notification badges, saving subscription data to LBRY’s API server for syncing across installations/devices and providing emails when new content is available. We also plan to experiment with several different rewards structure to incentivize use of subscription features.
|
||||
Channel subscriptions give users a reason to return to the LBRY app on a daily or weekly basis, so we will continue to focus development effort in this area. The next steps include global and per subscription content auto download settings, notification badges, saving subscription data to LBRY’s API server for syncing across installations/devices and providing emails when new content is available. We also plan to experiment with several different rewards structure to incentivize use of subscription features.
|
||||
|
||||
### Cool App Features in the Pipeline {#features-update}
|
||||
Check out the below pull requests to get a sense of a few exciting features coming to the LBRY app.
|
||||
|
|
@ -64,9 +64,9 @@ Over the past few weeks, we’ve been converting the code base of spee.ch so tha
|
|||
In terms of spee.ch site performance, the publishing function has been running without a hitch over the last 2 weeks after the team implemented a few patches to deal with wallet issues. Currently, publishes take about 15-20 seconds but we are hoping to get that number close to 5 seconds with additional refactoring and enhancements to the publishing process.
|
||||
|
||||
### Protocol - Wallet Server and Client Development Efforts
|
||||
We’ve found that elements of the LBRY wallet (LBRYum) and LBRY wallet server (LBRYum-server) are causing bottlenecks with claim resolution and publishing - two functions that are widely used throughout the LBRY app experience. Claim resolution occurs between the client and server to make sure that claim data is read correctly from the blockchain. Publishing is the process by which a claim id is generated and broadcast to the network - something the spee.ch server has been struggling with since there is lots of publishing activity.
|
||||
We’ve found that elements of the LBRY wallet (LBRYum) and LBRY wallet server (LBRYum-server) are causing bottlenecks with claim resolution and publishing - two functions that are widely used throughout the LBRY app experience. Claim resolution occurs between the client and server to make sure that claim data is read correctly from the blockchain. Publishing is the process by which a claim ID is generated and broadcast to the network - something the spee.ch server has been struggling with since there is lots of publishing activity.
|
||||
|
||||
In order to fix the client issue, the lbryum framework is being re-written into the LBRY daemon with performance and stability in mind. On the server side, we are migrating away from the Electrum code base and into [ElectrumX](https://github.com/kyuupichan/electrumx) which will bring numerous performance and stability enhancements. There is significant development and testing to be done in both areas and we believe this will result in a much better App and protocol experience.
|
||||
In order to fix the client issue, the LBRYum framework is being re-written into the LBRY daemon with performance and stability in mind. On the server side, we are migrating away from the Electrum code base and into [ElectrumX](https://github.com/kyuupichan/electrumx) which will bring numerous performance and stability enhancements. There is significant development and testing to be done in both areas and we believe this will result in a much better App and protocol experience.
|
||||
|
||||
### Blockchain - Preparing for a Hardfork
|
||||
There are two major changes/fixes to the LBRY blockchain in the pipeline that will require a hard fork of the network. Neither of these changes are controversial - both will improve the functionality of the blockchain. Our goal is to announce these at the end of April and allow for another month or two before the hardfork code will activate so that exchanges, miners and other services have time to update.
|
||||
|
|
@ -83,7 +83,7 @@ The Q1 coming to a close, we wanted to provide an update on our [roadmap objecti
|
|||
The [YouTube Sync partner program is live and getting feedback from testers, see additional information below](#youtube-updates).
|
||||
The Meetup program has also been launched on our [Meet](https://lbry.io/meet) and [College](https://lbry.io/college) landing pages, see [below for more information](#meetup-update).
|
||||
|
||||
Significant progress has been made on the white paper and a first draft is very close to being shared publicly. It will be released as a navigational document, in an in-progress state, on our new lbry.tech (not live yet) developer resource site and we’ll be asking the community for their feedback.
|
||||
Significant progress has been made on the white paper and a first draft is very close to being shared publicly. It will be released as a navigational document, in an in-progress state, on our new LBRY.tech (not live yet) developer resource site and we’ll be asking the community for their feedback.
|
||||
|
||||
Wallet encryption has been implemented on the daemon but is not yet available in the LBRY app. If you want to use this feature ASAP, check out the [CLI](https://lbryio.github.io/lbry/cli/#wallet_encrypt) documentation - the wallet will need to be [unlocked](https://lbryio.github.io/lbry/cli/#wallet_unlock) manually before app startup. Feel free to reach out on Discord with any questions!
|
||||
|
||||
|
|
@ -91,27 +91,27 @@ The UI redesign was recently merged on our lbry-app repo and we should have a re
|
|||
|
||||
And last but not least, the Search algorithm has undergone a number of optimizations (see [search update above](#search-updates)) which have added up to much better search results - give it a shot and let us know what you think! There's still a lot more work to do here when categories and tags come online, and we need your feedback!
|
||||
|
||||
A quick check-in on Q2 items shows that we are ahead of schedule with Android alpha being launched and progress being made on lbry.tech . Also, the ability to share free content on HTML websites via the new spee.ch sharing feature is mentioned in the [features update above](#features-update).
|
||||
A quick check-in on Q2 items shows that we are ahead of schedule with Android alpha being launched and progress being made on LBRY.tech . Also, the ability to share free content on HTML websites via the new spee.ch sharing feature is mentioned in the [features update above](#features-update).
|
||||
|
||||
### LBRY Merchandise Store
|
||||
Come visit our newly upgraded merchandise store! Following the launch in February, we’ve moved our swag shop to a new, easy to remember URL: [https://shop.lbry.io](https://shop.lbry.io). New t-shirt designs and products are frequently added, so please be sure to stop by! We’re very excited to offer some fresh items designed by our new marketing intern James Biller - if you like what you see, give him a shout out on [Twitter](https://twitter.com/BillerJames)!
|
||||
Come visit our newly upgraded merchandise store! Following the launch in February, we’ve moved our swag shop to a new, easy to remember URL: [https://shop.LBRY.io](https://shop.lbry.io). New t-shirt designs and products are frequently added, so please be sure to stop by! We’re very excited to offer some fresh items designed by our new marketing intern James Biller - if you like what you see, give him a shout out on [Twitter](https://twitter.com/BillerJames)!
|
||||
|
||||
Help us grow our community and get the word out about LBRY: We will tip LBC if you tag us (@LBRYio) on Twitter or Facebook with a picture of you rocking LBRY swag. Please upload to spee.ch and share the post on Discord or Reddit to claim your reward. Thanks for your support in spreading LBRY love!
|
||||
Help us grow our community and get the word out about LBRY: We will tip LBC if you tag us (@LBRYio) on Twitter or Facebook with a picture of you rocking LBRY swag. Please upload it to spee.ch and share the post on Discord or Reddit to claim your reward. Thanks for your support in spreading LBRY love!
|
||||
|
||||
### Youtube Sync Update {#youtube-updates}
|
||||
### YouTube Sync Update {#youtube-updates}
|
||||
We've re-launched our [Youtube Sync](https://lbry.io/youtube) campaign under a new design, process and Rewards system that allows YouTubers, who meet our subscriber requirements, to sync their content to LBRY within a few clicks. Once the creator is queued, they can claim their sync Reward in the LBRY app by signing in with the same email as their sync status page. The program launched as a pilot with our internal Discord community/targeted YouTubers and will continue expanding to a full fledged outreach on Social media and other direct targeting. The LBC rewards mentioned below are a first trial run and may increase depending on feedback.
|
||||
|
||||
The most common issue creators run into, especially those who have used the LBRY app prior to going through the sync process, is that their YouTube channel email is mismatched with the LBRY app email. This will require a manual fix my emailing [our Helpdesk](mailto:help@lbry.io) at the moment, but we hope to straighten this out automatically in the coming weeks. Having trouble or want to find out more? First make sure to check out our [FAQ page](https://lbry.io/faq/youtube) or you can email [Reilly](mailto:reilly@lbry.io) with any specific sync questions that aren’t covered.
|
||||
The most common issue creators run into, especially those who have used the LBRY app prior to going through the sync process, is that their YouTube channel email is mismatched with the LBRY app email. This will require a manual fix by emailing [our Helpdesk](mailto:help@lbry.io) at the moment, but we hope to straighten this out automatically in the coming weeks. Having trouble or want to find out more? First make sure to check out our [FAQ page](https://lbry.io/faq/youtube) or you can email [Reilly](mailto:reilly@lbry.io) with any specific sync questions that aren’t covered.
|
||||
|
||||
|
||||
|
||||
|
||||
### Twitter LBC Tip Bot
|
||||
The Twitter TipBot bounty was solved internally by the team after open source code was discovered that provided 90% of the functionality we were looking for. With a few modifications, we set up a test server and were able to send tips! The TipBot is now being migrated to an official LBRY server which will allow it to be used all across Twitter world to tip LBC - users, creators, fans, and even projects with similar missions! Stay tuned on our Discord server and [@LBC_TipBot](https://twitter.com/@LBC_TipBot) for updates.
|
||||
|
||||
|
||||
|
||||
|
||||
### LBRY.tech Update
|
||||
Initial legwork has begun on our developer/tech resource, lbry.tech. We don’t currently have an ETA on the launch, but it will be released as an early alpha version that includes an alpha draft of the LBRY white paper, all of which will be polished over time as we get feedback from the community. We weren’t joking about “release early, release often”! You can follow our progress on the [lbry.tech GitHub repository](https://github.com/lbryio/lbry.tech).
|
||||
Initial legwork has begun on our developer/tech resource, LBRY.tech. We don’t currently have an ETA on the launch, but it will be released as an early alpha version that includes an alpha draft of the LBRY white paper, all of which will be polished over time as we get feedback from the community. We weren’t joking about “release early, release often”! You can follow our progress on the [LBRY.tech GitHub repository](https://github.com/lbryio/lbry.tech).
|
||||
|
||||
### Discord Role Self Assignment and New Member Flow
|
||||
In order to improve the experience for new and existing members of our Discord community, we will be implementing a better system that will allow users to self assign roles based on their activity, purpose and interests. It will also allow more granular controls over which roles have access to particular channels/areas, which will also hopefully improve the overall user experience.
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ To skip the tech stuff, see what’s happened and what’s next in the LBRY comm
|
|||
[Skip to **Community Happenings**](#com-updates)
|
||||
|
||||
# Development Updates {#dev-updates}
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next month, we’ll be releasing a technical reference site which will be developer focused at [https://lbry.tech](#lbry-tech).
|
||||
All of our code is open source and available on [GitHub](https://github.com/lbryio). Are you a dev and want to find out more? Check out our [general contributing guide](https://lbry.io/faq/contributing) and our LBRY App specific contributing [document](https://github.com/lbryio/lbry-app/blob/master/CONTRIBUTING.md). Please be patient with us while we improve our technical documentation. In the next month, we’ll be releasing a technical reference site which will be developer focused at [https://LBRY.tech](#lbry-tech).
|
||||
|
||||
### App and Protocol Summary
|
||||
Due to travel time for and participation at [LBRY’s All Hands](#all-hands) gathering, development activities were on the lighter side this past month. The app team released version [0.21.3](https://github.com/lbryio/lbry-app/releases/tag/v0.21.3) which included a small patch to block content deemed infringing according to DMCA laws (see next section for more information). Otherwise, the main focus on the app side has been on testing and bug squashing on the [redesign](#redesign-updates). Part of this effort was spent on separating out the [lbry-redux](https://github.com/lbryio/lbry-redux) code into its own repository so that the the mobile and desktop apps can re-use redux states and functionality. We ran into a few quirks during this process but we were able to get things running smoothly!
|
||||
|
|
@ -28,14 +28,14 @@ Our [Content](https://lbry.io/faq/content) and [DMCA](https://lbry.io/faq/dmca)
|
|||
|
||||
|
||||
### LBRY for Android Update
|
||||
We're getting closer to a feature-complete mobile app with search functionality recently added to the current alpha and wallet features in the pipeline. Once full wallet functionality will be released with the next alpha, we will be transitioning to the Open Beta phase via Google Play Store. Open beta will allow us to release the Android app to a wider audience and get better feedback from testers. Rewards will be added in open beta and we may actually add some mobile-only rewards!
|
||||
We're getting closer to a feature-complete mobile app with search functionality recently added to the current alpha and wallet features in the pipeline. Once full wallet functionality is released with the next alpha, we will be transitioning to the Open Beta phase via Google Play Store. Open beta will allow us to release the Android app to a wider audience and get better feedback from testers. Rewards will be added in open beta and we may actually add some mobile-only rewards!
|
||||
|
||||
Want to participate in LBRY for Android alpha testing? [Sign up here](https://lbry.io/android-alpha) and you’ll be added to the waitlist! Not interested in alpha yet but want to know when we are ready for the next phase, join our regular [Android mailing list](https://lbry.io/android) instead. You can see the current status of testing and issues on our [Android GitHub repository](https://github.com/lbryio/lbry-android/issues).
|
||||
|
||||
|
||||
|
||||
### spee.ch Update
|
||||
The majority of our effort on the spee.ch codebase has been to convert the [spee.ch repository](https://github.com/lbryio/spee.ch) to hold the main server code, and create [www.spee.ch repository](https://github.com/lbryio/www.spee.ch) which will be the main entry point for spee.ch implementations that can be cloned to [create your own version of spee.ch](https://lbry.io/speech-admin). We are planning to hold a kick off event which will explain and walk through how you can setup and build your own clone. Are you interested in this feature? Learn more by checking out the [spee.ch community section](#speech-host).
|
||||
The majority of our effort on the spee.ch codebase has been to convert the [spee.ch repository](https://github.com/lbryio/spee.ch) to hold the main server code, and create the [www.spee.ch repository](https://github.com/lbryio/www.spee.ch) which will be the main entry point for spee.ch implementations that can be cloned to [create your own version of spee.ch](https://lbry.io/speech-admin). We are planning to hold a kick off event which will explain and walk through how you can setup and build your own clone. Are you interested in this feature? Learn more by checking out the [spee.ch community section](#speech-host).
|
||||
|
||||
### App Redesign {#redesign-updates}
|
||||
Since our last update, we’ve squashed a number of critical bugs and the LBRY app redesign has moved into a release candidate phase where we’ve invited testers from our Discord community to perform more rigorous testing and gather additional feedback. Want to help out? Join us on [Discord](https://chat.lbry.io) and ask about becoming an early tester. In addition to previewing the redesign before its officially released, you can earn LBRY Credits by finding bugs or providing suggestions.
|
||||
|
|
@ -47,19 +47,19 @@ We’ve identified a number of issues which are marked with the [redesign label]
|
|||
### Subscription Page Improvements
|
||||
Currently, the subscriptions page is organized similar to the explore page where each channel has its own single row of 10 latest items. It becomes difficult to monitor your subscriptions for updated content in this fashion, so we will be changing the the page to look and behave similar to the Downloads/Published pages where channels are no longer grouped together, but instead, the latest content updates will be displayed at the top of the page. We will still show the 10 latest items per subscribed channel but they will be sorted by publish date across all subscriptions.
|
||||
|
||||
We’re also working on syncing subscription data to the LBRY api server so that subscriptions are no longer lost if the LBRY cache is cleared or if you move to a new device (and we can sync to mobile too!). This will also allow us to recommend similar content / channels in the future.
|
||||
We’re also working on syncing subscription data to the LBRY API server so that subscriptions are no longer lost if the LBRY cache is cleared or if you move to a new device (and we can sync to mobile too!). This will also allow us to recommend similar content / channels in the future.
|
||||
|
||||
|
||||
|
||||
### Upcoming Feature: Hyperlinks to LBRY In-App Areas
|
||||
One of our new team members had a fantastic suggestion that would re-engage our users by providing hyperlinks to various areas in the LBRY app. Currently, we use the hyperlink functionality to provide users direct links to LBRY content and channel URLs (they open the app if you have it installed too!) via https://open.lbry.io but this new feature will allow us to hyperlink to areas such as Rewards, Publish, Wallet and Settings. On use case would be to send out an email encouraging publishing and provide the users a clickable URL that opens the app and brings them to the Publish feature.
|
||||
One of our new team members had a fantastic suggestion that would re-engage our users by providing hyperlinks to various areas in the LBRY app. Currently, we use the hyperlink functionality to provide users direct links to LBRY content and channel URLs (they open the app if you have it installed too!) via https://open.lbry.io but this new feature will allow us to hyperlink to areas such as Rewards, Publish, Wallet and Settings. One use case would be to send out an email encouraging publishing and provide the users a clickable URL that opens the app and brings them to the Publish feature.
|
||||
|
||||
### Protocol - Wallet Server and Client Development Updates {#wallet}
|
||||
Large chunks of progress have been made on both the [wallet server](https://github.com/lbryio/lbryum-server/issues/54) and [client](https://github.com/lbryio/lbry/issues/1155) redesign/reimplementation. Once the server side is implemented, we should see significant performance gains that will translate directly to an improved app experience as claim information will load much faster, especially for new users on a first run.
|
||||
|
||||
During the process of developing the Electrumx server to support LBRY claims, we were able to identify several improvements required on the full blockchain or LBRYcrd codebase. Initial testing is underway as e currently have a test server running these changes along with the enhanced Electrumx code that accepts wallet connections from the current LBRY wallet (and it will also support the new client when it’s ready).
|
||||
During the process of developing the ElectrumX server to support LBRY claims, we were able to identify several improvements required on the full blockchain or LBRYcrd codebase. Initial testing is underway as we currently have a test server running these changes along with the enhanced ElectrumX code that accepts wallet connections from the current LBRY wallet (and it will also support the new client when it’s ready).
|
||||
|
||||
The client side, which is a Twisted based implementation of the wallet, is still in development but is able to create and receive basic transactions. The next phase is to support claim related transactions. The wallet was architected in such as way (see below) that it will be able to support multiple LBC wallets and even Bitcoin wallets if and when we’d decide to support bitcoin payments in the app.
|
||||
The client side, which is a Twisted based implementation of the wallet, is still in development but is able to create and receive basic transactions. The next phase is to support claim related transactions. The wallet was architected in such a way (see below) that it will be able to support multiple LBC wallets and even Bitcoin wallets if and when we’d decide to support bitcoin payments in the app.
|
||||
|
||||
|
||||
|
||||
|
|
@ -110,24 +110,24 @@ Due to funding needs being met, no credits were moved from cold storage during t
|
|||
### LBRY Merchandise Store
|
||||
We’ve added some brand new designs to our [swag store!](https://shop.lbry.io). New t-shirt designs and products are frequently added, so please be sure to stop by! We’re very excited to offer some fresh items designed by our new marketing intern James Biller - if you like what you see, give him a shout out on [Twitter](https://twitter.com/BillerJames)!
|
||||
|
||||
Earn LBC! Help us grow our community and get the word out about LBRY: We will tip LBC if you tag us (@LBRYio) on Twitter or Facebook with a picture of you rocking LBRY swag. Please upload to spee.ch and share the post on Discord or Reddit to claim your reward. Thanks for your support in spreading LBRY love!
|
||||
Earn LBC! Help us grow our community and get the word out about LBRY: We will tip LBC if you tag us (@LBRYio) on Twitter or Facebook with a picture of you rocking LBRY swag. Please upload it to spee.ch and share the post on Discord or Reddit to claim your reward. Thanks for your support in spreading LBRY love!
|
||||
|
||||
|
||||
|
||||
### Youtube Sync Updates {#youtube-updates}
|
||||
### YouTube Sync Updates {#youtube-updates}
|
||||
Since the launch of our revamped YouTube Sync program in March, we are coming close to 10,000 total syncs and YouTubers have claimed a total of 40,000 LBRY Credits.
|
||||
|
||||
We are also refining our YouTube Sync process so that we can automate the syncing of new channels as well as updates to existing channels. This will allow for much more content to be uploaded to LBRY by running our sync process continuously and shorten the time between agreement to sync and having YouTubers’ content available on LBRY.
|
||||
|
||||
|
||||
|
||||
|
||||
### Twitter LBC Tip Bot
|
||||
The [LBRY Tipbot for Twitter](https://twitter.com/@LBC_TipBot) was tested internally by the team along with the help of community members, and is now ready for mainstream action! You can read our [Tipbot FAQ] for more information on how to use the tipbot. Hint: use the `lbryian` keyword and make sure to keep your entire command on a single line.
|
||||
The [LBRY Tipbot for Twitter](https://twitter.com/@LBC_TipBot) was tested internally by the team along with the help of community members, and is now ready for mainstream action! You can read our [Tipbot FAQ](https://lbry.io/faq/tipbot-twitter) for more information on how to use the tipbot. Hint: use the `lbryian` keyword and make sure to keep your entire command on a single line.
|
||||
|
||||
|
||||
|
||||
### LBRY.tech Update {#lbry-tech}
|
||||
We’ve recently hired additional help to shape our lbry.tech technical resource and its design and development is progressing quickly. Developers will be able to interact with a live LBRY daemon directly from the website and access various technical content like documentation on how to contribute, how to develop and other technical resources. Follow along the development on our github repository and check out an early preview below (disregard the poor design, it’s getting a facelift!). Our goal is to launch an early version of this site by the end of May, which will include the long awaited LBRY whitepaper in draft form.
|
||||
We’ve recently hired additional help to shape our LBRY.tech technical resource and its design and development is progressing quickly. Developers will be able to interact with a live LBRY daemon directly from the website and access various technical content like documentation on how to contribute, how to develop and other technical resources. Follow along the development on our GitHub repository and check out an early preview below (disregard the poor design, it’s getting a facelift!). Our goal is to launch an early version of this site by the end of May, which will include the long awaited LBRY whitepaper in draft form.
|
||||
|
||||
|
||||
|
||||
|
|
@ -143,7 +143,7 @@ When you join our Discord, you will first see the #welcome-to-lbry channel and h
|
|||
|
||||
Natalie Mitchell was delighted to attend Boston College’s second *Hack the Heights* hackathon event on behalf of LBRY. Students from all Boston area Colleges came together to rapidly “hack” together creative projects and compete for prizes.
|
||||
|
||||
LBRY is proud to be working with local colleges to encourage students to become in blockchain projects: through computer programming, business of blockchain, and creative design. Babson College is using LBRY as a case study in their Blockchain and Cryptocurrency class, and LBRY actively provides internships for local college students.
|
||||
LBRY is proud to be working with local colleges to encourage students to become involved in blockchain projects: through computer programming, business of blockchain, and creative design. Babson College is using LBRY as a case study in their Blockchain and Cryptocurrency class, and LBRY actively provides internships for local college students.
|
||||
|
||||
On the Meetup side of things, we’ve been hard at work creating a community hub for meetup resources, to be rolled out in May. The new hub will include slideshows and other resources to present to your group, a forum to talk to other Ambassadors and ask questions, and interact with LBRY staff.
|
||||
|
||||
|
|
@ -164,7 +164,7 @@ We are also looking for communities, subreddits and websites that could make use
|
|||
|
||||
|
||||
### 3D Printing Community on LBRY
|
||||
We are in the process of creating a landing page on Lbry.io specifically to attract users and creators of 3D printing models. We believe that LBRY is a perfect fit for creators as our platform will allow them to charge for their models or receive micropayments in terms of tips (Thingiverse allows payments, but there are large minimums). You can check out the
|
||||
We are in the process of creating a landing page on LBRY.io specifically to attract users and creators of 3D printing models. We believe that LBRY is a perfect fit for creators as our platform will allow them to charge for their models or receive micropayments in terms of tips (Thingiverse allows payments, but there are large minimums).
|
||||
|
||||
|
||||
[Back to **Development Updates**](#dev-updates)
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ If you’re just hearing about LBRY for the first time, it is an open-source, bl
|
|||
## Who we are
|
||||
<div class="column-fluid">
|
||||
<div class="span3"><img src="https://spee.ch/1/Sean2.jpeg" style="padding: 0 12px 24px 0" alt="Sean Yesmunt"></div><div class="span9"><p>I'm <a href="http://seanyesmunt.com"> Sean,</a> I joined LBRY in November to work on the LBRY desktop app after making a few small contributions on my own. Before that I was working with React and Node on Walmart.com for 1.5 years after teaching myself to code. I am very interested in user experience, and creating simple apps that are easy to use.</p></div>
|
||||
<div class="span3"><img align="left" style="padding: 0 12px 24px 0" src="https://spee.ch/c/Bill2.jpeg" alt="Bill Bittner"></div><div class="span9"><p>I’m <a href="https://github.com/billbitt"> Bill.</a> I found out about LBRY while exploring blockchain applications and was quickly hooked by the vibrant dev community that had already sprung up around their alpha build. I love building web apps and exploring new technologies, so it wasn’t long before I jumped in and starting to building on top of the LBRY network.</p></div>
|
||||
<div class="span3"><img align="left" style="padding: 0 12px 24px 0" src="https://spee.ch/c/Bill2.jpeg" alt="Bill Bittner"></div><div class="span9"><p>I’m <a href="https://github.com/billbitt"> Bill.</a> I found out about LBRY while exploring blockchain applications and was quickly hooked by the vibrant dev community that had already sprung up around their alpha build. I love building web apps and exploring new technologies, so it wasn’t long before I jumped in and started to build on top of the LBRY network.</p></div>
|
||||
<div class="span3"><img align="left" style="padding: 0 12px 24px 0" src="https://spee.ch/7/Akin2.jpeg" alt="Akinwale Ariwodola"></div><div class="span9"><p>I’m <a href="https://github.com/akinwale"> Akinwale.</a> I discovered LBRY when my interest in cryptocurrencies got rekindled in early 2017 and I was looking for a coin to mine. I found the project really exciting which led to my decision to start contributing to the desktop app. One thing led to another, and I eventually started working on getting the Android version up and running.</p></div>
|
||||
</div>
|
||||
## What we're looking for
|
||||
|
|
@ -27,7 +27,7 @@ If you’re wondering what we’re wondering about, these are some of our recent
|
|||
* Electron performance
|
||||
* How to model the data. What should the application state look like?
|
||||
* Efficient styling rules and patterns
|
||||
* Knowledge about javascript packaging
|
||||
* Knowledge about JavaScript packaging
|
||||
* Testing (What is worth testing)
|
||||
* Authentication
|
||||
* Devops (CI/CD)
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ By default, data from the LBRY blockchain is basically a raw dump of data in a c
|
|||
|
||||
*In addition to extracting this data, you’d have to run several hundred thousand commands to get the same data returned by a single command below.*
|
||||
|
||||
Since blockhain data is raw, compressed, and not accessibly structured, most blockchains have specifically designed methods to create more usable forms of the data.
|
||||
Since blockchain data is raw, compressed, and not accessibly structured, most blockchains have specifically designed methods to create more usable forms of the data.
|
||||
|
||||
In the case of LBRY, Chainquery is both the easiest and most feature-rich method of doing that to date.
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ Most LBRY users do not need to use Chainquery directly and instead will simply b
|
|||
|
||||
However, if you’re interested in using it directly or poking around with the data, all of our code is open-source and available on GitHub. Detailed setup instructions are inside of the repository.
|
||||
|
||||
Additionally, at least for now, we’ve provided a public, readonly MySQL server you can connect to. This is a generic sql api that is accessible from an http GET and returns JSON data. You can even use it in your browser!
|
||||
Additionally, at least for now, we’ve provided a public, readonly MySQL server you can connect to. This is a generic SQL API that is accessible from an HTTP GET and returns JSON data. You can even use it in your browser!
|
||||
|
||||
Get the latest block information:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue