Gnip 2.0 is in production! Gnip 1.0 is no longer accessible.
Open Wide: Full Data Is Here
We’re proud to introduce full data and expanded meta-data. You now have access to all the data associated with activities, as well as continued support for activity notifications. Full data provides you with additional meta-data about an activity, as well as the actual activity “body” (e.g. the comment text on a blog, or the text of a tweet). Gnip has been contributing to Diso in order to distill activity streams into a common format, and this release is our first attempt at getting this right.
Collections Are Dead; Long Live Filters!
Collections have been migrated to more feature rich “Filters.” You can now do more complex rule based filtering on data that comes through Gnip. For example, Publishers that support “tags” on their activities (e.g. delicious), can be filtered on specific tags/keywords). We currently only support the OR conditional, and not AND. AND introduces not only some interesting technical challenges, but also drives Gnip into some specific product directions we’re still evaluating.
Introducing XMPP
Data Producers can “publish” activities to Gnip via ATOM, REST, or XMPP. Data Consumers can get activities from Gnip via REST, and as of this release, XMPP. We’re just starting to dabble with XMPP for outbound activities, so please help test. Just give us your JID, and add our JID to your roster, and watch it flow. Note, this is not an implementation of XMPP PubSub; baby steps.
Migration Notes
- Existing implementations are now broken if you haven’t updated to the new API.
- Data Producers: please start pushing activities into Gnip using the new schema.
- Data Consumers
- Your accounts, and data, have been migrated to the new service.
- REST endpoints have changed, so please update (API doc here).
- Your collections have been migrated to the new Filter format as “actor” based Filters.
- The schema has changed, so please update (new schema).
- We’ve adopted the microblogging verb/noun of “notice” for microblogging service activity actions. e.g. a “tweet” is no longer a “tweet”, it’s a “notice.”