**"All code is A-GPL, you are not authorise to fork it, modify it and run it without refering to us!"** Original Founders Team will release from IPNS an IPFS reference (**/ipns/Qm*****) where to download CODE from the Demonstration #Swarm0 you will join.
## **This Software makes you responsible of your Digital and Social behaviour(s) ! It could make you evolve to a new level of consciousness. Ready...?**
- include ```$ASTROPORT/astroport/zen/tools/``` "natools", "nodename", ... tools in ```/usr/local/bin``` to make CODE lighter and easy use from all system App.
**On Astroport Station, NOW your Web2.0 code is running LOCAL! So it can access local filesystem where #Swarm0 shared data are connected with other Stations !!**
> No more need for Internet global routing available anytime. Once your stations are friends, they become SSB connected, and IPFS swarm peers connected also if possible...
http://localhost:10010 is the first official DApp we are presenting.
- ```natools.py``` (@tuxmain made) is used for **crypt/decrypt/sign/verify** using the ed25519 libsodium crypto
- ```nodename``` (@qo-op made) is finding the relative local or global Station hostname
- ```sbotc``` (@cel made) is used to send / read SSB chain.
- ```zen_MAKE.sh``` (@qo-op) is creating Zen containers. '***_zen***' open protocol IPNS nano DHT allowing PASSENGER mulitmedia file and json metadata.
- ```/g1sms``` (@qo-op) Main App & historical communication layer. Acting as a delegated "G1 wallet" manager, source of Zen IPFS technology and QRCode banking system.
Depending on your App available API, Front and Back End functions,
You'll get a level
- 1 Channel Scraping,
- 2 Synchronized API,
- 3 Dapp transformation OK :star: .
> 1 & 2 level benefit from new commnunication layers from (ssb libraries, js, go, rust, ...) and simple ipfs CLI commands. Notice that your Station will use double disk space until your data backend is fully using ipfs !!
2:star: Make use of G1/SSB/IPFS layers. Use localstore and publish/share/crypt your parameters, metadata with #Swarm0
```/home/$YOU/.zen/ipfs/.$IPFSNODEID/nextcloud```
3 :star: Store $WHOAMI DATA to ipfs #Swarm0 into.
```/home/$YOU/.zen/ipfs/$G1PUB/nextcloud```
An App on Astroport is a Flavour.
It is (like in UNIX) just a new FIFO data channel, it connects into its open protocol data and indexes layer. Could be host and routes, ipfs and ipns... Once your #Swarm0 gets bigger, It can read and write but soon extract coherence from your DATA with "conscious deep learning".
**Rememeber, even if you DApp can be accessed on localhost, relative security level depends on Trust levels within your friends and their friends! Crypt data as you need it**
- HyperWeb ipfs p2p layer. (```ipfs p2p --help```). YES! Forward any TCP port used by your Station App, and create an "Everywhere API" to anyone in same #Swarm0
Each USER (peer) is provising or needing a ressource, let's say :carrot:
Each RESSOURCE needs to be "made or consume", bu some "know how" have to be chained in time and space to succeed this cycle.
In **(now collapsing?) actual Industrial Global Economy**, you cannot be aware of how :carrot: are made and distributed before your can enjoy it... Only global "KNOW HOW" is increasing, while disappearing from your LOCAL perspective...
**In LOCAL Zen Economy : YES!! YOU CAN KEEP BOTH**
**In our model, all process from seeding, planting, growing, croping, sharing, consuming is included. FROM PEOPLE TO PEOPLE, P2P, every one is valuable. Individual and Global "KnowHow" is related and connected.**
**Then A, B, C, D, E, F, G, H, I, J, K, ... and as much as it has to be can share knwowledge, howto, know how and transform (-) into (+) to be and buid a MAKERS society**
> [Basically on Evolutionary Code your code evolves not because you plan, but because the environment around it pushes it into certain directions.](https://medium.com/@_rchaves_/designed-v-evolutionary-code-d52a54408c8f)