@Wyliesau@noauthority.social @RichardJohnson@noauthority.social
Please see this post for an explanation and lmk if you have more questions.
Remote
Podverse
@podverse@podcastindex.social
mastodon
4.6.6
Open source podcast app for iOS, Android, F-Droid, and web. Proud supporter of Podcasting 2.0 and Podcast Index. #FOSS #V4V http://newpodcastapps.com
⚡️:podverse@getalby.com
1139
Followers
793
Following
15
Posts
Joined January 25, 2022
Posts
@Wyliesau@noauthority.social it looks like the “Censor text” setting is on for your podverse. It uses a big open source list of words to obscure with * when enabled. Here is a screenshot of where it can be disabled. I’m pretty sure it is turned off by default on all fresh installs of Podverse. Maybe there was a version released a long time ago where it was on by default though. Hope that helps.
Hi @russell@podcastindex.social I'm sorry for the late reply! It has been a very busy 2 weeks.
I appreciate you reaching out to us for this. It is very generous of you to offer this program. If there are no strings attached to receiving this donation from PodToo, then I can't imagine any reason not to. At the same time, rarely does "no strings attached" exist in life...if we sign up, are we obligating ourselves to any conditions besides what is listed under the "who can apply?" section?
For Podverse Next Gen, we want to build a database that supports ALL of the Podcasting 2.0 RSS tags.
Whether or not we use each tag in apps will be decided over time, but we at least want the data there in case we need it.
If anyone would like to help review our database schema, we'd love your help.
The work-in-progress schema can be found here:
https://github.com/podverse/podverse-ops/blob/v5-develop/docs/database/0001_init_database.sql
And everyone is welcome to the HQ for Podverse Next Gen discussion in this Matrix room:
Replying to
@Salty_Crayon@mastodon.social
@Salty_Crayon good to know. As a last resort, it may come to that. It should a temporary problem anyway until the next gen Podverse is released.
Replying to
@podverse@podcastindex.social
@LC3 yes afaik Apple CarPlay should be working for months now. I don't have a car with CarPlay or Android Auto support tho so I only know what works in the emulators.
@mikeneumann@podcastindex.social @mikeneumann@podcastindex.social thanks for the encouragement.
The reality is we are just trying to keep this current version of Podverse on Google Play, and then 100% focus on the next generation Podverse which won't even have this quirky Android Auto setup. The problem is these GP rejections are holding me back from truly focusing on next-gen 🙄
Hopefully the next gen version will not have any of the issues you're seeing with other audio apps either.
Replying to
@steven@podcastindex.social
@steven yeah, that is our worst case fallback option. A big tradeoff though since a lot of people depend on Android Auto support for convenience and due to laws in their country.
Replying to
@podverse@podcastindex.social
Worst case scenario to prevent Podverse from getting removed from Google Play is we'd need to disable Android Auto...which is a pretty bad scenario.
Going to try adding test requirement info into the release notes, and hopefully some human on the other side at Google will see it and realize what needs to be done. Not sure if there is a better way to get this test info to a tester...
@melodiousowls@noauthority.social appreciate it ❤️ still exploring options. Hopefully we'll get past it.
Replying to
@podverse@podcastindex.social
Is it even possible to contact a human being at Google Play who can explain what the issue is? Who can explain why they are accepting some apps with "Draw over apps" as an Android Auto requirement, but not Podverse? Who can confirm if they're even trying to accept the permission in their tests? Seems like all we ever get is a template response to our appeals that sheds no light beyond the initial rejection.
Replying to
@podverse@podcastindex.social
We've already sent an appeal explaining the "Draw over apps" permission, but they rejected the appeal, and of course provide no additional info, such as whether they even enabled "Draw over apps" in their test or not. They rejected us in the past, but approved it after appeal explaining the permission needed.
We're currently working on an all-new version of Podverse that shouldn't require this permission, but that won't be done for months. I'm afraid current PV may be removed before then.
Podverse's standing in the Google Play Store is in a precarious position.
Our latest update is getting rejected, and they're saying "Application does not load in the Android Auto environment" but in our tests with the AA emulator, as long as the "Draw over apps" permission is enabled, Podverse + AA is working.
The thing is, we HAVE to release an update to Google Play that increases the SDK version of the app in the next few weeks, or Google Play says they'll remove the app 😞
@aperalesf@masto.es hello, thank you for sharing Podverse! If you have questions please let me know and I can try to translate for a reply.
@Jonycoo@fosstodon.org wonderful! Thank you for the contribution! I should have these changes in the next mobile app release within about a week, and live on the website tonight.
I just added some context for "remote" to the context document: https://github.com/podverse/podverse-rn/blob/develop/docs/translation-context.md