Age | Commit message (Collapse) | Author |
|
|
|
results
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to the API
|
|
Also fix reloading of timelines after merge-type events
|
|
|
|
|
|
|
|
|
|
status lists in API
|
|
variant)
|
|
through suggestions in UI
|
|
|
|
|
|
|
|
influential users
|
|
|
|
|
|
fix seed
|
|
|
|
|
|
|
|
|
|
|
|
threaded? check aware of orphaned replies
|
|
|