I would never connect to any relay that hasnt been authorized by the user. It's just a huge privacy leak. With Tor, I can make a route just for random relays. We have other settings in other events, like search relays use kind 10007 and so on.
Are you looking for any particular behaviour that are not defined yet for a relay? We can always create a new relay list for that particular reason.
CloudFodder misses the ability to browse "global" by specific relay. I miss the icons of the relays appearing beneath the note, it was useful for tracing note propagation across relays, for troubleshooting discoverability.
You can add that back on the app settings, by choosing the Complete UI mode. :) Global will change. We will have custom feeds where people can choose a filter (or global) and then pick a collection of relays to use for that feed alone. It will extend the top bar options to have relay choices as swell.
ohhhh, ok.. can i allow it to connect to 'random relays' over my default route if i trust my own netsec, like a vpn? or tor only?
Maybe... I haven't yet seen the need for additional options but it could be one. Besides IP leaks, the issue is colluding all filters together in the same req, avoiding auth, etc and doing all of that for all accounts that are logged into the phone at the same time. So it depends on how we assemble these queries to random relays. Since many relays limit one connection per IP, the use of Tor routes can keep users and subs separate from each other.
that sounds intense.. 😅 i am a vpn enjoyuure so just wanting to understand if i can opt-out of tor but still have all the outboxin' and auth. or r u gonna mak me tor 😂
We will see :)