Coding Interruptus

Building the next v4v.app v2

This is a value for value post: see the explanation in the footer.

Doing the Work

I started off the day doing the work.

I got the all import Dark Mode selector on the site;
a Language selector (because I'm determined to make the next site in Spanish and whatever other languages the Hive team can help me with);
I added an indicator for whether Keychain is installed;
I installed the hive-tx-js library by Hive account@mahdiyari

Hive-tx-js Needs a bit more Discussion

I say I installed hive-tx-js but actually I don't think I did. I tried the yarn add hive-tx way of doing this but try as I might I couldn't find the right magic spell to get that into my code.

In the end I copied a file called hive-tx.min.js which I got from Github into the assets folder on my site and when I want to use it I include import "src/assets/hive-tx.min.js" in my code.

I'd love to know if there is a better way to do this and I really do need to learn a whole lot more about how Javascript handles 3rd party libraries and importing. I'm pretty clueless about this stuff right now but I'll learn.

And then the interruption

At some point this afternoon I started listening to the second half of the Hive account@cttpodcast from Saturday night which I was on for the first hour but then dropped off.

I started listening on a newly released Beta version of the Fountain Podcasting App. As I listened I started streaming sats and after a couple of payments I noticed that my Telegram internal notification system was going nuts with errors:

Behind the Scenes on V4V for Podcasters

This system has been very reliable for over a year now so this is kinda rare.

That itemID is supposed to be an integer (int) but Fountain's new version was sending this string.

Fortunately I jumped on Podcastindex.social and Oscar Merry responded very quickly and fixed this immediately. This left me with a few messed up payments in my database and because these have already been sent by Fountain and received by my Lightning Node I can't really change them.

I'm actually stuck now permanently accounting for this mistake in my code (at least until I clear down my Lightning Node's database at some point which I will probably have to do one day).

Special code for special issues

That's all for today

I leave you with the show we recorded on Saturday night. I think the discussion I was involved in at the start with Hive account@theycallmedan and Hive account@starkerz is particularly important for a whole bunch of Bitcoin Maxis who'll never listen to it. Their loss.

Value for Value

For the last few months while building Hive account@v4vapp I was generously supported by the DHF. Going forward I have a much more modest support which covers direct server costs and a little of my time.

If you appreciate the work I do on and around Hive, you can express this directly: upvoting posts on Hive is great. Also consider a direct donation (there's a Tip button on Hive or a Lightning Address) on all my posts.

Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
Vote for Brianoflondon's Witness KeyChain or HiveSigner

Send Lightning to Me!