Back in August I released a WordPress plugin for showing a FeedLand river — the stream of items from the feeds a FeedLand user subscribes to — on a WordPress page or post. As of yesterday it's officially published on the WordPress.org Plugin Directory:

https://wordpress.org/plugins/river-embed-for-feedland/

That means you no longer need GitHub at all. From your site's dashboard:

1. Plugins > Add New, search "River Embed for FeedLand", install, activate.
2. Settings > River Embed, enter the FeedLand username whose river you want to show.
3. Drop the [feedland-rivers] shortcode on a page, post, or widget.

Everything from the original post still applies: it fetches the river server-side and renders it in a sandboxed iframe, so it can't leak feed content into your theme and your theme can't clobber its styling. No third-party fonts or scripts. You can show more than one river with the username, category, and server shortcode attributes — see the live example I've had running since August.

Bugs and feature requests welcome on GitHub issues.

I've released a WordPress plugin that shows a FeedLand river on a page or post: feedland-rivers.

Drop the shortcode `[feedland-rivers]' onto a page, point it at your FeedLand username in the settings, and it fetches the river JSON server-side and renders it in an isolated iframe. No FeedLand front-end scripts, no third-party fonts or stylesheets beyond an optional favicon lookup. Here is an example.

You can also show more than one river on a site by overriding the username, category or server per shortcode instance, e.g. '[feedland-rivers username="alice" category="tech"]'.

It's not on the WordPress.org plugin directory yet. Grab the zip from the latest release and upload it via Plugins > Add New > Upload.

I'd appreciate beta testers. Let me know in the issues if something looks wrong or the instructions are unclear.

I’ve been running a server that mirrors posts from my rss.chat feed to my WordPress site automatically — no browser tab required. It connects to the rss.chat firehose and calls the WordPress.com API whenever I publish or edit a post. Edits flow through too.

The code is at https://github.com/scotthansonde/rsschat-wordpress-service, if you care to try it out. The requirements are similar to WordLand. You’ll need a WordPress.com account (or a self-hosted site with Jetpack), and about 15 minutes to set it up.

I took a quick look at blurt, the new WordPress short-form blogging theme available on WordPress.com.

It's a theme, just like Baseline is a theme. Themes can alter the behavior of WordPress in almost any way imaginable. It's still just a theme, so if Blurt is not using too much WordPress.com magic, it should be able to used on a self-hosted site.

The artificial 500-character limit is clunky. The compose box simply is disabled if there are too many characters. If you edit the post in the WordPress dashboard, when saved extra characters are silently dropped.

With WordLand I can post 600 characters, and they don't get cut off. If I try to edit that, the save fails. It's an early version, Blurt doesn't know how to handle posts coming from outside its UI.

I'm not sure why everyone thinks a character limit is a defining feature of social media. That should be up to the writer, not the platform. It should be a threshold, not a wall. micro.blog seems to handle this well (at 300 characters the UI show a title field you may choose to use or not).

All in all, it's a cute idea, and I look forward to see how it develops. (Sorry for the fart joke title.) (Actually I'm not sorry. 😃)

When I was creating the FeedLand Docker Compose file, I was thinking of it running on a VPS with a public hostname. There was another use case I was not thinking about: running on a local machine in a private network, without any hostname in DNS. This would be pretty common for someone just wanting to run FeedLand for themselves on their own laptop, without wanting to set up any SSL or proxy.

For this case I've added an option to run FeedLand as localhost. When the initial script is called as `./scripts/generate-env.sh –http-localhost`, the URL of FeedLand is set to http://localhost:1452, and the Caddy web proxy is not started.

I've also added a script to easily determine the confirmation URL for a new user when email has not been configured.

Thanks to John Johnston and Frank McPherson for suggesting and testing the localhost installation. This should make it even easier to explore FeedLand.

Next I intend to explore other possibilities for using the FeedLand Docker image, for example with the Synology Container Manager or with Coolify.