• As often is the case..

    This is a test post.

    It has a title so it should be routed to the place where standard.site says they should go.

    And I will be able to read them in this place.

    Where I must imagine it behaves something like a feed reader.

  • Postscript. For the post that was to be routed to standard.site (whatever that means) I can find no evidence that something was sent somewhere.

  • The next test post

    The first one worked.

    It was routed through micro.blog. Basically everything I post to demo.rss.chat will go to my main account on Bluesky.Unless it has a title or is longer than 300 chars. Here's what we get using various Markdown features.

    A list of five countries.

    1. Portugal
    2. Tanzania
    3. Panama
    4. Canada
    5. Vietnam

    Obviously there's bold, italic and a link. The Big Three. Okay that's a big, almost 500 chars, and that's enough for a nice little test.

  • This is a test.

    This is a short less-than 300 char post, that is being routed to Bluesky via micro.blog.

    Because it's short it it won't have to be upgraded to standard.site class, it can go through the analog of coach (the current limits of Bluesky).

    Okay that's about it. Let's see if this mofo works.

  • WebSub support for RSS.chat

    Previously we were only able to notify via rssCloud.

    Now we also support WebSub because there are also a fair number of feed readers that only use WebSub.

    We're using Andrew Shell's rsscloud.io as our WebSub hub, as we have for a long time with rssCloud.

    Andrew please help us figure out if this is working correctly.

    The source is in the repo, along with a worknote.

  • Just made a small change in the way we prepare feeds, and I have to post something to cause the feeds to rebuild.

  • Hi Robert, I had Claude tell me that you're the generous developer who wrote us that thoughtful report last night about the security issue.

    FIrst, there are no plans for the /localnewuser function, we put it in because we watched some users struggle through installing the server because they had to set up the email server connection before they could log onto the site themselves. We could also see it as a way for a sysop to set up accounts for users. No plans to do anything more with it.

    We tried out a bunch of ideas here to integrate news with what rss.chat does, the best one imho was a blogroll, like the one you see on scripting.com, in the left column. That's the way I'd go. But if posts from Bluesky show in the timeline then the discussions are going to be like discussions on Bluesky. And we already have Bluesky for that. :-)

    What I really want is an RSS-to-Standard.site bridge, both ways. That will give an outlet to leaflet to the whole web, not just the ones who study AT Proto.

    And again thanks for the report. It was basically perfect. ;-)

  • Security issue

    A user contacted us about a potential security issue in the RSS.chat server. We responded quickly and with v0.6.11 the issue is removed. If you’re running rssnetwork.js on a publicly visible server, please install the new version asap.

  • You're absolutely right. With WordPress you can go from rss.chat to mastodon.

  • New features today

    A validator and a way to add menus to the RSS.chat menubar, if you're running your own instance.

    Links on today's Scripting home page.

  • No spam, personal stuff, etc

    I like this site, I want to keep it open, and as long as moderation is a rare thing, ie people behave like adults and professionals, we'll be fine. But if the moderation gets to be too much, it'll become read only.

  • This looks spammy.

  • 1. That's a new account, and a new feed.

    2. We were planning ahead, leaving space for an enclosure. We don't have a UI for that yet.

    3. Yes, use OPML, create a list of servers. That's what software that wants to work with federations will require as input.

  • Did this show up on the other side?

  • great to see you here matthias. wow.

    sent an email. definitely want to chat.

  • it would be interesting to hook up the output of rss.chat to the input of Jekyll using templates or themes or whatever they call them in the Jekyll.

  • I’ll have Claude look into this tomorrow. It will explain to me what’s going on and we may change something.

  • Did it work as you expected it would?

  • As you put it "html fragments" not full html pages.

    It's just a question of whether you prefer writing in the wizzy editor (the default) or the markdown editor. Since you're coming at it from a script, not sure exactly how it would work. I'm away from home right now and can't look it up. There are docs for the calls now, you could check that out.

  • New docs for the API that connects RSS.chat to the server.

    https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md

  • We’ll look into it, first thing I’d do is ask Claude what’s up. You could do that too. My theory is that it’s up to the system you copied it from to have a pref that protects this info.

  • Welcome Nakedjen. We’ve been waiting for you.

  • invite them to come here and join the conversation.

    i'm sure they'll want to do some part of this.

    we're on the web, we should get to know each other and work together. ;-)

  • At least we've started building a new nest on the web outside the silos.

    Just make sure they are challenged when they say their silo is the web. ;-)

subscribe via RSS