I tried before seeing this message. doesn't seem catastrophic. after hitting update, then clicking install in the dialog, it goes back to zapstore and indicates it's still on `0.2.3`. but otherwise it is still functional, and offers the same update again.
nostr will be the seed for our time's Republic of Letters
I mean that there is a legitimate reason to want to emit a rapid-fire stream of kind 30023 events, that being when a new RSS feed is onboarded to nostr.
so if that is a burden, it would be nice to sort out a way to allow the behavior and mitigate the burden.
one idea of how to do that would be to compensate the relay operator for the capacity to railgun a bunch of articles into their relay from time to time.
this is exactly what happens when you onboard an rss feed type of source. is operating your own relay the only reasonable way to get it done? maybe paying for higher rate limits?
well, I'm not aware of a site that will render a blog like site for a collection of articles published by an npub. I'm working on that.
why not an npub that publishes long form articles once a week?
gm 🌄 ☕
humanity is onboarding to bitcoin and nostr, this makes the future brighter than the past.
but the present is brightest of all, because we are lucky enough to be here, at this time, realizing that future is ours to build.
absolutely. each facet of a salt crystal is a square
what is the best practice for nostr CLIs accessing nsec's?
that did it, working smoothly now
cleared cache, reloaded, and I see the same result. (btw, this is not urgent for me, just hoping to be helpful in debugging)
The new nostr.watch looks really fancy 👀
https://cdn.hzrd149.com/284b314007e2de6f451ffd7bd019864a9694ce71e45c45e51482e12280c880b3.webp
hmm. I can get the legacy side working, but the next side loads a black background and a svelte favicon, but no visible elements.
