Akeda Bagus

~Despite of the issue of all connected stores get the same notice~, here's my tests based on PR's instruction: - [x] user connected; expired - [x] has one expired sub...

> has one expired sub — message: Your subscription for [product name] expired. Renew for [price] to continue receiving updates and streamlined support > > has multiple subs of the...

Given that issues of using local cached data and missing price were addressed already, I'll retest followings: - [x] user connected; expired - [x] has one expired sub — message:...

#### My tests - [x] site is not connected; no message introduced by this PR - [x] no expired or expiring; no message - [x] expiring and autorenew disabled; enable...

Hi, I think the best approach to organize `checkers` and `notifiers` is to package it. Thus, the structure becomes: ``` text checkers/ http_status.go http_status_test.go ssh.go ssh_test.go ... checkers.go // defines...

I don't have any obvious reason other than organizing the structure. But yeah, they can go to separate files under the package main.

@vasilishin I'm having trouble testing this because the way Instagram returns data only from sandbox users. How did you test this? Also, I don't see `count` listed as param in...

`/users/self/feed` endpoint was deprecated, see https://www.instagram.com/developer/changelog/. I'll remove `user_feed` command. `user_recent_media` should works when you've valid access token set via config. Try `--help` for more information about the command. >...

Apologize, I'm closing the PR as I don't have the bandwidth at the moment to continue this. Some notes: 1. This works well on my local but didn't work as...