Age | Commit message (Collapse) | Author |
|
|
|
|
|
resources that require a user context vs those that don't (such as public timeline)
/api/v1/statuses/public -> /api/v1/timelines/public
/api/v1/statuses/home -> /api/v1/timelines/home
/api/v1/statuses/mentions -> /api/v1/timelines/mentions
/api/v1/statuses/tag/:tag -> /api/v1/timelines/tag/:tag
|
|
|
|
|
|
status
|
|
|
|
|
|
to the API
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/api/v1/accounts/verify_credentials
|
|
|
|
|
|
registration API
|
|
|
|
|
|
fetching status context
|
|
Added stack trace for SQL queries in development
Removed badly thought out accounts/lookup API
|
|
|
|
|
|
|
|
|
|
in the pool, adding a throttle of 60rpm per IP, adding mini profiler, adding
admin status to users
|
|
|
|
|
|
simplify FanOutOnWriteService, add /api/accounts/lookup method
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
POST /api/statuses Params: status (text contents), in_reply_to_id (optional)
GET /api/statuses/:id
POST /api/statuses/:id/reblog
GET /api/accounts/:id
GET /api/accounts/:id/following
GET /api/accounts/:id/followers
POST /api/accounts/:id/follow
POST /api/accounts/:id/unfollow
POST /api/follows Params: uri (e.g. user@domain)
OAuth authentication is currently disabled, but the API can be used with HTTP Auth.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|