Open snarfed opened 4 months ago
I think it would be good to (eventually) also run your own mod service, to allow users from Bsky to send low-latency freeform reports to fedi admins.
Having this attached on the opt-in account on the Bsky side, if any, could be a good way to surface this option automatically to opted-in users. You'd also always have a real bridged account to use as originator of the report in AP, that way.
Hmm! In general, I'm not looking to actively moderate posts that flow through the bridge. More background: https://fed.brid.gy/docs#moderation-policy . TLDR: Every user of the bridge will already have a home instance/PDS that's responsible for and (generally) resourced for moderating them already. The most useful impact I can have is supporting and empowering them, vs duplicating their efforts (and poorly at that).
Fortunately, if I just want to send and consume Bluesky reports/labels, I don't need to run a mod service. I've already implemented translating AP Flag
s into Bluesky reports; this just tracks the other direction.
I think you misunderstood my comment. What I mean is running a "mod service" only as inbox, to forward them with the original report message towards the home instance, and without judging reports yourself.
On fedi, it's normal that users can send reports to remote instances without waiting on a moderation decision from their own moderation team. If you only look at labels, then Bsky users wouldn't have this option, and also couldn't send Flag
s for something that Bsky doesn't moderate for specifically.
(As an example, it's not actually possible to report copyright violations through Bsky's moderation system, they require a takedown notice using one's legal name instead. Most fedi instances are much more strict about this and will ban serial art reposting accounts after receiving "normal" reports.)
Ah! Got it, thanks.
That's definitely possible. The catch is that Bluesky users would need to explicitly find and subscribe to Bridgy Fed's mod service before they could report anything to it. Those wouldn't be people already aware of and using the bridge; they'd be other people, who likely have never heard of the bridge. Opt in rates for anything are famously low, so even with a big PR push, I'd be lucky to expect more than a single digit percentage of Bluesky users to do that.
Given that, and given the effort of running even a purely technical mod service, I'm reluctant.
When a Bluesky user reports a bridged user or one of their posts, the Bluesky user sends the report through their PDS to the mod service, so we won't see it. However, if we subscribe to those mod service(s), we'll be able to look for labels of bridged users.
This will take nontrivial work, more than eg receiving and bridging AP
Flag
activities. We should still do it eventually though!Background: