First off, signed up. This looks like a pretty sweet tool for home automation.

I'm slowly adding home automation to my house, but I'm a little more privacy oriented. I totally recognize I might not be your target audience with some of my constraints. Couple questions: If the service is paid (monthly or for a 1 time app purchase); how much is getting published to your servers? Because I like the control over something as intrusive as cameras in my house I'd prefer to self-host as much as I can.

Does it have to be the camera you provide/sell or could a high enough quality camera do that?

Pillar Technology http://pillartechnology.com/careers#apply-now

Locations: Des Moines, IA; Chicago, IL; Indianapolis, IN; Ann Arbor MI; Columbus, OH

Pillar is a software development and consulting company that focuses on speed to value for it's clients. On a daily basis developers practice TDD and Pair Programming (not just talk about it). Types of work range from embedded systems, web apps, and DevOps. Learn more about us at http://pillartechnology.com.

If you have any questions feel free to email me at crolek at pillartechnology dot com.

I would suggest checking out https://claudiajs.com/. I used it for a few quick API Gateway to Lambda things and it seems to be pretty sweet so far.

They switched from angular to essentially a static site for SEO reasons. I wonder if they're batch generating the static pages or making them dynamically on request.

We generate the pages dynamically. When code gets pushed to a repository indexed by Sourcegraph, we re-analyze it, which means that the location of definitions/references changes and the stats about who uses what change, too. This happens fairly often, so it's easier just to generate pages dynamically.

If you want to get an idea of our site architecture, you can check out https://sourcegraph.com/github.com/sourcegraph/thesrc. (It's a link aggregation site (thesrc.org) that pulls from HN, Reddit, and a few other places and only displays links with programming-related content.) We made it to share some patterns we found useful for building a web app in Go, and the interfaces and structure mirror how Sourcegraph.com is designed. There's also a talk here if you're interested: http://www.youtube.com/watch?v=7zYXhhrRn2E.

That hits close to home. I recently built a single page app with Backbone and SEO traffic is non-existent.

So now I'm dynamically generating pages on the backend, and serving them along with the javascript app so there's some some indexable static content. There are a few ways to directly reuse your client-side code on the server, but they all seem pretty hacky and convoluted.

I bought into the notion that the backend should just be a client-agnostic API, but that's an extreme position that should be considered when your site/app doesn't have any indexable content to begin with. If I could only go back in time...

ReactJS is awesome here. You write clientside code but you just run that clientside code on the server on request to prerender an initial DOM. And then your client hooks into that DOM. It has worked like a charm for me.

I tried an early version, and I was impressed, but my app relied on an CSS transition that was causing an issue with React. It looks like they've improved on that with ReactTransitionGroup, so I'll check it out again. Thanks!

> I bought into the notion that the backend should just be a client-agnostic API

There can be more than one backend -- your API is a microservice and you can have another backend that proxies this service and renders templates server-side. This also means you can define SEO-friendly URIs as opposed to your presumably RESTful API endpoints.

Yeah, this is the approach I've transitioned to. It's certainly better overall, but there's still an issue of maintaining some duplicated code on the server side and the client side.

There are some projects that specifically address this (Rendr, Lazo, Ezel), but I haven't made the switch to one of those yet.

I've used the "first" (?) version of Sourcegraph and now this new one, and I have to say I'm a huge fan. I'm learning Go in the evenings and I was struggling to grasp some of the concepts in Go and how to use the Gorilla package. Personally, I learn better after I skim the API, look at an example and rinse/repeat as needed. For me, Sourcegraph is a great way to help speed up that process of finding that one example that helps make whatever it is "click".

I've been using their Chrome Extension because it injects their stuff right onto Github pages. Now all they need to do is make one for Firefox, so I can go back to Firefox.

Disclaimer: I meet Quinn at GopherCon and we talked about Sourcegraph. I loved the idea then, and I still do now.

I'd totally use this to respond to my co-workers emails. If you post it to github or somewhere send me a link please. :)