Adjust for new stweet (user and id params)

content/posts/2019/02/old-dog-old-trick/index.md

@@ -106,4 +106,4 @@ Woof.
 
 *And, oh, yes: my continued thanks to [Chris Rosser](https://chrisrosser.net) for tweeting* (below) *about my last post. As he might say: "Thanks, mate!”*
 
-{{< stweet "1095457720709263360" >}}
+{{< stweet user="RosserWrites" id="1095457720709263360" >}}

content/posts/2019/04/why-left-ulysses/index.md

@@ -143,7 +143,7 @@ Yet another nail in the Ulysses sub's coffin.
 
 But it was hard to let go. Even as late as a couple of weeks ago, I found myself posting this on Twitter:
 
-{{< stweet "1114140807764893696" >}}
+{{< stweet user="BryceWrayTX" id="1114140807764893696" >}}
 
 And, almost as if it had gotten the message, Ulysses was good as gold across my devices --- until this morning.
 

content/posts/2019/06/ahoy-mate/index.md

@@ -115,4 +115,4 @@ However, the answers were "No" and "No." The [changes in Apple Mail in Catalina]
 
 My tweet tonight says it all:
 
-{{< stweet "1138614802518020096" >}}
+{{< stweet user="BryceWrayTX" id="1138614802518020096" >}}

content/posts/2019/07/why-staying-with-hugo/index.md

@@ -261,7 +261,7 @@ Early that afternoon, my mind finally at rest about it all, I tweeted:[^BEP]
 
 [^BEP]: I confess to being extremely pleased that, later that afternoon, none other than [@bepsays](https://twitter.com/bepsays) himself (Bjørn Erik Pedersen, the lead developer of Hugo) "liked" that tweet.
 
-{{< stweet "1150104013871955971" >}}
+{{< stweet user="BryceWrayTX" id="1150104013871955971" >}}
 
 ## "Interesting," indeed
 

content/posts/2019/08/backtracking-to-big-g/index.md

@@ -11,27 +11,27 @@ discussionId: "2019-08-backtracking-to-big-g"
 
 "Initially, the defendant made the following assertions:"
 
-{{< stweet "1140023324988313601" >}}
+{{< stweet user="BryceWrayTX" id="1140023324988313601" >}}
 
 ".&nbsp;.&nbsp;. and .&nbsp;.&nbsp;."
 
-{{< stweet "1142915419784863745" >}}
+{{< stweet user="BryceWrayTX" id="1142915419784863745" >}}
 
 ".&nbsp;.&nbsp;. followed a few weeks later by .&nbsp;.&nbsp;."
 
-{{< stweet "1150108543208579072" >}}
+{{< stweet user="BryceWrayTX" id="1150108543208579072" >}}
 
 "Unfortunately, your honor, this seemingly noble and well-intentioned course of action was derailed yesterday, as shown here&nbsp;.&nbsp;.&nbsp;."
 
-{{< stweet "1165327910078681088" >}}
+{{< stweet user="BryceWrayTX" id="1165327910078681088" >}}
 
 ".&nbsp;.&nbsp;. and here .&nbsp;.&nbsp;."
 
-{{< stweet "1165328656392232960" >}}
+{{< stweet user="BryceWrayTX" id="1165328656392232960" >}}
 
 ".&nbsp;.&nbsp;. and here .&nbsp;.&nbsp;."
 
-{{< stweet "1165357162551545857" >}}
+{{< stweet user="BryceWrayTX" id="1165357162551545857" >}}
 
 “--- and, as the defendant surmised in this most recent exhibit before the court, he did indeed end up stopping the usage of the tracking-free alternative, thus compounding his crime by no longer supporting it at the same time he was returning the Evil G Empire's tracking code to its former access to his site and its visitors.
 

content/posts/2019/09/why-left-hugo-eleventy/index.md

@@ -208,7 +208,7 @@ It doesn't build a site as quickly as Hugo --- nothing beats Hugo on that score
 
 While we're on the subject of speed: while I was working on this post, I saw this Leatherman tweet:
 
-{{< stweet "1169998370041208832" >}}
+{{< stweet user="zachleat" id="1169998370041208832" >}}
 
 React. Hmm. Wonder whom he might be zinging there? Good job, sir. Given the Gatsby team's continual boasting about how they can handle massive amounts of data with ease, I hope you're making them sweat, even if just a little.
 

content/posts/2020/01/two-cheers-tailwind/index.md

@@ -11,7 +11,7 @@ discussionId: "2020-01-two-cheers-tailwind"
 
 A couple of weekends ago, I tweeted a question for the web devs among my few but greatly appreciated Twitter followers. It was the Saturday between Christmas and New Year's, so I figured I'd be fortunate if I got a handful of responses.
 
-{{< stweet "1210975092999704578" >}}
+{{< stweet user="BryceWrayTX" id="1210975092999704578" >}}
 
 Then it got retweeted by the [Tailwind CSS](https://tailwindcss.com) [Twitter account](https://twitter.com/tailwindcss) and, well, my phone was pretty actively "bink"-ing at me for a few hours thereafter.
 
@@ -21,7 +21,7 @@ Tens of thousands of "[impressions](https://help.twitter.com/en/managing-your-ac
 
 So I spent my spare time during the next few days doing precisely that on a branch of my site and, during the first afternoon of 2020, merged that branch into `Master` and pushed it to Netlify:
 
-{{< stweet "1212496201385418753" >}}
+{{< stweet user="BryceWrayTX" id="1212496201385418753" >}}
 
 ## Not a purist
 

content/posts/2021/04/speaking-up-for-sass/index.md

@@ -198,7 +198,7 @@ Although I have previously acknowledged Tailwind's strengths and am all too awar
 
 Tailwind adherents say this isn't a problem because, once you recognize that you're re-using certain Tailwind classes too frequently, you then simply extract them to reusable components and then `@apply` them, [as the Tailwind documentation suggests](https://tailwindcss.com/docs/extracting-components).  I agree that this is a workable strategy, but my own experience suggests it can get out of hand quickly, even in a small project. YMMV, of course. By the way: please note what Tailwind creator Adam Wathan famously tweeted about `@apply` . . .
 
-{{< stweet "1226511611592085504" >}}
+{{< stweet user="adamwathan" id="1226511611592085504" >}}
 
 Once you've extracted a good quantity of components as I suspect happens more often than not, you'll run into the next issue that Tailwind fans say it solves . . .
 

content/posts/2021/12/fetching-remote-stuff-hugo-0-90-plus/index.md

@@ -17,7 +17,7 @@ The [release earlier this week of version 0.90.0](https://github.com/gohugoio/hu
 
 My initial reaction was: well, that’s surely cool, but I doubt I’ll ever need that functionality in my own relatively limited use[^1] of Hugo. Then, yesterday, a tweet by long-renowned Hugo expert [Régis Philibert](https://github.com/regisphilibert) gave me second thoughts:
 
-{{< stweet "1469417024518565900" >}}
+{{< stweet user="regisphilibert" id="1469417024518565900" >}}
 
 And, lo and behold, it hit me this morning: this new ability by Hugo to fetch remote stuff meant, now, I could use [Base64](https://en.wikipedia.org/wiki/Base64)-encoded [low-quality image placeholders](https://www.guypo.com/introducing-lqip-low-quality-image-placeholders) (LQIPs) in my image-handling shortcode (most recently described in “[Go big or Go home? The sequel](/posts/2021/11/go-big-go-home-sequel/)”).
 

content/posts/2022/01/fetching-remote-images-eleventy/index.md

@@ -69,4 +69,4 @@ And there you have it. Using your browser’s Inspector tool on nearly[^1] any i
 
 The official Eleventy Twitter account graciously retweeted my announcement of this post and added the following, which I pass along for your further edification:
 
-{{< stweet "1486347755404640257" >}}
+{{< stweet user="eleven_ty" id="1486347755404640257" >}}

content/posts/2022/01/gems-in-rough-13/index.md

@@ -46,7 +46,7 @@ While AVIFs have notable advantages, I feel that the horsepower they require whe
 
 As I was finishing this, I saw the following from the [Eleventy Twitter account](https://twitter.com/eleven_ty) regarding the still-in-beta Eleventy 1.0:
 
-{{< stweet "1478407921264377858" >}}
+{{< stweet user="eleven_ty" id="1478407921264377858" >}}
 
 This will be (is?[^3]) very, very cool stuff (as [Slinkity](https://slinkity.dev) fans already know). [Here’s just one example from that aforementioned updated documentation](https://www.11ty.dev/docs/languages/custom/#example-add-sass-support-to-eleventy), specifically showing how to add [Sass](https://sass-lang.com) support to an Eleventy 1.x project — and, yes, *without* all the hassles of the `package.json` method I’ve typically used in my own Eleventy-based endeavors.
 

content/posts/2022/02/gems-in-rough-14/index.md

@@ -94,7 +94,7 @@ I have now learned *why* this didn't work with the V2 API. I found the following
 
 However, thanks in particular to [Chris Swithinbank](https://twitter.com/swithinbank), I have added the appropriate code to my `stweet` shortcode from the [first](/posts/2022/02/static-tweets-eleventy-hugo/) of those posts, so you can see that particular tweet as [@podcasterJay](https://twitter.com/podcasterJay) originally intended it:
 
-{{< stweet "1493660193653207040" >}}
+{{< stweet user="podcasterJay" id="1493660193653207040" >}}
 
 (If the continuing animation drives you nuts, just click or tap on the image.)
 

content/posts/2022/02/static-tweets-eleventy-hugo/index.md

@@ -29,7 +29,7 @@ The solution is to present each tweet as *purely static* textual and image conte
 
 For example, here is a tweet I issued recently when I received[^2] some swag after having submitted some code to a Cloudflare contest:
 
-{{< stweet "1487140202141425673" >}}
+{{< stweet user="BryceWrayTX" id="1487140202141425673" >}}
 
 .&nbsp;.&nbsp;. so you get to see the tweet — complete with my Twitter avatar and, in this case, the “attached” photo of the Cloudflare swag — **but** you’re spared all the other stuff that usually would come with it.[^3]
 

content/posts/2022/03/gems-in-rough-16/index.md

@@ -42,7 +42,7 @@ To be sure, I’m *not* taking away the reply-by-email button/link, which will s
 
 A follow-up to something I [mentioned](/posts/2022/02/shameless-plug-time/) a few weeks ago: the nice folks at CloudCannon kindly asked me to write another piece for them, and the latest such effort is now live on their blog: “[The Ultimate Guide to Hugo Sections](https://cloudcannon.com/blog/the-ultimate-guide-to-hugo-sections/).” As I subsequently noted in a reply to my retweet of the article’s original announcement:
 
-{{< stweet "1502062544764162054" >}}
+{{< stweet user="BryceWrayTX" id="1502062544764162054" >}}
 
 And there’s more to come in the near future.
 

content/posts/2022/04/static-tweets-astro/index.md

@@ -207,7 +207,7 @@ import STweetV2 from '@components/STweetV2.astro'
 
 [^Inspector]: Use your browser's Inspector tool on the displayed tweet to see how I styled it. Of course, you should feel free to handle styling as you see fit.
 
-{{< stweet "1487140202141425673" >}}
+{{< stweet user="BryceWrayTX" id="1487140202141425673" >}}
 
 As was true for my Hugo `stweetv2` shortcode, I wrote this component to add "(UTC)" after the date because, once you use this in production, the remote web server will return the tweet's `created_at` information in whatever time zone the server uses --- which almost certainly is [UTC](https://www.timeanddate.com/time/aboututc.html).
 

content/posts/2022/04/winds-change/index.md

@@ -36,7 +36,7 @@ Then, the very next morning, a Twitter feed I regularly follow (I even have it c
 
 Fast-forward to this past Saturday afternoon — a month later to the day — when I tweeted:
 
-{{< stweet "1517957419447508992" >}}
+{{< stweet user="BryceWrayTX" id="1517957419447508992" >}}
 
 . . . and shortly thereafter, added *another* update to “Simplify, simplify (again)”:
 

content/posts/2022/05/checking-out-indieweb-again/index.md

@@ -16,7 +16,7 @@ discussionId: "2022-05-checking-out-indieweb-again"
 
 As I tweeted earlier:
 
-{{< stweet "1528446412169416704" >}}
+{{< stweet user="BryceWrayTX" id="1528446412169416704" >}}
 
 I even wrote a five-part **series** on incorporating [webmentions](https://indieweb.org/Webmention) on one's website back in April, 2020 (*e.g.*, [Part I](/posts/2020/04/webmentions-three-ssgs-1/)), but a few months later --- perhaps due to some uncertainty about how well [IndieWeb](https://indieweb.org) stuff was jibing with online privacy concerns --- dropped them from *this* site. So, when I decided earlier today to take another go at it, I had to dig back and find all the code from back then. (Thank Git for source-control history!)
 

content/posts/2022/05/gems-in-rough-18/index.md

@@ -57,7 +57,7 @@ Incidentally, I purposely chose not to add visible indications of each code bloc
 
 In recent months, the folks at [CloudCannon](https://cloudcannon.com) have been making significant gains to their support for Hugo. Up to now, that support has taken the form of software development and online content (some of the latter of which I've had the pleasure of helping to create). It now also includes an online event, [HugoConf](https://hugoconf.io), coming in July:
 
-{{< stweet "1524419059714039809" >}}
+{{< stweet user="hugoconf" id="1524419059714039809" >}}
 
 I'd urge Hugo aficionados, as well as those simply curious about Hugo, to give this a look-see.
 

content/posts/2022/05/simplify-simplify-maybe-for-real-this-time/index.md

@@ -51,7 +51,7 @@ One more thing: because CTCAJW Mode means I may be more frequently publishing po
 **Update, 2022‑05‑25**: Concerning that last paragraph, I've now pinned the following tweet/[toot](https://docs.joinmastodon.org/user/posting/) to my profiles on Twitter and the two [Mastodon](https://joinmastodon.org) instances where I’m currently active:
 {.yellowBox}
 
-{{< stweet "1529514823658110977" >}}
+{{< stweet user="BryceWrayTX" id="1529514823658110977" >}}
 
 ## It's not about SSG FOMO
 

content/posts/2022/06/hugo-hits-hundy/index.md

@@ -93,7 +93,7 @@ But, starting with Hugo 0.100.0, you get the desired indenting:
 
 All of this is possible because, as of v.0.100.0, Hugo's [`$page.RenderString` function](https://gohugo.io/functions/renderstring/) supports shortcodes. Hugo expert [Régis Philibert](https://github.com/regisphilibert), as he often does on such occasions, grasped added significance from the details in the release notes:
 
-{{< stweet "1531705641739460612" >}}
+{{< stweet user="regisphilibert" id="1531705641739460612" >}}
 
 Finally, 0.100.0 added a new [`resources.Copy` function](https://gohugo.io/hugo-pipes/introduction/#copy-a-resource) to Hugo's asset pipeline, [Hugo Pipes](https://gohugo.io/hugo-pipes/introduction/). The documentation says it's "possibly most useful for renaming things" --- as in this example (also from the documentation), in which Hugo's [built-in image-processing capability](https://gohugo.io/content-management/image-processing/) comes into play:
 

content/posts/2022/06/static-tweets-hugo-update/index.md

@@ -29,7 +29,7 @@ What's the difference? Before these latest changes, here's how `stweet` rendered
 
 And that works, to be sure. But now, `stweet` can do it this way:
 
-{{< stweet "1534248828559400960" >}}
+{{< stweet user="CloudCannon" id="1534248828559400960" >}}
 
 So, with that, friends and neighbors, here's the code.
 

content/posts/2022/06/wwdc-2022-thoughts/index.md

@@ -9,7 +9,7 @@ date: 2022-06-06T14:49:00-05:00
 
 As I joked (sort of) earlier today on Twitter and Mastodon:
 
-{{< stweet "1533830520030765057" >}}
+{{< stweet user="BryceWrayTX" id="1533830520030765057" >}}
 
 So, now, here are this Apple fanboy's initial takes on what that event revealed.
 

content/posts/2022/07/bundling-up-rebuilding-my-hugo-site/index.md

@@ -23,7 +23,7 @@ Not long ago, I began using Hugo's [`Text` filter](https://gohugo.io/functions/i
 
 The next day, I got a response from [@gaetawoo](https://twitter.com/gaetawoo) --- not about my post, but about that social/OG image:
 
-{{< stweet "1549779097978642432" >}}
+{{< stweet user="gaetawoo" id="1549779097978642432" >}}
 
 As we spent a few minutes discussing via Twitter how I'd used Hugo to generate the image, I began to think of ways to make it better. After all, I already wasn't enamored with the `Text` filter's inability (at least, as of this writing) to let me control either the text's word-wrapping or its alignment.
 

content/posts/2022/07/economy-words/index.md

@@ -28,4 +28,4 @@ For these reasons and some others, I'm trimming back the summaries, and may even
 
 Finally, please keep in mind that the site's **feeds** are *always* standing by to keep interested readers apprised of each new post when it hits the web. Just point your [feed reader app](https://en.wikipedia.org/wiki/RSS) to my [site URL](/) and let it do the rest. As the inestimable [Sara Soueidan](https://twitter.com/SaraSoueidan) expressed it so well today:
 
-{{< stweet "1544373617865129992" >}}
+{{< stweet user="SaraSoueidan" id="1544373617865129992" >}}