Open-source apps removed from Google Play Store due to donation links
lists.zx2c4.com
lists.zx2c4.com
Wireguard had 50k+ installs according to its (now dead) playstore page: https://webcache.googleusercontent.com/search?q=cache:kSsZsb...
AndOTP had 10k+ installs: https://webcache.googleusercontent.com/search?q=cache:buaKcF...
An update on the WireGuard situation: they have reinstated the app _without_ the donation link. From what I can tell from talking to Google insiders, there has been no change in policy. Officially, Google has not communicated at all with us about it, so we're not sure what's up. But at least our app is available again to users, which is great.
Disallowing developers from using in-app billing for donations, while also barring them from linking to external donation platforms, puts open source projects in a difficult position, and appears to be overly hostile towards funding open source development.
Google must clarify their position on whether they allow donation links in apps published on Google Play. The app takedowns [2] of the last few days show that this is a significant development, and it is of great importance for all open source developers.
It's best to publicly document the messages you receive during app takedowns, since app store policies are often vague, it's easy for reviewers to make mistakes, and having a clear reference for these decisions also helps the public assess the validity of the takedown.
[1] https://play.google.com/about/monetization-ads/
> Here are some examples of products not currently supported by Google Play In-app Billing:
> One time-payments, including peer-to-peer payments, online auctions, and donations.
This is the problem of developing free software on a non-free platform. They have absolute control of your work under their own terms, no matter how ridiculous they are. I never understood why the google play store is a socially acceptable idea for free software developers.
Google Play has been very clear about this[1]:
> Fund solicitations
> Examples: Donation solicitations from parties without a valid 501(c)(3) tax exempt status clearly displayed to the public; solicitations from parties without valid proof of exempt tax status or proof of registration with the relevant country's regulatory bodies and authorities; and political organizations that have registered with the Federal Election Commission (FEC)
For instance, Wikipedia displays an external "Support Wikipedia" link in the main menu of its Android app[2] without violating Google Play's terms and conditions.
But why are we forbidden from linking to an external page that lists other ways to support a project, such as Patreon?
I think we should stop being apologetic, and begin to call out Google for the damage they are inflicting upon open source developers.
Nobody is allowed to use Google Play's in-app billing for donations, and only organizations with a valid tax exempt status can link to an external page that lists donation options.
> Any individual or business processing transactions with Google payments must adhere to these policies.
[1]: https://sfconservancy.org/ [2]: https://www.spi-inc.org/
That's the question (at least for me) here: why are (non-tax-exempt) donations not allowed, beyond the tautological response of "because the rules say so"? I'm not familiar with the regulations around this area, so for all I know there's a great non-Google reason for this and Google just wants to avoid the hassle of conforming to some law. Or maybe donations is a feature they want to eventually support in Google Play and they don't want to have to force a bunch of apps in the future to switch once they add it (which would be a more disappointing reason). Perhaps they're afraid that it would create a loophole where people could get around the 30% cut since psychologically it feels shitty for someone to middle-man a donation, but then if they made donations Google-tax free, everyone would just choose "donation" and they'd have to police this.
By requiring government registration my guess is the hope is both that the fraudsters will be caught or dissuaded and if they do make it past the government registration then when the real devs complain Google can say "take it up with the government. They mis-licensed. We just followed their license"
Recently I created a small homepage with different re-packaged versions of Java: https://jdk.dev
All that alternative packages are free of charge but they have extended support from a number of big companies. All these companies funded separately, there's no common place for donations or something.
That's totally ok in the world of Free Software. Pick any source code you want, repackage, rebrand it, sell it as you wish and may the Force be with you. People do it all the time.
For example, if a person were to repackage someone else's open source project with a link that says, "Donate to support the development of this software" that's still fraud (assuming they keep the donations).
Back in days I paid for CDs with only open source software because internet was too slow. CDs were definitely priced for decent profit. The beauty of opensource is that we can do this legally.
taps finger on temple
Basically, if you include a donation link in your app without proving non-profit status you could be committing fraud, and Google could be held equally responsible to the crimes of the app being hosted. Google also has to report non-tax exempt profits made by any app/content they host in many locations, so only non-profit groups may link to a 3rd party payment system without violating legal statutes in some countries/states.
How is it fraud to ask for donations without being a non-profit?
> Google also has to report non-tax exempt profits made by any app/content they host in many locations,
I am not familiar with google's payment model, but is there no way to charge users except through Google for google play apps?
It's higher risk for sure. Non-501c3 donations are the kind of high risk small peanuts you can imagine a behemoth like Google wanting to get away from.
Likely this is Google avoiding additional regulatory complications/KYC. It's cumbersome to prove you're not enabling money laundering or funding terrorist organizations if you're an arbitrary money sink.
But I'd expect better than Google, a business with an astounding $836B market cap. They could just buy a company that primarily handles this sort of money flow (e.g. Streamlabs)
If an affiliated party is breaking regulations, you can often get in trouble by continuing to be associated with them once you're aware, and ignorance isn't a valid defense.
[1] https://help.github.com/en/articles/displaying-a-sponsor-but...
FWIW I agree with you, Google isn't prioritizing solving this properly and is opting to take the easy way out
We're talking about a hyperlink in the app. Linking to wireguard.com would be fine.
How about if wireguard.com had a big donate button?
How about if wireguard.com has 'Donate' in bold?
I know you're not the person actually signing off on this - but to the one that is - fuck you. In bold.
No-one is getting sued because of one step being removed in a hyperlink chain to a donate button. If they are it's getting thrown out instantaneously.
Characterising a link to a donate button as being in _any way_ related to aiding money laundering is ridiculous.
Cease this insanity.
Parties like Google and Apple are well aware of the potential consequences, and thus are similarly inflexible and disinterested in being nice to a fairly small group of use-cases that exposes them to an outsized amount of risk.
It's really, deeply unfortunate. It's incredibly painful for everyone who has to deal with this bureaucratic bullshit. Unfortunately, it being bullshit doesn't make it less real or less reasonable.
It is not a real concern for Google to have a hyperlink https://wireguard.com/donations buried inside an app distributed on the Google Play Store.
I don't believe your concern is legitimate. It's arse covering gone mad, sorry.
Rhetorical:
You can email me, my email is in my bio, and I will respond with a way that you can send me money. If dang reads this post and does not take it down, does that put HN at risk of AML action for potentially 'aiding the money flow'?
edit: actually, you can click through enough links on my bio and get directly to donation pages. now we're really fucked, right? who's gonna turn off the lights?
This website is different -- not just free -- there is no financial partnership in play (as far as I'm aware). But rules still apply. If you put a link in your profile taking donations for Syria, the operators of this site are obligated to comply with OFAC sanctions and I'd expect your profile to change pretty quickly.
In this case, I'm guessing Google is opting to choose the path of least resistance, and rather than perform due diligence and KYC for apps which solicit donations, they've chosen to just... not do that.
They've chosen to pre-emptively cover their arse against a risk less likely than an asteroid hitting Earth by just nuking the apps.
There's another thread on HN about this right now - I don't know how these people can like, exist, in this world, with every one of the hairs on their head individually combed into a perfect slick. Can you even eat breakfast without worrying about some tail risk?
Too much HN for today, methinks. I'm so glad that the normal people I interact with in the world aren't this wanky (I don't mean you or other posters here, but the bureautwats that actually implement this stuff)
You're right, and the Google is wrong.
Sure, maybe the argument can be made, but come on. We all know this is so that Google can get their nice 30% cut, and cut off any alternate funding sources for Android apps. Otherwise, shady developers will just require a "donation" instead of a purchase. That is behavior that Google would be reasonable to police, but to claim that action from financial regulators is what's causing this is just silly.
It's just your bog standard wanky corporate dishonesty. Nothing new under the sun.
It may also be worth considering that actions can, at some times and in some situations, be taken by human beings for multiple reasons with multiple independent motivations. All of which are real, genuine reasons.
Too many adverse effects you say? Sorry, that's just the way it is, no use complaining.
Since those are examples I hope this also covers tax-exempt charities in other jurisdictions.
I switched to the german site and it still only refers to american laws.
"Examples: Donation solicitations from parties without a valid 501(c)(3) tax exempt status clearly displayed to the public; solicitations from parties without valid proof of exempt tax status or proof of registration with the relevant country's regulatory bodies and authorities; and political organizations that have registered with the Federal Election Commission (FEC)."
Are the developers using google payments for other things/apps? Because in the context of these specific apps they are not using Google payments, so the policy wouldn't appear to be applicable.
"Any individual or business processing transactions with Google payments must adhere to these policies."
These apps weren't using Google payments, and it is suspected that they were taken down for not using Google's payment systems (despite not being allowed to).
As far as I can tell (though I am no expert) it would be very difficult or impossible for an open source project to qualify for 501(c)(3) tax exemption. And even if it was, the cost in both time and money to obtain such a status would not be worth it for small open source projects.
Ok, I had to stop there. They have no claim to this as long as they distribute within the store. It would be nice if google allowed this, but there is no obligation. App Stores are monopolies and should be regulated to allow open distribution.
Aside from that it should highlight problems with app stores as a model for software distriubtion in general, although I don't have much hope that this will happen in the immediate future.
That there even exists such a rule is ridiculous and unacceptable in my opinion.
Several other open source apps are still missing from Google Play, including andOTP.
While WireGuard was bought back online, version 0.0.20191013 was briefly made available (with a donation link) before it got updated to version 0.0.20191016. Again, the current version of WireGuard does not contain a donation link.
This is the original version of the post, which has become inaccurate minutes after it was posted:
> WireGuard has been reinstated [1], and the donation link is in the app menu (version 0.0.20191013).
> Google has reversed its decision to remove an app that contains a link to a donation page, likely because of public scrutiny.
> I'm hopeful that people will continue to seek answers for why Google has begun to remove these open source apps, there are several of them mentioned in this thread alone. Please don't allow this to go unnoticed, the future of a bunch of less popular open source projects may depend on how this issue is perceived by the public, and addressed by Google.
> [1] https://play.google.com/store/apps/details?id=com.wireguard....
Are we sure that this is a decision reversal, as opposed to just reinstating one (or a few) apps?
I haven't received any further emails from Google (yet?), so I'm still uncertain as to whether I have any sort of green light to republish a version with the link.
(slightly expanded version at https://news.ycombinator.com/item?id=20829422)
Too often they refuse to listen when there isn't an angry mob at the door.
How google tries to claim any sort of support for open source is beyond me. What open source app doesn't need a donation link? Those approved and funded by google don't, okay. But other than that?
These “donations” are more like tips, which are treated as taxable income.
I don’t see the problem here. The outrage in this thread seems more about people wanting a different set of rules for OSS and possibly avoiding income tax than anything else. If there are a different set of rules for OSS, then that just makes it easier to abuse the platform. Google’s policy seems fair to me.
But neither seems to have Google ! While the global license/patronage debates are already a decade old, and we have seen new companies get started and even established in this sector (Patreon). For instance this "donations" page only seems to cover non-profits ? https://www.google.com/nonprofits/offerings/google-donation-...
Do I have that option?
Wait. I suddenly understand something I've seen previously...
There is a workaround! You simply upload two versions of the app, the free edition and the supporter edition. The support's edition is a paid app. You can ask the users who want to support you to install the paid app in your free app. The program itself is still 100% free and open source, there is no functionality restrictions in the free app, the donation notice can be turned off - just as a way to encourage donations. And it's nothing against the rules of the store.
They're thinking that they're a monopoly and can do whatever the hell they want without needing to justify themselves?
To be fair they didn't. You can accept donations if you're an actual charity (like Wikipedia is). The line they drew isn't perfectly fair, no, but it's not a full ban hammer, either.
Now that I think of it, Uber has you put your credit card in. I'm not sure why that's allowed
Quote from policy [1]:
Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the method of payment, except for the following cases:
- Payment is solely for physical products
- Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
[1] https://play.google.com/about/monetization-ads/payments/
A donation doesn’t magically make everyone else work for free.
Yes, they charge 1/10 of what Google charges. The 30% has nothing to do with how much it cost them to run the service, so let's not pretend that they _have_ to charge them.
(I'm not saying they should offer cheap/free donations, I just don't think it's fair to talk about how much it costs them to run the service given that that's clearly not the driving factor)
I just wish F-Droid had a better design but I guess that's just the nature of OSS. It always looked a bit shady and out-of-date, which probably hurts it's popularity.
https://news.ycombinator.com/item?id=21269542
This is ridiculous. May as well only publish open source apps on F-Droid and similar.
> Here are some examples of products not currently supported by Google Play In-app Billing:
> One time-payments, including peer-to-peer payments, online auctions, and donations.
But anyway, now what? Let's say things return to normal, but we still want to put the silly link in the app. Our appeal was rejected. We could send letters, I suppose. Perhaps this article on HN will get the attention of the right people? We could appeal the appeal, maybe. And then appeal the appeal for the appeal. At what point does this become a waste of energy that could be spent coding and improving the app in other ways? It's hard to know where to draw the line and which battles are worth fighting. I'm happy to hear folks' opinions on the matter.
I certainly agree, though, that it is unfortunate.
I would resubmit the app with the donation link and continue to document and share what happened. Please do not allow them to set a precedent with a popular project like WireGuard.
It's important to share every detail of the issue, the messages you received, your replies, and the policy links you were given about the alleged policy violations.
Let me say that I think you're morally right, but it is probably not a reasonable choice of actions for the author and the users of the app.
I'm sure you believe that.
Do you work at Google in a position to supervise app reviews? Because if you do, then you can help straighten this out.
If you don't, then it is hopeless. Technically, Google has the right to drop any app for any reason whether it is fair or not (so suing them or something isn't an option). OP already followed the ONLY channel that Google provides (an "appeal" handled, I presume, by a bot that generally issues quick, automated rejections. Sure, I wish Google had a better policy, with some sort of genuine appeal policy which included genuine human review, followed a consistent policy, and most likely had a public record of decisions... but they don't.
You can look at r/videos and see how many examples there are, the link in [1] provides quite a few...
So hey, go get people to repost across social media, maybe get a nice trendy hashtag going like #freewireguard and maybe their "AI" (or PR department) might actually do something useful.
Because to me, I've noticed more and more companies only reverse decisions or backpeddle once there's enough shit flying at them (See Blizzard recently, for example).
[1]: https://old.reddit.com/r/videos/search?q=flair%3AYouTube%2BD...
> Donations to 527 designated tax exempt organizations are also permitted.
So if Wireguard becomes a proper tax exempt organisation it would be ok.
If you want donations but aren't tax exempt there is basically no way to do it. However you could easily work around it by offering something trivial like a badge (games can use IAP to purchase trivial things like hats). The downside is that Google take their 30% cut.
[0] https://developer.android.com/google/play/billing/billing_ov...
And then Google get 30% of it.
Yeah...
AKA follow the money.
just to stir the pot and see what happens.
A donation is not a purchase.
I've never donated to WireGuard before, and I didn't think about donation (I installed WireGuard from my package manager and didn't realize a donation link exists), until now.
Just donated 25 USD.
Thanks Jason. No thanks, Google.
Whoever came up with this policy and started enforcing it at Google is completely tone-deaf, needs to be fired and publicly called out so we can set an example as a community that this sort of behavior will not be tolerated.
We have contacted engineering leadership at Google and they are in the process of figuring out who it is internally.
We just need processes to learn and avoid doing mistakes twice, and shaming is a poor way to do it.
If I risked being ashamed when making decisions, I would probably avoid decisions altogether. This would be awful. The discussed decision is not even out of law.
What we can do though, is to tell people we know and love about F-Droid and suggest them to only fall back to the Play Store if they don't find what they want, and that they should be aware that by doing so, they enter the jungle and that this jungle follows Google's arbitrary rules, some of which are not in their own interests.
No one needs them for discovering new software. You go to the app store to get a specific piece of software you already know about and whose reputation you’ve already verified.
No one needs them for code signing. If you want the real firefox.apk you can download it from https://firefox.com/ and notice a lack of SSL alarms going off. What’s the code signing for — to let me know that HTTPS works?!
All I really want is an OS facility that only executes code that has been installed explicitly by me, and always in a sandbox. That’ll stop that dodgy email from executing r00t.sh via an exploit in my mail client.
App stores and code signing popups are proxies for that kind of OS facility, but I’d rather it was just part of the OS explicitly.
App stores leave me with all sorts of unwanted properties, namely Google / Apple throwing their unwanted opinion around. Search for Instagram in the iOS App Store: the top UI element is “InstaMap”, thanks Apple!
The website from which you, the customer, download the software often is built and managed under less controlled and more vulnerable circumstances, often with third party involvement. Any bad actor in a long chain of internal caretakers and potentially external hackers can replace the to-be-downloaded artifact HTTPS with malicious junk. Code-signing mitigates this.
If someone has changed the files on the distribution servers. A Hacker News reader will have no problem recognizing it and stop installing, another one will compare the signature and keep it as evidence.
Of course, the overwhelmingly majority cannot recognize it though.
But only the readers of Hacker News can recognize it. I think it's one of the most powerful argument for a walled garden. Not that I support it, but I acknowledge it's still a powerful argument.
"Isn't just clicking _next_ until the app starts?"
There's also people that don't know that they need "Firefox", they just want a browser. Or a tool to print envelopes or crop an image. So they search in the app store and they know it'll probably be okay.
If you search for this online you'd get a bunch of SEO spam sites, shady tools among other things. At least due to the developer fee and reviews there's at least some barrier of entry (Also if it's not perfect).
> App stores leave me with all sorts of unwanted properties, namely Google / Apple throwing their unwanted opinion around. Search for Instagram in the iOS App Store: the top UI element is “InstaMap”, thanks Apple!
Apple's search is notoriously bad and the perfect case to apply Hanlon's razor.
I trust it enough to believe it won't start crypto mining in the background or connect to random servers and sending the content of my computer somewhere. For the average user it's probably the better option than downloading the top Google result and just executing it.
The current migration towards more sandboxing also helps. For instance, Android has restrictions on how much an application can do in the background without showing up as a persistent notification, and xdg-app's sandboxing can restrict how much of the content of your computer an application can access without using a file open dialog.
Sure, they wont do crypto mining, but that's because it would drain your battery quickly, and people would notice and uninstall.
Isn't the whole point of sandboxing and the permission systems exactly preventing phonebook and location data misuse? Especially location tracking prevention was a pretty big part of the iOS 13 announcements.
I live in a city now and no longer have my own tools/garage, but I know enough about my car to know the shop down the street was trying to screw me when they did a bait in switch, wanting to charge $950 for an alternator repair (and claimed my battery; less than a year old was bad). I called around, towed it to another shop and paid less than half of that...and the battery was perfectly fine.
I should have checked the reviews on the first shop because they were some pretty bad ones. Now I know better, but there are a ton of people who just accept it, maybe because they're car was already towed there and they simply don't know any better.
Because that is the majority of the users and because it's hard to find reliable information on the internet even if you're willing to do the research into this sort of thing. I'm certain there are plenty of things that you are probably not knowledgable about and don't put the time to learn about as well.
Bad plan, both on iOS and Android. You should not be installing random apps unless you vet them first.
People keep going back to the "users are stupid" argument, but (particularly on Android) the app store does not protect users. Installing random apps or trusting the first app that shows up is a terrible thing to teach dumb users to do.
If you want to protect users to the point where they don't need to think at all, you need to be way more locked down than iOS/Android currently are -- you need Nintendo Switch levels of moderation, vetting, and sandboxing. The problem is that very few people (dumb users included) want that level of vetting for a smartphone.
Androids app sandbox is pretty leaky. It has a massive surface area, and the chances of finding exploits to get out of it to find root are high. Also, even from within the sandbox, there are lots of evil things you can do (for example, start on boot, and go fullscreen and use all the ram so the back and home button SystemUI process gets killed and your app is unkillable.).
The 'badness' of the android app model is a big chunk of the reason Google wants to be gatekeeper - otherwise android apps could just load and unload like webpages do. That and profit.
The most popular third party rooting services don't seem to support past Android 8.
Clearly it isn't easy to root these things.
But we have fdroid and the GNU/Linux ecosystem is going to eat android’s lunch anyway.
I so badly wish I could agree with you :)
Sadly, observing the non-tech folks around me, some of which don't even know what an app is, and some of which think the only apps they'll ever use on their phone is the ones it came loaded with ... it's not true.
What is needed is an android app. store that is decentralized / distributed, where the "trust" of an app is a consensus-based score and that has the popularity of whatsapp.
As mentioned in the announcement, you can switch over to F-Droid (for the time being) to get the latest version: https://f-droid.org/en/packages/com.wireguard.android.
Why do you have that caveat ? You can use f-droid forever.
I understand that it's probably Google's fault for not providing APIs/permissions but it's still terrible UX. I only use F-Droid when an app isn't available on the Play Store.
As evidence of this, Google does allow donations if the publisher is a 501(c)(3) (see https://support.google.com/faqs/answer/75724?hl=en).
There has to be a better way to handle these sorts of things.
Were they even notified beforehand?
If this is really an attempt at preventing garbage apps from spamming or tricking users, this is both overly broad (many false positives) and badly targeted (many false negatives). Why is it that iOS doesn't have this policy, and has significantly fewer garbage apps?
Maybe if Google were to allow third party app stores, folks could choose the one that fits their ability to evaluate the sophistication of apps themselves. For example, some folks might want to pay for extra security checks on the apps they use, while others want to install anything and everything under the sun.
Oh right, it's because Google wants me to have some kind of "pro" app that is effectively a license, that they can get their 30% cut of.
They don't give a damn about fraud via this method. They want their money.
I'm pretty sure they just want their cut.
All in all, that whole "break-up" argument is just political white-knighting by wanna-be elites (ie. Warren & co).
As for continuing being GAFA advocate (while still thinking they should be compelled to open up "Stores" to competition), vertical integration provides enough economy of scale to achieve ever greater complex things. Also, 1) you can't just "break-up" any GAFA. They're just gonna move out of State and be welcomed somewhere else, and 2) what you're asking put Government in a very awkward position as setting up both enough regulations to block new players, but also blocking player to achieve a certain size. Finally, this argument is getting awfully close to the "broken window" fallacy. You can't just "create competition" out of thin air.
Amazon/Facebook is a different problem. Amazon is colliding with the old retail chain and weakening their power in DC (Amazon is not doing anything more that has been done in brick and mortar stores ~forever). As for Facebook, it is threatening Governments themselves (privacy is just just a convenient red-herring).
A small amount relative to the value that you're giving to the world, but hopefully a few pints won't go amiss.
Fuck gatekeepers.
I'd love to use the F-Droid version but it's not up-to-date, and isn't published by Jason, so it's not signed by him either.
Publishing it on the website with a built in update-check might be one solution I'd be happy with, it'd only need a text file hosted on the website and a check, perhaps each time WG is activated to see if there is an update. Modern Android versions can be toggled to allow installing software from external sources, so the app could "install itself".
Cheers
I am curious how this ends up working out. Google takes a cut of the donations now... but the process of buying is probably easier. So maybe it will increase donation revenue, and make it easier to support free software.
(Taking a step back; it is pretty weird to have apps opening links to web pages that take your credit card number. The app store operators are right to view that with suspicion because I'm sure that for every legitimate open source project, there are a million phishing scams.)
Google could make a positive impact by introducing new features that help users seamlessly fund their favourite open source apps, right from their Google accounts. GitHub has recently introduced a similar initiative called GitHub Sponsors [1].
> Taking a step back; it is pretty weird to have apps opening links to web pages that take your credit card number.
There is nothing weird about accepting payments outside of Google Play, and it is allowed if the payment does not result in buying a product that is used within the app. Buying a movie ticket, or operating an online store with a third-party payment processor are perfectly fine use cases which are allowed on Google Play.
Annoying how hard it is to be independent of FAANG control.
Do they ban all donation verbiage or just IAPs that do nothing?
Until some morning when suddenly, they're not!
The additional feature can just be text that says thanks for the money, feel free to give us more money in the future.
Edit: I'm referring to https://opensource.org/osd
Edit2: Having read round some more, it seems you possibly could sell a different version, of course you would have to offer the source code which others would be free to give away, (this is for the gpl). I don't know if the discrimination clause of the Open Source Definition would come into play though.
For instance, D-Sub is available for free on F-Droid but costs something like ~$4 on Google Play.
AndOTP is available on F-Droid, not sure about Wireguard but I'd assume so.
This is great solution to sustain the app developmant and spread the word about F-Droid!
at some point someone gonna pay for the datacenters, the wires and all these stuff needed for software distribution.
Try running your own site on your own servers and paying for the data traffic and then do the math.
30% is ok
Say app has 10MiB, 100,000 downloads is ~1TiB, 1 have a 1GiB/20GiB VPS with that monthly bandwidth which I pay $1/month.
So distributing 100,000 copies costs $1.
I'll give Google $1 for distribution of 100000 copies of my app. Fair?
Yeah, I'll give Google a bit more for payment processing, perhaps. But actual distribution costs nothing really, for most apps.
I remember that being a problem in the app store for windows phones. Lots of fake apps that used the VLC name and logo, for example.
not every developer is willing to learn and spend time configuring & managing a server. that's not the same skill set.
First we're talking about the free app for a good cause, so you're already providing an app for free, so you've assumed some sacrifice for others for whatever reason, and setting up a website for it may be comparatively negligible part of the whole cost to you in terms of time.
In my case I would have already had an infrastructure and knowledge how to host things, so it might take a few minutes to put some new files up on a machine used for other projects. Additional costs being pretty much 0.
And there may be benefits (even if I didn't have the knowledge and infra) like learning something new, or now having an infrastructure and knowledge that helps you save expenses or time in the future. So that would offset the costs. You can't just look at costs alone.
Google should be thankful in the first place that developers are making apps on their ecosystem (doubly so for open source apps), because without them, Android and the Google Play Store itself isn't worth much. It's their part of the deal to stay relevant.
> Open source developers shouldn't be forced to lock away additional functionality in their apps
I don't think functionality was what was suggested. Literally cosmetics. A nice banner that says thanks for supporting the project would likely be sufficient.
Edit: Although I agree it shouldn't be required. As a workaround it doesn't seem too bad though.
Doesn't Google take a whopping 30% cut of the purchase price for both in-app purchases or direct purchase of the app itself? That's a pretty big bite out of the donation.
Unless I’m mistaken, this is only possible if you’re donating to a registered charity. Many view open source as more noble, but OSS developers don’t magically get a different rule book :)
(I don’t disagree with your perspective here, but the prevailing sentiment in this thread seems to be that OSS developers should get a different rule book.)
This is not tax advice; consult a tax professional for your own personal situation.
I contribute to projects that are committed to never locking away features behind licenses or in-app purchases, because most open-source projects in that space eventually went down that route.
My immediate thought at reading the title "So sell a supporter animation that plays in an about menu".
At the bottom of an “About” page:
Paypal: email-adress
Venmo: open-source-proj-maker
BTC/ETH: <address>
If someone is not a 501(c)3 org and just a solo person, why do donations have to go through a particular website link?
It seems like the same thing (getting money) can be accomplished without needing to use links from an app.
It's possible to make open source applications and still ask for payment on Google Play, either as the asking price, subscription or by adding in-app payments for donations. This is the right way to do it, and will probably also have a much better return since the payment workflow is much easier.
https://9to5mac.com/2019/09/06/apple-extends-deadline-for-ne...
Arguing that this is somehow related to software quality, safety or whatever is pure BS> There is simply no other explanation for this than "it will make us money and we can get away with it."
Basically Google and Apple both know that people will make more money by listing in their stores and taking a 30% cut than not listing at all.
As soon as you get a certain threeshold you become a monopoly, which essentialy means you controll who does business in that sector.
It should never be allowed to be a distributor as well as the owner of a marketplace.
It's the same problem with amazon marketplace and other similar things.
EDIT: Formatting
Just because Google Play is a monopoly, it doesn't mean that it's illegal or should be fined. Especially since there are other options, like amazon's app store, or manual installation of apps.
Especially compared to iOS, Android is a paradise of freedom.
This is an old claim by now, but these platforms matter a lot today, and since we only have two of them, and they are not in direct competition (users cannot switch at will) they really should be treated as the monopoly infrastructure that they are. What that means concretely is subject to negotiation within society. In my opinion blackmailing the devs of an application that is essentially written and maintained as a service to the public, for free, by volunteers, is a shit move to say the least.
I don’t know what you think the verb ‘to blackmail’ means, but nobody has been blackmailed or anything like it in this situation.
And they are in the process in doing so (partly by closing the platform through read-only system partition and expecting the app developer to sign the app through Apple means) with MacOS.
The platform is not yet closed, as the system partition can still be mounted in read-write mode and notarization can be bypassed for now. But their are clearly in the process to make these changes permanent in near future. Reason why they introduced them in Catalina.
Google could make the same choice but doesn't for some reason.
Might be convenient and great for Googles revenue, but it's the wrong way to do it if your priorities are to reduce the projects platform-dependence and to support the project with your full donation.
Usually, once I decide to contribute money to a project I want them to be as free as possible and I want them to get as much of that money as possible. Independent from the specific app store I pulled it from.
I think it's wrong that the Google Play Store treats donations like purchases.
That's also how I was thinking about doing "donationware" on a mobile app store.
Side note: They are also available on F-Droid.
[0] https://play.google.com/store/apps/collection/cluster?clp=ig...
[1] https://play.google.com/store/apps/details?id=com.simplemobi...
Has more than 100K downloads. i.e made at least 100K after Google cut.
https://play.google.com/about/spam-min-functionality/min-fun...
Thank heavens there's an alternate way of distributing apps on Android. Say what you want about Android vs. iOS, but at least there's an alternative if you as a consumer have a beef with Google Play.
Something like that already exists. I had to use one of these directories once to install an older release of Signal on a relative's phone (newer releases of Signal don't work on older phones, older releases of Signal aren't compatible with the current Signal server, but there's a single version in the middle which both works on older phones and is compatible with the current Signal server; unfortunately, that phone hadn't yet updated to that release before a newer release went out).
That's what we do in every other domains, what's the difference here ?
Same reasoning for forcing people to have their cars serviced by mechanics and not do their own maintenance in their backyards. Otherwise we'd have people driving cars without pipes and DIY break pads. I'd much rather have that enforced by megacorps/govt than by an infinite amount of businesses/individuals trying to game the system.
For most people a smartphone is an entertainment device, a tool at best, they don't give a single fuck about the underlying tech and they should not. Feel free to root your phone and install whatever you want, you can't ask people to become tech literate, it's your hobby/job, not their. Our job is to provide them safe tools, not teach them about tech. Look at your own life, chances are you don't even have surface knowledge of 99% of the things you use daily, and that's perfectly fine, nobody expects you to be a furniture designer, building safety inspector and car mechanic.
As a service tech if I fill a car with tomato sauce instead of oil I pay for the car.
As a programmer I can sell all the users data, leak it to hacks, then laugh all the way to the bank.
As a furniture salesman I can requirements on materials transparency. If I break those I'm liable.
As a programmer I can totally change the rules of my application at any time.
If society wants to trust tech it will have to hold it's creators responsible.
The back door encryption thing is a fun example of this.
For the record, I do my own break pads. And have done the master cylinder (thing that powers the breaks) on my cars a couple of times. Not just without formal training. Without any training except what I could quickly Google.
Not sure why you would assume that prohibiting people from working on their cars would increase the level of maintenance.
> And what does having to follow the law have to do with any of this
Google is free to handle its playstore as it please as long as it follow the law, I doubt google will pull a genocide anytime soon. Setting boundaries/rules doesn't make you an authoritarian regime. If you want to pull the "this reminds me of the darkest hours of our history" card you better find something more important than an app removal from a mobile phone app store if you want to be taken seriously. But I guess it's fashionable these days to compare everything to nazi germany/fascism/_insert_bad_people_, no matter how convoluted the comparison is.
Can you quote where I said anything about a "regime"?
> Google is free to handle its playstore as it please as long as it follow the law,
Which is true, but completely besides the point? I am free to call you a clueless asshole. But if the discussion is about how to have a constructive dialog, me pointing out that I am free to call you a clueless asshole contributes exactly nothing to the conversation and at best shows that I have no clue what the discussion is about.
> I doubt google will pull a genocide anytime soon.
Your point being? Authoritarianism is good when it's not a genocide, because ... ?
> Setting boundaries/rules doesn't make you an authoritarian regime.
Again: Where did you pull that "regime" from? And also, no, "setting boundaries/rules" does not make for authoritarianism, that is correct. Why did you assume that I wasn't aware of that?
> If you want to pull the "this reminds me of the darkest hours of our history" card you better find something more important than an app removal from a mobile phone app store if you want to be taken seriously.
Why? And no, simply pointing out that one thing is worse than the other is not a relevant argument, that's simply straw manning, because noone claimed that one was as bad as the other.
But, you can't really provide them safe tools without fixing some of the behavioral components, can you.
"Don't try to lick the sharp parts, especially when running the machine" is an implicit and important (albeit obscure) part of the safety to operating, let's say, a band saw. Unfortunately, the intellectual bar seems to be noticeably higher for "When a very urgent and heavily accented Microsoft Support representative calls you out of the blue, don't type into your shiny techno-thingy what they tell you to".
I'm generally all for sane defaults and constructing to make spontaneous use possible too, but a lot of the time there is ultimately no other protection against dangerously wrong use of tools than not using the tools dangerously wrongly. Too bad that's a tall order for very complicated machines that can do vastly different things depending on configuration.
I know people are going to quote Heinlein here, but civilisation exists so that not everybody has to be a specialist in everything.
We need to drop the attitude that technology is a new scary thing it's not. Technology is an extension of our selves we have been using it for thousands of years to expand our ability.
Pen and paper was the old technology if you don't know how to use it you are illiterate, if you don't know how to use the new technology you are still just illiterate.
The baby boomer attitude of "I can't be arsed to improve as a person so every one else has to dumb it down for me" is unacceptable.
Do you apply that to yourself out of tech ? Are you literate in art, philosophy, astrology, history, chemistry, medicine, &c. (more than surface knowledge) ? Where do you draw the line ? Is using google maps without knowing how the GPS system works in details an issue ? What about cooking ? Do you know which chemical reactions create tastes ? Are you buying food from supermarkets, why don't you hunt and grow your own ?
> The baby boomer attitude
As if millennials+ were better. Using a pc/smartphone daily doesn't mean you're tech literate, it's a prime example of familiarity != knowledge.
And do note that there was a point in history when even basic literacy belonged to a small few who argued in exactly the same manner than tech people do today, i.e., that most people will never be able to understand basic science and maths, and we cannot hope for any better than to be benevolent dictators. Later history proved the hollowness of those claims. Today the majority in most of the developed and some of the developing countries are basically literate and what their grandparents couldn't imagine doing, they do effortlessly today. I don't see a single reason why computer sector should be any different. I'm not talking about a deep understanding of computers, just basic literacy that would obviate the excuse for tight, walled gardens and locked down devices.
To be fair, I'm less confident poking around behind the surface because what used to be relatively straight forward has become --for various reasons, few of which are legitimate in my eyes-- absurdly complicated.
I disagree on this. I have a friend who has "basic computer literacy" as in knows how to use MS Excel, KeePass, etc. And yet, she inadvertently got a virus on her laptop. It was puzzling how she could have gotten it. She doesn't visit the usual suspects of porn/gaming/gambling/etc websites. Just normal stuff like CNN, WSJ, etc. The only reason we found out about it was her email account got locked out by the ISP. Apparently, the malware found her MS Outlook email account and used a hidden background service to send a bunch of spam messages using her email profile. Understandably, the ISP monitors SMTP traffic sent from residential addresses and when it hits an unusual threshold, they lock out the account. To clean up the malware, I reformatted her laptop and got the email reset with a new password.
On the other hand, with her Apple iPhone and the locked-down walled garden, I really don't have to worry about malware to the same degree. Yes, the Apple app review process is not infallible and theoretically, she could get infected by downloading a fake bank app that steals all her money. However, the possibilities for that nightmare scenario are drastically reduced in the closed Apple ecosystem.
Even programmers, who we'd classify has uber-computer-literate compared to the general population can unwittingly get bit by malware:
Javascript programmers vulnerable to NPM package repository malware: https://www.theregister.co.uk/2018/07/12/npm_eslint/
Microsoft's uber geek expert Mark Russinovich got infected by Sony's rootkit: https://blogs.technet.microsoft.com/markrussinovich/2005/10/...
What's the solution for those programmers? Educate them on how to use computers? But they're already educated.
Yes, I get the hacker ethos of not having locked-down devices but we also overestimate the ability for the general population to maintain safe computing devices. Heck, I'm a techie that programs in Xcode and I'm not confident I'm really literate on all the vulnerabilities of the iPhone. Thus, it seems unreasonable I would expect non-programmers to "just be educated" to make the App Store's curation unnecessary.
You can do whatever you want on a platform like Windows because they make their money off of selling support for their platform, and selling their own products for it.
Google and Apple do not make money selling support for their platform, and only Apple really focuses on selling products for it. But they both make money by tightly controlling their platforms, in order to to squeeze money from developers, [in the case of Google] from manufacturers, from carriers, from users' payments, and from all the data they collect about it all. They don't have to care about the customer at all, and they can just focus on engineering. It's the programmer's dream.
Their business model is a walled garden, and they pick the fruits of that garden. In the case of Google, they run the Android platform so they have a way to still make ad money if Apple denied them access to that platform. In the case of Apple, they run the Apple platform so they can make money from expensive consumer devices, and also use it to control more of the services/products we use.
So, it really doesn't have anything to do with literacy. Even if everyone were a genius, their choice is still A) don't use a smartphone, or B) use a walled-garden smartphone.
I have worked in this industry for long enough to know that even assuming a minimum of knowledge at all is a bad idea. You can fight this fight as you want, but this comment has nothing in it to convince be otherwise.
Because it's human nature to only care about details that you believe you need to know in order to manage some part of your life.
If you don't see a clear and immediate value in learning something, you won't. No matter what anyone else says or does to try and convince you, you won't.
Then you get burned by something you didn't know, and there's a 50/50 chance you'll learn about it then, and only if you're convinced that it's something YOU have to do, that can't be managed for you.
And most people resent having to learn that much.
I no longer try to convince anyone of anything tech related. And rarely answer much when I am asked, unless I can see that the person is truly interested, not just curious about some buzzword.
Meanwhile in 2019, most people still find "nothing to hide" attitude perfectly reasonable.
For the normal, everyday non-tech user, they see that all their friends use these apps and nothing has ever happened to them. The FBI didn't come knocking, they weren't fired from their jobs or anything like that.
From their point of view, why should they care about repositories, digital signatures etc., when they just want to use Instagram, Snapchat, Whatsapp and so on for some after-work (or during-work) fun / brain-swithoff. They just post some silly pictures or watch some Youtuber videos.
All these concerns about privacy just don't reach the everyday reality and real-life concerns of people and is in effect an ideological thing, similar to rejecting proprietary software on the desktop due to moral and political beliefs.
> They have to face the consequences, that's how it works
The consequences (app creators changing their practices and policies) will be spread over everyone, not on individual users. As long as their friends and society keeps using it, most people will as well. If it slowly dies out, people will use whatever is new. Most people are not that much attached to using these apps, just use them out of boredom or to interact with others. They'd easily move on if that's how things evolve.
Except the tech is already there, and you use it with or without understanding. You use a credit card, electricity, Internet and other communications, some kind of computing device, your entire life depends on it. And IT shapes your life way more than any other tech, so it probably makes sense to get a grasp on the general concepts at least. No need to become an IT expert, similarly to how there's no need to become a Shakespeare to be literate. And yes, being tech illiterate can fuck you up very visibly and personally, for example by losing money from a stolen credit card.
However only a minority of them knows how cars work under the hood. Most people understand the pedals and the steering wheel and that's it.
Same in tech. People understand there are screens, there are buttons you can click, text input fields you can type things in with the keyboard, on/off switch, sleep/standby, etc. All the things needed to operate it.
> for example by losing money from a stolen credit card.
I'm in Europe and I don't know anybody who had this happen to them, nor is identity theft a thing here. And this is mostly about phishing and social engineering anyway, not about understanding the tech background of package managers and digital signatures.
I have had the exact same experience. I've long given up trying to explain anything to normies, including anything related to privacy.
I really pains me to say this, but the bleating masses are the bleating masses, and getting them to internalize anything typically takes a generation.
And I'm happy with these stores and couldn't care less about your cyberpunk libertarianism.
This isn't 1984. The moment they seriously misbehave, the law will come at them, and customers will leave. Therefore they don't.
You're indulging in fantasies because you would like to believe that what interests you is all-important. That's normal: all epidemiologists belief we should talk about the flu a lot more.
But it's just a tiny slice of what matters. So don't disparage people as stupid just because they spend their energy and time with more important things than recompiling kernels.
1. https://chatsecure.org/blog/sustainable-open-source-starts-w...
And none of this is surprising, merely inconsistently applied logic. I fully understand what is happening here, clarifying statements will not help.
Says you, but obviously that's not how most people approach matters like this. Most people can reasonably be assumed to think that differences in degree, particularly an order of magnitude apart, are very relevant. At best you're being a pedantic pain in the ass, hassling people for not explicitly stating that a difference in degree is being considered, when such considerations should be reasonably assumed even when not explicitly stated.
Nothing is reasonable about what you're writing, not one thing. At best you're being absurdly pedantic yourself, and hiding behind a throwaway no less. At worst you're trolling. I'm guessing it's the latter, so stop trolling.
C'mon people, is Google we talk about, you know, those who bow to might $$$ only. You should've made a donation link INSIDE google, so they can charge their 30% before you get the money, that's how you keep your app in their store </sarcasm>.
The Android app is basically a web-view pointing to one of the many instances of the social network https://nl.movim.eu/?login.
Regarding the time (and also money) spent to publish the APK on the Play Store and the hassle it is to discuss with the Google moderation team I didn't bothered putting it back.
But Android is Android because of these apps. Without them it would be like the Windows phone which was nice but didn't get enough apps on it and so it failed.
These companies depend on our apps as much as we depend on their app store for distribution.
Fuck apple for starting this walled garden and creating a parasitic relationship rather than a symbiotic relationship.
I don't understand.
> Fuck apple for starting this walled garden
IIRC apple started it and now all the big players are following suite.. including even Windows 10 which has it's own app store and similar cut.
So how do you decide what a fair cut is? Over the course of a month, given all your app and system usage, and all the pieces of software you've touched or relied on, what percent of the engineer hours required for that stuff to work came from Google/Apple vs coming from third party app makers? Is that how you decide the split? Because I have a feeling the time it took to build the 15 third party apps I might touch in a month don't come close to the level of effort required to have built the system and first party apps.
They have the a free version available on the Play Store here: https://play.google.com/store/apps/details?id=org.ppsspp.pps...
They also have a "Gold" version available: https://play.google.com/store/apps/details?id=org.ppsspp.pps...
These two apps are functionally identical, only difference is the logo and that the "Gold" version costs money.
So if you want to contribute some cash to this project, you just buy the "Gold" version. Other open-source projects could adopt this model too to evade this policy.
The price you pay however, is that a part of the money goes to Google. Which is obviously the reason why donation links are not allowed in the first place.
However, before doing this, we corresponded with Apple Developer Support / App Review Team and asked them about the Acceptable Business Models of their developer guidelines, which states:
(vii) Apps may enable individual users to give a monetary gift to another individual without using in-app purchase, provided that (a) the gift is a completely optional choice by the giver, and (b) 100% of the funds go to the receiver of the gift. However, a gift that is connected to or associated at any point in time with receiving digital content or services must use in-app purchase.
They scheduled a “specialist” to call us from Apple and discuss this. However when they called a few days later, they repeatedly declined to give a single example of how this paragraph would ever apply. We tried asking many different ways, but they kept saying we would need to submit the app with the business model to get it reviewed. They would not give a single example of an app they approved with this business model. I personally was on the phone and said that we simply wanted to be compliant and it was very expensive to build something just to be rejected, so we wanted guidance about their policies. But the representative did not know anything. I asked if anyone else on their team knew but they basically said no.
So Apple seems to have certain “platitudes” in their Guidelines which companies can’t take advantage of.
Has anyone here seen a single exception to the 30% cut? I know ApplePay may be used to purchase “real-life” items and where you can’t afford to pay 30% less to the vendor. But what about services, like booking time with a teacher? What about digital services such as hosting a videoconference? Apple takes a 30% but you have to pay Twilio. That means any web-based app would cost 30% less!
We were hoping that maybe there can be some link to buy things with Ethereum and since Apple doesn’t offer that facility we can try to argue that we need transactions to be non-reversible etc. Doesn’t Apple allow apps that allow the user to send and receive bitcoin payments to some address? BOOM!
Another thing we can do is micropayments, maybe, and tell users how they can purchase credits elsewhere. But that last part is against Apple’s rules, isn’t it?
Not to downplay the effort that F-Droid contributors (or any Android FOSS groups) make, but it's a very legitimate concern.
Would an attacker have an easier time infiltrating Google or a member of F-Droid the development community?
Are users of F-Droid higher value than users of Google Play, to warrant a direct attack? If one wants to pick off users who are fairly technically inclined, other developers, system administrators, etc...F-Droid is a pretty good place to start.
Regardless of the fact that builds are reproducible, F-Droid has infrastructure. How is that infra secured? How are the servers that store signing keys secured? How are the build servers accessed? How is the access secured?
Okay, so the builds are reproducible -- is someone maintaining a concurrent system that verifies reproducibility and provides notification of a collision when things don't match up with built and served binaries?
If an automated process blocks/bans/rejects something, then the message to the developer MUST say "Our automated scanner discovered..."
Any time something is blocked/banned/rejected, the message to the developer MUST explain exactly why. In the case of this article: "Your update was rejected due to a link to a third party payment system. This violates section N of our terms. The link we detected was <insert link here>."
There should be two kinds of appeal processes. Automated, and manual. You should be able to appeal or resubmit to the automated process as often as you need to.
The manual process should involve real time communication between the developer and an appeal agent. Via phone or chat. To prevent the system from being overloaded, only allow developers a few free appeals, then start charging a fee.
Developer accounts should only be fully banned after multiple manual appeals and the appeals agent determining that the developer is operating in bad faith. Automated processes should never be able to fully ban an account. It must involve a real person. Full bans also must include a detailed email to the developer explaining exactly why they have been banned.
The biggest, and most important, change these companies really need to make is including exactly WHY something happened. No more of these general "you violated our TOS" without any explanation of how the TOS was violated messages.
Signing up as developer, paying the fee and building the app yourself is probably the better option. Even if you have to rebuild it every xx days.
> Testut imagines Apple could disable the ability to sync over Wi-Fi, but that would just mean plugging in your phone once a week to continue using AltStore
How about limit the number of disable WiFi syncs and force you to plug in once every 8 hours?
Well guess what ... the android team at google and the entire android ecosystem is the brainchild of Andy Rubin, who has recently been outed publicly as a total asshole (and who everyone at Google knew was a total asshole since pretty much the start of Android).
All the things wrong with Android, including the iron-fisted management of what can and cannot run on the platform ("I know, I'm squeezing your balls til you pass out, but don't worry, it's for your own protection") can easily be traced to him.
Perhaps the right thing to do is for Google to offer a discounted cut to legit open source apps, from the usual 30% to a lesser value or entirely waive it off so that they can still seek contributions through Google play billing.
http://www.google.com/search?q=wireguard+donate
Problem solved.
Thanks for the great work!
https://play.google.com/store/apps/details?id=com.navigation...
Spamming users with notifications is also against the rules and everybody does it anyways.
> Here are some examples of products not currently supported by Google Play In-app Billing:
> One time-payments, including peer-to-peer payments, online auctions, and donations.
Some examples are purchases that can be used outside the app, eg. cross platform purchases and things like transportation and finance.
How deep does it have to be before they cut you off? Can you link to a page that is only linking to another page where the donation happens? How much extra text would you need to "pass inspection". I find these kinds of arbitrary rules very unsettling. It's definitely time to break up the tech giants.
It is odd that they remove this though, I use at least two more open source apps that asks for a donation and will send me to their donation page if I click.
And before the "android can sideload" argument, how many normal people are going to do that with all the dark pattern warnings that google displays when you try to enable the feature.
Both are lying to you and everyone else. They instead demand their private tax while lying to you about it beforehand.
"Do the right thing"
Google in a nutshell.
But of course this impact googles bottom line so the sane approach goes out the window
Because that way, we can install these applications from F-Droid, by default. That allows us to cope out of the network effect of Google Play Store, allowing the more fair F-Droid (which specifically allows donation-ware) to increase its network effect.
> Google Project Zero researchers find 100 ZERO-DAY vulnerabilities in unofficial app store "FDroid"
https://www.reddit.com/r/assholedesign/comments/dhir1i/in_th...
https://battlepenguin.com/tech/android-fragmentation/#packag...
We could go on about how regular users wouldn't understand or care and blah blah blah and we'll keep getting software that's neutered, tracks us and becomes more like the proverbial car with the hood welded shut; where people who know about cars have to attach several sidecars just to keep our vehicle doing what we want it to do.
Of course, there are cases that essentially suffer from this, but for me as a user, I've got to say I'm pretty satisfied.
So "totally broken" just isn't a rational description.
F-Droid is both a repository of verified
free software Android apps as well as a
whole "app store kit"
F-Droid also allows to source multiple repositories within one app. [1]However, Apple totally rules their walled garden, with some added gross exploitation to boot (recent "Sherlocking" story for Luna Display).
So this is no excuse for Google banning apps to protect their profits at their users' expense.
This is very wordy and sounds a bit complicated, but it was simply a few extra taps and it installed. A pretty good balance of not too easy that a novice might do it by accident and still accessable.
Only Pixels from the official store are rootable.
I had hoped that the pure-Google devices would have just had a switch: "I am now root," but alas it wasn't to be.
That is a very good thing. I wish they also made "install from unknown sources" a bit harder.
Don't get me wrong, I love openness. But there must be a barrier of entry.
Now, why should they do this? Because I have seen malware sites tricking people into first enabling 3rd party apps and then installing their apk.
Some of this I can understand. Root permissions does introduce some additional security considerations. We haven't fixed this in decades of computer usage in a way that preserves security, ease of use, and giving people easy access under the hood.
My mother would click any number of scary UAC prompts in Windows just to get to the webpage she's trying to get to. That's not Windows' fault, but it is reality.
You certainly have access to a lot of things with adb, but it can hardly be considered root on non-rooted devices.
That's not true. It does have root support built in with 'adb root' that then runs future shell commands as root.
The factory image has this disabled, though, so you do need to flash a build that supports it. That would be a 'userdebug' build variant ( https://source.android.com/setup/build/building#choose-a-tar... )
So strictly speaking you can have root through purely first-party, open source, AOSP tools exclusively. It does, however, require doing a full build & flash yourself. That process is at least documented, though, so there's that. Just think of it like Gentoo
I do think it is a good thing though. For people like you and me, it's easy to do, but we also understand what root is and the dangers of it. For someone who doesn't, it's better off for them to not be able to root their device in the first place.
Of course, we could bring up the catch 22 that is learning. If I hadn't tried out rooting, the terminal, modifying the filesystem etc back when I was younger and didn't know anything, I probably wouldn't know much about that stuff now.
It kind of is Windows' fault, because it's pretending to protect you from things it doesn't actually understand.
I have had trouble getting people to install Signal on their phones because it wants access to your texts and contacts. But it only wants that because it's a messaging app. It's not as if it uploads your texts to the Signal Foundation -- its very purpose is to do the opposite, and the source code is published so that anyone can verify as much.
But because the validation provided by mobile app stores is theater, it doesn't understand that and treats Signal the same as any random flashlight app written by Some Guy in Russia who wants to sell your contacts to Viagra spammers in order to buy a new Mercedes.
If this idea of validation and curation is to mean anything then it should be that it validates that Signal has both a legitimate reason to access your contacts and doesn't do anything untoward with them, and then allows Signal to access your contacts by virtue of you having installed it, but not so for a flashlight app. There shouldn't be a pop up allowing naive relatives to either break Signal or volunteer your contact information to spammers. Even if it's possible to grant the flashlight app greater permissions, there is no need for that interface to present itself in a way that allows users inclined to mash buttons an easy way to do the wrong thing. Use better defaults and then making changes can be six taps deep in a scary system menu that the app itself can't launch.
Which is how Linux package managers already work. If you try to put an app that hoovers up your contacts and sends them to spammers into the Debian repositories, it'll get refused. And packagers can restrict apps to by default only doing the things they ought to be able to do using apparmor and the like, instead of relying on the untrusted author or the unknowing end user. The user can still override it manually, but then you're typing things at a command line, which deters novices who don't know what they're doing and gives experienced users a red flag that there had better be a good reason why they have to do it that way.
https://source.android.com/setup/build/running#unlocking-rec...
You're correct it's not trivial for the average user, but the average user should also not have a rooted device (nor does the average user even want a rooted device).
Is the learning curve perfect for the semi-advanced user? Probably not. But third-party software also fills this gap just fine. I don't think Google should be a required party here. They do provide officially supported tools & documentation for the process itself (and those tools work on all major platforms at that), just not a shiny GUI to do it. I think that's a reasonable point to be at.
An unlocked bootloader is strictly more powerful than simply gaining root. You can even install other operating systems. The ability to safely gain root falls out as one of the possible uses of an unlockable bootloader.
True, but having an unlocked bootloader makes rooting trivial.
Those wanting to root devices with locked bootloaders have to depend on exploiting security flaws in their OS to do so. This means intentionally ignoring security updates and potentially maintaining a vulnerable device just to be able to retain root. These exploits tend to be device specific as well and often carry a risk of at least soft-bricking.
Those with an unlockable bootloader can just unlock and flash in something like Magisk in a pretty much universal fashion.
It's the same thing that happened on PC ages ago. If you don't like DRM, don't support games & apps that use DRM. Complaining to SecuROM that they are supplying market demand isn't useful. At least SafetyNet isn't a badly made rootkit that destroys your hardware and it's only real flaw is being semi-functional DRM.
I've got enough blame for everyone involved, don't worry.
> Complaining to SecuROM that they are supplying market demand isn't useful.
Appealing to the ethics of an entity that doesn't have any is not useful. But I wasn't writing to Google.
> At least SafetyNet isn't a badly made rootkit that destroys your hardware and it's only real flaw is being semi-functional DRM.
"Whatabout SecuROM"?
I don't understand what you're attempting to get at with this.
PC DRM back in the day was notorious for rootkit vulnerabilities and even bricking CD/DVD drives (example: https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootk... ). The point was just at least SafetyNet isn't straight up broken like the wild-west of arbitrary DRM providers of yester-year.
But clearly there's no value to be had to anyone by continuing to debate with you, so sure I'll stop.
It's not always trivial to submit new apps and ensure it compiles correctly on their build servers. Same goes for updates, which can be silently dropped due to any number of tool issues.
If you are a front or backend developer please consider investing a weekend or two helping fdroid improve their systems.
F-Droid/Amazon/whatever can't automatically update installed apps unless the phone is rooted. It's not an even playing field - Google has a de facto monopoly on Android.
That's absolutely not true at all.
All that happens is that, the first time you try to install from such an application (or any other application other than your store, eg: the first time you try to install an apk after you download it from your browser), a settings windows appears telling you this application can't install more applications on your phone until you give it permissions. From there giving the permission is a two click matter, and you don't need to look for it the link is given. See the exemple 2 pictures (and that's the only two steps - note that the "settings" button in the first takes you directly to the second picture, aka straight to the right settings page for the correct application, no looking around needed): https://imgur.com/a/Vafqyic
Then you press back one time after giving the permission, which is the normal way to go back to what you were doing on android, and it works at expected, aka it goes back to the install screen except this time it enables the install button.
Any porn site like youporn and pornhub, or epic with fortnite, etc ... Do it this way with no major issue, because the messages are super clear, and where to click to allow it is super clear, no need to look for it.
If anything, this is almost too easy and I'm surprised there is not a bigger spread of malware through browsers using that, and I would be for it asking you to confirm your password before enabling that permission.
EDIT: it appears I missed that parent was talking about UPDATING apps, not installing.
To install apps without user prompt on Android, you need INSTALL_PACKAGE permission. Guess what? You cannot use that permission on third-party apps (meaning any app installed by the user, in opposition to apps that are pre-installed on the ROM), since it's for first-party apps only. The documentation backup this claim: https://developer.android.com/reference/android/Manifest.per... Without that permission, you cannot have automatic updates.
The feature you are referring to and shows in your screenshot refers to the ability to launch an APK install prompt (that the user have to click through) using an Intent. It cannot be considered as automatic update. So, yeah, it's not an even playing field.
Personally, I do all my own maintenance and love to look under my hood. My wife? She’d drive a car until it was devoid of oil or coolant and the block seized up without even batting an eye lash. I’m not passing judgement here, just offering a more realistic viewpoint.
The same is true for users of apps. There’s a reason the stores have grown to be so successful, and a reason the Google store is evolving to be more and more like Apple’s.
I don’t think that they are perfect, but I also would never consider the open source package systems to be perfect either. Everything has a trade off, you can’t have your cake and eat it too.
In fact this capability even enabled the community of these OSes to support the platform much longer than Nokia intended to. They made emulators, enabled hidden functionality (like FM Radio), even the bootloader was unlocked so you could go and install Android -but drivers were not open-source- if you wanted. It was liberating.
Too bad it got killed prematurely, and from its ashes Windows Phone was born.
They can. Debian does it on an opt-in basis: http://popcon.debian.org/
> search for discovery
You can use text search on APT repositories, and probably other ones.
> malware and abuse detection that scales to millions of apps
We don't need millions of apps.
A thing I like with distribution repos is curation: only trusted people can add new packages. Of course it means less packages, but it also means there is no junk at all.
Also, whenever I needed to do something, either F-Droid already had an application for it, or there wasn't any open source app doing what I needed.
People complain about app stores being restrictive and then you suggest only trusted people being able to distribute code that I can use? That's way worse.
When I want to use some popular software and it's missing from Debian, I can usually find a thread on Debian's bug tracker with a detailed discussion on what the issues around providing this particular software are.
You have to accept that these are commercial products for commercial gain. They are not a product of or for a community. Massive corporations use these systems to create products that drive their revenue. They will do whatever works for the majority; the fact that a minority wants certain kinds of changes does not impact their bottom line, so why should they consider it? They do not care about your outrage or opinions, they care about cash.
To all the entrepreneurs reading this: please create one. To all the VCs reading this: please fund one.
It's badly needed. I heard Huawei is working on one but I wouldn't bet on it.
I'm talking about a mainstream alternative android store. The design of f-droid is not appealing enough.
I don't think this is a solution.
2. Please, make it appealing for you and others! https://gitlab.com/fdroid/fdroidclient
Make it mainstream. Spread the word. Install it on family devices.
How else you think mainstream will happen?
Google owns the app store. So, developers should abide rules imposed by Google although the rules do not seem reasonable all the time.
My suggestion is, developer can still implement in-app billing, removing "donation" wording. For the in-app item, make it as good-to-have feature like "unlocking additional app color theme".
With such, he will still abide the rule, yet able to get his monetary reward.
> One time-payments, including peer-to-peer payments, online auctions, and donations.
I don't see anything wrong with this. Charging vs Donations, I don't see what the difference is. It's people paying money for good/services/software. The primary difference is the open ended pricing model.
Google, Apple put up networks and there's value in that network. Whether someone chooses to release their app for free or charge money for it, that app is dictated by the network fees. This network is extremely powerful in terms of its distribution reach. Does it warrant 30%? That's what the market is willing to put up with, but if we're debating 30% - it should be for the whole network not just because someone has an open ended pricing model.
If this app is registered as a non-profit (which it did not look like based on the website?) then I am 100% in the wrong and do believe the app should be able to operate under different pricing schemes.
At a philosophical level - what is the difference between a free-to-use app that has open ended pricing vs a FOSS with donations?
If there is a difference, let's discuss it.
It's a major failure of governments to allow monopolies.
Charging: Person paying gets something in return Donating: Person paying does not get something in return
>The primary difference is the open ended pricing model.
What does "an open ended pricing model" mean?
Agreed, donations do not necessarily mean I receive anything in return and I purely want to support like clean water efforts in 3rd world countries, but policing the difference seems unrealistic.
But that seems like it should be a special non-profit category. I think I'm beginning to convert to a 'middle' ground that there should be a sole proprietor non-profit, but that seems insanely hard to police.
https://www.apple.com/ios/app-store/principles-practices/
Also on the value prop front, worth noting a variety of digital app stores at scale have found operation costs 12% to 18% fees before the hands on “40% rejection” level of oversight that Apple is providing to end users.
This is simply not how the real world works. If it ever does, you've created a dystopia.
Google are being bureaucratic twats here. There's plainly and obviously a difference between WireGuard and the 10,000,000th iteration of some bullshit F2P casual game, and there's obviously a distinction between donations and purchases - the intent of the user, for one.
That they put prole-tier support on the case and 'accidentally or otherwise' sling the banhammer at pivotal pieces of software is their problem to figure out.
But again, what is FOSS with a donation link vs free-to-use software with pay-as-much-as-you-want.
One sounds like a non-profit while the other sounds like a for-profit.
Perhaps if you can directly show your software is FOSS via licensing etc that there should be a special exemption?
Seems like there needs to be a sole-proprietier non-profit... but man that seems like rife for abuse.
The for-profit vs non-profit distinction is immaterial to me; the distinction is between actually paying for products (e.g. buying an ingame item or support or a subscription or whatever; some sort of 'contractual' thing), and literally giving money away with no strings attached.
Google's particular funding model for their App Store is a different kettle of fish entirely - they can decide that apps beginning with the letter A pay a 90% fee and that's just how it works.
Through this discussion I do wish there was an exception for FOSS for individuals at a legal level.
I can 100% agree though that the fees which google/apple charge are extortionist.
the question is whether or not it is right for google to act as a gatekeeper here. i think not.
It would surprise me if that were not true globally.
A donation is definitionally a gift. If it's not due to some legal wankery, rename it, doesn't matter.
as far as i know, at least in the US only donations to registered non-profits are tax free. any other donation is taxed like any other income.
if it's a one-off, sure, calling that a donation may be trivial, but if you start getting donations on a regular basis, you have to prove that they are in fact donations, and not hidden payments for a service. if it weren't so, we would not need to have entities register as non-profit.
Edit: Wireguard literally make that case while soliciting donations
>We're extremely grateful for all donations, which enable us to continue developing WireGuard as free open source software. We are happy to receive donations from interested companies who would like to see WireGuard development continue and thrive, as well as individual donations from folks who would simply like to say "thanks".
I don't believe that the app stores would cease to function or even suffer appreciably decreased profit by doing so. In-app purchases result in new features or items or something being unlocked.
Donations do not. They are gifts.
I disagree with the concept of fees for the Google and Apple play stores because they are monopolies within the platform entirely, but if they must exist, attempting to charge fees for donations is just bad form.
Considering the amount of donations I got, it would have been much more profitable to clean toilets, to just go begging in the streets, collect bottles from public trash cans for the deposit, or just sell my body.
In fact let's have a look how much I got during the past 12 months for 250 hours of work:
$0.
Had I been working as someone who climbs onto roofs and cleans the dirt off of them I would have gotten this much for that in this country:
$16500
And then, as a cherry on top, you now demand that a giant monopoly, which is trying very hard to soak up as much of people's data as possible - without paying them for it! - should get a cut from donations for my work which I genereally give away for free.
Now I can understand that you did not know this when you wrote down your opinion!
But given that you do now, do you understand how insulting this feels? :) It actually itched me so much that I created this account solely for the purpose of telling you, and I would be very happy if you could change your mind :)
100% open source does not pay money for the vast majority of people, and thank you for your contributions to the community.
I also hope you understand that I get that FOSS donations won't make a liveable wage. At the same time, we want to be thanked for our contributions to the community - I get that.
My point is - by throwing up a donation link, we're circumventing their process. What's the difference between throwing up a donation link vs a Apple/Android pay link in app? It's the network fees. We're trying to avoid those because we feel they're unfair (which they 100% are).
If the Apple/Android pay fee was the same as the donation link, the majority of the time, we be using Apple/Android pay. Why not?
We want the benefits of the Apple/Android distribution network without paying their fees because "We belong to FOSS".