[cxr]

Note that the Google Podcasts mobile app differs greatly from the site at podcasts.google.com. When accessing Google Podcasts through the latter, the feed URL is encoded in a base-64 variant that you have to resort to extracting from Google's show page URL and descrambling. If you want to export your feed list, this can be tedious. (Made worse by how top-heavy the Google Podcasts site is just to load a page.)

[Ajedi32]

> If you want to export your feed list, this can be tedious

Does Google Takeout support Google Podcasts? That'd be the usual method of exporting everything from a Google product.

[cxr]

> Does Google Takeout support Google Podcasts?

Nope. One of the few use cases where I actually looked towards Google Takeout as an escape hatch for my data, instead of a mere novelty ("a ZIP of all my YouTube interactions—that's neat, I guess"), but Google Podcasts is not there. I've filed several complaints about this and several other shortcomings in response to the Google Podcasts app's spammy notifications requesting feedback.

I ended up writing a short set of procedures to follow (an SOP—written like a software manual, really) that walks you through how to select page elements that are shown on screen while logged in, and then drag and drop them from the podcasts.google.com tab into the "export tool". The punchline is that the export tool is just the SOP document itself. It's meant to be read in your browser, and it takes advantage of the fact that the browser also happens to be a universal runtime...

The exporter will descramble the links and output your subscriptions in text/uri-list format.

[Ajedi32]

That sounds useful; do you have that tool published somewhere?

[cxr]

I got pretty carried away writing the thing as if it were a mid-century technical repair manual for a piece of industrial equipment, and never got around to publishing it but here you go: <https://crussell.ichi.city/gpe.html>

It could really stand to have an associated 90-second video demonstration that walks through the steps because of how unorthodox the the-documentation-is-the-implementation paradigm that I was experimenting with is.