fix(pairing): offer relay.damus.io first - Amber never receives on primal/nos.lol
This commit is contained in:
parent
5456835cde
commit
e02417b18c
1 changed files with 9 additions and 0 deletions
|
|
@ -35,8 +35,17 @@ pub fn default_relays() -> Vec<RelayConfig> {
|
|||
/// conversation across relays the signer never reads.
|
||||
/// - wss://relay.snort.social accepts ephemeral 24133 publishes but does
|
||||
/// not persist them; with damus out it adds no shared ground.
|
||||
///
|
||||
/// Sep 23 PM addendum: Amber 6.6.5 receives our pairing publishes on NONE of
|
||||
/// the above (its activity log shows only the Connect ack; our get_public_key
|
||||
/// RPCs are accepted by both relays but never answered). Amber's own issue
|
||||
/// history documents NIP-46 working over relay.damus.io, and a same-day
|
||||
/// write-canary from this network shows damus connected + accepting ephemeral
|
||||
/// 24133 publishes, so damus rejoins the set FIRST — the signer is most
|
||||
/// likely to meet us where its own client is proven to work.
|
||||
pub fn pairing_relays() -> Vec<String> {
|
||||
vec![
|
||||
"wss://relay.damus.io".to_string(),
|
||||
"wss://relay.primal.net".to_string(),
|
||||
"wss://nos.lol".to_string(),
|
||||
]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue