#[2]
Anyone else having issues zapping with Zeus from Damus? Looking at Damus v1.2.0 (5) and Zeus v0.7.3.
Worked fine for me just now.
Challenging to click through several links in longer posts. It's like it's caching the previous post, and I have to back up and try a couple times before it goes to the right note.
What does it do? Broadcast someone else’s note to my connected relays?
Been reading a book about memory techniques, and the main idea is that imagery/storytelling is the key to recalling information. The more vivid and absurd of an association you make with some concept, the easier it is to remember and synthesize later.
Preliterate civilizations would form elaborate stories/lore to encode important information and insights about local food, geography, tradition, etc because those stories are easier to remember and communicate between generations.
So when is someone going to create a "Nostr Hub" - a live dashboard that I can throw on a separate monitor? Would love to be able to plug in an npub and get an auto-updating view of various metrics.
Could include a badge showcase, zap counter, most zapped/liked post, rolling feed of engagement, etc.
Need a bot that DMs a punch link to people if they zap over a given threshold. Room entrance fees 🤔
The main issue is if you have a budget set on something like Alby, you may zap more than intended. If you’re explicitly checking and approving each zap, you should be fine.
Eventually, I'd expect to see something where devs post a particular kind of nostr event with release notes for each build (including a digital signature, so you know it's legit). A particular client could allow you to watch for that message type (not sure if it'd be a dedicated note kind, posted to a specific relay, or just "any post from x npub"). If you see that message, automatically send a zap.
Could function similarly to value-for-value podcasting, except you'd send payments on nostr event trigger (e.g., new release announcement note from verified dev), rather than per-minute. You could still set a configurable number of sats to zap per software/dev, set budgets, etc., but it seems very doable if we standardize on some sort of process. I'm sure people are already working on something like that.
Sounds like Breez’s cloud architecture would do what you want, right?
Grilled pork chops 🐖
It’s getting a little too easy to zap all my sats away 🪫
npub1m72pdynrlmrpstrxu49k828r5xjlqc9hgtz9zfmy4m30u40uqxgsgkjxux
npub1m72pdynrlmrpstrxu49k828r5xjlqc9hgtz9zfmy4m30u40uqxgsgkjxux
💩 🛡️