surf_the_web_adrift_fix --------- "ce why do you keep making stupid proxies with zero use case"
Adrift is a fast and modern decentralized web proxy network, utilizing transport over WebRTC.
Clients will invisibly connect to one of several tracking servers to exchange an "offer". From there, it uses NAT traversal to link up with a random exit node also running adrift, without the need to port forward. This lightens the load on individial server hosters and makes the network difficult to effectively block. If you're familiar with tor snowflake, you can think of this as tor for the web
See a functional demo here. There is also a WIP limited standalone HTML file build in releases
If you want to contribute to the project and share your connection the best way is to host your own exit node. This does not require port forwarding and is very simple to setup.
Head over to releases and download the autoupdating binary corresponding to your platform. On windows, download adrift-server-windows-x64.exe
, move it to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp
and launch it. On Linux, use systemd or cron.
Adrift can be integrated very easily into existing proxy frontends using UV or Dynamic. First, download our prebuilt UV and/or Dynamic bundles from frontend/public
. Then npm install @mercuryworkshop/adrift
, @mercuryworkshop/bare-client-custom
and firebase. Here's a quick code example for connecting to Adrift
import { initializeApp } from "firebase/app";
import TrackerList from "@mercuryworkshop/adrift/tracker-list";
import {
SignalFirebase,
AdriftBareClient,
} from "@mercuryworkshop/adrift/client";
import {
registerRemoteListener,
setBareClientImplementation,
} from "bare-client-custom";
registerRemoteListener();
let tracker = TrackerList["us-central-1"];
initializeApp(tracker.firebase);
async function onTransportOpen() {
console.log("Transport opened");
let connection = new Connection(transport);
await connection.initialize();
let bare = new AdriftBareClient(connection);
setBareClientImplementation(bare);
}
async function connect() {
let rtctransport = new RTCTransport(onTransportOpen, () =>
console.log("transport closed")
);
let offer = await rtctransport.createOffer();
console.log("Routing you to an available node...");
let answer = await SignalFirebase.signalSwarm(JSON.stringify(offer));
console.log("Linking to node...");
rtctransport.answer(answer.answer, answer.candidates);
}
connect();
// after connect returns, UV/Dynamic can be used as it normally would
install dependencies and build bare-client-custom
pnpm install
cd bare-client-custom
pnpm install
pnpm build
cd ..
inside the server/ directory, run pnpm install
, followed by pnpm start
Inside the frontend/ directory, run pnpm install
and then VITE_ADRIFT_DEV=1 VITE_ADRIFT_SINGLEFILE= pnpm dev
git submodule update --init --recursive
pnpm install
cd bare-client-custom
pnpm install
pnpm build
cd ..
cd server/
pnpm install
pnpm dev
git submodule update --init --recursive
pnpm install
cd bare-client-custom
pnpm install
pnpm build
cd ..
cd frontend/
pnpm install
VITE_ADRIFT_DEV=1 VITE_ADRIFT_SINGLEFILE= pnpm dev
As of now, the project relies on at least one central tracking server to keep offers forwarded smoothly. If you have the infrastructure to keep a tracker of your own running 24/7 and want to host one yourself, here's how to.
Create a new firebase project. Enable authentication and a realtime DB. Set these rules in the realtime DB
{
"rules": {
"peers":{
"$uid": {
".read": "$uid === auth.uid",
".write": "$uid === auth.uid"
}
},
"swarm": {
"$id": {
".read": true,
".write":true,
}
}
}
}
Next, create a service account with all permissions. Download the authentication file and save it to tracker/src/admin-creds.json
cd into tracker/
, pnpm start
, and make sure to choose a port with the PORT
environment variable that's accessible from the internet.
Open tracker-list/index.ts
, and add a new entry. Name your entry accordingly, copying in the client-side firebase tokens for the firebase
field, and putting the domain where your tracker is available in the tracker
field. After testing, submit a PR and if we trust you, it will be merged and your tracker will show as an option.