reallysimple 0.5.2 → 0.5.3

package/package.json

@@ -1,7 +1,7 @@
 { 
 	"name": "reallysimple", 
 	"description": "A Node package that reads RSS-like feeds and calls back with a simple, consistent JavaScript object. Easy to use, hides the history.",
-	"version": "0.5.2", 
+	"version": "0.5.3", 
 	"author": "Dave Winer <dave@scripting.com>",
 	"license": "MIT",
 	"files": [

package/reallysimple.js

@@ -1,4 +1,4 @@
-var myProductName = "reallysimple", myVersion = "0.5.2";     
+var myProductName = "reallysimple", myVersion = "0.5.3";     
 
 exports.readFeed = readFeed;
 exports.convertFeedToOpml = convertFeedToOpml;
@@ -281,7 +281,6 @@ function convertFeed (oldFeed, whenstart) {
 		
 		if (item ["source:markdown"] !== undefined) { //7/18/22 by DW
 			let markdowntext = item ["source:markdown"] ["#"];
-			newItem.description = markdownProcess (emojiProcess (markdowntext));
 			newItem.markdowntext = markdowntext; //8/25/22 by DW
 			}
 		

package/worknotes.md

@@ -1,3 +1,17 @@
+#### 11/18/25; 8:09:33 AM by DW
+
+In convertFeed, if there's a source:markdown element present in an item, we were changing the value of the item description to a rendered version of the markdown text. There's no comment explaining why we did this and it seems wrong. It might make some sense if there's no description element present. 
+
+This caused problems in the scripting.com/rss.xml feed because we were generating the markdown text from the description, and it was screwing up fediverse addresses that it thought was a mailto. Like @scripting@daveverse.org.
+
+I commented the line of code out. It seems it should be up to the source of the feed to decide what the relationship is between the markdown text and the description.  
+
+#### 10/10/25; 11:13:23 AM by DW
+
+We now look for site id and post id in wordpress-generated sites. 
+
+No we don't. I misunderstood, the id's are not present in the feeds, they are present in the API.
+
 #### 8/23/25; 10:54:38 AM by DW
 
 wpSiteId and wpPostId are now numbers.