Over the weekend Dave posted a roadmap for FeedLand. As I understand the gist of the roadmap, there are two significant changes coming with what I will call FeedLand Version 2. The identity model is moving from Twitter Oauth to Email, which I think will work the same as micro.blog. The other major change is that the backend for Version 2 will be released as open source so that users can deploy the back end to their own servers.#

I think Dave is doing the same with FeedLand that he did with Little Outliner and I think Drummer but I am more familiar with Little Outliner. Little Outliner can integrate with a Nodejs app called nodeStorage.js. One can deploy nodeStorage to their own server and thus control where their data is stored, but the frontend remains proprietary and hosted by Dave. If Dave uses this same model, one will continue accessing FeedLand via feedland.org, but they will be able to change what backend is used by executing a command via the browser console. I regularly switch Little Outliner between the default backend that Dave hosts and my own that I host in Google Cloud.#

As an aside, nodeStorage also supports 1999.io, which is one of Dave's blogging platforms that preceded Drummer. Basically, nodeStorage handles the storage of files, in the case for Little Outliner outline files in OPML and in the case of 1999.io blog posts in a JSON file, on the server it is hosted on or in AWS. For 1999.io I believe nodeStorage also handles the generation of each blog post into a separate HTML file and all of the navigation that is needed to produce a blog of static HTML pages. I think nodeStorage can also serve the blog from the same server the app is hosted on, or, as I do, it copies the generated HTML to an AWS S3 bucket, and if that bucket is configured be a public Internet site then it hosts the blog. The blog that I wrote using 1999 is hosted in AWS and can exist independent of the server hosting nodeStorage but there are components (urlTwitterServer and urlChatLogSocket) that call back to originating server that causes a delay in the site loading if the originating server does not respond. (View source of my 1999.io blog to see what I mean.) Because I've stopped using 1999.io I have considered decommissioning the server I have hosting nodeStorage but have not so do this impact on the blog site loading.#

I think that Dave is hopeful that other developers will write and support their own frontend applications that will use FeedLand for feed management. It will be interesting to see whether any developers actually take the opportunity to produce their own RSS applications. #