> Like someone using a custom twitter client as a single user shouldn't get that label, no?
Why not? If it's a niche client not many people use such false positive would be rare. Also such people probably don't have huge audirnce and they and their audiences won't care.
And it might be deterrent against people trying to build popular alternative client that might compete with main twitter app.
I don't think aiming for 100% accurate label is on the table.
Yeah, but that was then and this is now. Thinghs kinda settled down since then.
The real danger of opening the API and marking all tweets made through API as BOT is that this label looses impact if some alternative client that uses API raises to prominence.
I'd say that current setup where users have no indication that something might have been posted by bot is way more horrible.
Why not? If it's a niche client not many people use such false positive would be rare. Also such people probably don't have huge audirnce and they and their audiences won't care.
And it might be deterrent against people trying to build popular alternative client that might compete with main twitter app.
I don't think aiming for 100% accurate label is on the table.