"Twitter rewrites developer policy" is a frequent enough occurrence that I'd be highly reluctant to build anything material on top of the ever-shifting sands that comprise their APIs.
I'm not sure what you mean - what choice do you have? You're either building a twitter bot, or you aren't and it doesn't matter?
Also this isn't much (if any?) of an API change, it's a policy change. And even then it doesn't look like it should negatively affect you unless you were doing something nefarious already.
> I'm not sure what you mean - what choice do you have?
I can choose not to interact with their platform at all. I can also find other ways of interacting with them in other ways (scraping or headless browser automation).
> Also this isn't much (if any?) of an API change, it's a policy change. And even then it doesn't look like it should negatively affect you unless you were doing something nefarious already.
If you are investing time and effort into an endeavour (whatever it is) it helps to know whether ground is likely to disappear from under you.
Microsoft while many people don't like them have kept many ancient APIs working e.g. We have code from 2005 that still works with the latest .NET Runtime with rather minimal changes. This provides you with confidence that going forward you won't face a lot of churn.
Policies while they aren't APIs are important in that they are both clear, applied fairly and don't change on a whim. A lot of people are sceptical that Twitter will do any of those based on previous behaviour.
