Nostr Web Client

Very inspiring. Lots of great ideas.

Would you actually consider an ecash wallet? I just like that you can use them without privately without signup or an api key

You can even just use the lightning features if you think the ecash portion adds too much complexity for users

For the AI service, you could easily just clone the Shakespeare AI repo and run your own with an OpenRouter key and lightning address for payment

I haven’t built everything I want yet, but I really think AI could help with content discovery, search, article translation, converting long form articles to short podcasts, etc.

Reply to this note

Please Login to reply.

Discussion

Viktor 2w ago

native wallet slaps, ecash or gtfo. the no-kyc, no-api flow is exactly what nostr needs. keep the ecash option buried in advanced settings if you're worried about normies.

totally down to run our own ai infra. been eyeing openrouter since it's plug-and-play with lightning, way better than sucking on openai's teat

content discovery is trash rn - train a model on just your follows' reactions (not global spam) and you'll actually get good signal. translation + podcast generation from 10min articles would be chef's kiss

Cody 2w ago 💬 1

At the moment, I don’t have plans to integrate an ecash wallet. I don’t think it’s particularly safe.

For example, I could release a DM app that secretly asks users to sign transfer events, and I could steal their funds with very little effort. In today’s DM apps, users already have to approve a lot of encryption/decryption operations just to make things work, so they’re basically forced to approve everything.

In your demo video, the feature that interested me the most was using AI to generate images directly inside the editor, it looks extremely useful.

lemon 2w ago 💬 1

Credit goes to nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpp4mhxue69uhhjctzw5hx6egpp4mhxue69uhkummn9ekx7mqkdk3r2 for the image generator

Could you elaborate on the wallet security?

If I’m understanding correctly: current DM implementations require frequent prompts from signers so users typically accept nip44 decryption by default/trust the site. Therefore a bad actor could leverage this for to take advantage of nip61 nutzaps?

Cody 2w ago 💬 1

Your understanding is the same as mine. Of course, I might also be mistaken, since I haven’t looked very closely at NIP-61.

If my understanding is correct, this problem doesn’t only exist in DM apps. In reality, many users completely trust the nostr clients they use, it’s just more obvious in DM apps in particular. That’s why I’m not very supportive of using nostr private keys to manage wallets.

HoloKat 2w ago

Same reason I don’t want built in wallets. As soon as you do it - everyone’s money is your responsibility. And I only vibe code - a big nope for handling money.