stilist / laminar Goto Github PK

Currently trapped inside the Activity data fields.

• posts
• votes
• comments

http://api.imgur.com

• https://www.mapbox.com/mapbox.js/
• https://www.mapbox.com/mapbox.js/example/v1.0.0/polyline/

Currently everything except the timestamp is extracted from the data field. Makes it difficult to build tag pages or generate Open Graph metadata.

• images
• title
• description
• original_id

https://www.etsy.com/developers/documentation/reference/transaction#method_findalluserbuyertransactions

https://coinbase.com/docs/api/overview
https://coinbase.com/api/doc/1.0/account_changes/index.html

• backed projects

Can integrate with the contacts system (7d26642).

Already scales down well with the current design, but could be improved.

• icon(s)
• manifest
• splash screen?

For every Activity item displayed the code is making two calls to Weather::nearest_observation, which in turn makes two database calls—so a page displaying the maximum 100 items makes 400 calls to the WeatherObservations table.

My idea for an alternative is:

1. fetch WeatherObservations between the first and last Activity records that will be displayed
2. map created_at into observation_times (Array)
3. use something from here to find the index of the observation nearest the Activity timestamp
4. return observation_times[idx]

Single database call, and everything else is done in ruby.

Useful to import flight paths (particularly dumping into the the #20 geo system).

http://flightaware.com/commercial/flightxml/pricing_class.rvt

Would apparently want Class 2 for GetHistoricalTrack.

• posts
• likes
• comments

I like the way the new Google Maps handles this.

Currently looking into jquery.gantt since I’m familiar with the code.

Partly implemented right now.

• import
• updates

http://developers.soundcloud.com/docs/api/reference
https://github.com/soundcloud/soundcloud-ruby

http://www.withings.com/en/api
https://github.com/simplificator/simplificator-withings
https://oauth.withings.com/en/partner/add

• weight
• blood pressure

Per support they don’t have an API, but it’s possible to download a partial transaction history as JSON.

https://pinboard.in/api/

• bookmarks import, https://pinboard.in/api/#posts_recent

http://www.tumblr.com/docs/en/api/v2
https://github.com/tumblr/tumblr_client

• posts
• likes

http://www.kmikeym.com/users/501/account_history_graph.json

https://developers.google.com/gmail/xoauth2_protocol
https://github.com/humanbagel/gmail

http://api.ihackernews.com

• comments
• votes (I wish)

https://dev.moves-app.com/

• ratings

For the moment probably just filtering with pagination, but ultimately could have activity graphs or something.

• year
• year/month
• year/month/day

No API, but user feeds.

• posts
• comments
• favorites

https://developer.valvesoftware.com/wiki/Steam_Web_API

https://developer.forecast.io/docs/v2

Can do a couple extra things at the same time:

• more frequent fetches
• hook into geolocation system for weather local to the activity

http://developer.github.com/v3/activity/events/
https://github.com/peter-murach/github

• commits
• issues
• follow
• star

• sleep
• activity

http://dev.cloudup.com/

• checkins
• comments
• ?

https://github.com/gittip/www.gittip.com#api

http://build.kiva.org/api

https://github.com/matthooks/vimeo
https://developer.vimeo.com/apis/advanced
https://developer.vimeo.com/apis/advanced/methods

• uploads
• likes
• comments (not sure if supported)

https://github.com/arsduo/koala

http://www.discogs.com/developers/

• collection

• edit history

https://github.com/cloudapp/api/blob/master/README.md

• likes

• favorites
• uploads
• comments

• play history

• comments
• votes