Grapevine Relays

[PrettyGoodFreedomTech]

This thread will be a place to discuss the role that specialized Grapevine Relays will play in the grapevine system. I envision two categories:

1. Personal Grapevine Relays
2. GRaaS: Grapevine Relays as a Service

Common features include:

• willingness to store Grapevine-formatted NIP-51 lists that are too large for most relays to accept

GRaaS

Features of a GRaaS relay:

• maintains kind 3, kind 10000, and maybe other kinds (1984) relevant to calculation of Grapevine Network
• calculates the Baseline Grapevine Network for customers
• stores and / or outputs them as NIP-51 lists

GRaaS will be a great way to introduce the Grapevine to the world. In an ideal world, everyone will run a Personal Grapevine Relay and will have no need for a GRaaS. But in the real world, that ain't gonna happen. In the short run, no one is going to run a personal grapevine relay without a good reason. And in the long run, there is no guarantee that everyone is ever going to run a personal relay at all.

Personal Grapevine Relays

In the long run, personalized grapevine relays are going to be the future of nostr. This makes sense because you're going to want assurance that the data that YOU care about is both persistent and readily available. And it makes sense that your Grapevine is going to help you decide which data to keep and which data to discard. This will be a function of many things, but will have to take into consideration how much data storage is available.

I would LOVE to see @jeremyd iterate relay.tools using these steps:

1. release it as a personal WoT relay (similar to what so many other relays offer)
2. replace the WoT score with the Grapevine WoT Score
3. use the Grapevine to curate what data gets stored in your Personal Relay