Split feeds into individual files

[nbastin]

Putting all the feeds in one file creates a few of problems:

• The file is completely rewritten from scratch during reload even if only a single feed is updated, causing extra wear on the type of flash devices that commonly exist on the types of machines that you might want a CLI podcast client on
• You can't selectively load parts of the file (at least using the standard json implementation), so if you have a large number of feeds with a large number of episodes, you load up megabytes of data you're never actually going to look at in the client

[xgi]

I don't thing this is unreasonable, but I would probably be more inclined to instead switch to a (serverless) database, i.e. sqlite. I thing manually handling paging (both reading and writing) may be more trouble than it's worth, personally.

[nbastin]

I wasn't thinking anything more exotic than simply putting individual feeds in their own files and continuing to use the filesystem as the datastore, although there are other things you could do with at least a k/v store. I haven't really thought too much about future uses of the data that might indicate a preference as to the type of datastore.