silverpill
@japananon @boilingsteam @MoeBritannica
>lizard shedding its tail kind of thing
Yes, this is a plausible scenario. But if they do "exit to community" instead, the system will probably collapse, because as you say it is designed to be centrally managed. Regular users have no idea how it works. So much for censorship resistance.
Compare it to fedi where the knowledge required for maintaining infrastructure is widespread.
チャノさん
@MoeBritannica @boilingsteam I believe LBRY is the technology stack underpinning Odysee, but they're separate corporate entities (though Odysee Inc was a wholly owned subsidiary of LBRY Inc as of 2021, no idea if that's changed).
Odysee has their own github repo with app and frontend code, but the backend is still LBRY. In theory, the backend protocol is open source under an MIT License so it could be carried forward by somebody else, but no idea if that'll actually happen. Odysee might have some legal trickery up its sleeve, where it spins off into a wholly independent company, forks the old LBRY code, and keeps working on the backend... lizard shedding its tail kind of thing.
Even if they did, though, their whole "decentralization" spiel was a crock of shit. It may be possible for users to host and run LBRY infrastructure on their own machines, but they do absolutely nothing to make that easy for anybody, and as a result 90%+ of all LBRY content and everything else is centralized under Odysee.
@silverpill was talking about this earlier, he might know things I don't.
? ⚔️ McCreeaboo ⚔️ ?
Boiling Steam
LBRY Is Dead: https://twitter.com/LBRYcom/status/1678866789407551489
#lbry #video #platform #termination
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.