npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mercuryworkshop/adrift

v1.0.4

Published

Adrift is a fast and modern decentralized web proxy network, utilizing transport over WebRTC.

Downloads

142

Readme

Adrift

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

For users:

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.

For frontend creators:

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

For contributors:

Before everything..

install dependencies and build bare-client-custom

pnpm install
cd bare-client-custom
pnpm install
pnpm build
cd ..

Getting started with the server

inside the server/ directory, run pnpm install, followed by pnpm start

Getting started with the client

Inside the frontend/ directory, run pnpm install and then VITE_ADRIFT_DEV=1 VITE_ADRIFT_SINGLEFILE= pnpm dev

Quick server setup (linux)

git submodule update --init --recursive
pnpm install
cd bare-client-custom
pnpm install
pnpm build
cd ..
cd server/
pnpm install
pnpm dev

Quick client setup (linux)

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

To host a tracker...

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.