Age | Commit message (Collapse) | Author |
|
This should eventually replace Pleroma.User.superuser?/1
|
|
Fixed the warning
[warning] Please change `clear_config([section], key: value)` to `clear_config([section, key], value)`
|
|
I still had three endpoints I didn't really know what to do with them. I added them under separate tags
* :instance_delete
* :moderation_log_read
* :stats_read
I also checked and these are the last changes done by MR https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3480/diffs this is trying to fix
|
|
|
|
It also allows to update a message, so it's not just deleting. I need a better name...
|
|
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
|
|
|
|
|
|
* 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
|
|
|
|
Ref: fix-local-public
|
|
Ref: fix-local-public
|
|
|
|
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
|
|
Delete report notifs when demoting from superuser
Closes #2840
See merge request pleroma/pleroma!3642
|
|
Fix test get_user_apps/1
See merge request pleroma/pleroma!3636
|
|
|
|
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.
|
|
|
|
|
|
|
|
Revert notice compatibility routes merge request
See merge request pleroma/pleroma!3576
|
|
|
|
For some reason I had a test who suddenly failed, mix test test/pleroma/web/o_auth/app_test.exs:54. A user has a list of applications and this test adds them and then sees if the list it gets back is the same as the apps it added.
When I ran mix test a day before I didn't have this problem and when I pushed code today in a different MR, the pipeline succeeded (see https://git.pleroma.social/ilja/pleroma/-/jobs/205827), yet locally it failed. So it seems the test can sometimes succeed and sometimes fail, which makes it untrustworthy.
The failure I see is because the returned list is in reverse order. I assume that's not per sé wrong. You just want to know if the apps you added are actually there. I fixed the test by first ordering the lists before comparing.
AFAICT (and as far as that's relevant) the test got introduced in commit cb2a072e6252b7c3f6473f7cfd1af5c0ec732d7b
|
|
https://git.pleroma.social/pleroma/pleroma-meta/-/issues/60
|
|
and add a test with a unicode 14 emoji
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
|
|
Moving it to "warning" would break tests on 1.12.x
|
|
|
|
|
|
|
|
|
|
|