After getting praise from the scifi community, I tried watching "Invasion" AGAIN. Still sucks IMHO.

New version of Pumpstr is out (pumpstr.coinmachin.es), a massive upgrade, please try to hold off pumping until I can verify everything is ok: RELEASE NOTES 2025-05-30 Previously a lot of content was handled server side. This fits poorly with how Nostr was meant to be. So Pumpstr have received massive improvements where it now behaves like a "proper" client app, running inside the browser as a PWA (progressive web app). This means the server is mostly there to allow clients to download the app. All content caching (user profiles and events) is now also done client side only. I added a "Relay Stats" choice in the sidebar which will show you stats and connection status for your relays. This can be useful to find and remove non-functional relays from your relay list. I added a "Storage Stats" choice in the sidebar which shows you the number of user profiles and events being cached in the client. The client will auto refresh client profiles every hour. The initial feeds list always get built with live data from relays, but mentioned events (like for replies and reposts) will get persisted to speed up post rendering. Eventually the client will do automatic cleanups to avoid profiles and events piling up endlessly, typically by removing unused profiles and events after a week or two. If you hide this message by clicking the X icon, you can get it back by selecting "Show sys.msg" from the sidebar.

Testing post-refactoring pumps (again), please leave this post alone.

As soon as remaining bugs from massive improvements to the Nostr client "Pumpstr" stabilizes (

Pump! Nostr "zaps" using BCH

I need to re-introduce mechanisms to share pump actions. Promoting these for Pumpstr users is one thing, but to gain traction there needs to be ways for non-Pumpstr users to see that sats are flying as well. Suggestions are welcome! Sharing a screenshot from "threaded view" with new app header on iOS/iPhone, just because!

As a developer, getting started writing a Nostr client can be a bit challenging. Nostr is supposed to be decentralized, connecting to whatever relays the user specifies. Weirdly enough, the user preferred relay lists lives on other relays. Which ones? You don't know. So even as Nostr users are supposed to maintain their own lists of preferred relays, a Nostr client app still needs to have some kind of dynamic/hardcoded list of relays to get that user preferred relay list. In addition, whatever list you start with, lists are dynamic. They come and go. Which means both as a Nostr developer and as a Nostr user, you need to do some upkeep to keep everything working properly over time. This is one area where Nostr could definitively improve. For all parties involved.

So another rewrite of the relay connection manager for Pumpstr and making the client work more independently of the server in preparation for a downloadable app. Not live yet, but soon!

What are the odds? I was just debugging some poor state management leading to pumps being accumulated wrongly. And simulatenously users start pumping the very post I used for a small test pump. Debugging a live service can be challenging. Still appreciated though. @Crypto Is Cash - Bitcoin for Small Businesses & Their Customers

I now have a Nostr client running, Pumpstr, that supports reading, replying and reposting. Let's see if pumps are still working (I will try to pump this post). If so, another nice set of features would be to display aggregated likes and reposts, in addition to pumps. Looks like many clients do not do this until a post is selected, so it may be a bit heavy on the relays for the "all posts" view. Time will show.

Are there any statistics on Nostr client popularity? I'm primarly interested in the open source web based ones for now, as I need to start adding client support for "Pump!" (Zap using BCH). I'm also thinking about maybe doing a plugin first instead. Opinions?

Pump! Nostr "zaps" using BCH

What do I need to do to get a "BCH payment receipt" "kind type", similar to kind 9735 "zap receipt"? Assuming I need to demonstrate working code and/or write a complete NIP first, any suggestions on what "kind" to use while testing?

So I'm thinking of doing the unspeakable. Adding support for layer 1 zapping to Nostr using BCH. Hate me gently.