r4 backup <channel> should download json, just as the app interface allows

[4www]

In order to make the "cross-app experience more isomorphic", it would be nice if r4 backup <channel> could download the json backup of a channel (or at least a user's if logged in).

With the new /settings/import/backup

Currently r4 dl <channel> creates the folders <channel>/tracks/, so somehow either:

• r4 dl would also download a backup (would work for anon users?)
• r4 backup would check/create the <channel>/backup-date.json folder & file?

Questions/Issues:

• dl and backup commands don't have the same "timeline", while backup is almost instant (json), dl could takes while (files); therefore a backup.json file could very well "not be in sync" with what the tracks are? Not sure it is an issue, better always have a fresh dl (at the right place, with correct naming), whatever the command that is run?
• maybe we can have backup (just for json), and dl (calls backup and dl files)?

[oskarrough]

it can!

r4 channel view ko002 --format json
r4 track list --channel ko002 --format json

I think it's good to avoid backup/export commands, when the above already exists. So view is stdout and dl is to disk. Two commands. And then we could have a shortcut backup <slug that simply calls the two above somehow into a {channel, tracks} format perhaps? Is that our "backup"

Edit, also looking at those two commands it's a bit confusing.. track list --channel is odd to get all tracks, but not sure what would be better if r4 track is the main command.

[4www]

but also nice to respect the user facing terminology no? it would be nice if backup produces the exact same output as the web app gui interface export btn?

We tried keeping backup version numbers before too, to be able to know "what format" it is and which data it contains.

[oskarrough]

yes! maybe

r4 backup <slug> = {
  channel: r4 channel view ko002 --format json
  tracks: r4 track list --channel ko002 --format json
  created_at: Date
  version: String
}