https://github.com/moneytoo/Player/issues/37 Skip to content Sign up * Why GitHub? Features - + Mobile - + Actions - + Codespaces - + Packages - + Security - + Code review - + Project management - + Integrations - + GitHub Sponsors - + Customer stories - + Security - * Team * Enterprise * Explore + Explore GitHub - Learn & contribute + Topics - + Collections - + Trending - + Learning Lab - + Open source guides - Connect with others + The ReadME Project - + Events - + Community forum - + GitHub Education - + GitHub Stars program - * Marketplace * Pricing Plans - + Compare plans - + Contact Sales - + Nonprofit - + Education - [ ] [search-key] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this user All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} moneytoo / Player * Watch 5 * Star 59 * Fork 3 * Code * Issues 24 * Pull requests 0 * Discussions * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Discussions * Actions * Projects * Security * Insights New issue Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Pick a username [ ] Email Address [ ] Password [ ] [ ] Sign up for GitHub By clicking "Sign up for GitHub", you agree to our terms of service and privacy statement. We'll occasionally send you account related emails. Already on GitHub? Sign in to your account Jump to bottom Suspended from Google Play for listing supported subtitle formats #37 Open moneytoo opened this issue Jan 25, 2021 * 22 comments Open Suspended from Google Play for listing supported subtitle formats #37 moneytoo opened this issue Jan 25, 2021 * 22 comments Comments @moneytoo Copy link Owner @moneytoo moneytoo commented Jan 25, 2021 After a tiny unrelated description update, Just Player got suspended from the Google Play Store for "Sexual Content and Profanity policy". Google finds issues with following: Full description (en_US): "* Subtitles: SRT, SSA, ASS, TTML, VTT" Based on this, I suspect that the issue is with the word ASS. But it's an actual file format (/extension). Just Player uses ExoPlayer (a Google library) which lists the very same on the support page: SubStationAlpha (SSA/ASS) | YES | MimeTypes.TEXT_SSA Wikipedia lists the same formats: Filename extension | .ssa, .ass I immediately filed an appeal. Original message from Google: suspension The text was updated successfully, but these errors were encountered: 3 105 27 [?] 5 9 @pkkid Copy link @pkkid pkkid commented Jan 25, 2021 * edited Maybe add a . in front of each format? .ASS ..or maybe stop trying to secretly add sexual content into your player! :D 18 @alexcarruthers Copy link @alexcarruthers alexcarruthers commented Jan 25, 2021 or follow google's version: SRT/SSA/ASS/TTML/VTT @moneytoo Copy link Owner Author @moneytoo moneytoo commented Jan 25, 2021 I knew this was going to happen but I was telling myself that I shouldn't be afraid (as usual) to just put it there - hoping that "computers" these days are smarter in reading the context. But I guess not... I will definitely better remove the (_G_) (if reinstated). This is too much stress for nothing. 10 3 @dessant Copy link @dessant dessant commented Jan 25, 2021 * edited That line is perfectly fine, you should not change the description in an attempt to evade automated detection. Google has taken down your app possibly without human review, and the only reasonable action is to file an appeal, otherwise they will never have to contend with their abusive review process and automated takedowns. 42 2 @wodencafe Copy link @wodencafe wodencafe commented Jan 25, 2021 Seconded, please file an appeal for all our (_G_)es 5 @stefanos82 Copy link @stefanos82 stefanos82 commented Jan 25, 2021 Coming next, the block of Arsenal, Bruce Dickinson, and anyone with a "Cumming(s)" for surname from Google as a whole. 8 5 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 @dessant - don't gas the fire without even reading the ticket. He already said he appealed. Nobody's going to "contend with an abusive review process" over a small developer's appeal over a glitch, besides. 1 16 @dessant Copy link @dessant dessant commented Jan 25, 2021 @StoneCypher, the developer is planning to redact the description after the app is reinstated, I was replying to that: #37 (comment) 2 1 @wodencafe Copy link @wodencafe wodencafe commented Jan 25, 2021 @StoneCypher Maybe this is a fire that needs a little bit of gas. 5 2 [?] 3 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 @dessant - that's the sensible response, is to just call it .SSA/.ASS (substation alpha), and not act like there's some kind of ethical problem here. In the real world, no-one was seriously harmed, and escalating makes this worse for everyone, especially the original author. There's no "abuse" here, and acting this way makes everything harder for everyone. @wodencafe - This isn't even the first time this has happened this week. People who handle it reasonably and kindly just get fixed and go on about their day. People who try to create a big public stink don't get anything better. All you're doing is manufacturing unhappy people at both ends to feel powerful. 1 24 @dessant Copy link @dessant dessant commented Jan 25, 2021 * edited @StoneCypher, an automated takedown is not a glitch, this process was deliberately designed this way to allow for takedowns without human involvement. Google obviously doesn't think that automated detection is infallible, but they have no respect for the developer's time, and they are not concerned about the financial loss you may incur when your commercial app is taken down for no reason. It has been shown time and time again that Google's review process is abusive, across all of their services, even when humans are involved. If this thread wouldn't have been shared everywhere, the app would most likely not have been reinstated after human review. dessant/search-by-image#63 31 1 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 Having been on the other side of this? Actually having written automated control systems? This is a simple bug. Stop being so weird. You're making things worse. Nothing is improving here. 1 44 @kevcmk Copy link @kevcmk kevcmk commented Jan 25, 2021 @StoneCypher What a strange flag to plant. I'd say you were a Google shill but I don't think this is that complicated [?] 2 @Theome Copy link @Theome Theome commented Jan 25, 2021 Having been on the other side of this? Actually having written automated control systems? This is a simple bug. Stop being so weird. You're making things worse. Nothing is improving here. One of our apps has been removed for a similar bizarre reason. It took 10 full days until it was reinstated. This is not a "simple bug". In some situations being offline for 10 days is fatal. This automated system can crush startups and should be replaced by a process run by actual humans. 15 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 Wow, I'm a "shill" for saying "don't throw a fit over an automated mistake" Okay guys, you have fun 19 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 One of our apps has been removed for a similar bizarre reason. It took 10 full days until it was reinstated. This is not a "simple bug". In some situations being offline for 10 days is fatal. The guaranteed response is two days. Was there back and forth? Did they just not make the two day line? Were there questions they needed to ask? Did over the top claims slow things down? I've been pulled for things like this, and it's never taken them more than 36 hours to respond and reinstate Why would your app being out of store for 10 days be fatal? Users can still use the app during . This automated system can crush startups If your startup is "crushed" by the app being unavailable for two days, your startup is problematically fragile. I've worked at companies where the app went dark for a couple days because someone forgot to renew an SSL cert. Did anyone blame the IT guy for crushing the business? No, because that's a friend, so we just handled it calmly like a regular problem and went on with our days. Things like this happen all the time in business. Paypal will hold your account, too. Your domain might go dark (now there's a real problem.) You might get sued, including over nonsense, and your contracts might get put on hold over it if they're with the state. If you aren't ready, that's on you, not them. There's a cultural sophistication in understanding that if your business can be destroyed by two days of mild unexpected problems, your business is already hanging by a thread. You're supposed to be making more durable things than this. Does this suck? Yes. Is being out of the store for two days the end of the world? It really shouldn't be. If it is, you've got bigger fish to fry. 2 37 @kevcmk Copy link @kevcmk kevcmk commented Jan 25, 2021 No in this case you're not a shill, you're just wasting your time clawing for dear life trying to convince some internet person to not raise this as a bug [?] 4 @StoneCypher Copy link @StoneCypher StoneCypher commented Jan 25, 2021 @kevcmk - You can stop throwing insults, dear heart. I'm not trying to convince to not raise a bug. I'm sorry that you find what I said so difficult to understand. 26 @Theome Copy link @Theome Theome commented Jan 25, 2021 @StoneCypher Yes, the guaranteed response is two days. But we immediately received an automated response that it could take longer "because Covid". There was no other communication, we appealed and then heard nothing for 10 days. These 10 days didn't crush our business, just being offline didn't matter much for us. But I bet there are situations where it might hurt some startups badly, for example if they just started a big ad campagin or whatever. Also, this was the first time we had an app removed from the Play Store. It might not have crushed our business, but boy did it crush our souls. Google makes it sound like there's no way your app is going to come back to the Play Store, ever. We just spent close to a year preparing a huge new release for our app, and then this. No way to talk to a human at Google, just silence. Believe me, when you have experienced this, it's very strange to see someone actually defending Google. "Don't throw a fit" lol. We all together should create much, much more noise about this. 18 [?] 2 @rahulpyd Copy link @rahulpyd rahulpyd commented Jan 25, 2021 Ambiguity is common. I suggest they do a manual review before they flag apps. @wswright Copy link @wswright wswright commented Jan 25, 2021 If your startup is "crushed" by the app being unavailable for two days, your startup is problematically fragile. These are the opinions you should have learned to keep to yourself. A bubble is allowing you to think this is normal behavior. 2 @rickknowles Copy link @rickknowles rickknowles commented Jan 25, 2021 Coming next, the block of Arsenal, Bruce Dickinson, and anyone with a "Cumming(s)" for surname from Google as a whole. Also, be sure not to allow any developers based in Scunthorpe, UK to join the project. 6 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Assignees No one assigned Labels None yet Projects None yet Milestone No milestone Linked pull requests Successfully merging a pull request may close this issue. None yet 12 participants @StoneCypher @wswright @pkkid @Theome @rickknowles @rahulpyd @moneytoo @stefanos82 @alexcarruthers @kevcmk @dessant @wodencafe * (c) 2021 GitHub, Inc. * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.