Hey Kids
-
I'm vibecoding so I just drop in GitHub repos and hope for the best but the Bitcoin Connect stuff is what really got the ball rolling for me but you already have the Alby stuff working in Podverse web.
This also does NWC that Oscar and Franco have been working on but that's still very early and has a lot of issues still.
@ChadF @martin wow, that's a lot of apps in Bitcoin Connect. I guess they don't all use WebLN, and therefore have different steps for connecting your wallet to the page?
I have not gone through the NWC payment flow yet, so I don't have good mental model of that works.
Also, the UX of stablekraft.app is cool. Has a nice music library feel to it.
If you ever have coding questions I may be able to help with, feel free to reach out. I'm on Discord and Matrix in addition to here.
-
@ChadF @martin wow, that's a lot of apps in Bitcoin Connect. I guess they don't all use WebLN, and therefore have different steps for connecting your wallet to the page?
I have not gone through the NWC payment flow yet, so I don't have good mental model of that works.
Also, the UX of stablekraft.app is cool. Has a nice music library feel to it.
If you ever have coding questions I may be able to help with, feel free to reach out. I'm on Discord and Matrix in addition to here.
Most apps listed in Bitcoin Connect are just NWC connections and when you click on them it gives you detailed instructions on how to connect them which is nice but kind of misleading.
Those wallets also don't support keysend and most feeds have keysend addresses still so it's a nonstarter anyways but I'm just throwing everything at the wall to see what sticks.
Thanks man.
-
-
-
I've been thinking about this and I know even know what to tell you guys tbh. TLDR Alby isn't "free" anymore and we need an alternative and it's not going well. We've been looking for an alternative for years and well doesn't look like one really exist.
Good news is that Alby still does it all and more but requires resources from the users.
Since you guys are talking web I think just using the Alby extension is still the way to go.
@ChadF @mitch @martin Look into NWC. It's not that hard and opens up the possibility to connect many different wallets. https://github.com/getAlby/awesome-nwc?tab=readme-ov-file
-
Most apps listed in Bitcoin Connect are just NWC connections and when you click on them it gives you detailed instructions on how to connect them which is nice but kind of misleading.
Those wallets also don't support keysend and most feeds have keysend addresses still so it's a nonstarter anyways but I'm just throwing everything at the wall to see what sticks.
Thanks man.
@ChadF @mitch @martin that's the reason many consider keysend “deprecated”. It still works great, but the vast majority of wallets don't support it. So we have two paths at this time: stay in an Alby-only world (I love them, but most users won't install AlbyHub to use a podcast app), or embrace LNAddress and extend it so it brings metadata. I'm chosing the second, and added NWC + Boostbox API to Castamatic.
-
@ChadF @mitch @martin that's the reason many consider keysend “deprecated”. It still works great, but the vast majority of wallets don't support it. So we have two paths at this time: stay in an Alby-only world (I love them, but most users won't install AlbyHub to use a podcast app), or embrace LNAddress and extend it so it brings metadata. I'm chosing the second, and added NWC + Boostbox API to Castamatic.
@francosolerio @ChadF @mitch I am completely new to NWC/Boostbox. Can you give me the tl;dr and maybe a link to get started? How easy is it for the end user? What I loved about the early days of Alby etc. was that you could just buy satoshis for 20$ (or whatever) and then it was mostly plug and play.
-
@martin @ChadF @mitch BoostBox API is a way to comunicate and store the old metadata payload we used to include in keysend, but on a separate server. It's quite simple, you POST the json metadata to a server, and get back a url to include in the LnAddress/LNURLp payment comments. The recipient of the payment uses that url to GET the same json metadata.
-
@martin @ChadF @mitch BoostBox API is a way to comunicate and store the old metadata payload we used to include in keysend, but on a separate server. It's quite simple, you POST the json metadata to a server, and get back a url to include in the LnAddress/LNURLp payment comments. The recipient of the payment uses that url to GET the same json metadata.
@martin @ChadF @mitch For the user it's quite simple. Get any wallet you like (eg. Primal app gives you a NWC wallet for free if I remember correctly). Scan a QR code to connect app<->wallet. Then send boosts and stream sats as before.
AlbyHub can still be used via NWC.
Most difficult part for newbies IMHO is buying sats with USD, but that’s the same as before.
-
@martin keysend still works as it did back in the beginning, I believe.
A key difference between keysend and lnaddress, is that keysend lets you send metadata with the payment, but lnaddress does not.
lnaddress does however, allow you send a memo, and so some apps are now hosting their own "boost metadata" endpoints, and including a link to boost metadata in the memo of the payments.
Add rss::payment Metadata by MerryOscar · Pull Request #734 · Podcastindex-org/podcast-namespace
A wholistic rss namespace for podcasting. Contribute to Podcastindex-org/podcast-namespace development by creating an account on GitHub.
GitHub (github.com)
So keysend adoption appears to be fading, while lnaddress adoption is rising.
@mitch @martin From the podcast creator side, lnaddress is much easier than keysend. With lnaddress you can pay me with a payment to james@podnews.net - with keysend it’s a complex set of numbers that are not portable. Strike is just one app that is available that acts as a (free) payment wallet.
Both allow you to send metadata with the payment. The difference is the length of that metadata. With lnaddress you need to send a URL pointing to JSON; with keysend you can send the data with your payment. It’s not true to say “no data” - just “less data”.
The privacy remains similar - the URL containing the JSON is still a long, GUID-like URL, which like Google Photos is open but is quite difficult to guess.
Worth remembering that the podcast creator side is one part of this; and then there’s the podcast listener side (for apps). We need both to be easy to develop
for and for humans to achieve. -
P Podcasting shared this topic
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginWelcome To Podcasting.Chat!
This forum is for podcasters, podcast guests, and podcast enthusiasts alike to share tips, tricks, and their love of the medium.
This forum is fully federated, so you are able to contribute to any discussion here through your own software of choice (e.g. Mastodon, Misskey, Lemmy, Piefed, etc.). So you can sign up for an account here and it federates around the Fediverse. You can also follow feeds and topics from your other Fedi-enabled accounts.
Recent Posts
-
Do NOT verify your Linkedin profile. Here's why:
https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
-
@theDanielJLewis I did!
-
-
@js What about bitrates?
Just because that's the way those providers are encoding doesn't mean we all have to do the same.
Did you check the HLS segment lengths?
