Skip to content

USER_GUIDE.md

Latest commit

 

History

History
109 lines (68 loc) · 4.25 KB

USER_GUIDE.md

File metadata and controls

109 lines (68 loc) · 4.25 KB
Raw

TFEP User Guide

Why join?

Email today is broken in a specific way: anyone can send you a message pretending to be anyone else. Your bank, your boss, your family — all fakeable. Spam filters catch some of it, but they're playing catch-up forever.

TFEP fixes this at the source. Every message on the TFEP network is cryptographically signed by the sender. You can verify, with certainty, that an email from alice@alice.tpt was actually sent by Alice. Not a filter. Not a guess. A mathematical proof.

When you join the TFEP network you get:

  • Verified email — every sender's identity is proven, not assumed
  • No spam — senders must earn your trust before they can reach your inbox
  • A permanent identity — your .tpt name is yours forever, one fee, no renewals
  • Access to .tpt websites — a growing web of sites and services on the network

Joining takes one step

To join the TFEP network, you change one DNS setting to point at the TFEP bridge.

The bridge address is published by whoever runs the gateway you're connecting to — think of it like Cloudflare publishes 1.1.1.1 as their DNS address. Your gateway operator will give you an address like 203.0.113.5. That's all you need.

Once you've set it, your normal internet is completely unchanged. Google, YouTube, your bank — all work exactly as before. The bridge only handles .tpt names and passes everything else through untouched.

Quickest way — use a setup script

Download the script for your platform and run it. It changes your DNS automatically.

Windows

  1. Download join-tfep.bat
  2. Right-click it and choose Run as administrator
  3. Enter the bridge IP address when prompted
  4. Done

Mac

  1. Download join-tfep.sh
  2. Open Terminal, run: sudo bash ~/Downloads/join-tfep.sh
  3. Enter the bridge IP address when prompted
  4. Done

Linux

sudo bash join-tfep.sh

Manual setup

If you'd rather do it yourself:

On your router (covers every device at home)

  1. Open a browser and go to your router's admin page — try 192.168.1.1 or 192.168.0.1. If neither works, check the sticker on the back of your router.
  2. Log in. The username and password are on that sticker if you haven't changed them.
  3. Find the DNS settings:
    • Netgear → Internet → Domain Name Server (DNS) Address
    • TP-Link → Advanced → Network → Internet → DNS
    • ASUS → WAN → WAN DNS Setting
    • Linksys → Connectivity → Local Network → DNS
    • BT / Sky / Virgin (UK) → Advanced Settings → DNS
  4. Set the primary DNS to the bridge IP address. Leave the secondary as your existing DNS.
  5. Save and restart the router.

On a single device

Windows — Settings → Network & Internet → your connection → Edit DNS → enter the bridge IP

Mac — System Settings → Network → your connection → Details → DNS → add the bridge IP

iPhone / iPad — Settings → Wi-Fi → tap (i) next to your network → Configure DNS → Manual → add the bridge IP

Android — Settings → Network → Private DNS → enter the bridge hostname

Keeping your preferred DNS

The bridge doesn't replace your existing DNS — it adds to it. All non-.tpt queries pass straight through to whatever DNS you currently use.

If you have a preferred DNS for privacy or speed (Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9) just let your gateway operator know. The bridge can forward to any upstream DNS you choose.

Frequently asked questions

Does this slow down my internet? No. Only .tpt queries hit the bridge. Everything else goes to your normal DNS at full speed.

What if I want to leave? Change your DNS back. Everything returns to exactly how it was.

Do I need to install any software? No. Just the one DNS setting, or run the setup script.

What is the bridge IP address? It's provided by whoever runs the gateway you're connecting to — like a phone number for the network. Ask your gateway operator.

Can I use .tpt email with my regular email app? Yes, if your gateway operator has set up SMTP compatibility.

Can I run my own gateway? Yes. See DEPLOY.md for server deployment or DESKTOP_HOSTING.md to run one from your home computer.