I’m hosting #[0]​ author of https://nostr.band for a video chat today. What topics should we add to the agenda?

1) Meta-apps, App Store replacement, Micro-app containers

2) How should relay discovery and surfacing work in the UI

3) The joy of Nostr development

4) Ads models that might work on Nostr

Reply to this note

Please Login to reply.

Discussion

Very interested in #2. Relay management is going to be super important as nostr grows imo.

My take on the state of relays.

Relay discovery is tied to people atm - if you follow someone, your client should probably look at their relays and try to read from there (that's part of gossip-model idea). It seems like almost no one chooses their relays manually based on some meaningful selection criteria.

That's because most of existing relays are a commodity - they don't differ in any meaningful consistent way and just contain some random subset of events (notable exception - paid relays). It makes not much sense to bring them to UI because you can't really choose meaningfully anyway.

However, there is this idea that fiatjaf is advocating that custom relays are the way to solve algorithms/discovery/curation - just give me a relay URL that has a curated feed on Bitcoin or Food, etc. Whether the feed is algorithmic or manually curated by admins or by the crowd becomes an implementation detail here.

I tend to think that such "custom relays" are a good idea at this point, and we could talk about two types of relays: "standard" - these are commodity, and will probably stay that, and "custom" - algorithms/curations.

And then standard relays probably need discovery at the protocol layer, maybe using dynamic pricing as the driver - your client gossips and chooses the best perf/price commodity relays. And the custom relays do need to be in UX, and need user-level discovery just like people or content.

Nostr.band Top posts and Top profiles ranking is still a mystery..! Who determines these important-enough profiles that goes into Top posts and Top profiles?

related to these questions, right?

nostr:note1yrmlmk73unvg9ejjr0xut3a9ce8cj0r8ugdlu9ktu53jh3tmd44ql0swxp

Right

5) Providing nostr stats and meta data as a service (maybe related to #1)

I think some of the discovery features are already exposed as a service and used by clients like Snort, Iris, and Current. Is that what you meant or some other kinds of data services you had in mind?

Discover features yeah. And what else can be built as a service. Algo as a service, for example. Right or wrong, it’s something the market will attempt.

There will definitely be some APIs for filtered/ranked feeds. Do you have any specific examples that you'd like to see sooner?

There will definitely be network stats as an API one day, and for more granular stats - would some of endpoints at https://api.nostr.band work?

Meta data as a service - do you mean APIs/special relays for kind-0 or relays-lists? Anything else?