Hacker News new | comments | show | ask | jobs | submit login

It's back up as of right now. I just downloaded Templar Assault.

Also, just to be clear: once again, we're responding to a one-sided media story without reference to the app in question or the facts on the ground. And, once again, we're jumping in for or against the side we curently favor in the smart phone wars (I'll bet good money there's an iPhone in your pocket, so let me put down my Galaxy Nexus to respond).

It seems you are trying to steer this into a "if you criticize Google you're an Apple fanboy, if you criticize Apple you're a Google fanboy" argument which is not only dangerous in itself but utterly ridiculous.

I think the demands he made are pretty reasonable. Both Google and Apple need to improve relations and communications with developers in cases like this and trying to avoid the subject or turn it into a fanboy war wont help the case.

So please, put back your Nexus in your holster, cowboy.

It's more "If you make a knee jerk criticism of Google or Apple that we've all heard a thousand times already, based on a single poorly sourced blog post, and bring no new insight to the table" then you're a fanboy and should be posting somewhere else. I'm tired of this.

You are tired, fair enough, but then don't try to make it a fanboy case, just let it slide.

I have my own perception about these things and that is that if this was an Apple case instead of a Google one it would have been overanalyzed and exaggerated ("devgate" or whatever other stupid name attached to it) and that one-sided stories would be welcomed instead of questioned.

This is probably coming across as a pro Apple statement, no doubt (and I do'nt really care, i don't make a big deal about what technology i decide to put in my pocket), but I also think it'd be against users and developer interests to say that the problem is not there or that is only a matter of perception based on your ecosystem preferences.

If there something wrong, or that needs improvement, it should be said regardless on what phone you use or your personal preference.

Given that both Apple and Google are notorious for not talking to anybody, even the devs they're making money on, I'm not sure what you see as the alternative. If a journalist can only get one side of the story, I think they should print it.

As a dev I can and do communicate with Apple reps.

Also, just to be clear: once again, we're responding to a one-sided media story without reference to the app in question

And just to be clear, the only reason you're responding is because ten thousand other people consumed and shared the story. And the reason they did that is because the narrative that nobody is home at Google is powerful in the development community. It threatens to spread to the rest of the web as well if you guys don't get in gear and start fixing this corporate culture problem.

Since an android app has to demand all possible permissions pre-installation (feel free to correct me here if I'm mistaken), then how else can one provide versions of said app that don't ask for the permissions that make some uncomfortable?

The Android guys even have videos that touch on this: http://www.youtube.com/watch?v=WDDgoxvQsrQ

And that's just one non-spammy reason for multiple versions. More sweaty Steve Ballmer and less Bill Lundburgh please...

That's just repeating the speculation in the article. We have no idea if the multiple app versions are the source of the warning. We haven't seen the letter, nor even read selective quotes from it. That's what drives me nuts about this: this is pure sensationalism. There's no journalism here at all, and almost no real facts. Yet all the "con-Google" crowd jump in with the tired old customer support meme anyway.

Stop it, people. Find some real evidence and indict them with that.

How is it not journalism? The story is admittedly one-sided but only because Google won't communicate with anyone. The author and the article's subject both reached out to Google and got no reply at all.

That is the story. Google is threatening to remove non-shady apps for reasons that are entirely mysterious.

Where are the quotes from the notifications from Google? Where is the independent verification? Where is the attempt by the author to "reach out to Google" (I just re-read the article -- they didn't do what you assume they did)? Literally all this is is an author using a few quotes from one source to rehash a meme and get clicks. And everyone here has jumped on it and pushes it to the top of YC. And I'm sick of this kind of discourse.

Here is a quote cut & pasted from the article: "Google didn't respond to a request for comment from me."

So the article details the attempt and failure of the devs to contact Google, and the author's attempt and failure to contact Google. What do you want, a seance?

The Trese Brothers have attempted to contact Google many times via email and through Google's support boards since the first warning and have heard nothing back.

Google didn't respond to a request for comment from me [the author of the article].

I think you need to read more closely.

And BTW I'm generally favorable toward Google, and my pocket holds an Android.

>Where is the independent verification?

How would you suggest getting it?

By asking Google. By looking for criticism of the apps elsewhere. By downloading and running them to validate there is no spam. By asking for a copy of the communication from Google. Are you serious about this, or did you just not think of that stuff?

Oh fer cryin' out loud. I downloaded and played this game (or an earlier version of it) over a year ago. It's not anything special, but it sure isn't spam, and the developers clearly have an engaged and enthusiastic audience...

If google is going to use an automated tool to detect violations of their rules that generates false positives, then if they have any clue whatsoever they need to put a human in between it and the developers to prune those out. Otherwise, it's like going to see your doctor and only getting a web browser set to WebMD instead.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact