Cross-app comments - in the board meeting #423
Replies: 6 comments 6 replies
-
My view is that any comments system for podcasting MUST include boosts. However on reflection I believe the the spec for my original idea for Lightning Comments is not suitable and since March we have also updated the comments architecture within Fountain so it is outdated. I have therefore closed that issue. My view is that nostr is actually very suitable for what we need and I would advocate going in this direction. I plan to spend some time on this to figure out what it would look like and demonstrating it in Fountain. |
Beta Was this translation helpful? Give feedback.
-
Hi James Podfans has implemented Boostergrams and integrated them with the Alby API. So users can pay for their boosts but also we can pull in any other boostergrams from other apps that support WebLN which is acting as a central repository. Tools like Saturn and this new Boostergram viewer https://boostagram-viewer-lnd.albylabs.com/ shows all the boostergrams. Boosts may be a better way for all Podcast Apps to implement a comment system and share them, so all apps can see the same boosts. Today most podcast users are struggling to understand wallets, sats and boosts. Having a secondary comments system via ActivityPub may cause further confusion. Like Oscar mentioned, I am reading about NOSTR and NIP-05 and still haven't fully understood what they are and how they may be useful when applied to Podcasting. These blog posts from Alby might help.
However this tweet today from Lyle Pratt from Vida piqued my interest. https://twitter.com/lylepratt/status/1608308619031756803?s=20&t=zr0bQaZCPynePMgxn3k5qg - "now your @VIDAislive username is a working Nostr NIP-05 validation address, a lightning payment address, and also a working email address." |
Beta Was this translation helpful? Give feedback.
-
@samsethi The boostagram viewer only works with the getalby extension that is connected to a standalone node, not the stock getalby wallet. @jamescridland I am staunchly against "by $5 get 500 comments" that is NOT value4value. It should remain open to the sender. @samsethi & @jamescridland Please also consider appropriate disclosures if you are commenting on a service or product you are an advisor for. |
Beta Was this translation helpful? Give feedback.
-
Hmm, I don't get the hair-on-fire when it comes to this topic. We have a good spec, and quite fortunate that now we have hundreds of thousands of new users on that platform (ActivityPub), this is the right time to double down on that. It seems critical to me that any successful open comment standard for podcasting not be gated by any particular crypto token, or a crypto token at all - they should all federate equally via AP. Nothing is stopping servers and apps from integrating this today - just give it some time, it's not an easy spec and now there are hundreds of eyes on it - there will be other new apps and tools on the scene in the new year... Happy new year! |
Beta Was this translation helpful? Give feedback.
-
As both a listener who boosts most shows I consume and a podcaster, I absolutely want to see cross app comments. My ideal scenario is that it is centered on ActivityPub and that boostagrams are bridged to AP like Dave mentions here: As @johnspurlock said, the ability to comment should not be predicated on paying money (or sats). Additionally, devs such as Marco from Overcast have made it clear they don’t want to bring boosts to their apps… tying cross app comments to crypto exclusively significantly limits the field of apps that would consider participating, and the number of people who’d potentially engage. If we want to build features Apple & Spotify don’t have, we should strive to have those features available in as many podcast apps as possible. |
Beta Was this translation helpful? Give feedback.
-
I like the way that live chat works in YouTube or Twitch: regular chat messages are mixed in with "superchats" that include money. That's the kind of experience I'd love to see in cross-app comments, only time-shifted instead of live. (But live-refresh for comments would be great!) |
Beta Was this translation helpful? Give feedback.
-
A strange listen this week to the board meeting (Dec 23), as Adam says that nobody wants cross-app comments, and that it seems impossible to do.
I thought it might be interesting to précis where we are and posit some ideas on where we should be going.
The user need
As a developer, I want to ensure that my podcast app offers features that bring people to my app and keep them using them. What will work for me best is features that are not available in Apple or Spotify - that will make listeners switch to my app because I support it and they don't. Ideally, I'd like to see features that offer me some kind of opportunity for revenue generation, too.
As a podcaster, I want to hear from my listeners. It's lonely making podcasts. Feedback helps me know that there are people out there listening to my work, and keeps me focused on them.
As a listener, I want to contribute to the show with my thoughts and views. I'd like to do that in the place where I'm listening to the show - not
As a podcast host, the biggest risk to my business is that people get bored of podcasting and stop producing a podcast. Anything that helps me retain a customer is an investment into my longevity as a podcast host. That could be encouraging my customers to keep podcasting; or be offering a product or service that my competitors do not produce.
The internet is littered with examples of comments - whether for YouTube videos, podcasts or news articles. I would suggest that it is evidence that it is a feature that is wanted by all parts of the podcasting ecosystem.
Where we are
We have:
socialInteract
. This proposal appears to require use of all of activitypub, twitter, and lightning, or alternatively requires use of one of these protocols (it's not clear from the specification whether you can "support"socialInteract
if you only have support for one of these proposals. The tag also included other commenting systems, including Facebook and xmpp, but has been pruned back.Three separate commenting systems - but wait, there's always time for a fourth!
But, as evidenced by the last twenty minutes of the board meeting, the last five minutes of Podnews Weekly Review, or the first five minutes of The New Media Show, we already have a de-facto commenting system: a boostagram, sent by listeners. These "comments" are sent directly to the podcaster, who reads them out in the next show (or, in Podnews Daily's case, never reads them out because it doesn't fit the output).
And, as Adam points out as soon as he says that nobody wants comments...
So, as Adam says, we already have a commenting system which:
a) listeners are already using
b) is "always positive" for podcast hosts
c) that has spam filtering built-in (because who wants to pay to spam)
d) that puts money into the podcasting ecosystem.
A proposal for it was put into the public Github in March as to how this might formally work - a JSON end-point which pulls in the boosts for that episode, allowing any app to display them.
There are issues - potential centralisation of this service is one of them; which could be avoided by either:
a) 1% split in the show to a commenting system would give that the detail needed to produce a JSON file of all the comments
b) an API from the creator's lightning wallet (like Alby) would enable lightning comments. Alby has an authenticated API that would do the trick; but it would ideally need to be unauthenticated, opt-in, and filtered. A third party could potentially do that work.
The discussion was warmly welcomed by some of us - but appeared to have stalled at the end of March. Neither Dave nor Adam have made any comments in the proposal.
If it's a bad idea, it would be great to have that discussion as to why, rather than pronouncing that cross-app comments are dead. I'm not sure they are.
(As a disclaimer: more than six months after Oscar's initial proposal, I became an advisor to Fountain; but we've not actually talked about this).
Beta Was this translation helpful? Give feedback.
All reactions