How fucked up would it have been if the USA had won the match with Belgium last night.

Quite possibly the reason the Knicks lost when Trump decided to show his face at an NBA Finals match at the Garden in June.  

Claude has a new skill -- it can debug software in the browser, so now I'm out of the loop for having to find the problems, it just did a full survey of common HTML elements you can create in Markdown, and figuring out which ones don't work and then fixing them.

These are some of them. ;-)

This post is a demo of everything a post can now carry. Written in Markdown mode, published from the editor.

A big heading

A medium heading

A small heading

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:

• RSS
• OPML
• Markdown

A numbered list:

1. Write
2. Publish
3. Read

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.

Andrew, this is what I changed that paragraph to.

There isn't very much I'd have to do beyond adding two Atom elements to my feed, and an Atom namespace declaration in the top line of the file. So it's not an easy thing to do, because I don't see the need for Atom to be a requirement for WebSub, and I'd like for them have had the maturity to do this a different way.

It was meant to make you think, and apparently it did that, but didn't help you see the reason.

It is explained in the next paragraph.

You say:

> There isn't very much I'd have to do beyond adding two Atom elements to my feed, and an Atom namespace declaration in the top line of the file. So it's not an easy thing to do.

Did you mean to say "it's not an easy thing to do" or was that a typo? I'm hoping the changes were easy. :-)

I got a little flummoxed by the new UI, but it was a good form of flummoxation. 

I replied to a post by Andrew. Back in the timeline there's the reply. First anxiety quelled. It made it to the server and people can see it.

But where is what it is in reply to?

Calm down and look above the reply, there's a link there, well-labeled.

Lots of changes in the last few days, and I need people to try reading it in a serial fashion. That is come back every few hours to see if something new is posted. And if you see something you have something to add to, reply. And see how quickly you are satisfied your reply was received. 

You are mentioned prominently in this post. 

Here's a list

1. hello
2. goodbye
3. you say

 

this is some bold and italic text and a link

Lots of changes in this release as Claude and I learn how to work with each other in new ways. We have a list of bugs, I keep a list, and add to it regularly. One of the big problems was I had trouble using the Markdown editor feature as opposed to the default wizzy edito...

Something I've wanted for a while. When you're entering a title in the editor, the title should be bold. That's how titles look. ;-)

There's now a worknotes.md file at the top level of both repos.

This is a test to see if my RSS feed is properly rebuilt with the new values for source:inReplyTo.

There is an rss.chat repo on GitHub. https://github.com/scripting/rss.chat The code folder contains the current code for the client, the software you're using to read this, and I am using to write this.  There isn't much in the way of docs, but there is ...