Back Home

RELAY LIFE

© 2025 privacyjam — licensed under the Privacyjam License Last updated: April 10, 2025

A game where you act as a Tor Relay operator, and face many obstacles.

TOR RELAY ONLINE

Consensus Weight: 0

Mode: Exit Relay

Status: Awaiting configuration

root@tor-relay:~$▌

[✓] Disk ok

[✓] CPU ok

[✓] ORPort [9001] reachable

[✓] Directory synced

[✓] GeoIP up-to-date

[✓] Time in sync

root@tor-relay:~$▌

[✓] Relay nickname set [EpicRelay12345]

[✓] Contact: admin@epictorrelays1234.com

[✓] Network Firewall Not Blocking any Ports

DNS: ⚠️ Using Google DNS

Consensus Weight: 25

root@tor-relay:~$▌

You disable DNS logging and setup a local Unbound resolver.

You have made your relay more resistant against surveillance and metadata leaks.

Consensus Weight: 30

root@tor-relay:~$▌

Allowing only ports 53 (DNS), 80 (HTTP), 443 (HTTPS).

Low abuse, lower functionality.

You relay is more useful for Tor Browser Users

Consensus Weight: 200

root@tor-relay:~$▌

All ports allowed.

Full freedom — high risk and abuse.

Consensus Weight: 300

root@tor-relay:~$▌

Your relay is fully published, active, and reachable.

[✓] Fast — Your node moves traffic like a pro

[✓] Stable — Uptime solid - You've been reliable

[✓] V2Dir — You're now serving directory info to others

Consensus Weight: 2000

root@tor-relay:~$▌

You start getting emails regarding your IPs activity

You ignore the complaints.

Your ISP warns you are starts considering dropping you

root@tor-relay:~$▌

You respond with Tor info + disclaimers that you are not the one doing the bad traffic.

Some understand, some don't and continue pressuring.

root@tor-relay:~$▌

Users report that Cloudflare and others are blocking exit traffic.

Sites become unusable and captchas increase.

root@tor-relay:~$▌

A government notice demands logs.

You don't log. Pressure builds.

root@tor-relay:~$▌

You resist and get support from other operators.

Consensus Weight: 2200

root@tor-relay:~$▌

You're pushing 98% of your limits.

root@tor-relay:~$▌

Upgraded RAM and bandwidth. Node now stable.

Consensus Weight: 2500

root@tor-relay:~$▌

You reduce your bandwidth limits in your torrc.

System stable, consensus weight reduced.

Consensus Weight: 1800

root@tor-relay:~$▌

You skip setting a relay family.

This is exactly how that one cluster — KAX17 — ran hundreds of relays without declaring a family, and allegedly tried to deanonymize users.

You're not doing that... right?

Consensus Weight stays unchanged, but this isn't ideal.

root@tor-relay:~$▌

You configure your MyFamily setting

to list your other relays' fingerprints.

This helps prevent traffic from traversing multiple nodes you operate.

Consensus Weight: 2600

root@tor-relay:~$▌

You're flagged as BadExit and MiddleOnly due to suspected traffic interference or a broken configuration (e.g., packet tampering, blocking port 443).

Consensus Weight: 100

Clients may avoid your node until resolved.

root@tor-relay:~$▌

You appeal via the tor-relays list.

Flag removed. Reputation restored.

Consensus Weight: 2500

root@tor-relay:~$▌

You're paying out of pocket.

Donations are low.

PS: You can donate to me Here!! (I have gotten $0!!)

root@tor-relay:~$▌

A small nonprofit group sponsors your relay.

You upgrade your relay slightly

You join their group to help other operators.

Consensus Weight: 3000

root@tor-relay:~$▌

You shut your relay down.

Disk wiped. No trace. The network thanks you.

The only evidence you were ever there is the Onioono archive

The only thing left is your mad ISP because now one of their IPs is forever fried with abuse

root@tor-relay:~$▌

You're now a trusted exit relay.

Uptime: 99.99% (stupid power went out)

Abuse handled. Traffic anonymized. Users helped. Trust earned.

Final Consensus Weight: 3500

PS: Send me an email with your thoughts on the game — jam@privacyjam.com