I’ve been talking about the case that you’re logged in with a Piped account, which makes your subscriptions and playlists become stored at Piped’s server.

Piped does more than just proxying at its backend, the only thing that you could really call to become proxied are thumbnails and video playback.

What you said is right, but I basically said the same thing.

I’m one of Piped’s main developers…

I don’t get the question. How’s that related to Mozhi?

Mozhi basically acts as a middleman between you and the translation api, it doesn’t store any user data.

Piped/Invidious proxy everything through YouTube, except for any kinds of user data, as that data is stored on the server you use.

Mozhi is proxied through the server/instance you use.

Yes, that’s a dependency of the relm4 crate we’re using, I haven’t yet figured out if we can disable it. The app doesn’t use any libadwaita component though.

No worries, I’m used to that from other projects I’m working on :)

Requested here: https://programming.dev/post/320260. Please upvote it in order to become considered as a new community on programming.dev :)

Yes, I don’t want to move the project to libadwaita either because I dislike its flat design and don’t use the GNOME environment in general. And I love theming Gtk apps :)

Not yet, but it would indeed be a good idea :) I created a request for a community here: https://programming.dev/post/320260. Not exactly sure if that fits programming.dev, we’ll see :)

Oh well, looks like I just misunderstood you then. No worries!

As already stated out, the project is still in alpha. Apart from that, there is a screenshot in the post …

There now are instructions how to build it using Docker in the Readme :)

Yes, that’s also the reason why the app uses gtk4 without libadwaita, I want to be able to use Catppuccin on it :)

Hey, thanks for your interest! What’s probably needed the most currently is someone spending some time to get all the things that require authentication done, but of course other things like adding screenshots to the README, adding CI via GitHub actions, etc would be useful too! :)

I don’t mind if someone creates a PR with some screenshots, however I would rather wait one or two weeks so that there’s no need to create a newscreenshots when a new feature is added.

Yes, I totally agree with you! I didn’t yet add screenshots to the README since some parts of the app are still matter to be changed in the near future. The development started actually just four days ago, so there’s still room for UI improvements. I’ll make sure to add screenshots to the README once it’s more mature.

Please keep in mind it’s still at a very early stage, so if things sometimes don’t work out perfectly yet, that’s matter to change in the future :)