wowlet: keep wownero clearnet nodes usable in Tor mode (fix empty remote-node list)

feather's websocket-node filter drops every non-onion node once the Tor privacy
level flips to onion-preferred (after initial sync) — it assumes an onion node
ecosystem. wownero's public nodes are clearnet, so the Settings list went empty
and autoConnect had nothing eligible -> Disconnected. Keep clearnet nodes
eligible in every proxy mode (routed over Tor's SOCKS proxy when Tor is on, so
still private); only hide onion/i2p nodes when their anonymity mode isn't active.
This commit is contained in:
jwinterm
2026-06-20 06:05:47 -04:00
parent ea22d5dbe4
commit 35af2db2ef
+4 -8
View File
@@ -612,14 +612,10 @@ QList<FeatherNode> Nodes::websocketNodes() {
QList<FeatherNode> nodes;
for (const auto &node : m_websocketNodes) {
if (onionNode && !node.isOnion()) {
continue;
}
if (i2pNode && !node.isI2P()) {
continue;
}
// wowlet: wownero's public nodes are clearnet (there is effectively no onion node ecosystem), so
// keep clearnet nodes eligible in EVERY proxy mode — they're routed over Tor's SOCKS proxy when Tor
// is enabled, so still private; just not onion-only. Only hide onion/i2p nodes when the matching
// anonymity-network mode isn't active.
if (!onionNode && node.isOnion()) {
continue;
}