arbedout on Nostr: Maintenance window complete! wss://nostr.relayer.se also reachable at ...
Maintenance window complete!
wss://nostr.relayer.se
also reachable at
geeafhmczfy5jmfc36ud2vgfotsrdnc2vwrp2kczjka4afx42quc3qqd.onion
is now serving as a relay and an aggregator - copying all received messages to relay.damus.io, relay.snort.social and nostr-relay.texashedge.xyz.
Going to start experimenting with inspecting payloads so a) clients can ensure that different events are routed to different relays and b) relays can decide what events they choose to receive.
There are some obvious wins here - less bandwidth usage for clients for the same level of relay availability - and some obvious drawbacks (relay aggregation makes the aggregator a de-facto chokepoint). Looking forward to exploring what sort of features can be built on top of this.
wss://nostr.relayer.se
also reachable at
geeafhmczfy5jmfc36ud2vgfotsrdnc2vwrp2kczjka4afx42quc3qqd.onion
is now serving as a relay and an aggregator - copying all received messages to relay.damus.io, relay.snort.social and nostr-relay.texashedge.xyz.
Going to start experimenting with inspecting payloads so a) clients can ensure that different events are routed to different relays and b) relays can decide what events they choose to receive.
There are some obvious wins here - less bandwidth usage for clients for the same level of relay availability - and some obvious drawbacks (relay aggregation makes the aggregator a de-facto chokepoint). Looking forward to exploring what sort of features can be built on top of this.