Skip to main content

market for a new video camera

I don't want to say I'm conservative when it comes to electronics but I try to conserve time and space. I don't need or want expensive camera equipment because I have a fine camera on my phone... I just want my phone to have good enough picture quality and the ability to start fast, work in low light, good enough resolution, some zoom, plenty of battery. This is the minimal list. Pros want a lot more.

As recent as 3 weeks ago I started looking for a waterproof video camera. I was going on a father/daughter camping weekend and I wanted to record it for her.... and her mother. (a) I could not execute on time (b) I trusted my sister in-law to loan me her GoPro (c) never really tried hard enough to see if local friends had something I could borrow.

I regret my non decision terribly. And so now I'm in the market for a video recorder with some of these options because I'm not eve sure what I want.

  • low light
  • waterproof
  • video and stills
  • battery capacity
  • remote
  • adjustable
  • some video quality
  • audio quality
  • smart phone software
  • SIMPLE story editing
  • compatable video files
My current top 3 are:
  1. Hero Session - seems expensive once you add in all the obvious accessories
  2. ION AIR 3 - only mounts self and so no external light source
  3. contour roam 3 - 
  4. and there are many more
What I probably want is a waterproof Sony Bloggy but the gopro is at the top of the list.

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…