Turned off “fediverse” sharing on my Threads account. This may or may not turn into a useful feature for Threads users who don’t also have a Mastodon account, but I do (obviously, if you’re reading this), and I think for someone who has both a Threads account and Mastodon account, and sees the utility in participating in both as discrete platforms, Threads’s fediverse bridging is only an avenue for confusion.
I get that. the tough part is having that icon visible everywhere on threads is good PR for advancing social media decentralization.
@gruber I stopped following your Threads account for this reason. I’ll just stick to your Mastodon account on Mastodon. Fediverse sharing is great for people who are primarily (or only) using Threads.
@gruber Reading this via OpenVibes alongside BlueSky posts and it’s working fine. Finally added my Threads account last week but not seeing peoples threads posts.
Mastodon on its own seems a bit niche (pronounced like Quiche)
@gruber Sorry if I'm being obtuse, but are you cross posting everything, or some things, or...?
@jcape Some things, as an experiment. I generally dislike crossposting because then I can never remember where I saw which replies.
@gruber I so agree - I wish more
People would participate in each platform separately
@gruber I had followed your threads account as it seemed that's only where you were posting, then you starting posting in all three places. Was gonna unfollow your threads account, but this seems like a better solution.
@gruber this would make even more sense if you had your domain as a fediverse presence…
@krisbrowne42 I think that's a terrible idea. Many small instances are already disappearing, most will be gone in 10 years.
@gruber crazy like hosting one’s own weblog instead of just using medium or substack? Most sites of any sort will be gone in 10 years… but owning your own platform and presence gives you a lot more choice about its survival.
@krisbrowne42 Paying to host your own website is easy and carefree. I don’t think that’s true for hosting a fedoverse social media node.
@gruber think the same probably applies to people who are really here setting up a bsky bridge as well.
@gruber Disagree. No one is forced to follow both accounts here. What’s the pain for you, anyone complain? Block em.
@DonSqueak I think it reduces confusion to keep them separate.
@gruber thanks for doing this. It will reduce duplication and confusion for me
@gruber But what if we want to keep an on what you tell “those people". You can't expect us to create an account *everywhere* you need supervision.
@gruber I see a lot of journalists doing this recently. Threads is, for all intents and purposes, a Mastodon instance. The logic to me would be, if you’re going to have a Threads account, enable fediverse sharing. When Meta eventually lets Threads users follow Mastodon accounts outside of Threads without previous interaction, tell Threads users to follow you on Mastodon. And if you’re a journalist, ideally run your own Mastodon instance on your own domain so you’re in control and everyone knows it’s really you.
@kenny113 That seems like a lot of bad advice, especially running one's own Mastodon instance. That's a huge headache and I think shortsighted. I’m already seeing many small and self-hosted Masto instances disappear, just a few years after they started. Many more will be gone in 5 years, and I suspect most in 10.
@kenny113 To me that's like telling people to run their own email servers.
@gruber @gruber haha, touché. For an independent journalist like yourself, it may not make sense to run your own instance. For NYT, WaPo, or even The Verge, it might make sense though. How else is there trust on the validity of the source without a commercial solution that provides a blue check?
Can you expand on why enabling fediverse sharing on Threads is bad advice? I don’t understand the point of using federated services and intentionally disabling federation.
@kenny113 I don't know that it's bad advice to enable fediverse sharing on Threads, but I think it's confusing and counterproductive for people like me who have a separate identity here on Mastodon proper.
I think fediverse sharing is good for:
Threads users to follow Mastodon-only accounts.
And for Mastodon users to follow Threads-only accounts.
Neither applies to me.
@gruber I’m interested to see how this separate identity evolves! Haha
I don’t understand the point of maintaining accounts on both a Mastodon instance and Threads for most people. It’s confusing to find two separate accounts in two separate places which could be found in a single place across both systems. Much like the federation/email analogy, I could put two email addresses on my website for people to reach me, but that would seem odd and confusing. Different strokes for different folks!
@kenny113 If you read my post about turning off fediverse sharing, you’ll see I in no way portray it as a recommendation for others to follow. My social media experience is somewhat unusual by nature of my work and relative popularity.
@gruber With BlueSky taking off, I have no further use for Threads as a place to hang out with normies, and I’ve basically stopped using it. I’m attempting to follow anyone there via Mastodon, but only about 20% of the accounts I followed on Threads have federation enabled.
@gruber It does simplify things in the rare case that someone posts something identical to Threads (federated) and Mastodon and I have to double check which one I want to like or reply to. But the times that’s ever come up are like you, @aaronrosspowell@threads.net, and maybe like one other account that I’m forgetting ATM.