It will now become an S3 site. Further simplifying things on my servers. This is a milestone. A big bit of content I want to keep around. Until now it's been hosted by server software I've been running. Now I'm giving it to Amazon to worry about.
I have a script uploading all the bits right now.
Configuring it so it will be properly hosted by S3 (index files will be served).
When garbage-collection was introduced, we created a problem for people who import OPML subscription lists into River2.
A subscription must be associated with a user or else the subscription will be collected. This happened to Les. He would subscribe to an OPML list, and it would work, but on the next scan it would be collected.
This happens when you import the OPML instead of subscribing to it, which is how I use the app, which is why I didn't catch this error.
This is why we need a number of serious users who use the product in different ways to monitor problems after big changes.
Bring river2.root to the front and choose Update front Tool from the Tools menu.
Choose Import OPML from the River2 sub-menu of the Tools menu in the OPML Editor. Wait for the next scan, and look at the log. Did it unsubscribe from the feeds in the OPML? Then the fix didn't work. If the feeds were read properly, the fix did work.