| <link rel="import" href="../cool-clock/cool-clock.html"> | |
| <polymer-element name="my-element"> | |
| <template> | |
| <style> | |
| :host { | |
| position: absolute; | |
| width: 100%; | |
| height: 100%; |
| The below is ruby(ish) - but is really about matrix math | |
| array.transpose flips array around diagonal axis (UL to LR): | |
| a = [[1, 2, 3], | |
| [4, 5, 6], | |
| [7, 8, 9]] | |
| a.transpose => [[1, 4, 7], | |
| [2, 5, 8], |
Inspired by http://bl.ocks.org - this is me trying to learn d3, especially regarding the interactive node stuff.
If you see me doing something bloody insane - don't pity me, or laugh, teach me the right way!
This started with a flat-out copy-paste of one of Mike's force-directed tree demos - http://bl.ocks.org/mbostock/1062288
No promises are made as to how functional it will be before I get distracted by bright lights and pretty colors.
| tbortels [12:03 PM] | |
| Sigh. "For fastest results, use email" - ok, i prefer that. Go thru making request, fill out nice details, "Unable to Complete Your Request | |
| The content is unavailable." boom | |
| tbortels [12:04 PM] | |
| so - I'm moving on to phone contact. grr | |
| tbortels [12:09 PM] | |
| I give up. vmware phone support is useless, unless someone can show me the "give me a live person" button. |
I hereby claim:
To claim this, I am signing this object:
While doing wildly unrelated research, I came across the "AI Box Experiment" pages. After reading a bit, I was surprised to see ANY outcomes where the AI was let out; it seems fairly self-evident to me this should not happen. Because the conversations are private, I have not seen the arguments the AI player made - but while thinking about it, I suspect I can make a Gatekeeper argument that can counter them all - ie. I can argue to keep it in the box, and what the AI says is irrelevant.
Here is the argument, in the form of a "proof". I hesitate to use that term - it lack the rigor of a proper proof - but it is perhaps the framework or outline of a real proof, if you agree that the logic is basically sound. If you do not - I, personally, would appreciate reasonable, supported arguments about where it fails. I trust this community will not fall prey to the usual tropes of wishful thinking and so on. I would ask you follow each item, and only proceed if you agree; like any
So - that was just complex enough that it might be nice to document and share it.
So - I am using docker and --link to expose a redis database to only the apps that use it. Which (as of now) is fine, so long as those apps are on the same host. But - I wanted to use the redis 'slaveof' command to quickly replicate the data to another redis running on a different host. Yes - I could grab the db from disk, scp, and restore. But it's handy to be able to quickly spawn a new copy elsewhere. I could not simply restart the original redis container exposing ports, because it is prod with people reading/writing to it.
So - The solution that works is: Run a new container, exposing the port you want, linked to the original container - and use socat to bridge the internal link to the external port.
| input { | |
| stdin { | |
| type => "stdin-type" | |
| } | |
| file { | |
| type => "logstash" | |
| path => [ "/var/log/logstash/logstash.log" ] | |
| start_position => "beginning" |
| <!DOCTYPE html> | |
| <meta charset="utf-8"> | |
| <html lang="en"> | |
| <head> | |
| <script src="https://cdnjs.cloudflare.com/ajax/libs/d3/3.5.6/d3.min.js" charset="utf-8"></script> | |
| </head> | |
| <body> | |
| <div id="main"> | |
| </div> | |
| </body> |
| <html> | |
| <head> | |
| <title>My first Three.js app</title> | |
| <style> | |
| body { | |
| margin: 0; | |
| } | |
| canvas { | |
| width: 100%; | |
| height: 100% |