• 0 Posts
  • 7 Comments
Joined 5 years ago
cake
Cake day: December 2nd, 2021

help-circle
    • one of most important problem you solved is centralised bookmark, history. When i watched a clip in mobile, i want my desktop client to know and hide it from me
    • considered continued trend of high ram price, nice to have light weight mem efficient desktop app without ts,electron,webview,java those mem eating monsters, if we utilize app like mpv, plus your clear be,fe architecture, it should not that hard and easy to maintain.
    • nuc+debian+flex launcher+remote control are such sweet combo compared to android tv. Way better than other media center solutions especially in noise, energy,codec, capacity, flexibility, security stand point. But i haven’t found remote control+nuc friendly linux desktop YouTube clients. That’s why I said centralised bookmark is important. Remote control doesn’t have keyboard, if I can bookmark in mobile/desktop and loop through in nuc via bookmark, it will be sweet. Again, you don’t have to finish by your own.
    • I have a few more on backup iff someone interested. tubearchivist,yt-dlp are sweet, but all solutions i seen are missing some piece

  • Normally I would skip all yet another YouTube clients which provide no additional benefits than existed solutions, especially YouTube is always being a jerk and change their api/interface frequently and new projects never caught up. It’s good that you don’t reinvented the wheel by using existed extraction lib and split fe+be in design. How stable your library against YouTube’s change and how fast will they jailbreak it usually? Most competitors don’t consider ecosystem, does yours provide hooks, api for third party? I can tell you my usecase or problems i seen iff you are interested






  • First of all, I like rust+tui stack and thanks to sharing to community,but I hate to see open source dev wasting valuable time on reinventing wheel on something constantly change. YouTube’s api, webpage constantly change to prevent third party sw. While we have invidious which can be use as backend, why ppl want to waste their time and abandon project quick? Freetube can use invidious api as source for example. What we need make invidious more backend friendly (i always confused why invidious dev not focus on their api only) and able to have single source of truth on subscription, history across mobile, desktop frontend app