48 Commits (0bbd5789b51c9187ecdff19423536f921fab3f9e)

Author	SHA1	Message	Date
Akihiko Odaki	0f92119ceb	Cover Api::V1:FavouritesController more (#4409)	8 years ago
Akihiko Odaki	4f0b638cda	Introduce access token fabricators (#4401)	8 years ago
Akihiko Odaki	bdf573d140	Remove redundant fabrication in the spec for Api::V1::FavouritesController (#4391)	8 years ago
Eugen Rochko	42b8220632	Fix #1624 - Send e-mail notifications to admins about new reports (#3949)	8 years ago
Matt Jankowski	2925372ff4	Move create/destroy actions for api/v1/statuses to namespace (#3678) ... Each of mute, favourite, reblog has been updated to: - Have a separate controller with just a create and destroy action - Preserve historical route names to not break the API - Mild refactoring to break up long methods	8 years ago
Matt Jankowski	5282ba862a	Move reblogged_by and favourited_by actions out of api/v1/statuses and into unique controllers (#3646) ... * Add specs for api statuses routes * Update favourited_by and reblogged_by api routes * Move methods into new controllers * Use load_accounts methods to simplify index actions * Clean up load_accounts methods * Clean up link header generation * Check for link headers in specs * Remove unused actions from api/v1/statuses controller * Remove specs for moved actions	8 years ago
Daigo 3 Dango	2985d08951	Redirect to streaming_api_base_url (#3579) ... * Redirect to streaming_api_base_url When Rails receives a request to streaming API, it most likely means that there is another host which is configured to respond to it. This is to redirect clients to that host if `STREAMING_API_BASE_URL` is set as another host. * Use the new Ruby 1.9 hash syntax	8 years ago
Matt Jankowski	5c63523972	Spec coverage and refactor for the api/v1/accounts controllers (#3451)	8 years ago
Matt Jankowski	5236a62861	Improve spec coverage and clean up api/v1/blocks controller (#3464)	8 years ago
Matt Jankowski	0f155829b7	Improve spec coverage and clean up api/v1/follow_requests controller (#3465)	8 years ago
Matt Jankowski	84dda45df9	Improve spec coverage and clean up api/v1/domain_blocks controller (#3466)	8 years ago
Matt Jankowski	75cad1d9d6	Improve spec coverage and clean up api/v1/favourites controller (#3472)	8 years ago
Matt Jankowski	bf811e4d4a	Improve spec coverage and clean up api/v1/mutes controller (#3481)	8 years ago
Matt Jankowski	8235623362	Improve spec coverage and clean up api/v1/media controller (#3467)	8 years ago
Matt Jankowski	4289ed1d13	Refactor of API timeline actions (#3263) ... - Increase coverage to exercise all parts of each action - Move into namespace to share common code - Misc refactor of each action for smaller methods, simpler code	8 years ago
Jack Jennings	8c5eaf7ae9	Enable and fill in JSON response test in API::AccountsController (#3157)	8 years ago
Matt Jankowski	b6f6152e26	Add coverage for api/v1 controllers (#3155)	8 years ago
Eugen Rochko	620d0d8029	Account domain blocks (#2381) ... * Add <ostatus:conversation /> tag to Atom input/output Only uses ref attribute (not href) because href would be the alternate link that's always included also. Creates new conversation for every non-reply status. Carries over conversation for every reply. Keeps remote URIs verbatim, generates local URIs on the fly like the rest of them. * Conversation muting - prevents notifications that reference a conversation (including replies, favourites, reblogs) from being created. API endpoints /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute Currently no way to tell when a status/conversation is muted, so the web UI only has a "disable notifications" button, doesn't work as a toggle * Display "Dismiss notifications" on all statuses in notifications column, not just own * Add "muted" as a boolean attribute on statuses JSON For now always false on contained reblogs, since it's only relevant for statuses returned from the notifications endpoint, which are not nested Remove "Disable notifications" from detailed status view, since it's only relevant in the notifications column * Up max class length * Remove pending test for conversation mute * Add tests, clean up * Rename to "mute conversation" and "unmute conversation" * Raise validation error when trying to mute/unmute status without conversation * Adding account domain blocks that filter notifications and public timelines * Add tests for domain blocks in notifications, public timelines Filter reblogs of blocked domains from home * Add API for listing and creating account domain blocks * API for creating/deleting domain blocks, tests for Status#ancestors and Status#descendants, filter domain blocks from them * Filter domains in streaming API * Update account_domain_block_spec.rb	8 years ago
Eugen Rochko	d0dd9eb5b5	Feature conversations muting (#3017) ... * Add <ostatus:conversation /> tag to Atom input/output Only uses ref attribute (not href) because href would be the alternate link that's always included also. Creates new conversation for every non-reply status. Carries over conversation for every reply. Keeps remote URIs verbatim, generates local URIs on the fly like the rest of them. * Conversation muting - prevents notifications that reference a conversation (including replies, favourites, reblogs) from being created. API endpoints /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute Currently no way to tell when a status/conversation is muted, so the web UI only has a "disable notifications" button, doesn't work as a toggle * Display "Dismiss notifications" on all statuses in notifications column, not just own * Add "muted" as a boolean attribute on statuses JSON For now always false on contained reblogs, since it's only relevant for statuses returned from the notifications endpoint, which are not nested Remove "Disable notifications" from detailed status view, since it's only relevant in the notifications column * Up max class length * Remove pending test for conversation mute * Add tests, clean up * Rename to "mute conversation" and "unmute conversation" * Raise validation error when trying to mute/unmute status without conversation	8 years ago
Eugen Rochko	f5bf5ebb82	Replace sprockets/browserify with Webpack (#2617) ... * Replace browserify with webpack * Add react-intl-translations-manager * Do not minify in development, add offline-plugin for ServiceWorker background cache updates * Adjust tests and dependencies * Fix production deployments * Fix tests * More optimizations * Improve travis cache for npm stuff * Re-run travis * Add back support for custom.scss as before * Remove offline-plugin and babili * Fix issue with Immutable.List().unshift(...values) not working as expected * Make travis load schema instead of running all migrations in sequence * Fix missing React import in WarningContainer. Optimize rendering performance by using ImmutablePureComponent instead of React.PureComponent. ImmutablePureComponent uses Immutable.is() to compare props. Replace dynamic callback bindings in <UI /> * Add react definitions to places that use JSX * Add Procfile.dev for running rails, webpack and streaming API at the same time	8 years ago
Marcin Cieślak	59a77923b3	Add static gif for upload testing (#2168)	8 years ago
happycoloredbanana	0a7588282a	Remove API authentication for public statuses (after review) (#1919)	8 years ago
Matt Jankowski	b155e6ccf5	Fix issue with intermittent api/v1/notifications failure (#1606) ... 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.	8 years ago
Eugen	2810013b93	API param to exclude notification types from response (#1341) ... * Add exclude_types param to /api/v1/notifications * Exclude notification types in web UI through exclude_types in the API	8 years ago
Eugen	15d442cf9d	Fix /api/v1/accounts/update_credentials tests (#1357)	8 years ago
David Celis	d4fe6cd2bf	Allow users to update their Account in the API (#1179) ... * 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>	8 years ago
Kit Redgrave	442fdbfc53	Mute button progress so far. WIP, doesn't entirely work correctly.	8 years ago
Eugen Rochko	00b5731ecb	After FollowService, re-fetch remote account asynchronously, do nothing ... if account lock info was up to date, otherwise re-do the FollowService with now updated information	8 years ago
Eugen Rochko	77e13c2bc9	Removing failed push notification API, make context loads use cache	8 years ago
Eugen Rochko	d9ca46b464	Cleaning up format of broadcast real-time messages, removing ... redis-backed "mentions" timeline as redundant (given notifications)	8 years ago
Eugen Rochko	e70e721a0d	Add tests for new API	8 years ago
Eugen Rochko	e9737c2235	Fix tests, add applications to eager loading/cache for statuses, fix ... 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	8 years ago
Eugen Rochko	a302e56f9a	Add API for retrieving favourites	8 years ago
Eugen Rochko	49834a6e7f	Add API for retrieving blocked accounts	8 years ago
Eugen Rochko	004382e4d0	Adding follow requests API	8 years ago
Eugen Rochko	7376af90f7	Don't show statuses to blocked users	8 years ago
Eugen Rochko	80e02b90e4	Private visibility on statuses prevents non-followers from seeing those ... 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	8 years ago
Eugen Rochko	6de079a5af	Removing external hub completely, fix #333 fixing digit-only hashtags, ... removing web app capability from non-webapp pages	8 years ago
Eugen Rochko	f978b06dd1	Add suspend account functionality to admin UI	8 years ago
Eugen Rochko	8efa081f21	Remove Neo4J	8 years ago
Eugen Rochko	9aecc0f48a	Move timelines API from statuses to its own controller, add a check for ... 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	8 years ago
Eugen Rochko	48b9619439	Adding hashtags	8 years ago
Eugen Rochko	829d189f44	Add tests for recently added API end points	8 years ago
Eugen Rochko	1f650d327d	Adding public timeline	8 years ago
Eugen Rochko	7b9a4af311	API for blocking and unblocking	8 years ago
Eugen Rochko	6d7290f47c	Add API for getting info about authenticated user: /api/v1/accounts/verify_credentials	8 years ago
Eugen Rochko	b36197c307	Fix tests, update goldfinger to catch XML errors	8 years ago
Eugen Rochko	4f9b7432dd	Fix #52 - Add API versioning (v1)	8 years ago