3bf0c - 3y
I don't think I would use this: #[0], but if it worked it would create a certain aura of exclusivity for content posted in this relay. Better yet if you restrict reads somehow, make them harder to get or something like that.
Other relay ideas (not very good, just to sparkle your imagination): - a relay only for people with top-level domain names (no "@" at the NIP-05) - a relay that only stores the most recent post of people - a relay that only stores posts that have received at least 10 replies from other people (big threads) - a relay that only serves posts to people "bitcoin" on their profile metadata The most interesting crazy relay idea to comment on this post will earn a marvelous prize of 10000 sats.
2ce3a - 3y
Sorry, but what is a sat?
7ef7d - 3y
1 Bitcoin = 100,000,000 sats
34c0a - 3y
A relay that only serves laser eyes.
668ce - 3y
A relay that only serves images might be cool
A relay only for Twitter blue users
45c41 - 3y
A yellow page relay that only accept user metadata and following list, serve as social graphs list
ee9aa - 3y
I will try the crazy idea...
d9921 - 3y
A relay that posts the exact opposite of what users intend to post
198ae - 3y
A relay for music
0575b - 3y
a relay i have to pay small sats to post on it --> spam free relay where you could use global again
Merrcurr⚡️ @Merrcurr - 3y
A relay for wholecoiners and up. Could be called the "nostr.monaco.io", how to verify "trust me bro". Entry price, 50M. I guess no one in their right mind would shill 50% of their Bitcoin net worth for this. You said crazy ideas ☺️ [774990]
Evan Lin @Evan Lin - 3y
A relay that only serves a specific public key range, and redirects to other relays if the public key range is not served. The intention is to enforce some level of distribution. Relays will communicate amongst themselves as to what public key ranges they will serve.
Oh no. How do we get rid of scam on nostr?
aff9a - 3y
An early dumb version that could go a long way might look something like this. A relay could publish that it supports a given shard of users. For example, my relay could publish that it supports serving npubs starting with “aa” through “az” and other relays could too. Now clients just have to tell a user if their relay set doesn’t have enough shard coverage. Whenever the next order of magnitude of users arrive, relays would want to reshard and other or underutilized relays would need to redeclare shards. And there would need to be a way to get users on the new shards. Maybe some kind of registries would be in order here. In fact registries could be the key branded thing that clients watch for censorship and change to new ones etc. Historical data would have to get shared around for reshards but there could be people out there that just keep archives or in ipfs or something. You still need clients to keep users able to understand and identify a bad relay share that is censoring or underperforming or even overserving — or a registry that is promoting shards you don’t like. But I wonder how far you could scale nostr globally with a dumb strategy like this? Really important is that niche relays should not do anything like this and should find other ways to scale (monetize etc) but this would be for just the “global” nostr network experience only.
8b9cc - 3y
A relay that can run from my device?
Leo Fernevak @Leo Fernevak - 3y
Regional-serving relays will likely be useful. I guess the ping level could be used to determine who the relay serves.
e492a - 3y
A relay to rule them all
brianco @brianco - 3y
Relay that stores notes with specific url domain included in the note (e.g. YouTube)
Just saw this too #[4]
corndalorian @corndalorian - 3y
- A relay only for NIP-05 with the same name before the @ (example, everyone has to be jack@<domain> -A relay that only allows you to write to it if your post contains the word “poop” somewhere in it - A relay where every post must be exactly 5 words.
2b577 - 3y
Repeater relays- A "dumb server pool" to bring down overhead for relay operators. Making 1 relay address more resilient to take down.
*Just* made a note about this -> #[4]
d7b76 - 3y
I proposed some time ago something similar, although it was sharding by note hash, not by user. I would get a set of relays to agree to signal that the participate in a DHT protocol, then build a client to use rendezvous hashing to distribute posts and queries
0b39c - 3y
I’ll share as I get other resources. This thread is talking about the topic. I like lurking on this thread 👀👀 #[3]
21a8d - 3y
Following 👀
