@nprofile1q... I'm using one that's fast, affordable, efficient, and supports even really long podcast episodes.

Tasks like this don't need powerful models. The prompting is often more important.

@nprofile1q... Thank you!

@nprofile1q... Awesome! When someone searches for a podcast in your app, do you just carry over the same results and order from PI?

@nprofile1q... If only there was an app that actually embedded those chapters in your MP3s, and hosted your Podcasting 2.0 chapters, and even provided YouTube-compatible timestamps and PodLove Simple Chapters.

Oh, wait. 😉

https://podchapters.com/

@nprofile1q... `socialInteract` is for—wait for it—social interaction, which is significantly different from contact methods.

"Contact" is more of a one-way flow. Audience sends feedback to the podcast, and the podcast might include that _in_ the podcast. There's less expectation for back-and-forth interaction.

Plus, this `contact` tag is structured to handle different types of contact: booking, sponsorship, audience feedback, and potentially more.

@nprofile1q... Essentially, `txt` could potentially handle _anything_, and we could just stop inventing tags altogether because the `txt` tag could handle it.

But that's messy, unstructured, wasteful, and difficult to parse.

@nprofile1q... See my response to the txt idea in the GitHub.

@nprofile1q... Then don't put email or phone numbers in there. Put a contact form URL.

That flexibility is the point of this tag.

And for podcasters, like me, who don't mind publishing a feedback email address and voicemail phone number, it provides that in a consistently structured way.

@nprofile1q... I'm sticking with 5.4, which is working well for me. 5.5's price jump makes it not worth using for most of my agentic stuff.