Hello, I’m the developer behind Materialious. Perhaps you came across my post a few weeks back regarding the launch of my Material design frontend for Invidious.

I’m reaching out to gauge interest in expanding Materialious to serve as a unified interface for TikTok (Via Proxitok), Twitch (Via SafeTwitch), YouTube (Via Invidious), and potentially even search (Via SearxNG).

I’d love to hear your ideas and thoughts on this!

  • Scolding0513@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    I agree with Mora. it’s a really bad idea to make this in a whole different project. it splits up communities, creates confusion, and reduces anonymity sets.

    Why not work with the invidious team and get your theme added to the project, and maybe contribute the other changes you may have made?

    god knows invidious needs a way better UI/UX anyway

    • WardPearce@lemmy.nzOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      7 months ago

      Isn’t just a theme, is a completely different application built on top of Invidious’ API. What works completely differently to Invidious’ current UI. A LOT of things are handled different then how Invidious handles it on their frontend. Replacing Invidious current interface with Materialious isn’t a good idea, because its quite a bit bigger & requires JS compared to Invidious’ current UI.

      Calling Materialious a theme would be like calling clipious a theme.

      • Scolding0513@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        yeah but clipious just connects to existing invidious instances, so it’s just a frontend to invidious. you are making your own frontend and backend both

        • WardPearce@lemmy.nzOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          Materialious does currently just use Invidious’ API. If extending it requires a custom backend it will be a completely different project (what will still be using Invidious)