A little help for anyone starting or restarting a developer relations program from someone who's done it a few times.

Today Slack launched the open beta of their future-generation, event-driven platform. This iteration features Typescript and Deno at the forefront, though support for other languages is being worked on.

Are you requiring that end users wanting to search Twitter content authenticate with their Twitter account? The best way to scale your usage of the API with your user base is to require users to authenticate. 180 search queries per 15 minutes is plenty to work with for most users.

Those seeking solace in a sample of what's happening on the public timeline need look no further than the sample hose of the Streaming API: https://dev.twitter.com/docs/api/1.1/get/statuses/sample

There are some tweets here and there with a corrupt timestamp. Best thing to do is report them to Twitter for correction on dev.twitter.com/discussions

This kind of limitation assumes that a user is human.

The Search API's limits are more fluid than the REST API. It generally allows for about 1 query per second.

Twitter provides a great way to communicate one-to-many: the simple tweet. It broadcasts to your account's followers and potentially beyond. Some might miss your message or not get it when you want them to since you didn't use an invasive technique, but this is the core use case of Twitter, what it enables. You know users won't see all your tweets. Users know they won't see all your tweets. And then you act accordingly within that system. Better to adapt to this model then to try to adapt the model to what you want to accomplish -- bulk atomic messaging.

As someone who writes a bit of documentation for dev.twitter.com, I admit that a full accounting of every field that passes through the API is certainly missing. The reasons are boring and mostly historical, related to the organic growth of the API & its documentation; for much of the existence of the API, deep pre-existing understanding of Twitter itself was assumed and required for success. That combined with the majority of developers using scripting languages with loose typing meant that devs could fill in the blanks pretty easily.

A more exhaustive index of the fields, a kind of bird watcher's guide for the fields of the Twitter API, should make an appearance in the coming weeks.

http://Everything2.com is a great community of writers; kind of an alternate reality, perspective-based wikipedia with a mix of fact, fiction, essays, drivel, and close-nit culture of folks who regularly meet up together.