@alecksgates @ericpp I think it's easily solved with your <podcast:metaboost> specified API receiver. If that tag appears, the app knows to also push the boost metadata back out to the podcaster's specified API.

@alecksgates The apps are hosting this metadata service, but there's no reason why it couldn't be moved to the podcaster host and pointed to in the feed with your metaBoost tag.

That would work well if you're the main podcaster, but how would guests and musicians know where to find the info?

Musicians have their music played on many different music shows and podcasts. They would need some way to collect and aggregate that data.

@ericpp guests or musicians would just look up metadata from the show they are on. It's public. That's the point.

A metadata server could offer them accounts to check as well. That's an implementation detail.

But both the apps and the host could display the public metadata under a show.

Just like looking at comments on a YouTube video. That's the precedent being set with certain apps anyway.

@alecksgates Musicians don't know what shows their music is being played on. The music podcasts pick up and play whatever songs they want to from the index.

They would need to check pretty much every podcast/music podcast to see which one played their music.

@ericpp

Remote items make building a tool for that rather trivial if a music host wants to provide that functionality.

They still get paid either way.

@alecksgates The comments are honestly more important than the payments for the artists. They like to know that people are listening and enjoying their music.

@ericpp

Well, the right answer to comments is to use a comment system. We already have that.

<podcast:socialInteract>

I can't help that we abused payments for comments up to this point. I've said this from the beginning.

@alecksgates Nostr sort of got that right by having the payment sent to the wallet and the metadata sent back to Nostr. They still comingle the two in part of the LNURL process though.

It's also easier to do that with a social network where you can look up people in a social graph and send them a message/data.

We don't really have an equivalent other than the socialInteract tag. Those can change over time and vary across feeds.

@alecksgates But I guess we do have semi-stable identifiers in the form of Lightning wallets. That's probably why we've abused it for this manner.

The Lightning wallet is our social network.

@ericpp Speak for yourself. I'm writing to you via Mastodon.

@alecksgates I mean, it's not the only one.

@ericpp @dave @alecksgates I didn’t know about the metaboost tag. Seems like exactly what we’d need to support LNURL without losing boost message data.

Boost message data should probably be pulled out of the keysend implementations anyway since it’s so restrictive.

Podverse might be open to hosting a metaboost API as well. I don’t know how we’d manage the spam and abuse problems though…Alecks if you have ideas and would ever be up to talking about them I’d appreciate it.

@dave

for a moment I thought you sold out to Meta (formerly known as Facebook)

@csb @dave sold out to Pedocoin... It's baked into PC 2.0... Should've made payments more flexible... Now you're tired to a payment system that was almost certainly the product of an intelligence agency...

@admin @csb The <podcast:value> tag can hold any payment information. It isn't tied to any particular one.