We now have transcripts (thanks Dreb), we have cross-app comments, we have lightning bitcoin payments (value4value4ever). Podcasting 2.0 got us living in the future. @funfactfriday @Drebscott @dave @adam
@Medus @funfactfriday @Drebscott @dave @adam Nice!
Your feed generator needs a small tweak to your socialInteract tags to conform to the final spec: https://github.com/Podcastindex-org/podcast-namespace#podcastsocialinteract---discuss
Basically the comments urls have moved out of the node content and into a "uri" attribute.
The error can be seen here, and then validate your fix when you regenerate:
https://validator.livewire.io/?validate=https://funfactfriday.com/rss/feed.xml
Dreb Scott 
@Medus @Drebscott @funfactfriday @dave @adam That means a browser-based app like podverse or podfriend will be blocked by the browser from fetching that url directly. They'll need to proxy that call through some server they manage.
You can allow direct calls from browser apps by including the following http header in your responses:
Access-Control-Allow-Origin: *
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin
If you're returning Mastodon responses directly, you'll be waiting on them: https://github.com/mastodon/mastodon/issues/10400
@js @Drebscott @funfactfriday @dave @adam Thank you again.
@Medus @Drebscott @funfactfriday @dave @adam Thanks for the quick fix - you're back on top of the early adopter list for the moment
@js @Drebscott @funfactfriday @dave @adam Sweet! I didn't know that was a thing.
@js @Drebscott @funfactfriday @dave @adam Ok, just updated. Wow, we have almost 20 episodes with the socialInteract tag. Didn't realize we had been doing it that long.
I am still getting "Local fetch failed (CORS disabled?)" and am unsure what that means.