--disable-module-dirauth does nothing without relay module also disabled

[bitmold]

https://gitlab.torproject.org/tpo/core/tor/-/issues/40904 i just learned that this never did anything

At the time of this someone is running a relay with Orbot that uses the default name:
https://metrics.torproject.org/rs.html#details/53BAC9FA7F057BE66DCF4AA68FA2443847789D28

though I imagine a small handful of other people are using Orbot for relay stuff too

Honestly the way Orbot is pitched as a lightweight VPN type app for bypassing censorship with some apps I feel like it hardly makes sense to use it as a relay. I could make a lightweight barebones app that uses TorService for people who want to run relays on Android and we could just chop this feature out of Orbot. I could see there being a small use case for this with people who have access to longrunning Android devices such as Android TVs or Chrome OS machines. To me the tradeoff seems worth it.

What do you think?

[bitmold]

Something like this could be merged into Orbot removing relay torrc config and string resources:
https://github.com/guardianproject/orbot/tree/no-relay

Then tor-android could keep --disable-module-dirauth while also adding --disable-module-relay

And perhaps ./tor-droid-make.sh build could have an -r flag for building tor with the relay module. A lightweight with clear logging of Tor, no Vpn service, no lyrebird/snowflake, etc could be released alongside tor-android that could support relays for the few users who want to run relays/have access to a situation in which it might be strategic to do so

[bitmold]

@n8fr8 what are your thoughts on this