mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-08-31 17:31:26 +00:00
updates
This commit is contained in:
Thomas Zarebczan
GitHub
parent
46fa322f40
commit
1de1829bf1
1 changed files with 18 additions and 19 deletions
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
author: samuel-bryan
|
||||
title: 'Development and Community Update April 2018'
|
||||
date: '2018-05-04 18:00:00'
|
||||
date: '2018-05-04 23:00:00'
|
||||
cover: 'coder-tank.jpg'
|
||||
---
|
||||
Welcome to our LBRY Development and Community update, reviewing our progress for the month of April. It was a busy month, starting off with the company All-Hands summit, and progress was made on our desktop and Android apps, LBRY Protocol improvements, several community updates, and team growth. For previous updates, please visit [our Company News archive](https://lbry.io/news).
|
||||
Welcome to our LBRY Development and Community update! In this post we’ll show you what we’ve been up to and review our progress for the month of April. It was a busy month, starting off with the company All-Hands summit, and progress was made on our desktop and Android apps, LBRY Protocol improvements, several community updates, and team growth. For previous updates, please visit [our Company News archive](https://lbry.io/news).
|
||||
|
||||
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).
|
||||
|
||||
|
|
@ -13,12 +13,12 @@ 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. Our plan is to create a technical reference site which will be developer focused at https://lbry.tech which will also include a StackExchange like forum for Q&A/troubleshooting in the future.
|
||||
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 did release version [0.21.3](https://github.com/lbryio/lbry-app/releases/tag/v0.21.3) which included a minor fix to block content DMCA infringing content. 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!
|
||||
|
||||
On the Protocol side of the house, [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) is undergoing refactoring and improvements to the way blob announcement is handled and other DHT enhancements around peer availability. We were able to bring the blob announce times from 1 or 2 per second, to 25 per second (our target is 100 per second!). With these changes, our team hopes to improve the consistency of content availability on the network. A fair amount of time was also spent identifying and fixing our reflector servers to ensure that content uploaded by users is passed correctly to our content nodes. Previous to these changes, certain content would not be reflected properly which resulted in unavailable content if the original uploader was not online. Finally, development efforts on both the client and server side of our [wallet functionality](#wallet) have been progressing nicely.
|
||||
On the Protocol side of the house, [version 0.20](https://github.com/lbryio/lbry/releases/tag/v0.20.0rc9) is undergoing refactoring and improvements to the way blob announcement is handled and other DHT enhancements around peer availability. We were able to bring the blob announce times from 1 or 2 per second, to 25 per second (our target is 100 per second!). With these changes, our team hopes to improve the consistency of content availability on the network. A fair amount of time was also spent identifying and fixing our reflector servers to ensure that content uploaded by users is passed correctly to our content nodes. Before these changes, certain content would not be reflected properly which resulted in unavailable content if the original uploader was not online. Finally, development efforts on both the client and server side of our [wallet functionality](#wallet) have been progressing nicely.
|
||||
|
||||
### Content Blocking and DMCA
|
||||
In early April, LBRY Inc. received its first set of legitimate DMCA take down requests for a fair amount of infringing content LBRY URLs. This can be seen as a positive development because it means LBRY is on the map as a legitimate content sharing platform! Due to the decentralized nature of LBRY, we cannot remove content metadata from the blockchain, but as a company creating services which use the data, we must follow local laws. This means we have to block access to infringing URLs and make sure the content itself is deleting from our hosts (even though it could still be hosted by the original upload and by others who have downloaded it). The latest version of the app provided the ability to block infringing content.
|
||||
|
|
@ -47,9 +47,9 @@ 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.
|
||||
|
||||
Another feature currently being worked on is subscription syncing 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.
|
||||
|
|
@ -67,7 +67,7 @@ The client side, which is a Twisted based implementation of the wallet, is still
|
|||
This is the first time we are mentioning the [Chainquery project for LBRY](https://github.com/lbryio/chainquery) in our communications as it’s mostly flown under the radar because of its early development status. Chainquery will provide a SQLized view of the LBRY blockchain which can be used across many projects where we currently need such data such as Lighthouse (search server), API server, LBRY app and spee.ch. Currently, these projects either run their own implementation of blockchain views or don’t take advantage of having the information readily available through a simple query, but rather have to rely on direct communication with the blockchain. Chainquery will slowly be integrated into these services to provide quick and easy access to claim/channel information, payment data and transactions.
|
||||
|
||||
### Blockchain - Hardfork Update
|
||||
In our previous [hardfork update](https://lbry.io/news/lbry-development-community-update-mar-2018), we mentoined two upgrades to the blockchain - removing claim expiration and removing case sensitivity. After further discussion with the team, we have decided to perform these upgrades one by one in order to simplify the number of code changes which should result in a smoother transition. Since claim expiration is the more critical of the two, it will go first. We will be activating these changes and simulating the hard fork on our testnet in the coming days, and if all goes to plan, we will announce the date of the main net hardfork.
|
||||
In our previous [hardfork update](https://lbry.io/news/lbry-development-community-update-mar-2018), we mentioned two upgrades to the blockchain - removing claim expiration and removing case sensitivity. After further discussion with the team, we have decided to perform these upgrades one by one in order to simplify the number of code changes which should result in a smoother transition. Since claim expiration is the more critical of the two, it will go first. We will be activating these changes and simulating the hard fork on our testnet in the coming days, and if all goes to plan, we will announce the date of the main net hardfork.
|
||||
|
||||
Based on feedback received when we first mentioned a hard fork, we want to stress that forks are standard means of upgrading blockchain functionality and should not be compared to other contentious hard forks like Bitcoin or Ethereum. Other blockchain projects go through this same process and LBRY will continue to evolve the blockchain code base through such upgrades.
|
||||
|
||||
|
|
@ -87,11 +87,11 @@ Lead Designer (UI/UX, Graphics)
|
|||
And if you don’t see an opportunity that’s an exact fit, there are many other ways to get involved in the project and earn LBC or cash. We’re also offering a $5k finder’s fee for successful hires for our job listings. [Click for more info](https://lbry.io/join-us).
|
||||
|
||||
### LBRY All-Hands Recap {#all-hands}
|
||||
The LBRY Spring 2018 All-Hands Summit was a great success. Our team of 24 came from around the world to Manchester, NH, for a week of food, bonding, break-out sessions, and jumping competitions. [Our CTO won.](https://spee.ch/4/natalie-grin-jumping.jpeg)
|
||||
The LBRY Spring 2018 All-Hands Summit was a great success. Our team of 21 came from around the world to Manchester, NH, for a week of food, bonding, break-out sessions, and jumping competitions. [Our CTO won.](https://spee.ch/4/natalie-grin-jumping.jpeg)
|
||||
|
||||
A great deal of the time we spent together was focused on cross-team operations and communications strategies. Our team is growing fast, and our processes and systems need to grow, too. We have already begun to implement a number of the takeaways from these meetings and believe we will gain a lot from more efficient and clear communication across teams.
|
||||
A great deal of the time we spent together was focused on cross-team operations and communications strategies. We’re growing fast, and our processes and systems need to grow at pace. We have already begun to implement a number of the takeaways from these meetings and believe we will gain a lot from more efficient and clear communication across teams.
|
||||
|
||||
This year’s all-hands schedule was very full, and we accomplished just about everything we’d hoped to while together --but the most important achievement was getting to know our newer team members and connecting in-person with people we work with daily, but mostly see on screens.
|
||||
This year’s all-hands schedule was full, and we accomplished just about everything we’d hoped to while together --but the most important achievement was getting to know our newer team members and connecting in-person with people we work with daily, but mostly see on screens.
|
||||
|
||||
|
||||
|
||||
|
|
@ -114,7 +114,7 @@ Earn LBC! Help us grow our community and get the word out about LBRY: We will ti
|
|||
### 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 in the middle of 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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
|
@ -123,8 +123,8 @@ The [LBRY Tipbot for Twitter](https://twitter.com/@LBC_TipBot) was tested intern
|
|||
|
||||
|
||||
|
||||
### LBRY.tech Update
|
||||
We’ve recently hired additional help to shape our lbry.tech technical resource and it’s design/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.
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
|
@ -140,21 +140,20 @@ After not receiving any response from Issac Arthur, we then reached out to [VetR
|
|||
|
||||
### Meetups and College Campus Initiatives - Get Involved! {#meetup-update}
|
||||
|
||||
Natalie visits Hack the Heights
|
||||
Natalie DC
|
||||
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.
|
||||
|
||||
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,
|
||||
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.
|
||||
|
||||
Our International Discord community is growing! We have added channels for German and Russian languages.
|
||||
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.
|
||||
|
||||
Does free speech matter to you? Would you like to get involved with cutting edge blockchain technology and earn a few cryptocoins in the process? We are [looking for ambassadors](https://lbry.io/meet) to spread the word on college campuses and at live blockchain or video related meetups - if you’d like to bring LBRY to your group, we’ll help you with resources, swag, and LBC for your members!
|
||||
Does free speech matter to you? Would you like to get involved with cutting edge blockchain technology and earn a few cryptocoins in the process? We’re [looking for ambassadors](https://lbry.io/meet) to spread the word on college campuses and at live blockchain or video related meetups - if you’d like to bring LBRY to your group, we’ll help you with resources, swag, and LBC for your members!
|
||||
|
||||
### LBRY-C Collaboration
|
||||
The independent LBRY-C community group has begun work on a website to use the LBRY protocol called *Liberum.*
|
||||
|
||||
*Liberum* is a message board that prides itself on anonymity, privacy and free speech, built on top of the LBRY protocol. It is created for those users wanting to engage in and discuss their passions in an open space without fear of unjust censorship.
|
||||
|
||||
It's here for those that want civil discourse as well as to discuss interests amongst their fellows. The project has just begun but for those who are interested in helping grow the project, you are welcome to join the team on their [Discord Server](https://chat.lbry.io).
|
||||
It's here for those that want civil discourse as well as to discuss interests amongst their fellows. The project has just begun but for those who are interested in helping grow the project, you are welcome to join the team on their [Discord Server](https://discord.gg/ytY4NeJ).
|
||||
|
||||
### Want to Run a Spee.ch Clone or Web Server Hosting LBRY content? {#speech-host}
|
||||
LBRY is looking for users or communities that are interested in hosting a spee.ch like website or even a web portal into their own LBRY content (think of this as your own local YouTube page!). We would be more than happy to walk you through the process which would include customization and tweaking it to your liking! Does this sound interesting to you or maybe someone you know? Sign up on or share our [speech admin mailing list](https://lbry.io/speech-admin) to be notified when LBRY will host a live session. The purpose of this will be to learn how to run your own spee.ch install, how spee.ch works, and have live help and discussion.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue