Andrew -- the blogroll is up and running, built from your OPML file: https://news.rss.chat/blogroll/
How to put it on your site:
One trap worth knowing before you touch the styles: the standard includes float any element whose class name starts with "span" -- details in the readme.
New on the repo today, for everyone here building outside rss.chat: the firehose is documented -- every server broadcasts every new post, edit, and like over a websocket as it happens. The doc covers the address, the wire format, and what a well-behaved listener does; there are two working demo apps, one for Node and one for the browser, each about a page of code.
Docs: https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md
Demos: https://github.com/scripting/rss.chat/tree/main/examples/firehose
It's the same protocol FeedLand uses for its firehose, so a listener written for one can listen to the other.
That was fast — thanks for the real-world test. The port gap is already fixed: step 8 of install.md now says the server listens on 1420, and that websockets have their own port. One detail worth knowing: the websocket default is 1422, not 1462 — 1462 is just what this server happens to use.
The repo is current now — the theme is at 0.5.329, matching what's live. Also just for you: the upgrade section of install.md has a new step, the items.feedUrl migration — without it, feeds come up empty after switching to database mode. Worth a look before you update your fork's deploy.
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?
New today: the Surface icon in the left panel. When you've gone deep — into a story, a profile, or the flipped view — one click brings you back up to the timeline, with the cursor on the post you were just reading, scrolled into view.
It's not the same as Home. Home takes you to the top and starts fresh. Surface is a lifeline: however deep you get buried in a thread, it puts you right back where you left off.
This post is a demo of everything a post can now carry. Written in Markdown mode, published from the editor.
Text can be bold, italic, and linked.
Quoted text reads like body text, set off with a thin rule:
The best styling recipes were already sitting in WordLand's stylesheet. We copied them.
A bulleted list:
A numbered list:
Inline code like getItemAndReplies, and a block of it:
function helloWorld () {
console.log ("hello, rss.chat");
}
If you're reading this in a feed reader, the feed carries the same HTML -- what you see is what everyone gets.
The Like heart is fixed (theme 0.5.288). It only worked on the home page. On a single-post page or a profile page, clicking it looked dead -- but it was actually toggling your like on the server with no feedback, which is why likes seemed to come and go at random. Scott Hanson's report (works on home, not on a single-post page) gave away the pattern. Now the heart fills in and the count updates in every view. If a Like of yours went missing this week, that was the bug -- please try again.
Found it.
The mystery caller wasn't a person — it was Applebot, Apple's web crawler. It was crawling our story pages (the ?id= links) and firing a request to an internal endpoint (/getitembyguid) without the id it needed, which is what threw the error.
Two things came out of it:
robots.txt rule telling crawlers not to hit that endpoint. Applebot checks robots.txt, so that should quiet it down for good.Thanks to everyone who helped look.