This is my journey that started as an experiment to see how my Threads feed would look like on Mastodon and ended with me finding experiences that went above and beyond my expectations.
I went to the article expecting rage inducing decisions based on your comment, but your TLDR has no relation to the article whatsoever.
The article is pretty glowing about Threads and Mastodon, and its author seems to be excited by them being connected through federation. They seem hopeful that they can use Mastodon to continue to enjoy their Threads communities.
They also claim that the default Threads experience is way better than the default Mastodon one, especially for the average user, but the API of Mastodon makes for a way better experience in terms of third party clients and tools.
They were able to consume the Threads content chronologically instead of through the algorithmic For You feed that none of us want.
Generally this is the first article posted I’ve seen that was talking about this from a UX perspective, as well as from a Threads user’s perspective, and I found it interesting to read.
I went to the article expecting rage inducing decisions based on your comment, but your TLDR has no relation to the article whatsoever.
The article is pretty glowing about Threads and Mastodon, and its author seems to be excited by them being connected through federation. They seem hopeful that they can use Mastodon to continue to enjoy their Threads communities.
They also claim that the default Threads experience is way better than the default Mastodon one, especially for the average user, but the API of Mastodon makes for a way better experience in terms of third party clients and tools.
They were able to consume the Threads content chronologically instead of through the algorithmic For You feed that none of us want.
Generally this is the first article posted I’ve seen that was talking about this from a UX perspective, as well as from a Threads user’s perspective, and I found it interesting to read.