2017-05-03 03:04:16 +03:00
|
|
|
import React from 'react';
|
2016-09-30 01:00:45 +03:00
|
|
|
import ImmutablePropTypes from 'react-immutable-proptypes';
|
2019-11-19 22:24:16 +02:00
|
|
|
import { connect } from 'react-redux';
|
2017-04-21 21:05:35 +03:00
|
|
|
import PropTypes from 'prop-types';
|
2016-11-16 18:20:52 +02:00
|
|
|
import IconButton from './icon_button';
|
2017-07-27 23:31:59 +03:00
|
|
|
import DropdownMenuContainer from '../containers/dropdown_menu_container';
|
2016-11-18 16:36:16 +02:00
|
|
|
import { defineMessages, injectIntl } from 'react-intl';
|
2017-05-26 15:05:52 +03:00
|
|
|
import ImmutablePureComponent from 'react-immutable-pure-component';
|
2022-07-05 03:41:40 +03:00
|
|
|
import { me } from '../initial_state';
|
2020-08-24 15:13:44 +03:00
|
|
|
import classNames from 'classnames';
|
2022-07-05 03:41:40 +03:00
|
|
|
import { PERMISSION_MANAGE_USERS } from 'mastodon/permissions';
|
2016-11-18 16:36:16 +02:00
|
|
|
|
|
|
|
const messages = defineMessages({
|
|
|
|
delete: { id: 'status.delete', defaultMessage: 'Delete' },
|
2018-06-05 01:17:38 +03:00
|
|
|
redraft: { id: 'status.redraft', defaultMessage: 'Delete & re-draft' },
|
2022-02-10 01:15:30 +02:00
|
|
|
edit: { id: 'status.edit', defaultMessage: 'Edit' },
|
2018-04-09 18:09:11 +03:00
|
|
|
direct: { id: 'status.direct', defaultMessage: 'Direct message @{name}' },
|
2017-03-01 01:53:11 +02:00
|
|
|
mention: { id: 'status.mention', defaultMessage: 'Mention @{name}' },
|
2017-04-03 10:56:01 +03:00
|
|
|
mute: { id: 'account.mute', defaultMessage: 'Mute @{name}' },
|
2017-03-01 01:53:11 +02:00
|
|
|
block: { id: 'account.block', defaultMessage: 'Block @{name}' },
|
2016-11-18 16:36:16 +02:00
|
|
|
reply: { id: 'status.reply', defaultMessage: 'Reply' },
|
2017-07-25 21:38:39 +03:00
|
|
|
share: { id: 'status.share', defaultMessage: 'Share' },
|
2017-10-16 10:31:47 +03:00
|
|
|
more: { id: 'status.more', defaultMessage: 'More' },
|
2017-04-19 15:20:04 +03:00
|
|
|
replyAll: { id: 'status.replyAll', defaultMessage: 'Reply to thread' },
|
2017-04-27 13:03:28 +03:00
|
|
|
reblog: { id: 'status.reblog', defaultMessage: 'Boost' },
|
2020-08-23 01:08:31 +03:00
|
|
|
reblog_private: { id: 'status.reblog_private', defaultMessage: 'Boost with original visibility' },
|
2018-04-18 00:35:45 +03:00
|
|
|
cancel_reblog_private: { id: 'status.cancel_reblog_private', defaultMessage: 'Unboost' },
|
2017-04-27 13:03:28 +03:00
|
|
|
cannot_reblog: { id: 'status.cannot_reblog', defaultMessage: 'This post cannot be boosted' },
|
2016-12-11 23:49:25 +02:00
|
|
|
favourite: { id: 'status.favourite', defaultMessage: 'Favourite' },
|
2019-11-14 00:02:10 +02:00
|
|
|
bookmark: { id: 'status.bookmark', defaultMessage: 'Bookmark' },
|
2019-11-19 22:24:16 +02:00
|
|
|
removeBookmark: { id: 'status.remove_bookmark', defaultMessage: 'Remove bookmark' },
|
2017-03-01 01:53:11 +02:00
|
|
|
open: { id: 'status.open', defaultMessage: 'Expand this status' },
|
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
2017-05-15 04:04:13 +03:00
|
|
|
report: { id: 'status.report', defaultMessage: 'Report @{name}' },
|
|
|
|
muteConversation: { id: 'status.mute_conversation', defaultMessage: 'Mute conversation' },
|
|
|
|
unmuteConversation: { id: 'status.unmute_conversation', defaultMessage: 'Unmute conversation' },
|
2017-08-25 02:41:18 +03:00
|
|
|
pin: { id: 'status.pin', defaultMessage: 'Pin on profile' },
|
|
|
|
unpin: { id: 'status.unpin', defaultMessage: 'Unpin from profile' },
|
2017-09-01 22:30:13 +03:00
|
|
|
embed: { id: 'status.embed', defaultMessage: 'Embed' },
|
2019-01-04 14:10:43 +02:00
|
|
|
admin_account: { id: 'status.admin_account', defaultMessage: 'Open moderation interface for @{name}' },
|
|
|
|
admin_status: { id: 'status.admin_status', defaultMessage: 'Open this status in the moderation interface' },
|
2019-02-11 05:19:49 +02:00
|
|
|
copy: { id: 'status.copy', defaultMessage: 'Copy link to status' },
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
hide: { id: 'status.hide', defaultMessage: 'Hide toot' },
|
2020-03-06 00:20:49 +02:00
|
|
|
blockDomain: { id: 'account.block_domain', defaultMessage: 'Block domain {domain}' },
|
|
|
|
unblockDomain: { id: 'account.unblock_domain', defaultMessage: 'Unblock domain {domain}' },
|
2019-11-19 22:24:16 +02:00
|
|
|
unmute: { id: 'account.unmute', defaultMessage: 'Unmute @{name}' },
|
|
|
|
unblock: { id: 'account.unblock', defaultMessage: 'Unblock @{name}' },
|
2022-08-25 05:27:47 +03:00
|
|
|
filter: { id: 'status.filter', defaultMessage: 'Filter this post' },
|
2016-11-18 16:36:16 +02:00
|
|
|
});
|
2016-09-30 01:00:45 +03:00
|
|
|
|
2019-11-19 22:24:16 +02:00
|
|
|
const mapStateToProps = (state, { status }) => ({
|
|
|
|
relationship: state.getIn(['relationships', status.getIn(['account', 'id'])]),
|
|
|
|
});
|
|
|
|
|
|
|
|
export default @connect(mapStateToProps)
|
|
|
|
@injectIntl
|
2018-09-14 18:59:48 +03:00
|
|
|
class StatusActionBar extends ImmutablePureComponent {
|
2017-04-21 21:05:35 +03:00
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
static contextTypes = {
|
2017-05-20 18:31:47 +03:00
|
|
|
router: PropTypes.object,
|
2022-07-05 03:41:40 +03:00
|
|
|
identity: PropTypes.object,
|
2017-05-12 15:44:10 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
static propTypes = {
|
|
|
|
status: ImmutablePropTypes.map.isRequired,
|
2019-11-19 22:24:16 +02:00
|
|
|
relationship: ImmutablePropTypes.map,
|
2017-05-12 15:44:10 +03:00
|
|
|
onReply: PropTypes.func,
|
|
|
|
onFavourite: PropTypes.func,
|
|
|
|
onReblog: PropTypes.func,
|
|
|
|
onDelete: PropTypes.func,
|
2018-04-09 18:09:11 +03:00
|
|
|
onDirect: PropTypes.func,
|
2017-05-12 15:44:10 +03:00
|
|
|
onMention: PropTypes.func,
|
|
|
|
onMute: PropTypes.func,
|
2019-11-19 22:24:16 +02:00
|
|
|
onUnmute: PropTypes.func,
|
2017-05-12 15:44:10 +03:00
|
|
|
onBlock: PropTypes.func,
|
2019-11-19 22:24:16 +02:00
|
|
|
onUnblock: PropTypes.func,
|
|
|
|
onBlockDomain: PropTypes.func,
|
|
|
|
onUnblockDomain: PropTypes.func,
|
2017-05-12 15:44:10 +03:00
|
|
|
onReport: PropTypes.func,
|
2017-09-01 22:30:13 +03:00
|
|
|
onEmbed: PropTypes.func,
|
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
2017-05-15 04:04:13 +03:00
|
|
|
onMuteConversation: PropTypes.func,
|
2017-08-25 02:41:18 +03:00
|
|
|
onPin: PropTypes.func,
|
2019-11-14 00:02:10 +02:00
|
|
|
onBookmark: PropTypes.func,
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
onFilter: PropTypes.func,
|
2022-08-25 05:27:47 +03:00
|
|
|
onAddFilter: PropTypes.func,
|
2022-10-07 11:14:31 +03:00
|
|
|
onInteractionModal: PropTypes.func,
|
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
2017-05-15 04:04:13 +03:00
|
|
|
withDismiss: PropTypes.bool,
|
2022-02-25 01:34:33 +02:00
|
|
|
withCounters: PropTypes.bool,
|
2020-07-09 16:09:19 +03:00
|
|
|
scrollKey: PropTypes.string,
|
2017-05-20 18:31:47 +03:00
|
|
|
intl: PropTypes.object.isRequired,
|
2017-05-12 15:44:10 +03:00
|
|
|
};
|
|
|
|
|
2017-05-26 15:05:52 +03:00
|
|
|
// Avoid checking props that are functions (and whose equality will always
|
|
|
|
// evaluate to false. See react-immutable-pure-component for usage.
|
|
|
|
updateOnProps = [
|
|
|
|
'status',
|
2019-11-19 22:24:16 +02:00
|
|
|
'relationship',
|
2017-05-26 15:05:52 +03:00
|
|
|
'withDismiss',
|
|
|
|
]
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleReplyClick = () => {
|
2022-10-07 11:14:31 +03:00
|
|
|
const { signedIn } = this.context.identity;
|
|
|
|
|
|
|
|
if (signedIn) {
|
2019-02-15 20:43:09 +02:00
|
|
|
this.props.onReply(this.props.status, this.context.router.history);
|
|
|
|
} else {
|
2022-10-07 11:14:31 +03:00
|
|
|
this.props.onInteractionModal('reply', this.props.status);
|
2019-02-15 20:43:09 +02:00
|
|
|
}
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-09-30 01:00:45 +03:00
|
|
|
|
2017-07-25 21:38:39 +03:00
|
|
|
handleShareClick = () => {
|
|
|
|
navigator.share({
|
|
|
|
text: this.props.status.get('search_index'),
|
|
|
|
url: this.props.status.get('url'),
|
2018-03-31 14:16:38 +03:00
|
|
|
}).catch((e) => {
|
|
|
|
if (e.name !== 'AbortError') console.error(e);
|
2017-07-25 21:38:39 +03:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleFavouriteClick = () => {
|
2022-10-07 11:14:31 +03:00
|
|
|
const { signedIn } = this.context.identity;
|
|
|
|
|
|
|
|
if (signedIn) {
|
2019-02-15 20:43:09 +02:00
|
|
|
this.props.onFavourite(this.props.status);
|
|
|
|
} else {
|
2022-10-07 11:14:31 +03:00
|
|
|
this.props.onInteractionModal('favourite', this.props.status);
|
2019-02-15 20:43:09 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
handleReblogClick = e => {
|
2022-10-07 11:14:31 +03:00
|
|
|
const { signedIn } = this.context.identity;
|
|
|
|
|
|
|
|
if (signedIn) {
|
2019-02-15 20:43:09 +02:00
|
|
|
this.props.onReblog(this.props.status, e);
|
|
|
|
} else {
|
2022-10-07 11:14:31 +03:00
|
|
|
this.props.onInteractionModal('reblog', this.props.status);
|
2019-02-15 20:43:09 +02:00
|
|
|
}
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-09-30 01:00:45 +03:00
|
|
|
|
2019-11-14 00:02:10 +02:00
|
|
|
handleBookmarkClick = () => {
|
|
|
|
this.props.onBookmark(this.props.status);
|
|
|
|
}
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleDeleteClick = () => {
|
2018-08-19 04:17:01 +03:00
|
|
|
this.props.onDelete(this.props.status, this.context.router.history);
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-09-30 01:00:45 +03:00
|
|
|
|
2018-06-05 01:17:38 +03:00
|
|
|
handleRedraftClick = () => {
|
2018-08-19 04:17:01 +03:00
|
|
|
this.props.onDelete(this.props.status, this.context.router.history, true);
|
2018-06-05 01:17:38 +03:00
|
|
|
}
|
|
|
|
|
2022-02-10 01:15:30 +02:00
|
|
|
handleEditClick = () => {
|
|
|
|
this.props.onEdit(this.props.status, this.context.router.history);
|
|
|
|
}
|
|
|
|
|
2017-08-25 02:41:18 +03:00
|
|
|
handlePinClick = () => {
|
|
|
|
this.props.onPin(this.props.status);
|
|
|
|
}
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleMentionClick = () => {
|
2017-06-20 21:40:03 +03:00
|
|
|
this.props.onMention(this.props.status.get('account'), this.context.router.history);
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-10-24 18:11:02 +03:00
|
|
|
|
2018-04-09 18:09:11 +03:00
|
|
|
handleDirectClick = () => {
|
|
|
|
this.props.onDirect(this.props.status.get('account'), this.context.router.history);
|
|
|
|
}
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleMuteClick = () => {
|
2019-11-19 22:24:16 +02:00
|
|
|
const { status, relationship, onMute, onUnmute } = this.props;
|
|
|
|
const account = status.get('account');
|
|
|
|
|
|
|
|
if (relationship && relationship.get('muting')) {
|
|
|
|
onUnmute(account);
|
|
|
|
} else {
|
|
|
|
onMute(account);
|
|
|
|
}
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2017-04-03 10:56:01 +03:00
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleBlockClick = () => {
|
2019-11-19 22:24:16 +02:00
|
|
|
const { status, relationship, onBlock, onUnblock } = this.props;
|
|
|
|
const account = status.get('account');
|
|
|
|
|
|
|
|
if (relationship && relationship.get('blocking')) {
|
|
|
|
onUnblock(account);
|
2019-12-02 19:25:24 +02:00
|
|
|
} else {
|
|
|
|
onBlock(status);
|
2019-11-19 22:24:16 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
handleBlockDomain = () => {
|
|
|
|
const { status, onBlockDomain } = this.props;
|
|
|
|
const account = status.get('account');
|
|
|
|
|
|
|
|
onBlockDomain(account.get('acct').split('@')[1]);
|
|
|
|
}
|
|
|
|
|
|
|
|
handleUnblockDomain = () => {
|
|
|
|
const { status, onUnblockDomain } = this.props;
|
|
|
|
const account = status.get('account');
|
|
|
|
|
|
|
|
onUnblockDomain(account.get('acct').split('@')[1]);
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-11-23 23:57:57 +02:00
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleOpen = () => {
|
2021-09-26 06:46:13 +03:00
|
|
|
this.context.router.history.push(`/@${this.props.status.getIn(['account', 'acct'])}/${this.props.status.get('id')}`);
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2016-12-11 23:49:25 +02:00
|
|
|
|
2017-09-01 22:30:13 +03:00
|
|
|
handleEmbed = () => {
|
|
|
|
this.props.onEmbed(this.props.status);
|
|
|
|
}
|
|
|
|
|
2017-05-12 15:44:10 +03:00
|
|
|
handleReport = () => {
|
2017-02-14 21:59:26 +02:00
|
|
|
this.props.onReport(this.props.status);
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|
2017-02-14 21:59:26 +02:00
|
|
|
|
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
2017-05-15 04:04:13 +03:00
|
|
|
handleConversationMuteClick = () => {
|
|
|
|
this.props.onMuteConversation(this.props.status);
|
|
|
|
}
|
|
|
|
|
2022-08-25 05:27:47 +03:00
|
|
|
handleFilterClick = () => {
|
|
|
|
this.props.onAddFilter(this.props.status);
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
}
|
|
|
|
|
2019-02-11 05:19:49 +02:00
|
|
|
handleCopy = () => {
|
|
|
|
const url = this.props.status.get('url');
|
|
|
|
const textarea = document.createElement('textarea');
|
|
|
|
|
|
|
|
textarea.textContent = url;
|
|
|
|
textarea.style.position = 'fixed';
|
|
|
|
|
|
|
|
document.body.appendChild(textarea);
|
|
|
|
|
|
|
|
try {
|
|
|
|
textarea.select();
|
|
|
|
document.execCommand('copy');
|
|
|
|
} catch (e) {
|
|
|
|
|
|
|
|
} finally {
|
|
|
|
document.body.removeChild(textarea);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
|
2022-08-25 05:27:47 +03:00
|
|
|
handleHideClick = () => {
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
this.props.onFilter();
|
|
|
|
}
|
|
|
|
|
2016-09-30 01:00:45 +03:00
|
|
|
render () {
|
2022-02-25 01:34:33 +02:00
|
|
|
const { status, relationship, intl, withDismiss, withCounters, scrollKey } = this.props;
|
2022-10-25 20:02:21 +03:00
|
|
|
const { signedIn } = this.context.identity;
|
2017-09-02 15:01:44 +03:00
|
|
|
|
2022-10-25 20:02:21 +03:00
|
|
|
const anonymousAccess = !signedIn;
|
2017-09-02 15:01:44 +03:00
|
|
|
const publicStatus = ['public', 'unlisted'].includes(status.get('visibility'));
|
2022-01-17 01:49:55 +02:00
|
|
|
const pinnableStatus = ['public', 'unlisted', 'private'].includes(status.get('visibility'));
|
2021-02-11 02:05:04 +02:00
|
|
|
const mutingConversation = status.get('muted');
|
2019-11-19 22:24:16 +02:00
|
|
|
const account = status.get('account');
|
2021-02-11 02:05:04 +02:00
|
|
|
const writtenByMe = status.getIn(['account', 'id']) === me;
|
2017-05-11 01:28:10 +03:00
|
|
|
|
2016-10-09 23:19:15 +03:00
|
|
|
let menu = [];
|
2016-09-30 01:00:45 +03:00
|
|
|
|
2016-12-11 23:49:25 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.open), action: this.handleOpen });
|
2017-09-02 15:01:44 +03:00
|
|
|
|
|
|
|
if (publicStatus) {
|
2019-02-11 05:19:49 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.copy), action: this.handleCopy });
|
2017-09-02 15:01:44 +03:00
|
|
|
menu.push({ text: intl.formatMessage(messages.embed), action: this.handleEmbed });
|
|
|
|
}
|
|
|
|
|
2021-02-11 02:05:04 +02:00
|
|
|
menu.push(null);
|
|
|
|
|
2019-11-19 22:24:16 +02:00
|
|
|
menu.push({ text: intl.formatMessage(status.get('bookmarked') ? messages.removeBookmark : messages.bookmark), action: this.handleBookmarkClick });
|
2021-02-11 02:05:04 +02:00
|
|
|
|
2022-01-17 01:49:55 +02:00
|
|
|
if (writtenByMe && pinnableStatus) {
|
2021-02-11 02:05:04 +02:00
|
|
|
menu.push({ text: intl.formatMessage(status.get('pinned') ? messages.unpin : messages.pin), action: this.handlePinClick });
|
|
|
|
}
|
|
|
|
|
2017-03-01 01:53:11 +02:00
|
|
|
menu.push(null);
|
2016-12-11 23:49:25 +02:00
|
|
|
|
2021-02-11 02:05:04 +02:00
|
|
|
if (writtenByMe || withDismiss) {
|
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
2017-05-15 04:04:13 +03:00
|
|
|
menu.push({ text: intl.formatMessage(mutingConversation ? messages.unmuteConversation : messages.muteConversation), action: this.handleConversationMuteClick });
|
|
|
|
menu.push(null);
|
|
|
|
}
|
|
|
|
|
2021-02-11 02:05:04 +02:00
|
|
|
if (writtenByMe) {
|
2022-02-10 16:28:53 +02:00
|
|
|
// menu.push({ text: intl.formatMessage(messages.edit), action: this.handleEditClick });
|
2016-11-18 16:36:16 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.delete), action: this.handleDeleteClick });
|
2018-06-05 01:17:38 +03:00
|
|
|
menu.push({ text: intl.formatMessage(messages.redraft), action: this.handleRedraftClick });
|
2016-10-24 18:11:02 +03:00
|
|
|
} else {
|
2019-11-19 22:24:16 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.mention, { name: account.get('username') }), action: this.handleMentionClick });
|
2022-05-03 10:09:09 +03:00
|
|
|
menu.push({ text: intl.formatMessage(messages.direct, { name: account.get('username') }), action: this.handleDirectClick });
|
2017-03-01 01:53:11 +02:00
|
|
|
menu.push(null);
|
2019-11-19 22:24:16 +02:00
|
|
|
|
|
|
|
if (relationship && relationship.get('muting')) {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.unmute, { name: account.get('username') }), action: this.handleMuteClick });
|
|
|
|
} else {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.mute, { name: account.get('username') }), action: this.handleMuteClick });
|
|
|
|
}
|
|
|
|
|
|
|
|
if (relationship && relationship.get('blocking')) {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.unblock, { name: account.get('username') }), action: this.handleBlockClick });
|
|
|
|
} else {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.block, { name: account.get('username') }), action: this.handleBlockClick });
|
|
|
|
}
|
|
|
|
|
2022-08-25 05:27:47 +03:00
|
|
|
if (!this.props.onFilter) {
|
|
|
|
menu.push(null);
|
|
|
|
menu.push({ text: intl.formatMessage(messages.filter), action: this.handleFilterClick });
|
|
|
|
menu.push(null);
|
|
|
|
}
|
|
|
|
|
2019-11-19 22:24:16 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.report, { name: account.get('username') }), action: this.handleReport });
|
|
|
|
|
|
|
|
if (account.get('acct') !== account.get('username')) {
|
|
|
|
const domain = account.get('acct').split('@')[1];
|
|
|
|
|
|
|
|
menu.push(null);
|
|
|
|
|
|
|
|
if (relationship && relationship.get('domain_blocking')) {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.unblockDomain, { domain }), action: this.handleUnblockDomain });
|
|
|
|
} else {
|
|
|
|
menu.push({ text: intl.formatMessage(messages.blockDomain, { domain }), action: this.handleBlockDomain });
|
|
|
|
}
|
|
|
|
}
|
2019-02-11 05:19:49 +02:00
|
|
|
|
2022-07-05 03:41:40 +03:00
|
|
|
if ((this.context.identity.permissions & PERMISSION_MANAGE_USERS) === PERMISSION_MANAGE_USERS) {
|
2019-01-04 14:10:43 +02:00
|
|
|
menu.push(null);
|
2019-11-19 22:24:16 +02:00
|
|
|
menu.push({ text: intl.formatMessage(messages.admin_account, { name: account.get('username') }), href: `/admin/accounts/${status.getIn(['account', 'id'])}` });
|
2022-10-26 14:42:29 +03:00
|
|
|
menu.push({ text: intl.formatMessage(messages.admin_status), href: `/admin/accounts/${status.getIn(['account', 'id'])}/statuses/${status.get('id')}` });
|
2019-01-04 14:10:43 +02:00
|
|
|
}
|
2016-09-30 01:00:45 +03:00
|
|
|
}
|
|
|
|
|
2020-06-25 23:44:19 +03:00
|
|
|
let replyIcon;
|
|
|
|
let replyTitle;
|
2017-04-19 15:20:04 +03:00
|
|
|
if (status.get('in_reply_to_id', null) === null) {
|
2018-12-28 04:51:32 +02:00
|
|
|
replyIcon = 'reply';
|
2017-05-11 01:28:10 +03:00
|
|
|
replyTitle = intl.formatMessage(messages.reply);
|
2017-04-19 15:20:04 +03:00
|
|
|
} else {
|
2018-12-28 04:51:32 +02:00
|
|
|
replyIcon = 'reply-all';
|
2017-05-11 01:28:10 +03:00
|
|
|
replyTitle = intl.formatMessage(messages.replyAll);
|
2017-04-19 15:20:04 +03:00
|
|
|
}
|
2017-04-15 03:57:26 +03:00
|
|
|
|
2020-06-25 23:44:19 +03:00
|
|
|
const reblogPrivate = status.getIn(['account', 'id']) === me && status.get('visibility') === 'private';
|
|
|
|
|
|
|
|
let reblogTitle = '';
|
|
|
|
if (status.get('reblogged')) {
|
|
|
|
reblogTitle = intl.formatMessage(messages.cancel_reblog_private);
|
|
|
|
} else if (publicStatus) {
|
|
|
|
reblogTitle = intl.formatMessage(messages.reblog);
|
|
|
|
} else if (reblogPrivate) {
|
|
|
|
reblogTitle = intl.formatMessage(messages.reblog_private);
|
|
|
|
} else {
|
|
|
|
reblogTitle = intl.formatMessage(messages.cannot_reblog);
|
|
|
|
}
|
|
|
|
|
2020-02-07 14:21:25 +02:00
|
|
|
const shareButton = ('share' in navigator) && publicStatus && (
|
2022-10-25 20:02:21 +03:00
|
|
|
<IconButton className='status__action-bar__button' title={intl.formatMessage(messages.share)} icon='share-alt' onClick={this.handleShareClick} />
|
2017-07-25 21:38:39 +03:00
|
|
|
);
|
|
|
|
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
const filterButton = this.props.onFilter && (
|
2022-10-25 20:02:21 +03:00
|
|
|
<IconButton className='status__action-bar__button' title={intl.formatMessage(messages.hide)} icon='eye' onClick={this.handleHideClick} />
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
);
|
|
|
|
|
2016-09-30 01:00:45 +03:00
|
|
|
return (
|
2017-04-23 05:26:55 +03:00
|
|
|
<div className='status__action-bar'>
|
2022-10-25 20:02:21 +03:00
|
|
|
<IconButton className='status__action-bar__button' title={replyTitle} icon={status.get('in_reply_to_account_id') === status.getIn(['account', 'id']) ? 'reply' : replyIcon} onClick={this.handleReplyClick} counter={status.get('replies_count')} obfuscateCount />
|
|
|
|
<IconButton className={classNames('status__action-bar__button', { reblogPrivate })} disabled={!publicStatus && !reblogPrivate} active={status.get('reblogged')} pressed={status.get('reblogged')} title={reblogTitle} icon='retweet' onClick={this.handleReblogClick} counter={withCounters ? status.get('reblogs_count') : undefined} />
|
|
|
|
<IconButton className='status__action-bar__button star-icon' animate active={status.get('favourited')} pressed={status.get('favourited')} title={intl.formatMessage(messages.favourite)} icon='star' onClick={this.handleFavouriteClick} counter={withCounters ? status.get('favourites_count') : undefined} />
|
|
|
|
<IconButton className='status__action-bar__button bookmark-icon' disabled={!signedIn} active={status.get('bookmarked')} title={intl.formatMessage(messages.bookmark)} icon='bookmark' onClick={this.handleBookmarkClick} />
|
2020-09-28 14:29:43 +03:00
|
|
|
|
2017-07-25 21:38:39 +03:00
|
|
|
{shareButton}
|
2016-09-30 01:00:45 +03:00
|
|
|
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
{filterButton}
|
|
|
|
|
2022-10-25 20:02:21 +03:00
|
|
|
<div className='status__action-bar__dropdown'>
|
2020-07-09 16:09:19 +03:00
|
|
|
<DropdownMenuContainer
|
|
|
|
scrollKey={scrollKey}
|
|
|
|
disabled={anonymousAccess}
|
|
|
|
status={status}
|
|
|
|
items={menu}
|
|
|
|
icon='ellipsis-h'
|
|
|
|
size={18}
|
|
|
|
direction='right'
|
|
|
|
title={intl.formatMessage(messages.more)}
|
|
|
|
/>
|
2016-09-30 01:00:45 +03:00
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2017-04-21 21:05:35 +03:00
|
|
|
}
|