minion-design.pdf / low bandwidth high latency long term connections

Zenaan Harkness zen at freedbms.net
Mon Oct 21 18:09:17 PDT 2019


On Mon, Oct 21, 2019 at 09:47:40PM -0300, Punk - Stasi 2.0 wrote:
> On Tue, 22 Oct 2019 11:03:59 +1100
> Zenaan Harkness <zen at freedbms.net> wrote:
> 
> > 1KiB/s is much too fat, and at 80MiB/day (2.4GiB per month) folks
> > will complain.
> 
> 	well it depends on what kind of activity you want to hide. If you
> 	want to make a VoIP call at say 4 kilobytes/s (or less?) then
> 	your link must operate at that rate for 'some' time  before and
> 	after you make the call. Say, a day? 

Indeed.

Phone calls, and high-value txts, are different streams.


> 	...so a good (best?) solution may be to run a file sharing service and serve 'pirated content'. 

HA :D


> > But let's consider just 512 bytes every 10 minutes (a single small
> > UDP packet):
> 
> 	so ypu're stuck with that rate of traffic. If you send more that
> 	one packet every 10 minutes you're leaking a certain amount of
> 	information. And 512 bytes every 10 minutes seems kinda slow...

Yes. It's a type of stream, that's all.

Teenagers probably need 10KiB/s just for text messaging their
"friends" :)

Different stream types are needed for different activities.

covfefe net is not limited to one stream at a time.

covfefe net is not limited to one stream type at a time.

I would personally be inclined to run a "regular txt" stream (which
can obviously cater for high value texts), as well as a "phone call
stream" - and yes, you're right, because we're packet switched by
design, we're just choosing a baseload - and if you can't afford that
at all times, then you run it for periods of time when you can afford
it, and/or can afford to provide that to your friends.





More information about the cypherpunks mailing list