diff --git a/graphs/.$anonsimplex.drawio.bkp b/graphs/.$anonsimplex.drawio.bkp
new file mode 100644
index 0000000..07ba4ce
--- /dev/null
+++ b/graphs/.$anonsimplex.drawio.bkp
@@ -0,0 +1,96 @@
+
A common misconception that people seem to have is that you wouldnt be able to communicate with regular simplex users that don't have Tor connectivity, when you're only using your own onion-only simplex servers. But that's not true, you're not even isolated when using onion-only servers. This mode of thinking comes the fact that traditional federated apps (like the fediverse) don't care about serverside anonymity. But, lucky for us, the official simplex servers also allow Tor connections in between simplex servers, which makes this whole setup possible.
+In reality, thanks to Simplex's Private Routing protocol, (which is a 2 hop routing protocol), your trusted simplex server (which is onion-only) communicates with the other party's trusted simplex server, as long as they have Tor connectivity. And if the other peer is using the default Simplex Servers, which all have Tor connectivity, then they can still communicate to your own onion-only simplex server, which ensures that you're not isolated when you want to have a public, yet anonymous community like the one we have at Nowhere.
+That's what we are going for in this tutorial. We're going to setup a simplex server that is onion-only, to protect the serverside anonymity, and we'll use our simplex client to only connect through our onion-only simplex server, and we'll create groupchats with it so that we can have our own public, yet anonymous chatroom.
+