What the highest priority thing for Nostr right now in your opinion?

Reply to this note

Please Login to reply.

Discussion

1. Scalability of infrastructure.

2. Great UX for new users.

Those can and should be developed at the same time.

Which infrastructure pieces you think need to become more scalable?

CDNs for media (like nostr.build)

And in general, sustainable revenue models for relays, API services (like yours), and CDNs

I also see us needing to build out other services, like Podstr

Great UX is 🔑

It will make it seemless, or make our job even harder. But at least, it can be a fun learning process.

Love your "profile progress" screen!

monetization ⚡️

if devs can't monetize their passion (fe nostr), they will give up.

Close 2nd. 😉 can’t monetize if people can’t use your app.

What are paths toward monetization that you think make the most sense? There are already zaps, zap splits, zap pools, subscriptions. Any of these? Anything else?

Marketplace fee splits. Subscriptions.

For subscriptions I’m thinking both sat subscriptions to locked content, but also client subscriptions. Can even just be stripe based.

There can also be relay subscriptions (for reading), since some clients now support relay-auth.

I see. For me it’s actually easier to pay a stripe subscription without having to fund my wallet all the time. I wouldn’t mind paying $8 for Damus for example. But I know Will said he wants to avoid dirty fiat 😂

I'm not against stripe/fiat. But those require long-term-ish subscriptions, so limit the range of business models.

Stripe might have an issue with zaps. I dunno if they will even play along? 🤷‍♂️

WDYM "issue w/ zaps" or "play along"? I'm not suggesting that we'd be able to zap w/ stripe, but some services could be paid w/ it.

Private messaging (including groupchats)

Why that?

Drives so much traffic outside of the clients.

Prime example was BTC Miami conference.

During the session, when there should be much more traffic and notes on Nostr, users actually moved to Telegram, where there was a group of 300+ people and all the updates and chats took place there.

Ok that makes sense now, agree!

Discovering new users and topics. Better reading reply threads.

Which client are you using for reading reply threads?

Is discovery on primal or nostr.band useful? What could be improved?

I’m using Damus. When I click into a conversation of replies and want to go back to the original thread it doesn’t take me there

simple micro apps that are super stable, documented decently so can be forked and others can carry the ball until at scale where monetization isn’t such a worry, and when one feature breaks it’s just one place instead of a super app feeling like a part is broke

which micro apps do you have in mind?

in this case, mostly like a simple feed reader, a simple direct messager, a simple notifications reader/receiver, just zap notifications, simple profile editor, simple global reader

ability to self host, but this way you not self hosting 2 sunset super clients one where the DM’s work and the other where you like the feed and notifications… you just have the working parts.

maybe there is a spec for both super host and micro app so one could piece together “widgets/plugin” but the spec also defines the host so it’s not just one host but anyone could also build a nostr “workstation”.

Build-your-own-app w/ a set of plugins/widgets sounds cool!