http://scripting.com/2025/09/17.html#a211133
http://scripting.com/2025/09/17.html#a211133
This question has come up quite a bit lately.
People don't know that there are two places you can use FeedLand, feedland.org and feedland.com.
There's a lot of history here, and some uncertainty about the future, so there's not much I can do other than explain the situation.
First you're welcome to use either of them.
feedland.org is running on a simple small server on Digital Ocean, and feedland.com is on Automattic's VIP network.
If feedland.org gets overloaded, it gets slow.
if feedland.com gets overloaded, it adds more servers and should stay about the same at all times.
You should pick one and use it and not have two accounts, but people accidentally create them, because in some places we point to .com and in others we the default is .org. It's because we haven't gotten it together yet.
There are also performance issues on .com -- ones that we still need to address.
That's about all I can say at this point. At the same time I'm working on a whole other product while all this is happening, and I'm not that young, and really can only work so many hours a day before I have to stop. A fact.
And I'm really glad so many new people are trying FeedLand. I use it myself in so many ways. And it will be deeply integrated with WordLand in the next release. I'm not kidding.
I wrote a piece in October 1996 after attending a conference of the tech industry that as it turns out was in its final stages. This was one of the last times it met. I was coming from the web, and wanted to see if anyone else was ready to change how we work with each other.
I've been following that ideal ever since, people seem to misinterpret it for subservience or weakness, or a pretense to cover another kind of greed, when it's really sincere, and all about strength. Sometimes people say yes, and when that happens magical things happen. I swear to god. I've been there. I've done it, it's not something you can do on your own, by definition. It's rare when people actually help each other and thereby create something. It's why the Beatles are such a great story. Someday I still hope to be part of a group like that. Right now, it's still totally everyone for themself. That is breaking. Read the news. But I believe if we did start really collaborating and not just talking about it, things would change very very quickly. Things would happen that can't happen until we work together.
I had it figured out in 1996, but still haven't figured out how to make it happen, and time is running out.
Reminder: Sept 18, one week from today, is the 3rd anniversary of the 20th anniversary of the release of RSS 2.0. I often forget to mark that day. It's not an event that's marked by others very often, but in my humble opinion, it deserves more respect than it gets.
Around the time of the 20th anniversary I decided to swing back and see what more we could do with RSS. It had been sitting there basically going nowhere for most of those 20 years. I want to be clear, there were good and useful products created and supported, but there was none of the innovation that would have happened if it hadn't been so severely injured by Google and the many VC-backed startups hacking away at it.
A format like RSS has to be loved. And if you make it too complicated or vague, with too much political shuffling of the deck what you get is ActivityPub. That's what RSS would have become if it went down the path the tech industry wanted to take it down. We have a perfect artifact to look at. An A-B comparison. Couldn't be more stark. And, after almost 23 years, RSS is still simple.
Anyway, around the 20th anniversary, in the leadup to it, I decided if no one else was going to invest in RSS, I would, and let's see what comes of it.
The result was FeedLand which is fundamentally different from all the other feed readers in that its subscription model is patterned after the twitter-like social media apps. Everyone's subscription list is public. I can look at your list and you can look at mine. You can also put categories on the feeds you subscribe to and route them to other servers doing other things, through the magic of the web. And get this -- you can even subscribe to a category of my subscriptions. Lots of power there, but still it's simple.
FeedLand is the perfect back-end for a twitter-like system, for the feeds part. And for the words, the perfect back-end is WordPress. I only discovered that about 1.5 years ago. And I had to see what it looks like. No more tiny little text boxes, WordLand is a real editor that supports the basic writing features of the web. How do I know? Because it saves its data in Markdown. That has come to be the defining format for the text-based web. One which has been totally ignored by the twitter-like systems. Markdown is like MP3. If you're mixing sound into feeds you use MP3 of course. It's there for you to use. As was Markdown. If you're mixing text you're mixing Markdown.
So while everyone was dancing on Twitter's dumpster fire of a social network I decided to build on something much bigger. The web. RSS and Markdown. WordPress and FeedLand.
The name Really Simple Syndication is supposed to make you smile, while most techie formats make you want to pull your hair out. RSS reads pretty well even if you know nothing about feeds and XML. I wish the browser people hadn't insisted on masking it with ugly CSS style sheets. I like lifting the hood of a car to see what's there even though I don't know what many of the things in there do. I learn by doing it.
RSS isn't ugly, it's brilliant, and shouldn't be fear-inducing, hence the promise: it's really simple.
I asked ChatGPT to provide bullet points for yesterday's podcast. I thought this time it did a really good job. It did misunderstand some things I said, I just deleted those, below.
There's a new version of FeedLand, v0.7.0.
Here's the thread where we discussed the testing of the new release. It worked everywhere we installed it, so it seems fair to open it up to people running their own FeedLand instances.
The only features it adds are ones needed to use it with the new version of WordLand, coming soon now.
But if you have the time, it requires an update to the database, so it's not the usual thing. It explains at the beginning of the thread what the change is to the database.
Here are the instructions for doing the upgrade.
If you're installing a new instance, the instructions are the same as always.
If you have trouble, post a note on the thread.
Thanks to Scott Hanson for validating the new version. It's always important to have someone to check my work.
Yesterday's note on scripting.com about feedland.org was not the whole story. In the end I thought it made more sense to start the database over from the start.
There were a few users who subscribed to feeds that were constantly updating, and they never came back to use FeedLand. So as soon as I started it back up it started loading new items at a very high rate, and after a couple of hours it was still going. There aren't that many people using feedland.org, so I thought the best thing to do is to start over and hopefully people will figure out how to resubscribe to the feeds they want to follow.
Then I felt that people might be able to use a few tips on how to get going again, so that's what this post is about.
Sign off and on
First thing you should do is sign off and sign back on.
You will still have the credentials in your browser, but the server doesn't know about them, so when you try to do something that requires you being logged in it will fail. But if you sign off and on again, that will take care of that problem.
To sign off, choose the command in the system menu at the right end of the menubar.
Once you're signed off the only option will be to sign back on. :-)
Restore subscription list
How to restore from a backup of your subscription list.
From the first menu, choose Subscribe/From an OPML File.
Here's a screen shot.
Questions?
I started a thread on the support site for questions.