After splitting off about 2/3rds of staff to work on Odysee, LBRY is staffed almost exclusively by engineers. As a result, we haven’t been talking much, but we’re still building.
With the SEC alleging that even talking about feature development is against United States law, there’s been a chilling effect on communication. But don’t take that to mean we’re slowing down in any way.
Here’s a look at the future.
### The future of LBRY social video is Odysee
LBRY is *not* the future of web3 social video. LBRY is a decentralized web3 publishing protocol.
Odysee is by far the easiest way to use the LBRY network for publishing or watching video. LBRY will not be engaging in marketing campaigns or community building around web3 social video.
Make sure you’re following @odysee on LBRY, as well as [Twitter](http://twitter.com/odyseeteam) and [Reddit](http://reddit.com/r/odyseeforever). Odysee is going full-speed ahead and continues to see record usage and growth.
### The future of LBRY is application diversity
2022 and 2023 will be about bringing LBRY into more apps and ecosystems. Some of the things we’re working with partners on include:
- A text-first news aggregator and publishing platform
- Two different music and podcasting apps (may the best team win)
- A file sharing app optimized for CAD files
We’ve started a new developer only chat, where people actively working on apps can hangout with core LBRY engineers. If you’re interested in that, email [email@example.com](mailto:firstname.lastname@example.org).
### The future of LBRY is even more decentralized
While LBRY is decentralized, Odysee has continued to push ahead with centralized feature development, such as livestreaming. Other features, like searching and commenting, are only semi-decentralized.
We’re continuing to work on bringing Odysee features into the LBRY protocol themselves, or otherwise improving the state of affairs with decentralization. Here’s a look at how the current LBRY network and Odysee backend interact.
Only a decentralized network can truly protect against the abuses we’ve regularly and repeatedly seen by big tech. So-called “alternative” tech is typically a subpar knock-off. Web3 tech is successor tech.
### The future of LBRY is Go
We’ve also been working on porting some core codebases from C++ and Python into Go. While this won’t immediately impact users, it will substantially improve development velocity over time.
The most substantial piece – the blockchain code – is already mostly ported and is now being tested. If you’re interested in trying running the new Go code, you can find the latest releases [here](https://github.com/lbryio/lbcd/releases).
### The future of LBRY is as one of the few legal cryptocurrencies
LBRY’s lawsuit with the SEC is poised to establish it as one of the few known-to-be legal cryptocurrencies in the United States. While there’s little news on this front yet, a lot will be happening over the next 6 months. We’ll post updates on this channel as well as on Twitter.
Thank you to the almost 50,000 people who have signed the [petition](https://www.change.org/p/cryptocurrency-is-not-a-crime)!
### The future of LBRY is technical community
One of the lessons we learned from launching lbry.tv, which was later rebranded to Odysee, is that the LBRY name should be reserved for the tech, not consumer apps. This doesn’t mean programmers only, but it does mean that LBRY is primarily for technically minded users. If you want to hang out with other LBRY users, join one of these chats:
- [LBRY Foundation Chat](http://chat.lbry.org/) (largest, open to the public, run by l[bry.org](http://lbry.org/))
- LBRY Developer Chat (mostly engineers, private, run by [lbry.com](http://lbry.com/), email [email@example.com](mailto:firstname.lastname@example.org) for access)
Additionally, with the shift away from consumer-oriented software being released from LBRY, lbry.com and lbry.tech will likely be merged sometime in 2022.
### The best is yet to come 🚀🚀🚀
There’s not really any other way to end one of these, is there?