GitLab

Simple policy reasons for instance specific policies

See merge request !3314

Mergeback: 2.4.0

See merge request !3494

based on 51d3d8d255de221f7ac99e41f2f8e56c7d6a21a9

Ilja authored Jan 17, 2021 and Haelwenn committed Aug 06, 2021

* kePlaceholder and valuePlaceholder of quarantined_instances where in wrong case, should be snake_case
* The mrf simple and transparency exclusion were already OK

Ilja authored Dec 26, 2020 and Haelwenn committed Aug 06, 2021

* Make it use tuples
* I also changed the keys for key_placeholder and value_placeholder to use snake_case instead of camelCase

Ilja authored Dec 18, 2020 and Haelwenn committed Aug 06, 2021

* I also added for keywordpolicy as well now. It was done in the admin-fe, but is better to be done here
* I also added comments to explain why we did the _info keys (backwards compatibility)

Ilja authored Dec 14, 2020 and Haelwenn committed Aug 06, 2021

* ./configuration/mrf.md
  * Change example
* ./configuration/cheatsheet.md
  * Change descriptions to include that a reason is given
* CHANGELOG.md
  * Add as breaking change

Ilja authored Nov 28, 2020 and Haelwenn committed Aug 06, 2021

Added a new field in the nodeinfo called quarantined_instances_info
This holds an object like `"quarantined_instances_info":{"quarantined_instances":{"quar.inst":{"reason":"whatever reason"}}}}`

Ilja authored Nov 20, 2020 and Haelwenn committed Aug 06, 2021

* Only for SimplePolicy for now
* I added an extra mrf_simple_info key that has an object as value. The object contains only relevant extra info

Ilja authored Oct 23, 2020 and Haelwenn committed Aug 06, 2021

It's easiest (and imo most proper) to use tuples {"instance, "reason"} in BE,
but for FE maps like %{"instance": "instance", "reason", "reason"} are better.
I changed it so that node_info returns maps now for simple_policy and quarantined instances.

Ilja authored Oct 05, 2020 and Haelwenn committed Aug 06, 2021

* SimplePolicy
* quarentine
* transparency_exclusions

Ilja authored Oct 05, 2020 and Haelwenn committed Aug 06, 2021

When a setting was deprecated, the code would stop checking for the rest of the possible deprications. This also meant that the settings weren't rewritten to the new settings for deprecated settings besides the first one.

Ilja authored Oct 02, 2020 and Haelwenn committed Aug 06, 2021

* Give deprecation message
* Rewrite configs

Ilja authored Oct 02, 2020 and Haelwenn committed Aug 06, 2021

* This is for the settings, not yet a DB migration

Ilja authored Sep 25, 2020 and Haelwenn committed Aug 06, 2021

No test was done for quarantined instances yet. I added a factory for followers_only notes and checked
* That no followers only post is send when the target server is quarantined
* That a followers only post is send when the target server is not quarantined

Ilja authored Sep 24, 2020 and Haelwenn committed Aug 06, 2021

* Changed SimplePolicy
* I also grepped in test/ for ':mrf_simple' to see what other things could be affected

Ilja authored Sep 24, 2020 and Haelwenn committed Aug 06, 2021

When strings are detected in the simplepolicy, a warning will be given and the config will be changed to use tuples instead

Moderators: add UserIsStaffPlug

See merge request !3495

Visibility: check Tombstone objects in visible_for_user?/2

See merge request !3490

Fix errors in ErrorView

See merge request !3489

Fixes ErrorView rendering

MastodonAPI: Fix list timelines

Closes mastofe#89 and #2693

See merge request !3477

AdminAPI: sort new users at the top

Closes #2709

See merge request !3481

AdminAPI: add created_at date to users

See merge request !3482