buku 4.1
========
- [x] Have you followed the [guidelines for contributing](https://github.com/Homebrew/homebrew-core/blob/master/CONTRIBUTING.md)?
- [x] Have you checked that there aren't other open [pull requests](https://github.com/Homebrew/homebrew-core/pulls) for the same formula update/change?
- [x] Have you built your formula locally with `brew install --build-from-source <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Is your test running fine `brew test <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Does your build pass `brew audit --strict <formula>` (after doing `brew install <formula>`)?
-----
> Unless someone you follow has been reassigned to another group, you don't need to change _config.yml a bit.
To expand on that, even if someone you follow has been reassigned, you don't need to update `_config.yml` unless you set `group_id` to something nonzero.
No problem. In fact, a `group_id` of 0 includes every single member — past, present, or future — in all groups. Unless someone you follow has been reassigned to another group, you don't need to change `_config.yml` a bit.
Thanks for the reminder.
I don't hard code or download any member list; see #1. In the default configuration, `group_id` is 0, so the entire group is crawled. One may set `group_id` to 10, 11 or 12 (I guess 13 and 14 will be shuttered?) to limit the scope, but that's the highest granularity, and that's entirely the user's decision.
I don't see any change in the API, so things should continue to work normally. There's also a daily Travis job to ensure this. But I can leave this open for a few days just in case.