When I checked in on my Threads account recently, I saw that the Fediverse sharing feature was available and turned it on.
As you can see above, I’ve added my Threads account in the last available metadata entry on my primary Fediverse account. In testing the new link before publishing this post, I found that Ivory desktop and mobile clients appear to rewrite the link to @genxjamerican (which doesn’t work). Clicking the Open in Browser button that comes up after the first failed site visit gives you another rewritten URL, https://www.threads.net/user/genxjamerican#. (which also doesn’t work). When I visit my profile in a browser however (at https://hachyderm.io/@genxjamerican), clicking the Threads link takes me directly to the profile as expected.
A search for my handle in the Ivory desktop client now shows my Threads account and my Mastodon account. Only time will tell whether or not the anti-Meta fedi pact I posted about last year has a meaningful impact on the growth of Threads in the fediverse. Meta could just as easily sabotage its own growth through strategic errors. One of the fediverse’s most consistent advocates and contributors, Dr. Jorge Caballero, makes a persuasive argument that paying for “good” Threads posts is one such mistake.
I haven’t really set up anything to cross-post the same content to multiple social media accounts beyond what Jetpack Social supports. My blog posts are automatically posted to Tumblr and to my Mastodon account. I might change that just to see how different the levels of engagement are. IFTTT is probably where I should look first, having set up a bunch of automations there in the past. So far, when it comes to sharing posts from this blog, followers on Mastodon engage far more often with them than in any other social media network where I have a presence.