summary refs log tree commit diff
path: root/synapse/server_notices (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Do not send consent notices if "no-consent-required" is set"Brendan Abolivier2019-08-221-4/+0
| | | | This reverts commit 27a686e53b8ba3f2e2f102fae73e598c00ec0086.
* Do not send consent notices if "no-consent-required" is setHalf-Shot2019-08-221-0/+4
|
* Replace returnValue with return (#5736)Amber Brown2019-07-232-4/+4
|
* Run Black. (#5482)Amber Brown2019-06-205-60/+39
|
* Merge branch 'develop' of github.com:matrix-org/synapse into erikj/admin_contactErik Johnston2018-08-241-4/+3
|\
| * Fix checking if service notice room is already taggedErik Johnston2018-08-241-4/+3
| | | | | | | | This manifested in synapse repeatedly setting the tag for the room
* | Change admin_uri to admin_contact in config and errorsErik Johnston2018-08-241-1/+1
|/
* Ensure we wake up /sync when we add tag to notice roomErik Johnston2018-08-242-2/+13
|
* Make content of tag an empty object rather than nullErik Johnston2018-08-242-2/+2
|
* Fix bug where we broke sync when using limit_usage_by_mauErik Johnston2018-08-241-0/+4
| | | | | We assumed that we always had service notices configured, but that is not always true
* Fix bug where we resent "limit exceeded" server noticesErik Johnston2018-08-231-1/+5
| | | | This was due to a bug where we mutated a cached event's contents
* Update notice formatErik Johnston2018-08-221-3/+11
|
* special case server_notices_mxidNeil Johnson2018-08-181-1/+1
|
* clean up, no functional changesNeil Johnson2018-08-172-41/+47
|
* flake8Neil Johnson2018-08-161-3/+2
|
* refactor for readability, and reuse caching for setting tagsNeil Johnson2018-08-162-68/+114
|
* add room taggingNeil Johnson2018-08-161-9/+5
|
* check for room state before deciding on actionNeil Johnson2018-08-162-67/+26
|
* WIP impl commiting to get feedbackNeil Johnson2018-08-161-6/+74
|
* fix case where empty string state check is evaulated as FalseNeil Johnson2018-08-161-1/+2
|
* wip cut at sending resource server noticesNeil Johnson2018-08-152-44/+55
|
* backout ability to pass in event type to server noticesNeil Johnson2018-08-143-4/+5
|
* support server notice state events for resource limitsNeil Johnson2018-08-143-8/+20
|
* fix typoNeil Johnson2018-08-131-1/+1
|
* implementation of server notices to alert on hitting resource limitsNeil Johnson2018-08-102-45/+65
|
* wip at implementing MSC 7075Neil Johnson2018-08-091-0/+84
|
* run isortAmber Brown2018-07-091-1/+2
|
* Avoid sending consent notice to guest usersRichard van der Hoff2018-05-251-0/+5
| | | | we think it makes sense not to send the notices to guest users.
* Allow overriding the server_notices user's avatarRichard van der Hoff2018-05-231-3/+14
| | | | probably should have done this in the first place, like @turt2live suggested.
* Merge pull request #3271 from matrix-org/rav/consent_uri_in_messagesRichard van der Hoff2018-05-231-2/+39
|\ | | | | Support for putting %(consent_uri)s in messages
| * Support for putting %(consent_uri)s in messagesRichard van der Hoff2018-05-231-2/+39
| | | | | | | | | | Make it possible to put the URI in the error message and the server notice that get sent by the server
* | fix typoRichard van der Hoff2018-05-231-1/+1
| |
* | Block attempts to send server notices to remote usersRichard van der Hoff2018-05-231-0/+4
|/
* fix synchrotronhera2018-05-221-1/+1
|
* Stub out ServerNoticesSender on the workersRichard van der Hoff2018-05-222-4/+50
| | | | | ... and have the sync endpoints call it directly rather than obsure indirection via PresenceHandler
* Move consent config parsing into ConsentConfigRichard van der Hoff2018-05-221-8/+2
| | | | turns out we need to reuse this, so it's better in the config class.
* Send users a server notice about consentRichard van der Hoff2018-05-222-0/+159
| | | | | When a user first syncs, we will send them a server notice asking them to consent to the privacy policy if they have not already done so.
* Better docstringsRichard van der Hoff2018-05-181-0/+16
|
* Make sure we reject attempts to invite the notices userRichard van der Hoff2018-05-181-0/+5
|
* Infrastructure for a server notices roomRichard van der Hoff2018-05-172-0/+110
Server Notices use a special room which the user can't dismiss. They are created on demand when some other bit of the code calls send_notice. (This doesn't actually do much yet becuse we don't call send_notice anywhere)