Recent searches
Search options
Administered by:
Does the Nostr community seem like they even care about value splits? The value splits seem so crucial to moving forward with any v4v model that isn't a simple paid like of a comment, and it's hard for me to get behind something that doesn't support value splits after being convinced of how valuable they are.
@StevenB nostr will never be a solid distribution system or model.
It has plenty of uses and I use it myself.
The last board meeting proved to me we are on the right path.
I've been talking to music people (artists and business) and am receiving good and positive feedback.
Once you explain how the value block circumvents the publishing and performance institutions, people really take notice.
nostr will never get past the "tipping" stage, and has zero incentives for developers.
@StevenB@podcastindex.socialWhat did you have in mind concerning AP?
@StevenB @adam I don't know much about Podcasting 2.0, but it looks like there are RSS extensions, and payment infrastructure built on top of that. So I'm wondering, how does AP fit into Podcasting 2.0, if at all? If there is an overlap between Fediverse and what @adam is doing, particularly in the domain of payments, I'd be interested to learn more about that
Yeah, there is an overlap. We're calling it cross-app comments, and it's using the socialInteract RSS tag.
Podverse has them in their app. https://podverse.fm/episode/dTWX_aqL- Click on the comments, and you'll see this.
Same thing with the Podcast Index page.
https://podcastindex.org/podcast/920666
Everything there is from AP.
One issue apps are having is how to make it easy to post comments from within the app. The displaying comments has been solved, but next is in-app replies to comments.
@StevenB @adam
I found this: https://github.com/Podcastindex-org/podcast-namespace/blob/main/value/value.md. What do you think about exposing payment information to ActivityPub users?
For example: ActivityPub representation of a podcast episode may contain a tag analogous to podcast:value tag. If commenter uses an app that recognizes this tag and the app supports specified payment method, he would be able to send a payment to the creator directly from that app (e.g. Mastodon).
I boosted it to the larger PC2.0 community. Someone who knows more about the AP protocol may be able to give a better answer then me.
Not directly related but
1) We're having similar talks with @John_Livingston regarding aligning chat specifications between the Podcast XML namespace and ActivityPub. I wonder if we could come up with some kind of "best practices" for going between XML Schema <-> JSON-LD?
2) Similarly, @John_Livingston mentioned PeerTube 5.1.0 allows plugins to modify the ActivityPub object which would allow this functionally, once we decide what it could be
CC @dave @errhead
@StevenB @adam
Also the @Castopod team was working on this but I think it stalled for now https://github.com/Podcastindex-org/activitypub-spec-work
@agates @dave @adam @StevenB @John_Livingston Yes, coming up with best practices is a good idea, otherwise we may end up with multiple incompatible implementations. I recommend using FEP process for coordination. It's a good way to gather feedback from potential implementers and a wider AP community.
@silverpill
Yes, in my case i plan to propose a FEP very soon!
@John_Livingston @dave @adam @StevenB @agates A new proposal has been submitted that describes how to map non-ActivityPub entities to ActivityPub objects: FEP-fffd: Proxy Objects.
I thought it might be relevant to apps supporting both RSS and AP. Discussion: https://socialhub.activitypub.rocks/t/fep-fffd-proxy-objects/3172