#Muddle might appear to be #vaporware since it fails the "show me the code" style test (#POCOGTFO) but in reality the code isn't important and, besides, #TMTOWTDI

What it is is a particular refinement of the idea of deniable encryption. One that is very practical and flexible. It does, however, rely on the idea that it should be OK for normal people to have access to decent cryptographic tools to enable them to exchange messages securely while also allowing them freedom of association and the ability to build up their own networks, regardless of external snoops who might be using the metadata (who is in contact with who) to infer association.

#Muddle starts with #noise but beyond that, it should be possible to embed #signals and beyond that it could could be used to build #communities

The biggest problem, of course, is that all of our metadata is being fed into systems that map our social networks. That's why #muddle as a #SharedNoise network helps to frustrate this.

IDK... this is kind of like a partial #manifesto but I'm not sure about how to write such things ...

The MTA site I found lists bus routes at each stop using commas with alpha first.
like: "OR, 40, 59, 63".
In other words, way the physical signs are ordered.
In #OSM, routes have been joined with semi-colons, and alpha last (ASCII sort).
To compare each stop record in OSM against the bus company, I reached for the camel book.
#TMTOWTDI

$ cat bus1.t
OR, 40, 59, 63
40, 59, 63
40

$ cat bus1.t | perl bus_route.pl
OR, 40, 59, 63
40;59;63;OR
40, 59, 63
40;59;63
40
40

Next, SQL materialized view?

A short style poll for the #SAPCommunityRevamp - which do you prefer?

##BluePencil
#TMTOWTDI