> Play billing "must not be used in cases where payments include … tax exempt donations"
> Note: 501(c)(6) is a tax-exempt status; donations are not tax-deductible for the donor. Google's communications explicitly state "tax-exempt".
Isn't it pretty obvious that the problem is the donations aren't tax-exempt, despite the organization being tax-exempt? Your note suggests you already understand this.
Logically, the payment processor (who deals with sales taxes rather than income taxes) should worry about the taxability of the transaction rather than the tax status of the recipient, right?
> Specifically, your app allows users to contribute donations to an organization that is not tax-exempt.
So whoever is writing their email is mixing these two up, but you're reading the policy itself and it is fairly clear-cut what it means for you, right?
This is why software should not be subjected to an "app store" type distribution system, where a monopolist retains absolute control of what software can run on your devices, and can capriciously deny distribution to developers for whatever reason it likes.
You can install from other stores (AnkiDroid is on F-Droid, for example), or from direct file download on Android already. The problem is rather thay most users just use the store preinstalled on their phone as part of Google's deal with OEMs to bundle Google Play Services. So either you follow Google's rules, or you lose all the users who don't want to leave the walled garden, even though they can.
Everyone is speed running towards a future where you need a permit to write software.
Try to run a binary that doesn’t have the right cert( or whatever it’s called on Windows) and you get a bunch of warnings.
Even if Android is open , normal people will only use the App Store. I can imagine China forcing Apple to allow 3rd party installations of software one day .
The EU did something where to my knowledge Apple still gets a cut of each sale.
Google is making it increasingly difficult to freely install software from app stores that they don't control and tax. Quoting https://keepandroidopen.org :
> Starting in 2027*, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.
> Every app and every device, worldwide, with no opt-out.
- the "24 hours" is Google's first formulation of plausible deniability. They've likely done testing to hone that number to find a sweet spot.
- the "24 hours" is enforced by remotely-run code, meaning Google remains in control of it and can unilaterally alter how this works, any time they feel like.
Imagine you went to the shops, and found that one shop, while it had the goods on display, and could totally just let you pick them up and buy them, was required by the shop next door to make you go away and come back no sooner than 24 hours later. Meanwhile, the shop next door is right there, and it's open, and it has no such restriction.
On what planet do you think anyone other than the most dedicated of dedicated people would choose the shop that requires waiting a whole day to use it when the alternative has no such restriction?
> unverified developers
The developers in F-Droid are verified, just not by Google. That's the whole fucking point. Google is not the be-all and end-all, but with this power-play, they are making themselves that.
> On what planet do you think anyone other than the most dedicated of dedicated people would choose the shop that requires waiting a whole day to use it when the alternative has no such restriction?
I have no clue what you're referring to or worried about here, could you clarify? Are you worried Android is going to lose power users to iPhone? What are the shops you're referring to here? We're not buying pastries.
> The developers in F-Droid are verified, just not by Google.
"Unverified" in my comment was a shorthand for "unverified by Google", not an insult.
> Google is not the be-all and end-all, but with this power-play, they are making themselves that.
The complain about that? Rather than wasting time complaining about the 24h wait?
I don't know if people's imaginations are lacking here, but there could easily be a world in which your "alternative" verifier would still make you wait 24h (or longer). The wait is clearly a security mechanism, regardless of who makes you do it. Is your actual problem the wait, or is your actual problem the identity of the entity making you do it?
> I'm guessing you've never shown up to a foreign country without a phone. First thing I do after I get through customs is find the phone store.
Indeed I have not. In fact I haven't even heard of people doing this until your comment. And that's before unknown app developers coming into the picture. I assume you do this to avoid border phone searches? And you feel the (ostensibly) security-related mechanisms for the rest of the world to be centered around this use case? Meaning the rest of the world should pay the cost to their own security to cater to this flow?
I just print out all my stuff and go old school. Pick up a cheap android phone at the airport and go about my business. Not sure why this is uncommon. Maybe I'll switch it up next time and bring my phone loaded up with dick pics.
Why shouldn't people be free to install their preferred software immediately after purchasing a phone? How does it help anyone other than Alphabet shareholders to restrict that?
So we started with an OS (when Google still needed to gain market share and goodwill) which was opensource. Now Google is no longer developing Android source code in the open and decreasing the "opensourcing" to a couple of source drops each year (the interval has been decreased multiple times). Google Play was introduced (basically clamping down the app store ecosystem) and from there Google has only made it harder to get around Google Play. Introducing things like phone attestation. Supposedly a security measure, yet for some reason a Samsung phone which hasn't had an update in 4 years still passes basic level attestation. And now Google is yet again making it harder to get around the Play store.
And for some reason you seem to think it is reasonable to assume it is going to stop here?
> And for some reason you seem to think it is reasonable to assume it is going to stop here?
I really don't. That is, actually, my entire point: people are going to roll their eyes at this right now. And then you're going to lack/lose the supporters you'll need when things really get bad.
To me it's not really the concept of the app store that's dystopian, it's not that different from a deb or rpm repository. What is dystopian is the level of control the OS vendor maintains over the entire ecosystem.
> Because we are a 501(c)(6), OSC is not a registered 501(c)(3) charity; donations to hosted member projects are not tax-deductible. This is consistent with IRS guidelines — open source donations aren't automatically classified as charitable simply because they are FOSS.
> If your project has a clear charitable purpose, a 501(c)(3) fiscal sponsor may be a good fit.
If only PWA were not made invisible by Apple. The install button has been moved voluntarily to the share menu.
The UE should make it mandatory to permit PWA install popups on all platforms.
Such problems wouldn't arise, because this app could be installable as a cached Web app. A native mobile application could be installed only for specific functionalities.
Every day Google commits to more Evil. How much more Evil can this world take from Google?
Also - all those monopoly-stores need to be broken up. It can not be that these mega-corporations continue to be protected by a selfish US government wanting to install monopolies globally.
> GitHub Sponsors is another way to raise for an open source organization.
Which they do in fact use, with OSC as a fiscal host. Still doesn’t help here though – Google is unhappy with the nature of transaction (donation that is not tax-exempt in the U.S.), not with the platform on which it occurs.
If they instead made the donations go to e.g. the lead developer, it would probably be allowed (“peer-to-peer payments” can’t use Google Play billing, so the app can “lead users to [another] payment method” [1]). Whether this is a good idea is a whole another question.
> Note: 501(c)(6) is a tax-exempt status; donations are not tax-deductible for the donor. Google's communications explicitly state "tax-exempt".
Isn't it pretty obvious that the problem is the donations aren't tax-exempt, despite the organization being tax-exempt? Your note suggests you already understand this.
Logically, the payment processor (who deals with sales taxes rather than income taxes) should worry about the taxability of the transaction rather than the tax status of the recipient, right?
> Specifically, your app allows users to contribute donations to an organization that is not tax-exempt.
So whoever is writing their email is mixing these two up, but you're reading the policy itself and it is fairly clear-cut what it means for you, right?
It's not clear given Google's policy wording and replies. We've removed the links, and can move forward once clarification has been provided.
This is why software should not be subjected to an "app store" type distribution system, where a monopolist retains absolute control of what software can run on your devices, and can capriciously deny distribution to developers for whatever reason it likes.
Everyone is speed running towards a future where you need a permit to write software.
Try to run a binary that doesn’t have the right cert( or whatever it’s called on Windows) and you get a bunch of warnings.
Even if Android is open , normal people will only use the App Store. I can imagine China forcing Apple to allow 3rd party installations of software one day .
The EU did something where to my knowledge Apple still gets a cut of each sale.
This article appeared in the February 1997 issue of Communications of the ACM (Volume 40, Number 2).
> Starting in 2027*, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.
> Every app and every device, worldwide, with no opt-out.
- the "24 hours" is enforced by remotely-run code, meaning Google remains in control of it and can unilaterally alter how this works, any time they feel like.
Imagine you went to the shops, and found that one shop, while it had the goods on display, and could totally just let you pick them up and buy them, was required by the shop next door to make you go away and come back no sooner than 24 hours later. Meanwhile, the shop next door is right there, and it's open, and it has no such restriction.
On what planet do you think anyone other than the most dedicated of dedicated people would choose the shop that requires waiting a whole day to use it when the alternative has no such restriction?
> unverified developers
The developers in F-Droid are verified, just not by Google. That's the whole fucking point. Google is not the be-all and end-all, but with this power-play, they are making themselves that.
I have no clue what you're referring to or worried about here, could you clarify? Are you worried Android is going to lose power users to iPhone? What are the shops you're referring to here? We're not buying pastries.
> The developers in F-Droid are verified, just not by Google.
"Unverified" in my comment was a shorthand for "unverified by Google", not an insult.
> Google is not the be-all and end-all, but with this power-play, they are making themselves that.
The complain about that? Rather than wasting time complaining about the 24h wait?
I don't know if people's imaginations are lacking here, but there could easily be a world in which your "alternative" verifier would still make you wait 24h (or longer). The wait is clearly a security mechanism, regardless of who makes you do it. Is your actual problem the wait, or is your actual problem the identity of the entity making you do it?
Indeed I have not. In fact I haven't even heard of people doing this until your comment. And that's before unknown app developers coming into the picture. I assume you do this to avoid border phone searches? And you feel the (ostensibly) security-related mechanisms for the rest of the world to be centered around this use case? Meaning the rest of the world should pay the cost to their own security to cater to this flow?
Why shouldn't people be free to install their preferred software immediately after purchasing a phone? How does it help anyone other than Alphabet shareholders to restrict that?
So we started with an OS (when Google still needed to gain market share and goodwill) which was opensource. Now Google is no longer developing Android source code in the open and decreasing the "opensourcing" to a couple of source drops each year (the interval has been decreased multiple times). Google Play was introduced (basically clamping down the app store ecosystem) and from there Google has only made it harder to get around Google Play. Introducing things like phone attestation. Supposedly a security measure, yet for some reason a Samsung phone which hasn't had an update in 4 years still passes basic level attestation. And now Google is yet again making it harder to get around the Play store.
And for some reason you seem to think it is reasonable to assume it is going to stop here?
I really don't. That is, actually, my entire point: people are going to roll their eyes at this right now. And then you're going to lack/lose the supporters you'll need when things really get bad.
> Because we are a 501(c)(6), OSC is not a registered 501(c)(3) charity; donations to hosted member projects are not tax-deductible. This is consistent with IRS guidelines — open source donations aren't automatically classified as charitable simply because they are FOSS.
> If your project has a clear charitable purpose, a 501(c)(3) fiscal sponsor may be a good fit.
- https://docs.oscollective.org/welcome-and-introduction-to-os...
These donations aren't tax exempt. 501(c)(3) are tax exempt. If users are paying via Google pay these payments must be tax exempt to the *user*.
The UE should make it mandatory to permit PWA install popups on all platforms.
Such problems wouldn't arise, because this app could be installable as a cached Web app. A native mobile application could be installed only for specific functionalities.
https://support.google.com/googleplay/android-developer/answ...
but make sure to "pay the relevant Play service fee, starting October 1, 2026."
Very cool, Google.
Also - all those monopoly-stores need to be broken up. It can not be that these mega-corporations continue to be protected by a selfish US government wanting to install monopolies globally.
― Benito Mussolini
Epic Games v. Google: https://en.wikipedia.org/wiki/Epic_Games_v._Google
GitHub Sponsors is another way to raise for an open source organization.
Which they do in fact use, with OSC as a fiscal host. Still doesn’t help here though – Google is unhappy with the nature of transaction (donation that is not tax-exempt in the U.S.), not with the platform on which it occurs.
If they instead made the donations go to e.g. the lead developer, it would probably be allowed (“peer-to-peer payments” can’t use Google Play billing, so the app can “lead users to [another] payment method” [1]). Whether this is a good idea is a whole another question.
[1]: https://support.google.com/googleplay/android-developer/answ...
So you are still complying.