de68c251f8
Instrument the receipt sender executor
2022-03-11 17:20:52 -08:00
7c9ae3561d
Send delivery receipts asynchronously
2022-03-11 16:34:22 -08:00
b608ece57e
Remove `supportsAnnouncementGroups` metric
2022-03-11 16:18:00 -08:00
8dfffebaf1
Remove unnecessary check for destination UUID
2022-03-11 16:17:54 -08:00
109a3bb2b9
Update to Pushy 0.15.1
2022-03-10 11:08:53 -05:00
fef37f739b
Remove unused classes and methods
2022-03-10 11:08:38 -05:00
7a5615182a
Update to the latest version of the abusive message filter
2022-03-10 11:06:04 -05:00
02a7003ffe
Update to the latest version of the abusive message filter
2022-03-09 14:14:47 -06:00
1571f14815
Add a feature flag to disable account normalization
2022-03-09 14:03:21 -06:00
9cb098ad8a
Add a top-level uak to existing items
...
Items wirtten before we started storing the uak at
the top level only store the uak in the
account blob. The will be updated on account
crawl
2022-03-09 14:03:21 -06:00
6283f5952d
Update to the latest version of the abusive message filter
2022-03-08 10:03:38 -05:00
9b9edbae0e
Drop `DeadLetterHandler` (which is functionally unused)
2022-03-08 10:03:06 -05:00
491155d1cf
Remove `@Consumes` from GET/DELETE in `/v1/subscriptions`
2022-03-04 15:36:02 -08:00
54207254f1
Remove unused configuration
2022-03-04 11:44:17 -08:00
1395dcc0be
Make the enterprise client canonical
2022-03-04 11:44:17 -08:00
2a68d9095d
Remove transitional and legacy client
2022-03-04 11:44:17 -08:00
a984b3640e
Further refine score distribution summary
2022-03-04 11:44:17 -08:00
f9c1e411aa
Remove netty-tcnative as a dependency
2022-03-04 10:45:18 -05:00
f6cbc32ee7
Align "link device" and "fetch pre-keys" rate limits
2022-03-04 10:45:06 -05:00
602614acf6
Refine assessment metrics
2022-03-03 16:09:49 -08:00
3854b7d472
Remove `@Consumes` from `GET /v1/config`
2022-03-03 16:08:55 -08:00
5e25481088
Fix a trivial typo in a constant's name
2022-03-03 10:59:19 -05:00
fe86e15d80
Remove PNI repair code
2022-03-03 10:25:11 -05:00
179b4a69eb
Clear one-time pre-keys when PNIs are assigned
2022-03-03 10:24:54 -05:00
eee6307789
Move score floor to dynamic configuration, add distribution summary
2022-03-02 15:18:33 -08:00
9fc5002619
Add stories capability
2022-03-02 15:16:21 -08:00
faa6ae284a
Add uak as a top level attribute
2022-03-02 10:41:09 -06:00
8b4355b21d
Add a "challenge issued" counter tagged by country and platform
2022-03-02 10:40:47 -06:00
e8835da740
Tag captcha success rate counter by country
2022-03-02 10:40:47 -06:00
75854e104e
Fix typo
...
Co-authored-by: Chris Eager <79161849+eager-signal@users.noreply.github.com>
2022-03-01 14:14:52 -08:00
93d06e3f4d
Fix typos
2022-03-01 14:14:52 -08:00
c560b9229c
Update to the latest version of the abusive message filter
2022-03-01 10:43:12 -08:00
935e268dec
Parameterize sitekey
2022-03-01 10:40:42 -08:00
3a1c716c73
Remove an unused rate limiter
2022-02-25 13:50:17 -08:00
f3457502a6
Support different v2 captcha actions
2022-02-25 13:49:47 -08:00
7ded802df4
Update to the latest version of the abusive message filter
2022-02-24 17:30:02 -06:00
d3cd1d1b15
Use GetLatestConfiguration in config manager
...
Use StartConfigurationSession/GetLatestConfiguration instead of
GetConfiguration since the latter has been deprecated
2022-02-23 15:36:33 -06:00
f5a75c6319
Simplify RateLimitExceeded with no retry-duration
...
- Avoid passing negative durations in error cases
- Drop unused message
- Return a duration for a bad forwarded-for
2022-02-23 15:25:24 -06:00
ae3a5c5f5e
Return a Retry-After on rate-limited responses
...
Previously, only endpoints throwing a RetryLaterException would include
a Retry-After header in the 413 response. Now, by default, all
RateLimitExceededExceptions will be marshalled into a 413 with a
Retry-After included if possible.
2022-02-23 15:25:24 -06:00
43792e2426
Update to the latest version of the abusive message filter
2022-02-22 11:03:41 -05:00
551d639951
Update Postgres driver to 42.3.3
2022-02-18 10:41:29 -05:00
c367a71223
APNS: include a collapse-id for non-VOIP notifications
...
This has two benefits:
- The APNS server should only send an iOS client a single push
notification for any missed messages while the device is offline
(server-side coalescing). Note that the client can still turn that
into multiple "user notifications" as it pulls from its queue.
- If multiple notifications get delivered but iOS is unable to process
them (say, because the phone just restarted and hasn't been unlocked
yet), the user should only get one "You may have received messages"
notification (client-side coalescing).
2022-02-18 10:41:10 -05:00
d259ef0348
Update rate limit exceeded counter
2022-02-17 13:23:48 -08:00
288cbf4a80
Clean up null-ability of incoming message entity fields
2022-02-17 13:23:48 -08:00
ba5e5a780f
Throw an exception instead of using Optional<Resposne>
2022-02-17 13:23:48 -08:00
73fa3c3fe4
Add test for content length validation
2022-02-17 13:23:48 -08:00
579eb85175
Reject invalid envelope types
2022-02-17 13:23:48 -08:00
b2b20072ae
Add `MicrometerRegistryManager`
2022-02-17 13:18:30 -08:00
a2c4d3fe95
Use a strong reference to the application shutdown gauge
2022-02-17 13:18:30 -08:00
31e2be2e4d
Fixup invalid accept-language counter
...
- Fix name
- Add platform/version tags to the counter
2022-02-10 11:57:25 -06:00
Chris Eager