I get that, but in what world do you release a feature incomplete beta for a messaging platform integration where the “reading other people’s messages” part is one of the features you’re waiting until later in the cycle to develop?
And I’m not saying API access killed Facebook, I’m saying bot-scheduled inorganic content coming in a flood into everyone’s feed even though literally 0 people want it there is what killed Facebook. And that by specifically calling out that stuff as what they want to bring to Threads (above and ahead of reading the Mastodon people’s messages), they’re showing that their priorities are so toxic that no good can come of interacting with them. It’s the types of posting they want to create that is the problem, not the API that let those postings come into existence.
It’s a public beta, so by the nature of things it’s going to be incomplete. Flipboard is doing the same thing with one-way federation and only federating certain profiles during the test period.
They also didn’t say they want bot-scheduled inorganic content coming in a flood into everyone’s feed though, they said they’re releasing an API. An API could be used by a developer with ill-intentions to automate spam posting, but the alternative is to not have an API and never support third-party apps.
/cdn.vox-cdn.com/uploads/chorus_asset/file/24774110/STK156_Instagram_threads_1.jpg)
I get that, but in what world do you release a feature incomplete beta for a messaging platform integration where the “reading other people’s messages” part is one of the features you’re waiting until later in the cycle to develop?
And I’m not saying API access killed Facebook, I’m saying bot-scheduled inorganic content coming in a flood into everyone’s feed even though literally 0 people want it there is what killed Facebook. And that by specifically calling out that stuff as what they want to bring to Threads (above and ahead of reading the Mastodon people’s messages), they’re showing that their priorities are so toxic that no good can come of interacting with them. It’s the types of posting they want to create that is the problem, not the API that let those postings come into existence.
It’s a public beta, so by the nature of things it’s going to be incomplete. Flipboard is doing the same thing with one-way federation and only federating certain profiles during the test period.
They also didn’t say they want bot-scheduled inorganic content coming in a flood into everyone’s feed though, they said they’re releasing an API. An API could be used by a developer with ill-intentions to automate spam posting, but the alternative is to not have an API and never support third-party apps.
I think we’re gonna have to agree to disagree on what they’re saying they want