the problem i see with this whole thing is that twitter (which is the company you are disappointed of) is a pain only to developers because they want to use their (more and more restrictive) api but not to the users. obviously they suffer too in the long run by not getting any innovative third party twitter clients or other useful stuff that's based on the twitter api. but this is (a) too far away in the future and (b) most of them won't know why that is or worse not even care.

the thing is: the reason why developers want access to the twitter api in the first place is because the users are there. you cannot just make a paradise for developers when there are no actual users feeding data into the system. one of the main reasons twitter got to where it is today is because celebrities started using it and their fans followed... you cannot reconstruct this phenomenon in the way you're trying to pull it off.

maybe, what you're trying to do is something completey else. maybe you want a service rather for machines to talk to, as a service purely for developers. than that's something completely else.