[Mesh] Infographic

[Stuart Gathman]

On 08/15/2017 05:48 PM, John wrote:
> Also I had some downtime on a Windows machine and made some propaganda
> (same image in two formats):
>
> https://cityofclay.000webhostapp.com/CMN.svg 
Cool!  When we have a box (like the pittmesh box) ready, we can make
bookmarks (have them printed) to hand out.  But I also want to list the
software stack that is taking shape (probably on another handout).

  Cjdns        Windows, Mac, Linux, Android (experimental)       

        IP6 mesh (provides global static IP6 not under central control)

  Linphone (IP6 SIP client)    Windows,Mac,Linux,Android.iOS            
                      Needs IP6 on device to be decentralized
                Also any SIP client supporting IP6

        voice/video calls and text messaging with no telco, no sip
provider, no registration, no centralized anything

  Patchwork (SSB client)  Windows,Mac,Linux,Android (experimental)      
Needs improved packaging (npm doesn't cut it)
              Also other ssb clients: minbay,patchfoo,patchbay
 
        Social media (like facebook) with no registration, no
centralized collecting of data
        Gathering  coordination (like meetup)
        decentralized git repositories (like github)
        ...  other applications utilizing signed append only logs as
they are developed

BTW, I'm happy to just use the pittmesh box - although I wasn't planning
on offering any access to ICANN internet.  I'll have to look at
protocols and requirements.  CJdns easily provides tunneled access to
ICANN via a box on both ICANN and cjdns - but configuration involves
editing a text config file, which is probably beyond typical Windows
users.  We'd probably need a gui with a simple dialog to assign local
private ips to cjdns public keys (we can assume that gui users will have
a typical ip4 only natted ICANN connection).

How does Pittmesh handle legal protection for mesh operators?  (I.e.
what if some jerk is sharing child porn or other illegal material over
the mesh?)