Am Samstag, 11. April 2015, 01:34:17 schrieb Matthew Toseland: > Transport plugins are written by a GSoC student (Chetan), but need major > refactoring and fixing of concurrency issues (plus implementing > stream/TCP plugins)
How much work would it be if you left out stream stuff? If we have packet-based transports, plugins should be able to handle the transformation to and from TCP, so first doing only packet-based transports would give the capabilities to do more. > Traffic flow analysis is cheap nowadays, and no amount of stego can > get us away from that. We could simulate full traffic profiles: capture the traffic between applications, then fake it. Video telephony, static noise on a mumble chat (using an intermediate server for spreading it), bunny cams. Even simply sending emails with attachments. That increases latency and decreases throughput a lot, but that’s something Freenet can already cope with to some degree: The bandwidth of nodes already varies over several orders of magnitude. And it’s not like the proposal is new. But it needs core support ⇒ transport plugins I don’t intend to say “toad should do this over summer”, just “please don’t discard it prematurely”. Best wishes, Arne
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
