Mastodon seems to be having a lot of trouble picking up al the #crossappcomments to an episode. Props to podcastindex.org, they're picking up all the comments so far.

@dave Is there a particular resource you recommend for learning about the Nostr key pair thing so I can consider it for my #CrossAppComments proposal?

@dave @adam Thanks for talking about my #CrossAppComments model!

I think "centralized" and "decentralized" are the wrong words to use in podcasting. Instead, I think we need to talk about portability and control.

I also think my comments model doesn't have a spam or identity problem. But it can support crossposting with stuff like importing chat, syncing with Boostagrams, and more interoperability.

At this point, what more would you like to see built into the code to get this moving?

@james @dave That's what I needed to know I didn't communicate well.

I can get carried away with explaining all the potential I see, and putting out multiple ideas to be discussed and refined.

I'm learning that this community doesn't really like that. It seems the ideas that make progress are when there's actual code and specifics, not general ideas.

(Thus why I actually _built_ something for my #CrossAppComments proposal.)

I'll work on clarifying my podroll/recommendation proposal.

@dave, if you'll be talking about my #CrossAppComments proposal today, do you need to chat first?

I just had a great chat with @martin about #CrossAppComments and we came up with some additional good ideas!

@dovydas But if you call it a chapters file now, that's going to confuse people later. It's only (incorrectly) called that now because that's all it's been used for so far. But as you know, chapters are merely one section of several that it already holds. And my proposal for #CrossAppComments would put them in the same file.

The full way I word it is something like this, "chapters go inside your episode metadata file, along with the description, episode artwork, comments, and more."

Yikes! I never realized how slow the #CrossAppComments are on podcastindex.org.

My working, open, portable, extensible, and easy-to-implement proposal fixes that.

https://github.com/Podcastindex-org/podcast-namespace/discussions/505

I just pushed a new update to my #CrossAppComments engine so it can now handle authentication, generate key pairs, and generate the necessary encrypted auth token.

https://github.com/theDanielJLewis/cross-app-comments-engine

#RunningWithScissors

I think I've solved the authentication challenge for #CrossAppComments, now that I understand how key pairs work.

I haven't pushed the changes to my GitHub repo, yet, because I'm still working out some kinks.

Okay, everyone! I'll post more thoughts once @dave moves my previous #CrossAppComments GitHub issue to a discussion, but I'm so excited about this that I want to share the source code and demo video now!

https://github.com/theDanielJLewis/cross-app-comments-engine

@adam

Guys, I have a working #crossappcomments system! It's fast, portable, platform-agnostic, developer-friendly, podcaster-friendly, and audience-friendly!

I'll share my source code and demo video soon!

I have a new idea for #CrossAppComments. But this time, I'll build a proof-of-concept app that will show how easy it is to use and support.

Plus, I'm going back to the fundamentals of podcasting in my approach to this.

I hope I make @adam proud and can get app-devs on board!

Hear me out: what if we make #crossappcomments use V4V?

Here's my proposal: https://github.com/Podcastindex-org/podcast-namespace/discussions/503

@brianoflondon Then we should definitely push for #boostagrams to appear in #crossappcomments.

@adam @dave The <comments> tag is used by nearly every WordPress website. So that means it's already in the 80K+ PowerPress/Seriously Simple Podcasting feeds. I advocated for building #CrossAppComments on that in the beginning of the idea.

(Can you tell I'm catching up and listening to episode 115?)

The biggest benefit I think this approach would bring would be simple adoption, which seems to be what's holding back development on #CrossAppComments anyway.

It would be a breeze to integrate this with WordPress comments or a standalone system (you'd need only a listener webhook and a JSON feed of existing comments). It would also make the data highly portable, in case a podcaster wants to move from one provider to another.

#CrossAppComments: I think we need to step back and simplify things.

Instead of trying to integrate a complicated technology, why don't we simply make it a <podcast:webhook> endpoint that receives a particular JSON payload from the app, and the app will be authorized by its own key in Podcast Index's GitHub repo?

This would make it much easier for hosting providers, app-devs, WordPress sites, and more to integrate the comments, while still allowing hosts the moderation abilities they need.

Anyone knows of podcast client besides #podverse that supports #crossappcomments? Having trouble testing the socialinteract tag with peertube comments.

I had a thought about #CrossAppComments today. Wouldn't it be cool if they could be grouped by chapters?

I know a timestamp comment can be handy, but also sometimes _too_ specific. Like a listener might want to comment on the whole section, not only a single sentence.

Combine this with my proposal for expanding chapter features (https://github.com/Podcastindex-org/podcast-namespace/issues/400) and chapters could show those specific comments during playback of that chapter!