Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

odysee-android-floss is not the FLOSS version of odysee-android #9

Open
pixel2user opened this issue Jul 2, 2022 · 4 comments
Open

Comments

@pixel2user
Copy link

pixel2user commented Jul 2, 2022

The naming scheme leads people to think that [odysee-android-floss] is the FLOSS version of [odysee-android], which is not the case. For example: OdyseeTeam/odysee-android#139 (comment) and OdyseeTeam/odysee-android#148 (comment)

This is not a fork of odysee-android, but instead is a wrapper for [odysee-frontend] (code that runs odysee.com).

Please make this clear in the README.md file! #8

@BRBsoup
Copy link

BRBsoup commented Dec 16, 2022

I think it's done, from newest readme file of odysee-android :

Build Variants
There are two build variants: Full and FOSS. The Full variant uses Google APIs and the FOSS variant doesn't. You can switch between them on the "Build Variants" tab in Android Studio.

@pixel2user
Copy link
Author

Sadly, it hasn't been done. In your own words: #14 (comment)

@BRBsoup
Copy link

BRBsoup commented Dec 16, 2022

Sadly, it hasn't been done. In your own words: #14 (comment)

Yeah, it's actually all done and gone drove me about mad... sorry for presuming to correct you/second guessing you, I could have saved myself a dose of lost sanity if I just trusted your posts the first time I understood them!

Unfortunately this all is enough to seriously undermine the trust in an app that's drawn an image of itself as, and a community that that looks at it as, alternative platform to Big Bad Tech... However, the obvious is overlooked so egregiously that it might almost seem that the devs have just maybe perhaps purposefully cooked in some amount of discord into their own ecosystem. This isn't the first such misstep the devs took which has eroded trust, and I'm certainly not the first who has raised such points, therefore I do hope it's at least one of the lasts of this magnitude of gross negligence...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@pixel2user @BRBsoup and others