Bugs still in the system, frustrate individuals coming from services that “just work”, so there’s a ton of development and bug squashing needed.
More robust relay infrastructure.
A way for individuals to, discover, interact, import, publish and filter relays from a repository that is decentralized and preferably blockchain based.
For example, if I click relays. I should be met with a list of available options.
This list should be distributed, and categorized.
A mechanism for sharing this list should be a NIP, including its format, how one registers a server to it, including basic metrics, geographical location, and uptime stats. Including notes from those running the relay about the relay.
Group into paid, vs free categories - including filter by price.
Additionally, there should also be relays on the list accessible over TOR and other platforms.
Ability to trigger in app WireGuard, per relay with separate keys should also be available.
So, someone running a relay, can place the relay behind a WireGuard connection. & all data transmitted between the client and the server is WireGuard encrypted.
This should be part of the NIP protocol, where keys are seamlessly issued, and rotated to the client if enabled, based on their public key.
So, I connect to a relay, if it provides the service and my client has the feature turned on. My public key requests a WireGuard key pair, good for say a couple days. Then if the relay is still being used, keys get rotated and re-issued automatically.
This adds a layer of big brother protection against snooping that can be enabled by default on relays. Trying to get users to take their security seriously and run a VPN, is like trying to direct a choir of cats.
I think the protocol has potential, it just needs more work IMO.
Will be digging more into the NIPs and documentation to really sort this beast out and see what other options I can offer.
Clem Morton /
npub1gc…yxhyx
2024-09-01 18:13:05
Author Public Key
npub1gca5whd7xs05rpt9yspg42wrxhw2luxdd6fp62skmkuzl7t9au0syyxhyxPublished at
2024-09-01 18:13:05Event JSON
{
"id": "8775cf593b5fe0eea6ee9e2f6d3d727ab455ffb82006b8b1c26e4c36cebd7e65",
"pubkey": "463b475dbe341f41856524028aa9c335dcaff0cd6e921d2a16ddb82ff965ef1f",
"created_at": 1725214385,
"kind": 1,
"tags": [
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Bugs still in the system, frustrate individuals coming from services that “just work”, so there’s a ton of development and bug squashing needed.\n\nMore robust relay infrastructure.\n\nA way for individuals to, discover, interact, import, publish and filter relays from a repository that is decentralized and preferably blockchain based.\n\nFor example, if I click relays. I should be met with a list of available options.\nThis list should be distributed, and categorized.\nA mechanism for sharing this list should be a NIP, including its format, how one registers a server to it, including basic metrics, geographical location, and uptime stats. Including notes from those running the relay about the relay.\n\nGroup into paid, vs free categories - including filter by price.\n\nAdditionally, there should also be relays on the list accessible over TOR and other platforms.\nAbility to trigger in app WireGuard, per relay with separate keys should also be available.\n\nSo, someone running a relay, can place the relay behind a WireGuard connection. \u0026 all data transmitted between the client and the server is WireGuard encrypted.\nThis should be part of the NIP protocol, where keys are seamlessly issued, and rotated to the client if enabled, based on their public key.\n\nSo, I connect to a relay, if it provides the service and my client has the feature turned on. My public key requests a WireGuard key pair, good for say a couple days. Then if the relay is still being used, keys get rotated and re-issued automatically.\n\nThis adds a layer of big brother protection against snooping that can be enabled by default on relays. Trying to get users to take their security seriously and run a VPN, is like trying to direct a choir of cats.\n\nI think the protocol has potential, it just needs more work IMO.\n\nWill be digging more into the NIPs and documentation to really sort this beast out and see what other options I can offer.",
"sig": "37584f79075b8a3c188a53b3249aed742dd588b5dd53fa05a2470e7f3b8ba4f73f9348a1760e4ee651c33edcc6610cd9f9f6e5ce4aadbe3ece9d3aef4e8a772f"
}