Nostr Web Client

My prediction on how different sized relays will play out:

mega relay = hot cache, short term storage for reliable realtime note retrieval, optimal for microblogging use cases. No guarantees for longterm storage.

edge relays = long term storage, private notes, note backups. Personal nodes. “Right to be forgotten” nodes. Custom use cases and products. Small communities.

Outbox/autopilot moves us from the niche microblogging usecase to a true large-scale nostr web. nostr:note1m6eargjah6dxvu4l8zxgrtf5jr4km6rzlerl0ztxw4aegqu2xszq5h5ea6

Reply to this note

Please Login to reply.

Discussion

MeredithAnne 1y ago

Size doesn’t matter. It’s how you use it.

Niel Liesmons 1y ago

How do you see the mega relays monetize?

jb55 1y ago

Monetization happens through clients. Relays are just a business expense, not even the highest compared to paying employees.

liminal 🦠 1y ago

You monetize the service paired with the relay. Twitter clones make everyone think its all one system.

Niel Liesmons 1y ago

Yup exactly, for edge and community relays I can easily imagine that. Somehow I'm having a harder time thinking of examples for mega relays.

semisol 1y ago

The same as small relays

Braydon Fuller 1y ago

Cool part of having relays as part of the protocol design is that all of these are an option without adding complexity.

One of the largest centralizing forces on the web has been DDoS mitigation services like CloudFlare, which often goes undiscussed or unnoticed. Same for email.

Lightning, Ecash, Bitcoin, PoW, WoT all help mitigate DDoS and spam without centralizing. It's huge.

nostr:nevent1qqs2wcmw4zu478927g73tdldrcat55aeg9nfftu6ysah59hh65ar74spz9mhxue69uhkummnw3ezuamfdejj7q3qxtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsxpqqqqqqzfepn23