This project can stream audio to an Apple TV and includes details about the (now required) pairing protocol: https://github.com/philippe44/RAOP-Player

Thank you!

Possibly relevant tidbit from a recent Guccifer 1.0 interview: He used 'Russian proxy servers because they were “the fastest.”' I imagine they're referring to VPNs. http://www.foxnews.com/us/2017/08/11/guccifer-calls-fox-from...

To help solve the nested/recursive query problem, Facebook created dataloader: https://github.com/facebook/dataloader There's graphql integration info on the blog: http://graphql.org/blog/rest-api-graphql-wrapper/#taming-pat...

I probably was a bit unclear. Lets say I've got a family tree stored in a db that goes back 1000 years.

Through graphql I want to find my first ancestor following all mothers backwards. The query would be:

  query familyTree {
    name,
    mother {
      name,
      mother {
        ..and so on for an unknown number of nestings
      }
    }
  }

Dataloader solves batching of the nested query on the server, but doesn't solve the problem of not knowing what the correct number of nestings the query should have.

Of course it's possible to create a new graphql endpoint for this type of query, but then we've just recreated REST in graphql.

Hmm, you're not quite thinking in GraphQL properly. That isn't how your schema should be designed.

Your mother field should resolve to a Person type, with a mother and/or ancestors field, which would be a graphql list type of the Person type.

Something like this:

  Person {
    mother: Person
    femaleAncestors: [Person]
  }

Yeah ideally ancestors would be a `connection`/`edge` with filters:

``` Person { ancestors(gender: Female, orderby: [AGE], first: 10) { node { name } } } ```

Absolutely. Personally I haven't made much use of NoSQL, I'm sure there are plenty of use cases, but for ancestry I would still use a relational db.

I do see how nested objects might look like a perfect fit for this, since families are literally "nested objects". Perhaps there are plenty of advantages to using NoSQL and shaping the data this way... but the thought of creating an API With that structure is terrifying to me, haha.

Question to OP: are you using this structure for a live api/website I can take a look at? Does each node have an absolute ID? Do you normalize your data? Maybe I'm thinking too much in relational terms here? I'm genuinely curious about this.

Home-assistant also has a great homebridge plugin (https://github.com/home-assistant/homebridge-homeassistant) to easily bridge devices to HomeKit. I got home-assistant talking to zwave and zigbee with a Linear HUSBZB-1 stick (new version does both) and finally threw my wink hub in the garbage. Even through Home app -> homebridge -> home-assistant, everything is super fast and 100% local, unlike most of the commercial hubs.

But we either elect them or elect the reps that appoint them, and we have (some) recourse to make them explain their reasoning, which they usually offer openly.

And judges' results are checked by appeals courts. If a judge is found to, consistently, base their decisions on some illegal bias, they can be impeached and discharged of their duties. It's unfortunate for their victims, but it's small scale.

When you move biases from one person into a whole system, be encoding them in some poorly considered model and executing it at scale, then the process of correcting it can be far more difficult (though problems should also arise much faster so it shouldn't persist as long, but that's only in theory, not practice).

Your guide mentions setting window size and taking screenshots, which I thought were not currently working via chromedriver. Do you know if that was fixed or is there something else going on?

Setting window size via the ChromeDriver API didn't work for me but I was able to set it using a ChromeOptions command-line argument as I do in the guide. Screenshots seem to work fine on Linux but I haven't tried on other platforms.

My outgoing message is a close proximity iPhone recording of my 93 dodge dakota's door buzzer. Seems to also solve the VM problem, although the diligent VMers express confusion often. But those aren't VMs I'm interested in receiving, so it kinda works out.

Steely Dan even wrote a song about it.

I've read the lyrics and don't have the cultural background to get everything. I couldn't find anything racist in it and don't think it was supposed to. Is that correct? I'm asking because you mentioned it in this context here.

In the case of left-pad, 2538464 of its 2550569 downloads last month are attributed to dependents of the line-numbers package (https://www.npmjs.com/package/line-numbers). So it would appear that relatively few people directly rely on left-pad, which highlights the importance of vetting the dependencies of dependencies.

This is in the description of line-numbers:

DEPRECATED. This is a rather silly package that I do not recommend using. It's easier to copy the ~20 lines of code of this package and customize that code, rather than downloading and learning how to use this package.

Committed five hours ago: https://github.com/lydell/line-numbers/commit/711f6ad0eb1771...

This mess appears to have convinced the author of that.

About 2/3 of those (1.7M) were from babel-code-frame, which is a core dependency of babel:

https://www.npmjs.com/package/babel-code-frame

And the fix was just to drop the functionality and inline the function as a no-op:

https://github.com/babel/babel/commit/09287643c712bcd203bbd6...

I wonder if they're kilns or furnaces rather than non-functional monuments, given the historical record of trade from the region.

I would expect the interior to still be blackened. Here is the photo from the article closer up:

https://maptia.imgix.net/photos/75985/1456101557.jpg?cs=srgb...

From what I gather from other articles, no human remains have ever been extracted from them. Perhaps the buildings were used for a religious purpose or for temporary shelter.