diff options
author | Eugen Rochko <eugen@zeonfederated.com> | 2018-05-19 14:46:47 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-05-19 14:46:47 +0200 |
commit | 4b94e9c65efd227c58f8be9b3db6b667d403ed3c (patch) | |
tree | 32c3e4f22fa78fb6d74062e192ea8cc7c59f135b /config/locales/ru.yml | |
parent | 1951ff41b33b264fd8179998648c3cbbf2834cd5 (diff) |
Improve payload format of Web Push API now that it's open (#7521)
> Good lord what is happening in there Previously the contents of the Web Push API payloads closely resembled the structure of JavaScript's [Notification](https://developer.mozilla.org/en-US/docs/Web/API/Notification). But now that the API is open to non-browser apps, and given that there is no required coupling between contents of the payload and a Notification object, here is how I changed the payload: ```json { "access_token": "...", "preferred_locale": "en", "notification_id": "12345", "notification_type": "follow", "title": "So and so followed you", "body": "This is my bio", "icon": "https://example.com/avatar.png" } ``` The title, body and icon attributes are included as a fallback so you can construct a minimal notification if you cannot perform a network request to the API to get more data.
Diffstat (limited to 'config/locales/ru.yml')
-rw-r--r-- | config/locales/ru.yml | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/config/locales/ru.yml b/config/locales/ru.yml index 2363bba12..19b844612 100644 --- a/config/locales/ru.yml +++ b/config/locales/ru.yml @@ -606,20 +606,6 @@ ru: other: Другое publishing: Публикация web: WWW - push_notifications: - favourite: - title: Ваш статус понравился %{name} - follow: - title: "%{name} теперь подписан(а) на Вас" - group: - title: "%{count} уведомлений" - mention: - action_boost: Продвинуть - action_expand: Развернуть - action_favourite: Нравится - title: Вас упомянул(а) %{name} - reblog: - title: "%{name} продвинул(а) Ваш статус" remote_follow: acct: Введите username@domain, откуда Вы хотите подписаться missing_resource: Поиск требуемого перенаправления URL для Вашего аккаунта завершился неудачей |