Jon Sully

@joshmn any chance you could take a peek at this one?

Since `active` directly impacts the `find_or_create_by` from earlier this morning, it's a careful question 🤔 If a Subscription has no unsent mailings but isn't unsubscribed and isn't `ended`, should `active`...

Coming back to this quite a bit later. I now do think that the `active` scope _should_ include campaign subscriptions that are `completed?`. Subscriptions that have sent all their drips...

Under the hood `periodical` just clones the was-just-sent `mailing` and essentially calls ```ruby previous_mailing.send_at + params[:every] # e.g. 2.weeks ``` Which, is already pretty close to being jitter-able, but currently...

Ah, and one other note about your API thought there ^ (a separate issue we should open) is that calling `drip` multiple times with the same action name only yields...

I think the ideal periodical API ought to support a dynamic `every` _and_ an `until` arg, (optionally). IMO these should all work: ```ruby # these wouldn't be used together, they're...

Ah, to my last idea, I think that's already the case. I didn't realize it before but I think that while the `every:` key is supported in the basic `drip`...

> Do you have any instance where you have a mix of periodic and regular one-off drips in a Dripper? I don't know that my app has that at the...

I'm starting down the track of supporting a `Proc` for the `every:` key + adding `until:` support, since I think that would cover 90% of the bases with much less...

Hey @joshmn 👋 Just wanted to reach out and offer interest in helping with this gem/project if you're looking for some! I've spent the last couple of weeks integrating Caffeinate...