wikimedia/mediawiki-extensions-Echo
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/Echo synced 2024-11-27 17:20:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Echo/i18n/api/en.json

94 lines
8.8 KiB
JSON
Raw Normal View History

Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
{
"@metadata": {
"authors": [
"Brad Jorsch",
"Matthew Flaschen",
"Matthias Mullie",
"Moriel Schottlender",
"Roan Kattouw",
"Stephane Bisson"
]
},
Add API module for sending notifications Allows users to send notifications to themselves (T306211). For sending notifications to others, a new permission is created (echo-create), assigned only to bots by default. For now, only one user can be notified in one API request. If the email flag is set in the API params, the notification is also sent as an email, provided the user hasn't disabled email notifications for the "api-triggered" category. This feature is behind a feature flag. Set $wgEchoEnableApiEvents = true to use. Adapted from If0267a38be7d454e3d284d30f93c93a828288dd7. Co-authored-by: TheresNoTime <starling-ctr@wikimedia.org> Bug: T58362 Bug: T306211 Change-Id: I94642bff5dcb075cb9db862206d59c19edad9fd1
2023-06-07 20:18:51 +00:00
"apihelp-echocreateevent-description": "Manually trigger a notification to a user",
"apihelp-echocreateevent-summary": "Manually trigger a notification to a user",
"apihelp-echocreateevent-example": "Send a notification",
"apihelp-echocreateevent-param-user": "User to send the notification to",
"apihelp-echocreateevent-param-header": "Header content of the notification",
"apihelp-echocreateevent-param-content": "Body content of the notification",
"apihelp-echocreateevent-param-page": "Page to link to in the notification",
"apihelp-echocreateevent-param-section": "Section where notification would be delivered",
"apihelp-echocreateevent-param-email": "Whether to send an email as well",
API: Split description messages into summary + additional text See MediaWiki core patch I778bab2b Change-Id: I7b246e8998f918b15923cd17b941c2cc9d0a30a0
2017-05-26 19:36:35 +00:00
"apihelp-echomarkread-summary": "Mark notifications as read for the current user.",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apihelp-echomarkread-param-list": "A list of notification IDs to mark as read.",
"apihelp-echomarkread-param-unreadlist": "A list of notification IDs to mark as unread.",
"apihelp-echomarkread-param-all": "If set, marks all of a user's notifications as read.",
"apihelp-echomarkread-param-sections": "A list of sections to mark as read.",
Set apihelp message for wikis parameter of echomarkread It is set by a trait, but each module using the trait defines its own message for it, so adding a new one for this module Bug: T238520 Change-Id: Id247a40296960f3c95d3fc95bd046113e07dc0ff
2019-11-18 19:09:15 +00:00
"apihelp-echomarkread-param-wikis": "List of wikis to mark notification as read (defaults to only current wiki).",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apihelp-echomarkread-example-1": "Mark notification 8 as read",
"apihelp-echomarkread-example-2": "Mark all notifications as read",
"apihelp-echomarkread-example-3": "Mark notification 1 as unread",
API: Split description messages into summary + additional text See MediaWiki core patch I778bab2b Change-Id: I7b246e8998f918b15923cd17b941c2cc9d0a30a0
2017-05-26 19:36:35 +00:00
"apihelp-echomarkseen-summary": "Mark notifications as seen for the current user.",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apihelp-echomarkseen-example-1": "Mark notifications of all types as seen",
"apihelp-echomarkseen-param-type": "Type of notifications to mark as seen: 'alert', 'message' or 'all'.",
Remove double spaces from messages Change-Id: I8f8b9e729296ed87315048e4113ab9773c1415cf
2021-08-26 14:50:53 +00:00
"apihelp-echomarkseen-param-timestampFormat": "Timestamp format to use for output, 'ISO_8601' or 'MW'. 'MW' is deprecated here, so all clients should switch to 'ISO_8601'. This parameter will be removed, and 'ISO_8601' will become the only output format.",
Add dynamic secondary action to mute/unmute page-linked notifications Also adds an API module for muting and unmuting pages (and users). Bug: T46787 Bug: T115264 Change-Id: Icf4e4bfa9fd7fa27b4c40892e3d5ce000eb22d5a
2020-04-28 03:39:40 +00:00
"apihelp-echomute-summary": "Mute or unmute notifications from certain users or pages.",
"apihelp-echomute-param-type": "Which mute list to add to or remove from",
"apihelp-echomute-param-mute": "Pages or users to add to the mute list",
"apihelp-echomute-param-unmute": "Pages or users to remove from the mute list",
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62
2020-05-15 17:19:03 +00:00
"apihelp-echopushsubscriptions-summary": "Manage push subscriptions for the current user.",
"apihelp-echopushsubscriptions-param-command": "Action to perform.",
"apihelp-echopushsubscriptions+create-summary": "Register push subscriptions for the current user.",
"apihelp-echopushsubscriptions+create-param-provider": "The push service provider for which to register a token.",
"apihelp-echopushsubscriptions+create-param-providertoken": "The token to register.",
push: document description of topic parameter Bug: T285573 Change-Id: I875681ca3bdfe006d68b15f3cffc0089c9677ef1
2021-07-01 14:08:46 +00:00
"apihelp-echopushsubscriptions+create-param-topic": "The APNS topic (app bundle ID) to send the notification to.",
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62
2020-05-15 17:19:03 +00:00
"apihelp-echopushsubscriptions+create-example": "Register a push subscription for the current user.",
Fix grammar in push notification delete api string Follow-up from Ia6c17588ee94e6be74e5e3a75eb33e38f172fc93. Change-Id: I7ae5a4fb9dad7dc89b0d0a7292c5f87aec225698
2020-08-24 17:33:20 +00:00
"apihelp-echopushsubscriptions+delete-summary": "Unregister push subscriptions for the current user or another specified user.",
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62
2020-05-15 17:19:03 +00:00
"apihelp-echopushsubscriptions+delete-param-providertoken": "The token associated with the push subscription to unregister.",
Create push subscription manager group/right to clean up dead subs Creates a new push-subscription-manager group and an associated right, manage-all-push-subscriptions. The purpose of this is to allow privileged accounts to purge expired subscriptions from the database on behalf of other users. A user with this right will be permitted to delete any subscription from the DB based on the token alone. For all other users, deletion requests will be limited to those associated with the requesting user's central ID. This right will be granted to a bot account on Metawiki associated with the Wikimedia push notifications service, and the push notifications service account will make push subscription delete requests to the API for subscriptions for which vendor APIs return bad subscription responses. Additionally, the providertoken parameter to ApiPushSubscriptionDelete is updated to allow multiple providertoken values. Bug: T259148 Change-Id: Ia6c17588ee94e6be74e5e3a75eb33e38f172fc93
2020-08-11 20:34:21 +00:00
"apihelp-echopushsubscriptions+delete-param-centraluserid": "The central user ID associated with the subscription to unregister.",
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62
2020-05-15 17:19:03 +00:00
"apihelp-echopushsubscriptions+delete-example": "Unregister a push subscription for the current user.",
API: Split description messages into summary + additional text See MediaWiki core patch I778bab2b Change-Id: I7b246e8998f918b15923cd17b941c2cc9d0a30a0
2017-05-26 19:36:35 +00:00
"apihelp-query+notifications-summary": "Get notifications waiting for the current user.",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apihelp-query+notifications-param-prop": "Details to request.",
"apihelp-query+notifications-param-sections": "The notification sections to query (i.e. some combination of 'alert' and 'message').",
"apihelp-query+notifications-param-groupbysection": "Whether to group the result by section. Each section is fetched separately if set.",
"apihelp-query+notifications-param-filter": "Filter notifications returned.",
"apihelp-query+notifications-param-format": "If specified, notifications will be returned formatted this way.",
"apihelp-query+notifications-paramvalue-format-model": "Raw notification data",
"apihelp-query+notifications-paramvalue-format-special": "Formatted for Special:Notifications page (and only that!) Do not rely on the HTML as it may change at any given time.",
"apihelp-query+notifications-paramvalue-format-flyout": "<span class=\"apihelp-deprecated\">Deprecated</span>. Use <kbd>$1format=model</kbd> for raw data",
"apihelp-query+notifications-paramvalue-format-html": "<span class=\"apihelp-deprecated\">Deprecated</span>. Use <kbd>$1format=model</kbd> for raw data",
"apihelp-query+notifications-param-limit": "The maximum number of notifications to return.",
"apihelp-query+notifications-param-wikis": "List of wikis to fetch notifications from (defaults to only current wiki).",
"apihelp-query+notifications-param-crosswikisummary": "True to opt in to a summary notification of notifications on foreign wikis.",
"apihelp-query+notifications-param-alertcontinue": "When more alert results are available, use this to continue.",
"apihelp-query+notifications-param-unreadfirst": "Whether to show unread notifications first (only used if groupbysection is not set).",
"apihelp-query+notifications-param-alertunreadfirst": "Whether to show unread message notifications first (only used if groupbysection is set).",
"apihelp-query+notifications-param-messagecontinue": "When more message results are available, use this to continue.",
"apihelp-query+notifications-param-messageunreadfirst": "Whether to show unread alert notifications first (only used if groupbysection is set).",
"apihelp-query+notifications-param-titles": "Only return notifications for these pages. To get notifications not associated with any page, use [] as a title.",
"apihelp-query+notifications-param-bundle": "Whether to show bundle compatible unread notifications according to notification types bundling rules.",
Add notifiertypes parameter to ApiEchoNotifications Previously, ApiEchoNotifications returned only events which were enabled for the `web` notifier type. With this change, the notifier type or types to consider can be specified by argument to the new `notifiertypes` parameter. This change is required so that the apps can request notification content from the API for push notifications. Bug: T287909 Change-Id: I2d1155e113f2defb0f02416a7a659c3ee162d3a6
2021-08-13 15:53:55 +00:00
"apihelp-query+notifications-param-notifiertypes": "Notifier types for which to return notifications.",
"apihelp-query+notifications-example-1": "List web notifications",
"apihelp-query+notifications-example-2": "List web notifications, grouped by section, with counts",
"apihelp-query+notifications-example-3": "List email notifications",
API: Split description messages into summary + additional text See MediaWiki core patch I778bab2b Change-Id: I7b246e8998f918b15923cd17b941c2cc9d0a30a0
2017-05-26 19:36:35 +00:00
"apihelp-query+unreadnotificationpages-summary": "Get pages for which there are unread notifications for the current user.",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apihelp-query+unreadnotificationpages-param-grouppages": "Group talk pages together with their subject page, and group notifications not associated with a page together with the current user's user page.",
"apihelp-query+unreadnotificationpages-param-limit": "The maximum number of pages to return.",
"apihelp-query+unreadnotificationpages-param-wikis": "List of wikis to fetch pages with unread notifications from (defaults to only current wiki).",
"apihelp-query+unreadnotificationpages-example-1": "List pages with (their amount of) unread notifications",
New Article Reminder API This will be used to submit a new article reminder, for a specified date. The delay is not implemented yet. Bug: T166973 Bug: T167450 Change-Id: I773bbe98e781957912350c481c850b3263cb1821
2017-06-08 16:38:06 +00:00
"apihelp-echoarticlereminder-summary": "Request a future reminder about the specified article",
"apihelp-echoarticlereminder-param-pageid": "ID of article to remind the user about",
"apihelp-echoarticlereminder-param-title": "Title of article to remind the user about",
"apihelp-echoarticlereminder-param-timestamp": "On which timestamp to remind the user",
"apihelp-echoarticlereminder-param-comment": "Optional user comment to include in the reminder",
build: Updating dependencies composer: * mediawiki/mediawiki-codesniffer: 34.0.0 → 35.0.0 The following sniffs are failing and were disabled: * MediaWiki.Commenting.FunctionComment.WrongStyle * mediawiki/minus-x: 1.1.0 → 1.1.1 npm: * eslint-config-wikimedia: 0.17.0 → 0.18.1 The following rules are failing and were disabled: * compat/compat Additional changes: * Added the "composer phan" command to conveniently run phan. Change-Id: Icc5ae88b205d4b122efef7aef2826eb334b27820
2021-01-29 08:26:08 +00:00
"apihelp-echoarticlereminder-example-1": "Create an article reminder notification for tomorrow with comment",
"apihelp-echoarticlereminder-example-2": "Create an article reminder notification for tomorrow without comment",
Remove double spaces from messages Change-Id: I8f8b9e729296ed87315048e4113ab9773c1415cf
2021-08-26 14:50:53 +00:00
"apiwarn-echo-deprecation-timestampformat": "The MW timestamp output format is deprecated here. In the future, ISO 8601 will always be used for the output timestamp format. Adjust your client and set <var>timestampFormat</var> to <kbd>ISO_8601</kbd>.",
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
"apiwarn-echo-deprecation-flyout": "<kbd>notformat=flyout</kbd> has been deprecated and will be removed soon. Use <kbd>notformat=model</kbd> to get the raw data or <kbd>notformat=special</kbd> for pre-rendered HTML.",
New Article Reminder API This will be used to submit a new article reminder, for a specified date. The delay is not implemented yet. Bug: T166973 Bug: T167450 Change-Id: I773bbe98e781957912350c481c850b3263cb1821
2017-06-08 16:38:06 +00:00
"apiwarn-echo-deprecation-html": "<kbd>notformat=html</kbd> has been deprecated and will be removed soon. Use <kbd>notformat=special</kbd> instead.",
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62
2020-05-15 17:19:03 +00:00
"apierror-echo-event-creation-failed": "Could not create Echo event",
"apierror-echo-push-token-exists": "The provided token already exists in the database.",
Create and enforce a config setting for max subscriptions per user Creates a EchoPushMaxSubscriptionsPerUser config setting (default: 0) that controls the maximum number of subscriptions a user may associate with the user's central user ID. The setting is enforced in EchoPush\SubscriptionManager::create(). To allow creating push subscriptions for development, set $wgEchoPushMaxSubscriptionsPerUser to a positive integer value in LocalSettings.php: $wgEchoPushMaxSubscriptionsPerUser = 10; Bug: T259150 Change-Id: Ib97b6b6cbb8161dd75dad92c54b4fe4fff80c421
2020-08-12 21:33:06 +00:00
"apierror-echo-push-token-not-found": "The provided token was not found in the database.",
push: send apns topic when present 1) send apns topic when present in subscription metadata 2) check if subscription metadata is a valid JSON string 3) make epp_id column at echo_push_provider table auto_increment, otherwise it will fail when trying to add a second row in the table Bug: T259394 Change-Id: I785435e9f2d4ba9c14977d431d271f0fa2d0c795
2020-08-03 18:27:47 +00:00
"apierror-echo-push-too-many-subscriptions": "The current user has already registered the maximum allowed number of push subscriptions ($1).",
"apierror-echo-push-topic-required": "The topic field is required for this provider."
Split API messages to a separate file There are many API messages in Echo, so to make it easier for translators, they are now in a separate group. This is similar in Flow. Must be merged along with the translatewiki change at Iecedfe4cb9dc8e62a446a3e1c415a79e116ca27e Change-Id: I1d3baea708107a7f15bf19671f7386eaf7e33a1b
2016-12-07 10:02:11 +00:00
}
Reference in a new issue Copy permalink