Phil 1.10.19

7:00 – 4:00 ASRC

  • The fragility of decentralised trustless socio-technical systems
    • The blockchain technology promises to transform finance, money and even governments. However, analyses of blockchain applicability and robustness typically focus on isolated systems whose actors contribute mainly by running the consensus algorithm. Here, we highlight the importance of considering trustless platforms within the broader ecosystem that includes social and communication networks. As an example, we analyse the flash-crash observed on 21st June 2017 in the Ethereum platform and show that a major phenomenon of social coordination led to a catastrophic cascade of events across several interconnected systems. We propose the concept of “emergent centralisation” to describe situations where a single system becomes critically important for the functioning of the whole ecosystem, and argue that such situations are likely to become more and more frequent in interconnected socio-technical systems. We anticipate that the systemic approach we propose will have implications for future assessments of trustless systems and call for the attention of policy-makers on the fragility of our interconnected and rapidly changing world.
  • Realized this morning that the weight matrix is a connectivity matrix between the neurons. That means that there are some very interesting things that we could do with partially connected layers. Sending signals just to adjacent downstream nodes in 2D – nD
  • More DNN post. Need to incorporate neuron graphs with the weight graphs, and update the sections of code about graphing. Done! And yet, somehow I’m still tweaking…
  • Working on the NoI. It’s a grind… Done? Sent off to John D.
  • Back to Docker
    • docker build -t friendlyhello . # Create image using this directory’s Dockerfile
    • docker run -p 4000:80 friendlyhello # Run “friendlyname” mapping port 4000 to 80
    • docker run -d -p 4000:80 friendlyhello # Same thing, but in detached mode
    • docker container ls # List all running containers docker container ls -a # List all containers, even those not running
    • docker container stop <hash> # Gracefully stop the specified container
    • docker container kill <hash> # Force shutdown of the specified container
    • docker container rm <hash> # Remove specified container from this machine
    • docker container rm $(docker container ls -a -q) # Remove all containers
    • docker image ls -a # List all images on this machine
    • docker image rm <image id> # Remove specified image from this machine
    • docker image rm $(docker image ls -a -q) # Remove all images from this machine
    • docker login # Log in this CLI session using your Docker credentials
    • docker tag <image> username/repository:tag # Tag <image> for upload to registry
    • docker push username/repository:tag # Upload tagged image to registry
    • docker run username/repository:tag # Run image from a registry
  • Ok, let’s see how to integrate with IntelliJ – Nope, reworking the data structures for better queries (and best practices as well). Sigh.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.