#1

In the coming weeks, we will no longer be delivering compliance events through the streaming endpoints below:

https://stream.twitter.com/1.1/statuses/sample.json

https://stream.twitter.com/1.1/statuses/filter.json

The following event types will no longer be delivered through the streaming endpoints above:

  • Status deletion notices (delete)
  • Location deletion notices (scrub_geo)
  • Withheld content notices (status_withheld, user_withheld)
  • User update (user_update)

See more in the docs here.

This impacts developers using the statuses/filter and statuses/sample streaming endpoints, who also may be consuming or tracking compliance data delivered in the streaming connections.

We are making this change to better align this endpoint with our Filter Stream and Sampled Stream endpoints that we recently launched in Labs. We have been given feedback that the compliance events are low value and that developers would prefer more pure streaming endpoints.

Here is how you can prepare for this change:

  1. Please be aware that these events will stop being delivered through these endpoints and update your parser and system logic to accommodate.
  2. Explore the recommended options for keeping data compliant here. Tweet compliance data should be used to keep databases compliant as required by the Twitter Developer Policy, and for display purposes.

We would love to hear your feedback or use cases around receiving this data for future endpoints that we build within Labs. Please let us know your feedback/concerns or suggestions within our feedback portal here.

Regards,
The Twitter Developer Relations team

2 Likes
#2