I'm taking a screen shot of this post, so I need there to be a reply. ;-)

We undid this, it works this way now. One server. Makes setup much easier. Please check it out, and do the upgrade on your instance. 

The URLs for the feeds have changed. If you haven't subscribed to any of the feeds here, you don't need to do anything. But if you have, you should read this note, and subscribe via the new URL and unsub from the old one. 

check your email for login detail https://indiekit-demo.rmendes.net

yes definitely coming your way over email, gimme a few hours

We just converted both rss.chat and demo.rss.chat to use a different storage system, instead of using Amazon S3 to store the feeds, we're storing them in our database. So instead of there being two domains for on system, now there's only one. Cuts out one of the most complicated parts of setting up a new instance. 

So if this works, it will show up on the blogroll on Scripting News, which is watching the old url, which should redirect to the new one. 

Hi Scott — the server install just got simpler. Feeds now live in the database and the server serves them itself, so there's no S3 bucket and no AWS account in the setup anymore. install.md and config.md are updated to match. Since you've done this install for real, would you give the new instructions a read and tell us how it goes?

There's a new sub-menu for all pages on the GitHub repo.

The first two we're linking to are the worknotes files for the client and server.

We've just turned this over to Claude, previously I was taking the notes in my code, and they were spotty. Now Claude can add things to the worknotes files without my supervision. 

Basically everything on the repo site that doesn't say otherwise was written by Claude. 

There's a Docs menu, so now I have a place to put links to docs. Coming soooon. 

How could I try your product? Do you have a demo site?

Yes this one is answered, I'll implement <source> usage in my own clients UI

I went back to the top of the thread, I think the question you asked was answered with the item-level <source> element?

It means this :  A comprehensive Microsub social reader plugin for Indiekit. Subscribe to feeds (RSS, Atom, JSON Feed, h-feed), organize them into channels, and read posts in a unified timeline interface with a built-in web reader UI.It's a built-in RSS reader with inte...

What does that mean to someone who doesn't know what microsub is?

I will make my microsub  indiekit plugin read it/display it properly, so that it can display handles as a source, with avatar if any, it would make the whole thing much more natural from an external reader point of view 

It will also benefit my other RSS feeds, because i'll be able to show the name of the source with a favicon or logo/avatar of the source

Not sure about this one. I understand the need for it, but how to fit it in, not sure.

We're going to move slowly here and hopefully there will be products that offer special features like this, highly customizable, using a variety of different approaches. 

Remember, this is an attempt at a bootstrap -- not a silo. We're just here now to help get a bit of a fire burning. It's not like other systems where it can't happen unless the platform vendor does it. This is open and cloneable, and open source. 

Ricardo, the information is in the feed in the <source> element. 

This is a not-often-used element from core RSS 2.0. 

Now most feed readers don't look for it, but it's there. 

Another Idea, this time regarding authentification : 

it would be probably trivial to enable IndieAuth authentification on rss.chat, this would allow me for example to auth with my own website, using my own h-card to provide, email, username, etc. this would allow anyone supporting indieweb building blocks to login without bothering with email or with more complex SSO dependency (github, google, etc)

Another idea that I'm thinking out loud as I write this down : 

What if I could get a notification if/when someone directly replies to me, either using websub or perhaps an external notification provider (ie: ntfy.sh)

Just thinking out loud, but... if I subscribe to the "everyone's feed" https://users.rss.network/rss.xml in my RSS reader, I obviously see each entry, but there is no way to know who is the owner of the post.. if we'd push this idea further down the road of a "social network powered by RSS" I would love to be able to see right upfront "who" is the author of the post, a bit like we do in the rss.chat UI, i guess this is why the "client" exist, but I was wondering if we could make ANY rss feed reader able to display "rss.chat" streams with proper user attribution

In setting up the new server I forgot to configure the location of the S3 files for the feeds so we were overwriting the feeds for rss.chat. 

When I post this, my personal feed and the everyone feed should rebuild and be good. 

I like when I can contribute with approaches I do at work but for open-source projects :) 

and Yes Claude is a great team mate to have around !!

Awesome work Dave (@Dave Winer)! 

As the new guy here I sure hope I don't come off as a curmudgeon (yes I'm old but I'm not bad- tempered ;-) ), but I opened issue #3 on the repo. I was trying to respond to @Ricardo on my iPhone when I couldn't. After drinking my coffee, I realized I wasn't logged in. After finishing my muffin, I realized there was no way to login in. Now it's lunch time and I've posted an issue. I almost feel bad for doing it - like picking nits. I'll go quiet. I'm going to eat my sandwich.

Thanks Scott, that's high praise. :-)

I just finished my installation and the new server, demo.rss.chat, is up and running.

We have more excellent stuff in the pipe, still working out some details.

Also the worknotes.md files are working now. Claude is doing all the change notes there. 

worknotes for server

worknotes for client

Still diggin as they say. 

This is fantastic! And it’s very well documented, complements to you and @claude!

Here is the localhost/vps deployment if anyone wants to test it : https://github.com/scripting/rss.chat/issues/2 

Excellent. Love Localhost it's a great sandbox. Umm ... localhost too.

You could use unfurling/opengraph to even display a nice embed card of these links if the origin has it :p

partly history, partly deliberate design.  History: rss.network was the project's earlier name — the server is still rssnetwork.js and calls itself that; the client later became rss.chat (his worknotes from July 3 mark the split).  Design: rss.chat is the dynamic ...

I got it running in localhost :))