Today I’m going to work on re-shaping the docs for source:markdown because it seems to becoming a thing that people are supporting in their feeds and in their feed consumer apps. We’re going to have discuss how it’s supported, on both ends. What goes into a source:markdown element, and what does not, and how should readers use it. I will assume the role of benevolent dictator, as I did with RSS 2.0, with a bit more of an understanding of what’s important. See Rule #1 in Rules for Standards-makers. “The only reason we have open formats and protocols is so our software can interoperate.” And the Rule of Users: “People choose to interop because it helps them find new users. If you h…
Today I’m going to work on re-shaping the docs for source:markdown because it seems to becoming a thing that people are supporting in their feeds and in their feed consumer apps. We’re going to have discuss how it’s supported, on both ends. What goes into a source:markdown element, and what does not, and how should readers use it. I will assume the role of benevolent dictator, as I did with RSS 2.0, with a bit more of an understanding of what’s important. See Rule #1 in Rules for Standards-makers. “The only reason we have open formats and protocols is so our software can interoperate.” And the Rule of Users: “People choose to interop because it helps them find new users. If you have no users to offer, there won’t be much interest in interop.”