Orbot 4+

I don't know how, but Orbot is completely bricked, either iOS and Orbot updates or ISP limitations (Russian ISP, traffic maybe blocked by DPI). Either way, Orbot is NOT STARTING. API access functionality is useless and should be removed, since we can only work with Onion Browser from traditional VPNs, untunneled or improperly tunneled Tor traffic is caught by the ISP and blocked. Traffic masking should be worked on, big trouble with obfs4. Orbot should be brought up to adequate and reliable operation. Updates should be done under the necessary supervision of The Tor Project, otherwise the Orbot and Onion Browser officially supported by The Tor Project will not work properly.

I have a couple content blockers I use in safari, and then I have some DNS content blocking going on as well. I’ve always used Orbot to block things that are still there and now, for the second time in around 2 weeks the content blocker has completely stopped. I went through the motions trying to debug it, rebooting my phone, disabling each content blocker and extension leaving only Orbot to run, killing both apps, disabling content blocking entirely, and deleting all of orbots rules did not seem to work. I’m unsure what the issue is. Also, whenever enabling the VPN, if it doesn’t start showing that is has made any progress at all, the cache has to be cleared first and then everything works just fine. Maybe this is more of an iOS issue, but I haven’t done anything differently with my phone anytime recently. I still haven’t updated to iOS 17 either

A feature request that I would have would be to allow one to disable the content blockers individually within the app without having to delete them. That would be very nice

Orbot flat out doesn’t work. It won’t get past 50% and it won’t keep a session alive for longer than 5 minutes. Tor’s Foundation aren’t negligent, but they’re not on top of this. Something’s going horribly wrong right now where even custom bridges just don’t work.

Tor doesn’t work on iOS and it’s completely due to a memory limit hitting the ceiling. The only option that works is a direct connection. That’ll last 5 minutes. I think Apple’s restricting Tor connections completely. I’ve seen the same thing happen on Mac OS if you hit up the Tor Browser with lockdown mode enabled - you just can’t connect no matter what. Apple’s walled garden is hurting Tor, but I have to rate so low and even write because Tor isn’t vocal about what’s happening and assuming it’s known to everyone. It’s not.