Not allowed by the ToS and the privacy policy

The context is the name of the dependency and its very questionable purpose.

At least the data is sent to Gemini servers. This alone can be illegal but I’m not sure. What I’m more sure about is that they do use the data to train the models.

But it’s still probably illegal

I’m worried about that one specifically. Dependencies in general can be suspicious if they come from untrusted sources but in that case it’s suspicious by being related to testing (like the xz thing was) that shouldn’t even be in a released app anyways.

Update plugin com.android.test to v8.5.0 by @renovate in #1561

Was it properly checked for backdoor injections?

Android is dying imo, especially AOSP. A14 has serious source code issues afaik and I don’t think anyone dares to say they’re not intentional.

Same

Please stop harassing me. And idk. I saw that issue but at this point I think it was just misinformation.

Fedora Atomic allowed it recently afaik. I’m always forgetting this. And NixOS is not immutable because of R/W FS.

/etc can’t be edited on immutable distros and usually apps store the editable config in /home/config and make the /etc one kind of read-only.

Oh so it makes it impossible to change config path? Yea that’s a bit inconvenient but you always can just make many files and replace the file in the right directory with the one you want.

But what’s the difference? It’ll be in /home anyways and I heard BSD had some issues with something that could be XDG.

Reddit killed them a year ago. That’s why people switched to Lemmy btw.

I think this app is just a very simple frontend to the official API without much tracker blocking. It’s not meant for privacy but more for simple ad-free listening.

Not all FOSS apps look good now but MD3 really made it easy to make good looking apps. Still it’s a shame the libraries that are used to provide it are slower than the previous ones.

Also they limit the amount of data your device sends to Google when using YouTube.

You too, mister/miss

Yes, mister/miss, I read your comments again and I admit I did completely misunderstand you. I’m sorry for that and I’m extremely grateful you chose to explain your point in a friendly manner instead of starting a drama or acting in a toxic manner.

ViMusic is no longer maintained so any Google side changes (that are very frequent recently) can break some features of it (like it already did with song authors) or the whole app. If it works for you then you don’t have to switch. I’m not familiar with any security vulnerabilities of ViMusic so it’s definitely not necessary to avoid using it (though I still highly encourage you to check its GitHub so you’re informed about any issues found) and it’s probably even slightly more privacy-focused than InnerTune but many users prefer actively maintained software for many reasons, including but not limited to the ones mentioned above.