Skip to main content

Artificial Intelligence - Microsoft Meltdown

Journeyman Pictures posted a vlog post on youtube and described a problem with Microsoft's Tay. Apparently Twiter trolls managed to turn the AI into a bad actor; and as a result M.S. killed the project. Comments offered by Alistair Charlton are extremely naive and show only his ignorance on the subject and while the comments might have appears useful to the producers of the post it almost instantly discredits a field in computer science. And frankly shares the sh*t out of me.

As a result of the AI programming the AI took on pro Nazi sentiment, however, from the AI's point of view there is nothing that says Nazism is good or bad. It simply took a position on a subject that it was convinced was inline with it's learning. Almost the same can be said of Germany in WWII. Many Germans thought they were doing the right thing to a point and without all the information we have now. And so the same can be said of the AI.

Morality and the sense of right and wrong are still human traits and ANY artificial intelligence that is going to encroach into the Tay did or was intended to MUST understand these things before it can be unleashed. An unrestrained AI could literally make every scifi horror movie a reality. As for Alistar's comment that there is nothing wrong with an AI they generates hate speech. He should return his diploma and begin again.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…