Nice list. I have however one picky pique within the Split it Up recommendation:
> Example: If you’re looking for me I’ll be in my office.
> Revision: If you’re looking for me, I’ll be in my office.
> Example: Due to the fog our flight was delayed.
> Revision: Due to the fog, our flight was delayed.
If the sentence is unambiguous without the comma then lean towards omitting it. Especially with the second example, with the clause being only four syllables long, the comma slows down the reader so much that the music of the sentence is broken. "Fog our flight" cannot be misinterpreted — nobody thinks of fogging a flight. Indeed the lack of a comma foretells to the reader they can confidently plow ahead through a well-tended sentence.
Also on the topic, Larry McEnerney's 2014 video "The Craft of Writing Effectively" https://www.youtube.com/watch?v=vtIzMaLkCaM (100m). He was Director of the University of Chicago's Writing Program.
This is probably the place to note how the internet first came to Deep Springs. As Librarian, I reached out to Caltech's Owens Valley Radio Observatory near Bishop and one of the researchers there (sorry, it was decades ago, 1992, and I forget his name) generously set us up with a dial-in connection and an account.
I can't remember whether there was much debate about this breaking the isolation policy, but there was practical opposition: DSC only had a single telephone line at the time, and my desire to be online drew consternation from the office manager, who sometimes needed to make calls.
Shout out to the h-feed / h-entry microformat https://microformats.org/wiki/h-feed, sadly underutilized but an extremely easy way to make the web much more syndicable.
They're comprised of standardized CSS class names to be inserted into HTML and enable meaningful scraping. Especially given that more and more sites are produced using JS frameworks, which have a harder time producing XML than older generation PHP and the like, h-feed seems a no-brainer.
Unless I'm being obtuse, wouldn't it be right for Twitter to state that it’s disabled an account in order to protect the user and others rather than because it violates their rules?
Unless I'm being obtuse, wouldn't it be right for Twitter to state that it's disabled an account to protect the user and others rather than because it violates their rules?
Ah thanks, didn't know about hAtom, will investigate that.
I do think it's (much) easier to add some HTML classes than output an entire separate file.
I've been using Nuxt + Strapi as my new CMS stack, and while it's a big step forward in so many other ways, outputting an RSS feed is far from automatic.
This entire post has galvanized me to write up an idea I've been noodling over as I work on a reader myself: a standard that would eliminate precisely the waste you mention by specifying within the HTML all that's needed for a feed.
See https://sfeed.org. In the spirit of the multi-meaninged RSS acronym itself, the S might stand for scrape, selector, speed, or of course Scotty.
Vinni, might you be interested in enabling the standard in Feed Me Up?
> Example: If you’re looking for me I’ll be in my office. > Revision: If you’re looking for me, I’ll be in my office. > Example: Due to the fog our flight was delayed. > Revision: Due to the fog, our flight was delayed.
If the sentence is unambiguous without the comma then lean towards omitting it. Especially with the second example, with the clause being only four syllables long, the comma slows down the reader so much that the music of the sentence is broken. "Fog our flight" cannot be misinterpreted — nobody thinks of fogging a flight. Indeed the lack of a comma foretells to the reader they can confidently plow ahead through a well-tended sentence.
Also on the topic, Larry McEnerney's 2014 video "The Craft of Writing Effectively" https://www.youtube.com/watch?v=vtIzMaLkCaM (100m). He was Director of the University of Chicago's Writing Program.