If you can see this, Tor is now inside of Amethyst.
No more Orbot.
Login to reply
Replies (110)
Woah ... you are amazing.
Wow!!!
👀
E o que precisamos fazer pra lançar pra iOS?
👀👀👀
Oh damn we on #Tor ⚡⚡⚡
Comprar um pixel e instalar grafeno
Tor in Amethyst is a fantastic idea, but I still see this note in Damus.
When Amethyst on iOS?
Well done Sir! We appreciate your efforts.
Did you package and run the binary inside of the apk?
Hell yes. Is it active for everything, or just onion relays?
dope
View quoted note →
Awesome
Maybe @npub1sn0w...jdv9 will come back
Yeah, the "new" package they are offering seems to have worked quite well for the past few hours. I didn't notice any crash from the lib itself, which was fairly common in the past.
black magik
everything
Released yet or just in your test env?
Can somebody explain how or why this is a big deal i would love to understand more. Its sounds important
Legend!
The #Tor is inside #Amethyst ⚡️ 
Wen release
There is orbot on phone
There is Tor/Orbot selection in Amethyst
Now it is just running
Does Amethyst need to be selected in Orbot app on phone at all anymore?
I second this emotion
Are you not supposed to?
I agree. Eli5 please
Nice! 🫡
Please release an iOS version!
nah.. I avoid centralized stacks.
Justo!
I dunno, what's it mean "if I can see this"? Was it published to an onion relay? If so I assume it was republished, which defeats the demonstration of tor-in-nostr.
This
On the dev version, you need to activate as before, but there is no need to have Orbot installed anymore.
👀
aí sim!
View quoted note →
A good policy.
Baller
Or does it simply mean that the original post doesn’t expose the authors IP address to any relays. I’m trying to understand what all this means too.
The option to have baked-in privacy to a widely-nostr client is significant.
Without this, users are dependent on making sure they have an always-on VPN (or Orbot) enabled. Otherwise your IP is shown to pretty much every relay, all the time. Needless to say, terrible for privacy, dealbreaker for anonymity (think journalists under oppressive regimes).
The always-on VPN can be unreliable on mobile devices. Orbot slows all your web traffic and some websites/apps block the traffic entirely, so many people disable it (to do mobile banking, or just get on Reddit, for example) and don’t always remember to turn it back on. Just a host of opportunities for it to be a problem unless you’re meticulous about it.
Granted, one probably needs to enable Tor in Amethyst the first time around, unless the default setting is on (Vitor, could that be the default?), but still, this is a big step toward privacy-by-default in freedom tech tools.
There may be another impressive quality of this, having to do with being able to send events to relays over Tor regardless of whether or not the relay normally accepts Tor connections. I don’t know (because I haven’t read the spec and likely wouldn’t understand it, if it’s all code, anyway), but by the wording of the OP it sounds like there may be something to this as well.
Correct. It just transfers through Tor instead of the regular web. Everybody else can see it as soon as it reaches any open web relay.
Probably after they no longer have a centralized stack, judging from his many answers to this question.
While it's great to have the feature, privacy focused users should not rely on it and use Orbot instead. Orbot avoids that an app leaks the IP address while Tor-enabled leaves it to the dev of the app to enable tor for all calls and not only for some.
Humm.. good point. Is Orbot really that good? I had cases of leaking IP with Orbot. If the dev is not carefu with connection setup (mostly issues with dependencies doing the connection), it can leak indeed.
Would you consider nip-60/61 (built-in ecash support) centralized stacks? Seems like a grey area for me as the nips aren't centralized but allow the user to choose between centralized mints.
Maybe. I don't like turning amethyst into a wallet, but maybe this can change...
iOS plz
I'm too dumb to fully understand what this means but it's provocative and it gets me going
Unfortunately some image hosting sites block #tor with #cloudflare.
As a #TorOnly #nostr user it looks like nostpic.com is blocked for us #privacy enjoying #Tor folks.
Can anyone else confirm?
Ping @npub138s5...x624
Sorry, no time for centralized stacks.
My .onion relay node doesn't seem to connect without the Orbot.
Yeah i have always had a vpn on when using amethyst so i guess thats good. I do see people i follow that are NOSTR OGs i would consider and they always said they wont reply to DMs for privacy and security reasons i believe. Does this Tor integration help that as well?
I'm not an expert on Orbot but in which case and how could an IP leak using Orbot, assuming Orbot routs all the activated app's communication only over TOR? And how can an app developer fix this reliably? And how can the user know the client dev fixed it reliably 100% all the time with every update?
I'm talking out of the experience where an app used an installed Orbot to talk to some servers then a new dev team introduced other servers but did not care about using Orbot when the still available TOR option was activated, misleading the user to assume to be private where they are not.
😆
🤯
Nice! When will it be pushed out live to Google play?
Still showing a tag of v0.90.6-PLAY
What version tag means no more Orbot.
Excelente trabalho, Vitor!
Your work? Fantastic... Thanks!
Orbot utilizes android's VPN API so I assume it controls the full applications network stack (or full device if configured that way).
Still I think androids VPN stack has some holes.
@Vitor Pamplona Can the in-app component cooperate with an ambient orbot? Best of both worlds?
rely on orbot as proxy put pretty the same trust in app devs not leaking ip. Using it with orbot as vpn put this trust into the os.
Now we are going to need relay runners to also run their relay over TOR instead of just the naked web.
So Amethyst on TOR will only relay to a relay on TOR, not on naked web?
And then we should hope that this relay also has a naked web address so that other clients can download the note?
congrats
Not necessarily. Orbot runs with and without VPN mode.
You shouldn't give privacy advice if you don't know what you're talking about.
Nice work 👍
Can't connect to any Relay after turning on the tor feature.
It only does that if you are using orbot as a vpn
Orbot always breaks for me
cool man
It depends on whether Orbot is used as a VPN or as a proxy. In the former case, the application cannot escape Tor, in the latter case it can of course, avoiding using the proxy.
So Orbot as VPN is safer than current Amethyst's implementation, while the new built-in support has the same robustness, but avoid a dependency and all the troubles related to the configuration, offering a better experience to the user.
Probably you don't have Orbot running as proxy. This update will remove this additional step.
BLESS YOU VITOR
MORE NATIVE TOR PLEASE CLIENTS & WALLETS TAKE NOTE
The mentioned problem is related to the "old" NIP-04 specs, with which DMs leak metadata. The new NIP-17 version is safe.
Tor has no role in this.
No, it also works directly with naked relays, just as with a tor browser one can visit any website.
So, if now tor is pre Baked in amethyst, how can i disable it? Its just a question, and where can i see if its really active? Does it have a feedback?
On the other side you have to monitor that Orbot is indeed running on the system, and not closed or crashed.
Sometimes, rarely, Orbot just closes.
It would be useful to have an indicator in the app whether it's on tor or clearnet, so I can be sure about what connections I'm using.
Oh cool thanks for the advice. Now it works.
It's likely going to be using both at the same time for the vast amount of users.
How it started
View quoted note →
How it's going
View quoted note →
4 days 🤯
Congrats! Nice work
First thought. Maybe @jack can inform him
Amethyst - juicy, crisp, pleasing acerbity
h/t @Vitor Pamplona
h/t @Vitor Pamplona
I saw you write it while you wrote it. Inspired by the npub most of us know a well. 🤭
@ZEUS consider @Vitor Pamplona feedback as an extra input in favour of uptading the TOR library in @ZEUS wallet!!!
@KoalaSat also has succesfully implemented in #robosats
Halt!
You have committed an international violation of state sovereignty. This shall be taken as a declaration of war.
Cease and desist now, or suffer the consequences next time you visit a French airport.
Can people with no background in coding understand and adopt it?
That's the goal
if you can see this, you can also see the tip below:
I see it but have no idea what it means
Congrats!
There is indeed a PR with the same code in Robosats fully working for Android 
the only problem is iOS, which is becoming some sort of headache 😅
GitHub
New Tor engine Android test by KoalaSat · Pull Request #2268 · ZeusLN/zeus
Description
This is a POC for including a new Tor engine that is being used by Samourai's Sentinel and Robosats' app.
I implemented a simpl...
Are you also starting and stopping Tor on onResume and onPause? I thougtht it would create some issues, but it seems to be working just fine.
🎯
Yep, it depends on Zeus callbacks but it they are doing it right, as you say, it works fine.
I tested once to keep it off for 48h and onResume still worked
This is a huge thing.
Same.
Cool! Looking forward to giving that a spin!
I also should really get around to setting up an exit node. Or at the very least a routing node.
Tor is such a fundamental part of this space!
Fair enough, but it's a big market