[feat] MRF based on part of user name #774

New issue

Open

opened 2024-05-09 11:42:09 +00:00 by snan · 0 comments

snan commented

2024-05-09 11:42:09 +00:00

Contributor

The idea

Bridged Bluesky accounts appear in the fediverse as @[handle]@bsky.brid.gy. For example, @snarfed.bsky.social on Bluesky is bridged into the fediverse as @snarfed.bsky.social@bsky.brid.gy.

That means that to moderate Bluesky, one way to handle that is to block the entire bridge, but a more fine-grained approach could be to use an MRF that could block just some users depending on what Bluesky instance they're using.

I dunno, maybe that's not feasible; AT proto seems to be sliced a li'l differently than Fediverse and maybe they won't end up having the same grouping of instances divided up based on moderation policies that we've got over in ActivityPub land. But just an idea 🤷🏻‍♀️

The reasoning

No response

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the Akkoma backend specifically, and not pleroma-fe.

### The idea > Bridged Bluesky accounts appear in the fediverse as @[handle]@bsky.brid.gy. For example, @snarfed.bsky.social on Bluesky is bridged into the fediverse as @snarfed.bsky.social@bsky.brid.gy. That means that to moderate Bluesky, one way to handle that is to block the entire bridge, but a more fine-grained approach could be to use an MRF that could block just some users depending on what Bluesky instance they're using. I dunno, maybe that's not feasible; AT proto seems to be sliced a li'l differently than Fediverse and maybe they won't end up having the same grouping of instances divided up based on moderation policies that we've got over in ActivityPub land. But just an idea 🤷🏻‍♀️ ### The reasoning _No response_ ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.

snan added the

feature request

label 2024-05-09 11:42:09 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#774

No description provided.