Not technically no, though neither does it fully embrace the spirit of FOSS either. Anyway I was explaining the appearance of those two being at odds with one another in the meme. Anyone who does not enjoy meme content can simply block this community and move on with the serious side of life.:-)
Correct me if I’m wrong but does FOSS not simply mean the following?
software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge
source: Wikipedia
From my understanding AOSP’s license grants all those rights. I think what you might be opposed to is that it isn’t developed out in the open, which is a fair criticism.
Well, they wrote the “spirit of FOSS” and you pulled out a completely sterile definition, which has no spirit at all.
At the very least, even with that sterile definition, embracing the spirit would mean making all the software you’re distributing FOSS. Instead, Google has been doing all kinds of bundle deals and whatnot to ensure that most distributions of their FOSS software come with their proprietary parts.
However, going further in embracing the spirit, particularly the “free software” part of FOSS is idealistic. It doesn’t just fulfill that definition to fulfill that definition. Rather, it sees that definition as the baseline, to help ensure that the freedom of users is respected.
AOSP, despite being under an appropriate license, does not respect that freedom.
For example, many users would want their keyboard app (which has access to their typed passwords) to not have internet access. AOSP has a myriad of permissions, but not for internet access, since Google wants their ads to be displayed.
In theory, the license ensures that AOSP can be forked, and Custom ROMs do soft-fork it (i.e. make slight amendments to what Google puts out), but due to how much development Google puts into Android rather than there being a development community, it’s effectively not viable for anyone to truly hard-fork AOSP (i.e. take it into a new direction, independent from Google).
it can always be forked as a project that does. this is part of the point of foss and why you should be using lineage or graphene instead if you care about this
yeah, again, just like Chromium technically speaking.
Let’s use the lesser, Foss version of Google’s product so they can continue to have a monopoly, so then later they can force you to install a proprietary blob or account apps or services need.
nothing lesser about grapheneos or lineageos at all.
iirc there are problems with trying to use some mainstream apps on these operating systems. When I say lesser I don’t mean to demean them, I mean they’re the lesser used and not really known about alternative and thus not really supported unless you can live your life in f-droid which if so, kudos to you, you’re livin’ the dream.
but im all ears if you have a usable alternative for a foss phone.
Tell that to Google…
Google having their own proprietary crap embedded in their version doesnt make AOSP not FOSS.
Thats the entirety of the basis for things like GrapheneOS, despite Google gobbling it up.
Not technically no, though neither does it fully embrace the spirit of FOSS either. Anyway I was explaining the appearance of those two being at odds with one another in the meme. Anyone who does not enjoy meme content can simply block this community and move on with the serious side of life.:-)
Correct me if I’m wrong but does FOSS not simply mean the following?
source: Wikipedia
From my understanding AOSP’s license grants all those rights. I think what you might be opposed to is that it isn’t developed out in the open, which is a fair criticism.
Well, they wrote the “spirit of FOSS” and you pulled out a completely sterile definition, which has no spirit at all.
At the very least, even with that sterile definition, embracing the spirit would mean making all the software you’re distributing FOSS. Instead, Google has been doing all kinds of bundle deals and whatnot to ensure that most distributions of their FOSS software come with their proprietary parts.
However, going further in embracing the spirit, particularly the “free software” part of FOSS is idealistic. It doesn’t just fulfill that definition to fulfill that definition. Rather, it sees that definition as the baseline, to help ensure that the freedom of users is respected.
AOSP, despite being under an appropriate license, does not respect that freedom.
For example, many users would want their keyboard app (which has access to their typed passwords) to not have internet access. AOSP has a myriad of permissions, but not for internet access, since Google wants their ads to be displayed.
In theory, the license ensures that AOSP can be forked, and Custom ROMs do soft-fork it (i.e. make slight amendments to what Google puts out), but due to how much development Google puts into Android rather than there being a development community, it’s effectively not viable for anyone to truly hard-fork AOSP (i.e. take it into a new direction, independent from Google).
it can always be forked as a project that does. this is part of the point of foss and why you should be using lineage or graphene instead if you care about this
yeah, again, just like Chromium technically speaking.
Let’s use the lesser, Foss version of Google’s product so they can continue to have a monopoly, so then later they can force you to install a proprietary blob or account apps or services need.
nothing lesser about grapheneos or lineageos at all.
but im all ears if you have a usable alternative for a foss phone.
iirc there are problems with trying to use some mainstream apps on these operating systems. When I say lesser I don’t mean to demean them, I mean they’re the lesser used and not really known about alternative and thus not really supported unless you can live your life in f-droid which if so, kudos to you, you’re livin’ the dream.
https://postmarketos.org/
postmarket is way more of a dream than fdroid rn.