Podcasting Chat Community

Used AI to examine a strange obfuscated file in a piece of (paid) hosted software I use. I’m not very happy about obfuscated code on my own server - who knows what it’s doing - but I didn’t really know how to find out.

First time I’ve actually found AI useful - it told me a little about what the file did: it checks that I have a licence by sending my details to a server somewhere, and does so every time a page loads or a script runs. It also hides a number of functions used by the tool.

From that, it wasn’t particularly difficult to find a pirated version of the software in which this file has removed this licence check (and is no longer obfuscated). I’m now using that file, to no ill effects.

I think this is legally dubious in the US under the DMCA, where you’re not allowed to remove copy protection from a thing you have paid for; but luckily not so a) where the server is physically, or b) where my own company is based.

Finally, then, AI has finally been useful. Whatever next?

If you are on Android and you miss Google Podcasts, then this is fun: https://play.google.com/store/apps/details?id=com.simplecityapps.shuttle.podcasts&hl=en_US

@ChadF Runway will show payments FROM Alby as well. But the creator needs to use Strike for Runway to work, so the creator can see their boosts/streams.

You’ve reminded me to take a look at the code - I wasnt convinced that it was pulling in new payments when I used it a few days ago.

In 2017, Joe Rogan already had a fan - Jeffrey Epstein. Here's more about Epstein's connections with podcasting.

Jeffrey Epstein - the podcast files

What so far do we know about Jeffrey Epstein's connections into podcasting? We know he listened - and was a fan of Joe Rogan...

Podnews (podnews.net)

@transistor

I don’t know how bluntly I can say this - you’re too late. Only 10% of podcasts support XSLT. It’s going away. We’ve lost this one. It is a waste of your time and your boundless energy trying to fight it. Please stop! Let’s do something constructive instead.

Let’s fix this UX issue - that people click on RSS feeds when we give them a big link marked “RSS feed” - with clear signposting about how to use an RSS feed and what it’s for (and a suggested user journey if they do click on one). Let’s work on wording that listeners understand for the CSS “error message”. Let’s see if we can get user testing through the PSP, to get some science behind it; and formulate some guidelines for the industry on how to handle this properly.

You’ve highlighted a problem. Let’s fix it constructively - with science!

@dave @js @transistor @adam We have CSS for XML which avoids the “OH NO A BIG SCREEN OF CODE SOMETHING HAS GONE WRONG”.

But this is a UX issue. We shouldn’t be putting an RSS feed in front of a user as an equivalent click to Apple Podcasts, Pocket Casts etc. Any links to RSS visible by the user should be carefully explained, and probably accompanied with a dialog box with details of how to use it to hand-hold them.

I’d be happy to write a first pass of that, but someone needs to put it into user testing to ensure users understand it.

Only 10% of podcasts use XSLT. It is a waste of energy trying to retain it. It’s gone. Let’s sort out the UX issue.