jb55's avatar
jb55 _@jb55.com 1 year ago
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. View quoted note →

Replies (7)

jb55's avatar
jb55 _@jb55.com 1 year ago
Monetization happens through clients. Relays are just a business expense, not even the highest compared to paying employees.
Braydon Fuller's avatar
Braydon Fuller _@braydon.com 1 year 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.
jb55's avatar jb55
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. View quoted note →
View quoted note →
2 replies ↓
Niel Liesmons's avatar
Niel Liesmons 1 year 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.
↑