Off by one while parsing vertex limit.
Things work better when you initialize memory.
Ensure string_t stays null-terminated.

Reallocating didn't fill with zeros.
Replace hand-written memcpy with memcpy.

It's much faster.  Honest.
Turn on NDEBUG in community code.

There are painful race conditions in community.c's self-debugging bits.
Let client read from stdin to support piping compressed data.
Output min/max timestamp information for each batch, for Pacific.

This is specialized for output in the Pacific timezone, the two demos of
which I know.  I don't change my laptop's timezone from Eastern no
matter where I am, so I won't rely on the TZ setting.

Not sure I have all the timezone aspects quite right...  Thought
the PST->PDT transition occurred within this period, but it doesn't.
Add some processing time information.

Looks too good to be true.  Printing it seems to have reduced the time.
I'm worried.
Fix client stdin argument parsing.
Move date output formating outside of timed section.
Add a simple seed-set expansion routine.

The routine is in the wrong place (json utils), adds a total weight into
STINGER that likely is best maintained separately, etc.  The algorithn
is O(|S|^2 + volume of one more step out) where |S| is the size of the
output.  Not pretty.

Amusingly, this runs concurrently with changes to the STINGER data
structure.  Because we have only insertions, this is ok.  Deletions,
well, that's kinda an open problem.  The later routine that picks up the
set and lists the edges may have to cope.

Maintaining the total weight separately can work entirely on the batch
for insertions, but not removals:

  - Given a batch of insertions / positive increments:
    - Just add the weights.
  - Given a batch of removals / decrements:
    - Need to know the edge weights being removed.

STING batch preprocessing should (eventually) annotate the edge removals
and weight decrements with existing edge information that summarizes all
the edges the requested types to be removed/decremented.
Outline the current handle in red.
Grow the labeled display according to modularity.

Seems to produce more interesting images.
Futz with the HTML & CSS to display properly for me; move filters up.

Removing many of the class="row" leaves the text on the screen rather
than far off to the left.

Also, moved two interesting filters up for playing.
Add a first-level tie-breaking rule for local clustering.

Overall, gives a pretty dang clustered-looking visual.  There is one
place where I think I'm double-counting, but it "works."
Do not *display* the Twitter handle.

This makes a bit too much information available for a public demo.
scrubbing names
merging changes