Post B2vLuZGXupPWIxYSB6 by james@bne.social
(DIR) More posts by james@bne.social
(DIR) Post #B2qRZ1mmpHxiK0wnw0 by james@bne.social
2026-01-31T10:57:31Z
0 likes, 0 repeats
Building a thing after I randomly mentioned it to @samsethi in the last PWR - for showing streaming sats payments to a Strike account."Runway" is a kind of Helipad but for Strike payments. Writing it entirely in JavaScript, client-side, so I can't see into your own Strike account, and so the code is open and readable. I need to build the code to parse the payment details properly (it's currently ugly JSON) but it works.Will build a configurable "delimiter" (probably set for "this time last week"), as well as automatically get payment details of boosts. For Podcast Guru, who don't yet support the spec, that means I'll have to assume that more than 200 sats is a boost.https://podnews.net/runway if you want to play along. As you'll see from the API details, it's safe from me emptying your account! But there's not much error handling here yet.@dave @merryoscar @adam
(DIR) Post #B2qRZ3CLZk0ChZujPk by dave@podcastindex.social
2026-01-31T13:11:01Z
0 likes, 0 repeats
@james @samsethi @merryoscar @adam Awesome!I wonder if @podcastguru can help with what they are sending.
(DIR) Post #B2qU29i6drO3Cnm7jk by podcastguru@podcastindex.social
2026-01-31T13:38:43Z
0 likes, 0 repeats
@dave @james @samsethi @merryoscar @adam looking into it.
(DIR) Post #B2qUumDNhQJ2GKRua0 by adam@podcastindex.social
2026-01-31T13:48:35Z
0 likes, 0 repeats
@james @samsethi @dave @merryoscar VERY cool James!
(DIR) Post #B2uUrkHdCXJ82Gpbyy by james@bne.social
2026-02-01T04:10:21Z
0 likes, 1 repeats
@samsethi @dave @merryoscar @adam @podcastguru Progress! Runway - Helipad for Strike accounts - now displays boosts (and streaming payments) on demand, by hitting "proxy parse". Individual payment information currently has to be fetched by my own server, because of CORS issues.Here is an example - showing a boost from Podcast Guru and Fountain; and streaming sats from Podcast Guru. (TrueFans is currently broken for lightning payments, I hope it comes back soon, no pressure). These are the only apps currently supporting streaming or boosts, as I understand it.https://podnews.net/runway to play, if you have a Strike account yourself.I guess I *could* load these into a local database in localStorage, if I can work out how to do that. Want to keep it as clearly private as possible.
(DIR) Post #B2ulILvFTuPBZC4U4G by adam@podcastindex.social
2026-02-02T15:10:54Z
0 likes, 0 repeats
@james @samsethi @dave @merryoscar I get a lot of transactions. Being able to filter out below a certain level would be helpful. Also, are the apps sending the total amount information? Or is runway only able to get the amount received?
(DIR) Post #B2vLuZGXupPWIxYSB6 by james@bne.social
2026-02-02T22:01:08Z
0 likes, 0 repeats
@adam @samsethi @dave @merryoscar Working on pulling the info into a database (local to your browser); and then filtering only boosts, etc.Total payment info is in the JSON, yes - again, hoping to locally database that for speed.
(DIR) Post #B2yPnDKi2svPXr8Ak4 by james@bne.social
2026-02-04T09:28:47Z
0 likes, 0 repeats
@adam @samsethi @dave @merryoscar @francosolerio Update:https://podnews.net/runway is now loading payments into your browser's local storage, if not actually doing anything with that yet. It'll get the first two weeks when you first connect it (and when you next connect it, should only get newer ones). That will make filtering below a certain level very possible, I think.The calls to payment info (which are now mostly direct from the browser) will also go into your local database as well.> I get a lot of transactions.Any guesses how many per week, so I know what kind of size?
(DIR) Post #B2yrSu4MkrpKj0ad2e by adam@podcastindex.social
2026-02-04T14:38:56Z
0 likes, 0 repeats
@james @samsethi @dave @merryoscar @francosolerio Thousands
(DIR) Post #B2zmJEqOM5sBeDaMPg by james@bne.social
2026-02-05T01:15:38Z
0 likes, 0 repeats
@adam OK! It should be performant enough I think. Let’s see.
(DIR) Post #B30r83dKOFAYcbvGxk by adam@podcastindex.social
2026-02-05T13:44:36Z
0 likes, 0 repeats
@james @samsethi @dave @merryoscar @francosolerio Really love what you're doing here James. Export to csv in the future?
(DIR) Post #B31loLIOhsTWzps9Uu by james@bne.social
2026-02-06T00:19:35Z
0 likes, 0 repeats
@adam @samsethi @dave @francosolerio Sure, why not... ;)It's now writing into the database, and then reading from it, so I've got that bit done. Current UI isn't very clear, but will fix that.We could do with a look at the Boostbox API to address the issue with the x-rss-payment header and browser requests. Or, to issue a 'wontfix' if it's not seen as important (that's cool too).https://github.com/noblepayne/boostbox/issues/8#issue-3894858104@noblepayne @merryoscar
(DIR) Post #B32vGOzldg7DK9ZaNc by james@bne.social
2026-02-06T00:35:59Z
0 likes, 0 repeats
@adam CSV export was quite easy to do. Now live - with three colums: timestamp, sats paid (i.e. what you got), and a metadata URL. Best work on the tool to properly pull in the big list of payments.
(DIR) Post #B32vGQ3LhqZgbYFxbM by james@bne.social
2026-02-06T00:37:34Z
0 likes, 0 repeats
@adam My guess is that you'd want a better date/time than a unixtime...
(DIR) Post #B32vGQxMLbNTPGSgu8 by adam@podcastindex.social
2026-02-06T13:40:19Z
0 likes, 0 repeats
@james Looking good James!Yes, local time would be nice, but not top priority.I broke my phone yesterday before I could read your signal message. Please resend so I can retrieve it on the bakcup!
(DIR) Post #B32vM5Zkkm3Kph7ILA by algrid@podcastindex.social
2026-01-31T19:23:54Z
0 likes, 0 repeats
@podcastguru @dave @james @samsethi @merryoscar @adam If I recall correctly we have a boost vs stream flag in our metadata (basically it’s the same metadata that’s going with keysend payments). If that helps..
(DIR) Post #B32vM6xXbofv7lFo3c by james@bne.social
2026-01-31T21:40:26Z
0 likes, 0 repeats
@algrid @podcastguru @dave @samsethi @merryoscar @adam Your ones just send “V4V” at the start of the payment metadata; rather than an indication of whether it’s a boost or a stream like Oscar’s. An indication here would help us make a decision on which to fetch.
(DIR) Post #B32vM879JZxGhqkzfk by algrid@podcastindex.social
2026-01-31T22:20:07Z
0 likes, 0 repeats
@james @podcastguru @dave @samsethi @merryoscar @adam yes, in our case the information is inside the json that you can fetch by accessing the url following V4V. The description field can be too short to put actual data there, that’s why we only put a url there.
(DIR) Post #B32vM99JT1HPuqmEgS by james@bne.social
2026-02-01T03:01:17Z
0 likes, 0 repeats
@algrid @podcastguru Would you mind enabling CORS on the JSON file? > Access to fetch at 'https://boost.podcastguru.io/boost/KhrpuJh7' from origin 'https://podnews.net' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
(DIR) Post #B32vM9xITBGKPsA9aq by algrid@podcastindex.social
2026-02-02T13:13:15Z
0 likes, 0 repeats
@james @podcastguru yes, I guess we should be able to enable CORS there, thanks for the reminder. And we'll see what we can do about the data format. Not sure about completely changing it to the Fountain spec, but we can try to include a hint into the bolt11 description to distinguish boost vs stream payments. Like V4VB:... or V4VS:... prefix depending on the case or something like that.
(DIR) Post #B32vMAn3Mkf90ONUGW by merryoscar@podcastindex.social
2026-02-02T13:31:14Z
0 likes, 1 repeats
@algrid @james @podcastguru @algrid I know it's probably annoying but would it be a massive amount of work for you guys to switch to the same spec Fountain and Castamatic are using?https://github.com/Podcastindex-org/podcast-namespace/pull/734I think we would really turn a corner if we could all align here!
(DIR) Post #B34lLpBZ55Tam3xS2y by james@bne.social
2026-02-07T10:58:33Z
0 likes, 0 repeats
@adam I've added a datetime field in there, in ISO8601 format. "Local time" is the default in the UX for Runway, but not for this export (because it's quite hard to get the export to be consistent if using locales). Sender details (and type) is there if we have it.