Surely they could disable instead of destroy, then let the content creator plead a case or at least click a button, “This is a mistake”? After a few weeks it would otherwise be destroyed.
I mean, yeah, if you’re paying the slightest bit of attention, app store owners screw over app developers all the time. It should be expected. But since people still develop apps, it’s evidently not, so it’s not a waste of time to keep bringing it up.
The article doesn’t read like humblebragging to me; the author wrote a popular app, which got pulled with no meaningful communication. He’s not talking about how awesome he is, just how popular his app was, which is foundational information for the article.
I never imagined this would generate this amount of attention: featured by Medium, 80k+ views, heated discussions on Reddit or Hackernews. I don’t really expect this to change anything for me, but I’m glad people are speaking up.
:|
EDIT: Folks, use “incorrect” here instead of “troll”. Believe me, when I’m trolling, you’ll know it.
I don’t really think that’s humblebragging, either; it’s a relevant statement of fact. He’s neither
claiming this is because of how awesome he is (in fact, “I never imagined” weakly implies the opposite), nor
bringing it up for no reason (it’s to explain why he’s A-ing FQs).
I’ll certainly grant it’s somewhat subjective, but I still think this article is useful even if it is the author ego-stroking, for the reason I outlined above: people keep doing this, so the warnings are clearly not dire enough yet.
The problem is that the net is rife with these sorts of stories. I cannot imagine anyone with two brain cells to rub together not learning about this before hitting it.
Instead, I wonder if sufficiently cynical people know that by complaining about this they get cheap publicity. I would rather we not indulge that here–and yeah, I agree there is a grey area.
This is how the DMCA works. Google has to take the thing down within like 24 hours or something ridiculous by law. Fuck the DMCA
The DMCA does not require them to ignore all emails about the takedown or send inaccurate canned responses.
No, it just encourages it.
Surely they could disable instead of destroy, then let the content creator plead a case or at least click a button, “This is a mistake”? After a few weeks it would otherwise be destroyed.
I think everyone would click the button
Google screws devs, water is wet, etc.
This is just somebody humbleranting to raise product awareness…just look at the tone.
That feels a little blasé.
I mean, yeah, if you’re paying the slightest bit of attention, app store owners screw over app developers all the time. It should be expected. But since people still develop apps, it’s evidently not, so it’s not a waste of time to keep bringing it up.
The article doesn’t read like humblebragging to me; the author wrote a popular app, which got pulled with no meaningful communication. He’s not talking about how awesome he is, just how popular his app was, which is foundational information for the article.
:|
EDIT: Folks, use “incorrect” here instead of “troll”. Believe me, when I’m trolling, you’ll know it.
…or will you?
I don’t really think that’s humblebragging, either; it’s a relevant statement of fact. He’s neither
I’ll certainly grant it’s somewhat subjective, but I still think this article is useful even if it is the author ego-stroking, for the reason I outlined above: people keep doing this, so the warnings are clearly not dire enough yet.
The problem is that the net is rife with these sorts of stories. I cannot imagine anyone with two brain cells to rub together not learning about this before hitting it.
Instead, I wonder if sufficiently cynical people know that by complaining about this they get cheap publicity. I would rather we not indulge that here–and yeah, I agree there is a grey area.
I’m not really sure if that’s something to be proud of, it might seem funny to you but it’s rather grating to me.