# Citrine setup Go to the settings tab. https://i.nostr.build/ex9B7IdQK1q0AerO.jpg Fill things in as appropriate. Leave the network related settings default. # Orbot setup In orbot got to more/hosted onion services. Add a new service. Citrine uses port 4869, so set that for both ports. Name it anything. "Nostr" will do. You will need to restart orbot after you save. Then you can go back and copy your onion service address. # Amethyst Setup Add ws://ONIONADDRESS:4869 as an outbox and DM address in Amethyst. Also add ws://127.0.0.1:4869 as a local relay https://i.nostr.build/vnvHQEEHAn4e3Kl5.jpg https://i.nostr.build/UhKC9mEknjHF7BJ2.jpg This requires running Tor at all times! 😎👌
Where can I find #Citrine?
here come the 'how do i do this on iOs' questions 😂
Does this setup an anonymous hidden service by default? There are ways to leak your IP while hosting onion addresses.
After setting up, do all the previous DMs that were stored in different relays disappear if we only leave this relay for DMs? That's what I encountered.
That's a possibility. Mine did come back from other relays, but ymmv. This doesn't necessarily have to be your only DM relay either. It's more like a backup communication channel under your control. Hopefully we see more integration by the devs soon 🤙
Nostr clients should TOR route all traffic by default. Wider adoption is a pipe-dream until this happens.
nostr:nprofile1qqsda2memtapc2lykjnd8t9px4ake2stw39lg6k49xj6u3jz3pteu6qpzfmhxue69uhkummnw3eryvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tc3qeapn I had added the ws://address.onion:4869 but it don't worked, do you have any idea?
Every time I hit "copy address" for the hosted onion service, the "restart orbot for changes" message appears and the address never hits the clipboard. Any ideas?
If stopping and starting the Tor service doesn't work, try a force restart and open the app again.
Thanks, I've done that a bunch of times. Tried most of the UI options ("exit", restart, delete and recreate onion service, etc.) and the same thing happens. Maybe it's a GrapheneOS thing..?