Egregoros

Signal feed

Timeline

Post

Remote status

Context

2
SLUFI is published!

https://thegoodwork.substack.com/p/slufi

A Simple, Lightweight, Unopinionated, Federation Interconnect.

The problem: While numerous network transports exist (cjdns, Yggdrasil, I2P, Tor, etc), and numerous name services exist (Namecoin, ENS, Unstoppable Domains, PKT, etc), almost all federation takes place over ICANN+IP because we currently have no way to federate across network boundaries, and ICANN+IP is the only thing that everybody has.

I claim that there is no possible solution SIMPLER than SLUFI, except with central authority or PRECIPITOUS loss of security. Furthermore, I claim there is no possible solution that is more secure than SLUFI, except with something like a blockchain and a PRECIPITOUS loss of simplicity.

So while I do not think this protocol is complete (yet), I do think SLUFI is the only realistic starting point for reaching a solution to this problem.

Tagging some people who might be interested:
@sun
@lain
@p
@mint
@jaff
@silverpill

I probably forgot a bunch of very important people, apologies in advance...
@cjd @sun @lain @mint @jaff @silverpill Interesting indeed.

> For each hostname, the node must periodically poll for updates since the time of its last request

This is not super practical for Tor hosts, I think. It involves hidden directory lookups that'll periodically fail.

> It’s important to note that because this proxy uses standard HTTPS CONNECT

SOCKS5 might be more useful unless you wanna do web only.
> that'll periodically fail

Might have mis-spoke here, what you want to put is the highest first_recv_time in the previous response. Failures are okay, just keep re-trying. ${exponential_backoff_best_practice_template}

> SOCKS5 might be more useful

(little known) HTTPS CONNECT switches to raw TCP so it's equivalent to SOCKS5 with the exception that it doesn't do UDP. That's actually required because SLUFI onion-tunnels another TLS through the proxy.

Huge advantage of HTTPS CONNECT over SOCKS5: You can identify with a client cert so you don't need to fuss around with per-proxy user/pass.

Replies

0
No replies yet.