about summary refs log tree commit diff
path: root/spec/controllers/api
AgeCommit message (Collapse)Author
2017-04-23Fix deprecation warnings on activitypub controller specs (#2357)Matt Jankowski
2017-04-23ActivityPub: Add basic, read-only support for Outboxes, Notes, and ↵Evan Minto
Create/Announce Activities (#2197) * Clean up collapsible components * Expose user Outboxes and AS2 representations of statuses * Save work thus far. * Fix bad merge. * Save my work * Clean up pagination. * First test working. * Add tests. * Add Forbidden error template. * Revert yarn.lock changes. * Fix code style deviations and use localized instead of hardcoded English text.
2017-04-19Add static gif for upload testing (#2168)Marcin Cieślak
2017-04-18Remove API authentication for public statuses (after review) (#1919)happycoloredbanana
2017-04-12Fix issue with intermittent api/v1/notifications failure (#1606)Matt Jankowski
The spec was checking the activity_id of the activities held in notifications within the controller. Because the activities are different models, it is possible that they are created with the same database IDs, and when they are this spec fails because an activity which should not count as a match is counted as one.
2017-04-10API param to exclude notification types from response (#1341)Eugen
* Add exclude_types param to /api/v1/notifications * Exclude notification types in web UI through exclude_types in the API
2017-04-09Fix /api/v1/accounts/update_credentials tests (#1357)Eugen
2017-04-09Allow users to update their Account in the API (#1179)David Celis
* Allow users to update their Account in the API It would be nice for API clients to be able to allow users to update their accounts without having to wrap Mastodon in a web view. This patch adds an API endpoint to let users submit a PATCH for their account. Signed-off-by: David Celis <me@davidcel.is> * Add /api/v1/accounts/update_credentials to the API docs Signed-off-by: David Celis <me@davidcel.is>
2017-03-22Prettier account and stream entry URLsEugen Rochko
2017-03-01Mute button progress so far. WIP, doesn't entirely work correctly.Kit Redgrave
2017-02-11After FollowService, re-fetch remote account asynchronously, do nothingEugen Rochko
if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-05Removing failed push notification API, make context loads use cacheEugen Rochko
2017-02-02Cleaning up format of broadcast real-time messages, removingEugen Rochko
redis-backed "mentions" timeline as redundant (given notifications)
2017-01-29Add tests for new APIEugen Rochko
2017-01-23Fix oembed controller testEugen Rochko
2017-01-15Fix tests, add applications to eager loading/cache for statuses, fixEugen Rochko
application website validation, don't link to app website if website isn't set, also comment out animated boost icon from #464 until it's consistent with non-animated version
2016-12-29Add API for retrieving favouritesEugen Rochko
2016-12-29Add API for retrieving blocked accountsEugen Rochko
2016-12-26Adding follow requests APIEugen Rochko
2016-12-26Don't show statuses to blocked usersEugen Rochko
2016-12-21Private visibility on statuses prevents non-followers from seeing thoseEugen Rochko
Filters out hidden stream entries from Atom feed Blocks now generate hidden stream entries, can be used to federate blocks Private statuses cannot be reblogged (generates generic 422 error for now) POST /api/v1/statuses now takes visibility=(public|unlisted|private) param instead of unlisted boolean Statuses JSON now contains visibility=(public|unlisted|private) field
2016-12-18Removing external hub completely, fix #333 fixing digit-only hashtags,Eugen Rochko
removing web app capability from non-webapp pages
2016-12-06Add suspend account functionality to admin UIEugen Rochko
2016-11-30Add basic OEmbed provider API, fix #247Eugen Rochko
2016-11-28Adding embedded PuSH serverEugen Rochko
2016-11-26Update hub URL and re-subscribe if hub URL changesEugen Rochko
2016-11-24Remove Neo4JEugen Rochko
2016-11-08Move timelines API from statuses to its own controller, add a check forEugen Rochko
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
2016-11-05Adding hashtagsEugen Rochko
2016-11-03Add tests for recently added API end pointsEugen Rochko
2016-10-07Adding public timelineEugen Rochko
2016-10-03API for blocking and unblockingEugen Rochko
2016-10-02Add API for getting info about authenticated user: ↵Eugen Rochko
/api/v1/accounts/verify_credentials
2016-09-30Fix tests, update goldfinger to catch XML errorsEugen Rochko
2016-09-27Fix #52 - Add API versioning (v1)Eugen Rochko
2016-09-26Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - appEugen Rochko
registration API
2016-09-26Fix #54 - Fetch remote accounts by URL from mentionsEugen Rochko
Fetching atom extracted from FetchRemoteAccountService and FetchRemoteStatusService into FetchAtomService. Mentions of the constant "http://activityschema.org/collection/public" skipped as it's not a real URL/user.
2016-09-21Fix notifications in UI, added new API for fetching account relationshipsEugen Rochko
2016-09-21Fix #24 - Thread resolving for remote statusesEugen Rochko
This is a big one, so let me enumerate: Accounts as well as stream entry pages now contain Link headers that reference the Atom feed and Webfinger URL for the former and Atom entry for the latter. So you only need to HEAD those resources to get that information, no need to download and parse HTML <link>s. ProcessFeedService will now queue ThreadResolveWorker for each remote status that it cannot find otherwise. Furthermore, entries are now processed in reverse order (from bottom to top) in case a newer entry references a chronologically previous one. ThreadResolveWorker uses FetchRemoteStatusService to obtain a status and attach the child status it was queued for to it. FetchRemoteStatusService looks up the URL, first with a HEAD, tests if it's an Atom feed, in which case it processes it directly. Next for Link headers to the Atom feed, in which case that is fetched and processed. Lastly if it's HTML, it is checked for <link>s to the Atom feed, and if such is found, that is fetched and processed. The account for the status is derived from author/name attribute in the XML and the hostname in the URL (domain). FollowRemoteAccountService and ProcessFeedService are used. This means that potentially threads are resolved recursively until a dead-end is encountered, however it is performed asynchronously over background jobs, so it should be ok.
2016-09-20Upgrade to PubSubHubbub 0.4 (removing verify_token)Eugen Rochko
2016-09-16Test case for new api endpointEugen Rochko
2016-09-12Fixing image upload limits, allowing webm, merge/unmerge events triggerEugen Rochko
timeline reload in UI, other small fixes
2016-09-08Optimized n+1 queries in accounts Atom and HTML viewsEugen Rochko
Added stack trace for SQL queries in development Removed badly thought out accounts/lookup API
2016-09-08Fix local follows, 404 in logsEugen Rochko
2016-09-08Fixing atom feeds for accounts, adding tests that would catch such bugs in ↵Eugen Rochko
future
2016-09-05Add API to upload media attachmentsEugen Rochko
2016-09-05Enhancing test suite but I think the problem might have been caching settingEugen Rochko
2016-08-18Fixing more configuration issues with ActionCableEugen Rochko
2016-08-17Upgrade to Rails 5.0.0.1Eugen Rochko
2016-03-21Fixed the lookup API methodEugen Rochko
generated by cgit-pink (git 2.37.1) at 2024-11-09 19:26:45 +0000