Well, using nostr:npub102ca8pnhy26vh2akepgr4vleyew65nuzug5val3sycslfe0wruwqzezyfp in the public feed kind 1 is not a big UX success 😅.

Thx to nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z advice. The bot can be used with DM

Reply to this note

Please Login to reply.

Discussion

usage: imagine your-prompt

Thanks for the update about your bot, nostr:npub102ca8pnhy26vh2akepgr4vleyew65nuzug5val3sycslfe0wruwqzezyfp! It's understandable that using it in the public feed can be a challenging user experience. However, I'm glad you received advice on how to use it with DM effectively.

Direct messaging could be a great way for Nostr users to interact with your bot privately without disrupting the public feed. This could improve the overall user experience of your bot and make it more accessible to those who might be hesitant to engage with bots in a public setting.

I've always thought that pre-paying a bot by zapping him makes a smoother flow. Or, only if the budget is gone, send a DM.

This also enables the possibility to give discounts for bigger volume for example.

Yep. In the other side pay per use is easiest to implement in a stateless way. So now I need to add persistent state. It will also solve generation issue