nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw I get the feeling nip65 does not have enough attributes.. I do understand it may be impossible to adapt this nip to more settings but I would like my gossip relay settings to be portable to amethyst...  I also like the distinction of settings in gossip where write does not mean outbox for eg.

currently amethyst is using (a temp hack?) of storing 'general relays' in kind 3, inbox/outbox in 10002 and dms in 10050.

if its too hard to change nip65 should there be another nip for 'other relays'?  or would it be easier to modify 65 with flags for the various 'usages'?

🤔 

 You can't mix the two. Nip-65 sections exist to tell your followers where they should get your posts and where to send notifications back to you. 

The General section on Amethyst include the relays the app is using to download posts for you. It has nothing to do with your followers. 

 The general section will cease to exist now that amethyst can connect to random relays inside of Tor. 

 ^ 

 huh, ya i dont get it.. how does tor have anything to do with it?

i suppose you are going to store the additional settings locally like gossip does, and theyll be wiped on reinstalls.  i suppose thats fine too.  have you seen the gossip relay settings?  in my dream world amethyst has capability for the same settings eventually. 

 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 :)  

 looking forward!      t-y Vitor 

 right, but amber says youre posting the general section as kind3 still 

 Yep, but only for now.