First, it's good that people are working on new features for RSS for podcasts. Why not. But you should choose a modest name for your effort. By calling it Podcasting 2.0 you're basically forcing anyone else who wants to do something here to call theirs 3.0 or 4.0. Just come up with a random name, like The Oslo Project. How did I come up with that name? I asked ChatGPT to do it : "Please give me 10 random names of European cities with less than 4 syllables in their names." Here's what it came up with. Or you can ask for children's names. Or color names. Or Yiddish words. And then please, look at what the other guys are doing and instead of implementing something slightly different with a different name, just do it their way. The only goal here should be upgrading the user experience and interop, so there's no freaking lockin. Keep the bullshit to a minimum. "Available where you get your podcasts."#

I'm still trying to figure out how to retrofit Instant Outlining in Electric Drummer without having to implement support for the new email-based identity system. It's especially hard to do that for an Electron app, it took a huge effort to get Twitter identity in there. E/D stores files locally, and combined with Public Folder, means it doesn't need any help storing stuff where it's public accessible. The hard part, I'm finding, is to figure out where I need to stop it from overwriting one of the head-level attributes. I wrote all this code, but it's so freaking complicated. Having cleared that up, I'm now ready to take another approach. I'll let you know how it goes. #