Only reduce if we have entries
Disable most of the setOneCat logs
adding more timings for firstrun and nextrun
dooooooof
Make Facebook friends synclet pege properly

Getting all the friends in one run takes 20-30 seconds and may be timing out the
worker in the eyes of its supervisor.
Fix podClient referencing error on undefined

Looks like `timings` doesn't always come back, so checking for `errors` on it
would bail and break my task loop.

Also linted.
Some debug output to see the timings a bit more
Fetch Facebook friends in smaller pages

At 500 friends/page, it take about 400ms to get a list of IDs, then 9-10s to get
all their data. At 100/page, it's ~270ms for the IDs and <3s for data. This is a
lot friendlier to the task queue and IJOD, so let's try it out.
Show the lengths of the injects
Make sure we have a valid object here
Need a valid object here
Make pods logic optional
Improve logging for task updating
lconfig extend by default, enable pods
Merge pull request #845 from Singly/bg-pods-local

Short-circuit pods, better logging
Make testSynclet.js unexecutable

Just so we can autocomplete `.sh` more easily.
Add script to reset one profile's config

Simple script, just resets the pid's config for testing.
Fix paging when testing sandboxed synclets

`testSynclet.js` wasn't looking at the sandboxed `nextRun`. Now it's hoisted up
where it's expected.
Make Instagram synclets page properly

These were taking up the worker process for upwards of 150 seconds during
recursion on long feeds. Now they page like everyone else, and I upped the page
size from `20` to `100` to be more efficient about it in general.

There's some fun behavior documented in `feed` regarding instagram's `/feed`
endpoint not accepting a timestamp like the rest of the endpoints. In short, we
get an empty set back if ever we pass a cursor ID that doesn't exist (was
probably deleted). This can only happen if someone deleted the post in between
us receiving the cursor URL from Instagram and the next synclet run, which if
the system is running well will be short. In that event, we'll think we've found
the end of the feed and stop going back in time. So while it's possible for us
to miss chunks in this event, I expect it to be quite rare.
Bugfixes for devices in friends.