You can reply to your own post.  In which case, the reply notes who it replying to:

How does 

• https://demo.rss.chat/#  &   https://github.com/scripting/rss.chat

relate to 

• https://wordland.social/  & https://this.how/wordland/  & https://github.com/scripting/wordlandSupport

Not sure why I’m responding either, but thanks for the opportunity!

When my students and I studied historical episodes of active citizenship, we saw that six things needed to be in place for the activists to have a chance for success.

One of them was the ability to affiliate with others. Not just write as we please and read what others write. Beyond that: to find partners and allies and take on the shared work of effective citizenship, through public speech and private planning, just as historical examples have shown.

By now we take for granted that we can read and write as soloists on the web. Looks like rss.chat, however, is taking a very practical step forward in the power to affiliate.

We have images. 

Limit of 2MB per.

Works like Slack or GitHub.

Put the image on the clipboard, create a post, paste.

This is a test of the emergency RSS system.

Don't lose sight of what you're doing something in service of.

Ya, SMTP is why you like having other people in the world to set that up. I'm still waiting to get out of the sandbox on AWS SES and I've had a case open for five days.

rss chat is now simper to set up so I gave it a wee go on local host. So far I've just run it from my downloads folder. The instructions worked but I am a node-no-nothing so I tripped a couple of times.

First I didn't npm install so nothing worked.

I tried to set up SMTP using SendGrid, but I lost the will to live half way through. Got an API key but

Message failed: 550 The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit https://sendgrid.com/docs/for-developers/sending-email/sender-identity/ to see the Sender Identity requirements

So I just copied the magicString from the terminal and constructed my own url: http://localhost:1420/userconfirms?emailConfirmCode=ysugstk4yc

Which did the trick.

Ofcouse a localhost oneperson social network is not much use ;-) but interesting none the less.

Ohhh, not that ICE.

You got it. Groups of writers. As small as one.

If "there's also a feed of everyone's posts together," I see that a small group of writers could collaborate on a topic of concern in a single instance of rss.chat, creating something they think of as a single-topic publication.

This could be a topic of pressing short-term interest, and that response would be nimble, wouldn't it? When a weather disaster threatens a region of the country, for example, the tools are already in place here and there's a low barrier to entry for new writers to contribute. The feed would send the posts to a WordPress blog built in minutes for the occasion, yes?

If I understand correctly, it's RSS-in, RSS-out, small pieces designed to be loosely joined, and all meant to be locked open . . . yes, please.

that post by Chris Hardie is a classic nerd response :-) I love it!

not sure why.  Checking out editing original post

Manton says this works now! ;-)

Testing rss.chat, the most recent product from @dave

This is a test. We just gave this server the same upgrade rss.chat got last night. 

But this time there are some glitches. 

Let's see if this post appears.

We just did an upgrade on both servers, first rss.chat and now demo.rss.chat.

There's a new feature coming that's pretty exciting, at least for anyone wanting to set up their own instance. The install instructions are about to get much shorter. ;-)

If it all works, that is! :-)

I posted a reply to your report, i understand the message, but i don't understand why. Hopefully someone will give us a response soon. We have to get this working with micro.blog. Pretty sure we will. ;-)

I posted an issue in the help-forum, since there are some errors in my logfile with regards to the feed. I hope it gets sorted soon.

It would be nice to see the other side, the post you authored here that's on micro.blog.

You mourn the sites where the domain expired, or the DNS is unset, or hasn't been updated in a while, and keep some around so that you can leaf through them (virtually) for nostalgia’s sake, and remove others because you can finally let go of them.

You periodically back up the OPML file of the feeds you subscribe to, just in case you need to switch aggregators or the service suddenly goes defunct.

Speaking of RSS feeds, you periodically go through all of the feeds in your aggregator and see if they are broken, right? And if they are, you update the URLs or just unsubscribe from them, I assume. And if you know what's wrong with an RSS feed (sudden absence, malformed, URL has changed), you contact the author or the publication. And if that doesn't work, you create an RSS feed out of the site using tools like Huginn or NewsBlur (one of its paid tiers has a feature to turn any website into an RSS feed). wouldn't say I've gone as far as Chris Harding, but I've done a lot of those things.

BOOM!