Most web clients should just switch to nostr.ts for a better performance. nostr.ts provides native connection pooling and easy reconnection. It also separtes network from event computation. A storage abstraction layer is coming to nostr.ts shortly as well (by extracting from Blowater) The slowness of many web clients are just unbearable once you leave that tab open for hours. Blowater can be left open overnight and it still works. Another reason for the slowness might be caused by the O(n^2) algorithm for followers. Blowater will implement a O(n) follower/following algorithm and submit a NIP to fix it once for all. I will submit the NIP after Blowater can support 100,000+ events locally and 1000+ social graphs.

Just added this beautiful coverage report

I would like to pay a UI designer to refine the UI of Blowater a bit, anyone interested?

GitHub

Release 1.2.0 · waterblower/nostr.ts

Full Changelog: 1.1.1...1.2.0

is released

What should be the de facto Zapertising amount? My current is 21, but it's cheap. 21 represents the 2100M Bitcoin limits. 42 is also a nice default amount because it's the answer of the universe. I can also go 32 or 64 for obvious programming reasons. What do you think? Also, Zapvertising or Zapertising? I vote for #Zapertising

Accidentally clicked & discovered that this light bubble can change color theme to dark mode. @hodlbod It was so invisible or maybe I'm blind.

Zapertising doesn't work very well with the current client UI design. Many clients atm doesn't show the comment of the zap message so that unless the user checks their wallet, they won't know what's going on.

Lamport Timestamp has been implemented and it's awesome! I set my phone's time to a day ago and talking to my computer, the DM order is correct!