Age | Commit message (Collapse) | Author |
|
future
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and atom feed generation to some extent, as well as the way mentions are
stored
|
|
relations on Status#mentions
|
|
|
|
|
|
related to #20
|
|
|
|
|
|
simplify FanOutOnWriteService, add /api/accounts/lookup method
|
|
|
|
|
|
|
|
|
|
the block, even though the last line of a block is an implicit return. I am
confused to say the least
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|