I have a FL icon in my browser window, the second one after Gmail, and now it points at the A8C instance, not feedland.org. I’m going to try to make this my main feedland. I think at this point it may be possible to do this, after the recent fixes.
What domain name to use?
I posted this a week or so ago on Slack, and today I figured out what a good first cut at the name would be: feedland.automattic.com. It matches the email address we use for confirmations, and I think it very clearly says what this server is. We’re booting up FeedLand at Automattic.
FeedLand docs converted to Markdown
To prepare for a future where hopefully lots of people are contributing to the user docs for FeedLand, I’ve converted them to Markdown, and they’re now in the docs folder on the a8c-FeedLand-Support repo, which is still currently private. If you’re at A8C and want to get involved, please let me know and I’ll authorize you for the site.
Here’s a link to the Getting Started document.
Still more work to do here.
New version of FeedLand server
Hooks up the new way of finding updated items to the river cache, so we can turn an config.flUseRiverCache back on, for better performance for users like me. 🙂
Update note here.
New features considered
I’ve written up two new ideas for features.
- Dynamic subscription lists.
- myTitle and myDescription for feeds. (Low-tech approach described.)
- Fixed keyboard problem in Feed List.
- Viewing a feed list with only one category.
- Video demo of Feed List page as a feed reader.
Removed items
I had two items here, one about wanting to review how we do static storage, and the other of very long delays in page loading, but I have new thinking on static storage (I guess I did the review myself) and the delays were probably due to connectivity where I’m working, so unless they reappear, I’m not concerned. There was an update (see below) that allows us to start caching rivers again on the A8C server, which will give the service an important performance boost.