Email Test Post - 16Jan2020 0817

toledoweather.info AM Flash Briefing

The following important weather statements exist: A Hazardous Weather Outlook. Visit toledoweather.info for details.

Here are the conditions at Toledo Express Airport as of Jan 16, 2020 7:52 am EST. Weather was Overcast. Temperature was 35 degrees. Humidity was 59 percent. The wind was from the west-northwest at 16 miles per hour. The winds gusted to 25 miles per hour. The wind chill was 25 degrees.

Here is the synopsis from the most recent area forecast discussion. High pressure will continue to build into the area from the northwest today and persist through Friday. A deepening low pressure developing in the Central Plains will track northeast into the Central Great Lakes region on Saturday and linger into Sunday. High pressure will build back into the area on Monday and persist into mid week.

Here is Toledo's short-term forecast as of Jan 16, 2020 6:36 am. Today will be Mostly cloudy, with a temperature falling to around 27 by 5pm. West wind around 18 miles per hour, with gusts as high as 29 miles per hour. Tonight will be Partly cloudy, with a low around 20. Northwest wind 7 to 14 miles per hour. Friday will be Partly sunny, with a high near 30. Northeast wind 5 to 8 miles per hour becoming east in the afternoon. Friday Night will be Snow showers likely before 8pm, then snow, mainly after 8pm. The snow could be heavy at times. Low around 26. East wind 5 to 9 miles per hour. Chance of precipitation is 100%. New snow accumulation of 2 to 4 inches possible. Saturday will be Rain and snow, possibly mixed with freezing rain, becoming all rain after 8am. High near 43. South wind 10 to 18 miles per hour becoming southwest in the afternoon. Winds could gust as high as 37 miles per hour. Chance of precipitation is 100%. Little or no ice accumulation expected. New snow accumulation of around an inch possible.

BTW, I deleted my test Twitter account in the fall of 2019. I used this Twitter account to test IndieWeb concepts. I have no interest in using the cesspool for anything. But the experience was good in case a future project needs to do this.

Update

The above post was created in my Fastmail email account. I emailed the post to my IndieAuth enabled "account" at https://quill.p3k.io, which also provides a web-based MicroPub client (editor).

I placed the title text in the subject line and within the body of the email message. I used the single pound sign to indicate the title when I used the text within the email body. Obviously, I also added a double-pound (H2) line in the above post.

At the bottom of the post, I added my dir command to specify the date directory where I wanted my CMS to store the HTML and .txt files.

Also at the bottom of the post, I added my reply_to command. I wanted the email post to be a Webmention reply to a post at my test site wren.soupmode.com. It worked. I replied to this post: http://wren.soupmode.com/posting-to-twitter-via-bridgy.html.

The Webmentions page for wren.soupmode.com is located at: http://wren.soupmode.com/webmentions.html. At the moment (for the past 3.5 years), I store Webmentions on one page. If I desired, I could manually copy replies to the target page. I rarely receive a Webmention reply here at sawv.org. I like the Webmention idea, but it's mainly a test feature for me, which is why I don't do more with them.

Anyway, this is how the above worked.

  1. I used my Fastmail email account to send a post to quill.p3k.io, which knows my website info because I logged into quill.p3k.io long ago via IndieAuth.

  2. quill.p3k.io made a post to sawv.org by using MicroPub. quill.p3k.io is a MicroPub client. My CMS at sawv.org supports MicroPub on the server.

  3. My Wren CMS at sawv.org received the post and stored it as usual to the server file system.

  4. My CMS processed the dir and the reply_to commands, contained within the post. The Wren CMS made a Webmention post to wren.soupmode.com, based upon the URL contained after the reply_to command. My Wren CMS supports sending and receiving Webmentions.

  5. wren.soupmode.com received the Webmention post and stored the info accordingly. For now, I only store the source URL (sawv.org post). At the moment, I'm not interested in storing all or even parts of the source (reply) post.

The above steps:

Fastmail --> quill.p3k.io --> sawv.org --> reply to wren.soupmode.com.

If I still had my test Twitter account, then I could have also syndicated the post to my Twitter account via my syn_to command. The above would have looked like this:

Fastmail --> quill.p3k.io --> sawv.org 
                                       --> wren.soupmode.com
                                       --> brid.gy --> twitter.com

If I wanted to syndicate the post to my Twitter account, my Wren CMS at sawv.org would have made a Webmention post to brid.gy, which knows my site info also because of an IndieAuth login process long ago. brid.gy would also know about my Twitter account, and brid.gy would then make the post to Twitter.

If the email post contained the HTML image tag with IndieWeb-supported Microformats, then brid.gy would make that a part of the post to my Twitter account, and the tweet would display the image, an excerpt of the post at sawv.org, and a link to the post at sawv.org.

That's a lot of moving parts, but it's interesting that via an email message, I could post to my personal website, reply to someone who receives Webmentions, and syndicate the post to my Twitter account, all within one post, thanks to IndieWeb concepts and third party services.

The IndieWeb concepts used if I had posted to Twitter and the post contained an image:

IndieAuth was not used to create this post via quill.p3k.io, etc. But I logged into or connected with quill.p3k.io and brid.gy via IndieAuth in the past.

-30-