[bug] MRF transparency showing policies not actually enabled #622
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#622
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
Fedora 38
Version
2023.08
PostgreSQL version
15
What were you trying to do?
I currently have the following MRF policies enabled via AdminFE:
Despite this, the MRF transparency also shows the the following policies (from the about page):
I can confirm the DirectMessageDisabledPolicy is not active for instance since we still get DMs from remote instances just fine.
What did you expect to happen?
The MRF transparency only shows the policies enabled on the instance.
What actually happened?
MRF transparency shows policies that aren't actually enabled as stated above.
Logs
No response
Severity
I can manage
Have you searched for this issue?
ah now this is actually incorrect, those policies are enabled, they're built in and configurationless and they're how some functionality is implemented
see: https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/web/activity_pub/mrf.ex#L146
InlineQuotePolicy is the thing that adds the fallback "RE: link" to posts
NormalizeMarkup is a security one and ensures all content goes through scrubbers
DirectMessageDisabledPolicy checks if a user has disabled or limited direct messages before accepting
as for hashtag policy i'm genuinely not sure why it's perma-enabled, it was there from pleroma - i'll look into that one
but as for the issue itself, this is not an issue and is 100% intentional