IPv6Droid

about

description

<p>To actually use this app, a tunnel service is required. You can run your own tunnel service on suitable infrastructure. See <a href="https://codeberg.org/Flying-Snail/IPv6DroidServer">IPv6DroidServer</a> for more details.</p> <p>Notes:</p> <ol> <li>This approach towards IPv6 has subtle implications on your privacy: for IPv6 connections, you have a fixed IP and you - as a person! - are easily identifyable by all IPv6 communication partners. Also, your mobile device suddenly has an IP on which it is reachable from the outside. </li> <li>This app cannot be used when another VPN is active.</li> <li>It is not required to have a rooted device.</li> </ol> <p>About license:</p> <p>You can opt for the convenience package, and install IPv6Droid right from here. It will download, install, guide you to the setup of your account details and update from time to time as new features or bugfixes are implemented.</p> <p>But I am looking for supporters! So, I'd like to promote the approach that you set up a build environment (e.g. Android Studio), download the sources (see web site) and build it by yourself. That's it. You may use the tool, modify and even redistribute the sources under the terms of the General Public License. No obligations, but in this case you have the tools, you have the sources and you have the engagement that drives me to hope that you're going to play a more active part in bringing forward this client. E.g. by submitting detailed error reports, by submitting patches, by providing better artwork, writing better documentation, designing a better user experience, ...</p>

publisher

78ce6faa72264387284e647ba6938995735ec8c7d5c5a65737e55130f026307d

first seen

2026-10-08T22:41:26.458462+00:00

last event

2025-06-07 22:35 UTC

install

zapstore.dev or any Zapstore-compatible client

source & build

repository

https://codeberg.org/Flying-Snail/IPv6Droid

arch flags

android-arm64-v8a

manifest

skipped

releases (kind 30063)

1 release indexed; latest 3.0.4.

assets & verification

Every app, release and asset event is schnorr-verified (NIP-01 id + signature) before it enters the catalog, and assets are content-addressed by sha256. We subscribe read-only to the catalog relay — never write to it.

Showing the newest 0 asset descriptors; the full set is in /api/apps/78ce6faa…