20250501-0118. Earlier this morning, I was able to reconnect and post to the Jetpack Social: Bluesky: FLYNN under my original Bluesky handle, which I changed to my custom domain name.
Unfortunately, after I verified successfully my Bluesky account using my custom domain name, I could NOT post the follow-up post! I was pissed-off! After queried unsuccessful queries with the Jetpack Support AI Assistant, I submitted my request to team Jetpack Support.
However, I am happy again! After attempting vainly to reconnect to my Bluesky account using my custom domain name, I finally got in! This was possible by regenerating the App password over at Bluesky!
But I needed to repost my post and saw and clicked the links from the generic email about “Your post could not be shared.”
After reading the Jetpack online documentation on “Re‑sharing posts with the Block Editor”, I finally learned how to re-share my post, which got knocked-out after I changed my Bluesky handle!
But I could NOT re-share my knocked-out post from the Classic Editor mode! I had to re-share my post from the Block Editor mode! This was becoming a short but sweet nightmare!
I never had this much of a problem! But I calmed down and opened-up the Block Editor mode, clicked on the green-colored Jetpack icon button at the top of my post php page, scrolled all the way down until I saw the menu detail labeled as “Share this post” and Voila!
I had another problem! The Share button was “grayed-out”. But I saw the Connection was disabled at the top. And so I switched-on/enabled the Connection and I was able to see that the Share button was NO longer “grayed-out”.
So I edited and previewed my maxed-out 255 characters message before sharing. And that my pals is what I do for fun after all of these year: cross-training myself with online documentations and the ongoing nuances of simply trying to blog or rant about my concerns and problems and to connect with my social media accounts.
Sheesh! End of transmission 0138 PST.
Leave a Reply