James Cridland

@jamescridland@podcastindex.social
34 Followers
994 Following
0 Posts

Passionate about audio · Editor of Podnews https://podnews.net · Host of the Podnews Weekly Review https://weekly.podnews.net/ · I also write about radio https://james.crid.land · These messages self-destruct · ⚡james@crid.land

I also have a thing for craft beer, and did so before it was quite as trendy as today.

I live in Meanjin/Brisbane QLD Australia, on the land of the Turrbul and Jagera people. I'm British and moved here almost seven years ago.

Mehttps://james.cridland.net
Signal+61 447 692743
Podnewshttps://podnews.net
VERIFIED BY PRESSCHECK.ORGhttps://presscheck.org/journalists/james-cridland

@adam @samsethi @Todd_Blubrry It's perplexing that I'm being blamed by @adam in the Podcasting 2.0 podcast for a number of things that I'm not responsible for. While criticism isn't normally something that worries me too much, and Adam probably doesn't mean to criticise, he has a number of superfans that have decided to harass me here for apparently upsetting him.

Perhaps my support for this project is misplaced.

@adam @samsethi @Todd_Blubrry Adam also claimed that I was behind the ?premature? removal of email addresses from feeds because I was "whining about too much spam".

On the contrary: I've been consistent in wanting something OAuth-like that is simple and straightforward for users. I even wrote a proposal for it: https://github.com/Podcastindex-org/podcast-namespace/issues/342

This was disregarded, because one Apple employee decided that typing a token into a random field called podcast:txt was better.

Claiming podcasts - what can we do to help? · Issue #342 · Podcastindex-org/podcast-namespace

Use case Currently, if you want to "claim" a podcast on most podcast directories, then they achieve this in one of two ways. Publisher types in their RSS feed into a podcast directory Pod...

GitHub

For the record: @adam said I'd reported on a story about Buzzsprout and support questions following the removal of emails from their feeds. I have not reported about this at all.

Instead, @samsethi reminds me that @Todd_Blubrry said this in last week's @podnews weekly review.

Great to see my jobs board getting first (and second!) place in Castos's guide. Now, I'm wondering what isn't showing the emojis... https://castos.com/podcast-jobs/
Where to Find Podcast Jobs (Including the Best Job Boards) | Castos

Looking for a job in podcasting? In this article, we discuss podcast jobs and job boards, and offer some key advice to find your next job. 

Castos

Now that we can have a new COVID vaccination, I was hoping to get one booked as soon as I can, since I've a lot of flights and events in March/April/May.

The first question is "what brand of vaccine do you want" - how the hell should I know? I want the one that has been tweaked for the latest variants. What's that one? None of the websites appear to want to tell me. Sigh...

An email from the broadband company tells me that the #NBN is going to turn off our internet. I go and make a cup of coffee. Internet is now off, and will be for 90 minutes. Peace and quiet. Lovely. #Brisbane

@thomaswilburn Oh, you know exactly how this will play out.

Google's search teams will build AI text and image tools into the search engine.

The Google Assistant teams will incorporate their own AI creation solution.

Clearly, the Android team will say, this is a mobile computing issue, so there'll be an Android app. Preinstalled and separate to the assistant AI and the search AI.

No, the Chrome/ChromeOS folks will say, this really needs to be baked into the browser.

The Google Workspace folk will create an enterprise app for it. Separately, AI writing will be built into Google Docs.

Three separate messaging teams will say it's a chat problem, and clearly what Google needs is a new chat app (or four) to solve it.

YouTube and Google Photos will see this as a video/photo problem, and will incorporate AI creation tools.

Google Cloud will create a cloud-based solution for third-party developers.

None of these tools will be interoperable. Different APIs. Most will be quietly closed within 12 months without warning.

Oooh. New ffmpeg scripts now bake in the captions, as well as take the initial audio from the WAV rather than a scratchy low-bitrate AAC file. Progress. https://www.youtube.com/watch?v=XkEVdp8QlOg
Google Search dumps podcasts from Feb 13

YouTube
Just spent the morning rewriting the Podnews podcast publishing code. I now output one WAV file of each audio variant, and the code produces all the right versions - I hope. And the video now has subtitles baked in!

Embarks on new "publish Podnews" script on the new MacBook, which makes the right audio files and sends them all off in the right place.

Writes the AppleScript to export the images, which works so perfectly, it erases everything in the folder I had written all the code in, including the code.

Sigh.

Will try again tomorrow, but probably use a temporary folder rather than temporary files in the code folder.