So I'm thinking, should I publish specs or wait till I have the releasable code… IRL gets in the way of development. What do tech anons think?

True peer to peer mesh over IP.

Linux sockets in C - protocol implementation.

Port agile.

Independent of DNS - IP to IP as IP4 or IPv6

Short message (burst) data exchange.

File, document, image exchange.

Runs on a $35 Raspberry Pi up to a high end Linux machine.

LAMP architecture, served to local devices as web page.

Requires only knowing one active IP on this mesh. (IP can be communicate anywhere)

Active IPs shared amongst peers.

Transmits in the open because there is no way to prove message origination without a full snapshot in time of entire internet state, and deters illegality pr abuse, because Feds can run a peer just like anyone else.

Messages propagate across active mesh.

No way to communicate in groups without being universally visible.

NO CENTRAL POINT OF CONTROL/CENSORSHIP

If the Internet is functioning, this works.

I call it HiveMesh.

>>14272920

Commercial VPNs block torrent traffic actively.

This is why torrents don't work over VPN.

>TCP: Typically, BitTorrent uses TCP as its transport protocol. The well known TCP port for BitTorrent traffic is 6881-6889 (and 6969 for the tracker port).

Network infrastructure owners simply block those port numbers and u r fuxxed.

You out there CM?

>>14272969

I'll write it up and push it out. No ownership claims.

And there's more in it to eliminate bots and shills.

I call that Darwinian propagation. It's pretty cool. Only the messages with consensus as being worthy propagate.

>>14273008

Fuck off with your bigot shit Gary