| Age | Commit message (Collapse) | Author | 
 | 
From the endpoints left to do, I believe these should be under :statuses_read.
These should be the last for that privilege for this MR
 | 
 | 
One of the things we do during the tests is change the config. But that's global state and different tests were interfering.
E.g. one test would set `clear_config([:instance, :admin_privileges], [:statuses_read])`, but while that runs, another test may
do `clear_config([:instance, :admin_privileges], [:user_invite])`. Now the code for the first test checks the setting, and it
finds `:user_invite` instead of `:statuses_read`.
Now the modules where this happens are marked to run synchronously, so they don't interfere with each other.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Everything that was done through this setting, can now be set by giving the proper privileges to the roles.
 | 
 | 
This was the last in :require_privileged_staff. I'll remove that in the next commit
 | 
 | 
I only moved the ones from the :require_privileged_staff block for now
 | 
 | 
 | 
 | 
 | 
 | 
Instruct users to run 'git pull' as the pleroma user
See merge request pleroma/pleroma!3667
 | 
 | 
StealEmojiPolicy: fix String rejected_shortcodes
See merge request pleroma/pleroma!3673
 | 
 | 
* rejected_shortcodes is defined as a list of strings in the
  configuration description. As such, database-based configuration was
  led to handle those settings as strings, and not as the actually
  expected type, Regex.
* This caused each message passing through this MRF, if a rejected
  shortcode was set and the emoji did not exist already on the instance,
  to fail federating, as an exception was raised, swiftly caught and
  mostly silenced.
* This commit fixes the issue by introducing new behavior: strings are
  now handled as perfect matches for an emoji shortcode (meaning that if
  the emoji-to-be-pulled's shortcode is in the blacklist, it will be
  rejected), while still supporting Regex types as before.
 | 
 | 
 | 
 | 
Also use actor_type to determine if an account is a bot in antiFollowbotPolicy
Closes #2561
See merge request pleroma/pleroma!3498
 | 
 | 
 | 
 | 
Merge back 2.4.3
See merge request pleroma/pleroma!3663
 | 
 | 
 | 
 | 
Ref: fix-local-public
 | 
 | 
Ref: fix-local-public
 | 
 | 
 | 
 | 
Fix incorrect fallback when English is set to first language
See merge request pleroma/pleroma!3656
 | 
 | 
 | 
 | 
Fix eratic test for POST /api/pleroma/admin/reports/:id/notes
See merge request pleroma/pleroma!3653
 | 
 | 
It retrieved two ReportNotes and then checked one of them. But the order isn't guaranteed, while the test tested on the content of the first ReportNote.
I made the test on the content more generic
 | 
 | 
Translate backend-rendered pages
See merge request pleroma/pleroma!3634
 | 
 | 
Update Caddyfile to Caddy v2
Closes #2764
See merge request pleroma/pleroma!3641
 | 
 | 
Delete report notifs when demoting from superuser
Closes #2840
See merge request pleroma/pleroma!3642
 | 
 | 
mix: Check `.git` presence
See merge request pleroma/pleroma!3638
 | 
 | 
Use patern matching to see if someone was superuser before
 | 
 | 
Fix test get_user_apps/1
See merge request pleroma/pleroma!3636
 | 
 | 
Copyright bump for 2022
See merge request pleroma/pleroma!3593
 | 
 | 
 | 
 | 
When someone isn't a superuser any more, they shouldn't see the reporsts any more either.
Here we delete the report notifications from a user when that user gets updated from being a superuser to a non-superuser.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
elixir gettext current does not fully support fallback to another language [0].
But it might in the future. We adapt it so that all languages in Accept-Language
headers are received by Pleroma.Web.Gettext. User.languages is now a comma-separated
list.
[0]: https://github.com/elixir-gettext/gettext/issues/303
 | 
 | 
 | 
 | 
 | 
 | 
For an example, here, zh is not supported, but zh_Hans and zh_Hant
are. If the user asks for zh, we should choose a variant for them
instead of fallbacking to default.
Some browsers (e.g. Firefox) does not allow users to customize
their language codes. For example, there is no zh-Hans, but only
zh, zh-CN, zh-TW, zh-HK, etc. This provides a workaround for
those users suffering from bad design decisions.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 |