Here's a rough draft of how I think I report could look in mastodon with the changes I'm working on relating to forwarding reports to other servers:
Here I've reported from my dev instance hachyderm.wtf, who replied to hachyderm.io, but I only chose to forward to hachyderm.wtf
This allows for the moderator on my dev instance to then decide to forward it to hachyderm.io (there'll be a separate screen for that)
Gives a bit more clarity as to where the report has gone.
https://github.com/mastodon/mastodon/pull/31706#issuecomment-2327497442
Also, that's not a mockup as such, that's actually legit a report on my local development server to test with.
(it was harder than you might imagine to setup this scenario to test)
The idea is that rather than just tracking a boolean "was the report forwarded” (which currently means “was the report forwarded to the target account's server”), we track all the domains forwarded to, and who did the last forwarding, and when.
If there's just one domain to potentially forward to, it'll only show one item in that list, which would either be checked or not — I'm not sure on the best visual design for this, hence just using disabled checkbox inputs for now.
Arguably I could go to an extreme here and create an entire report_forwards table, such that each forwarding is independently tracked and who / when that happened; but I think this information will end up in the audit log somehow (not sure how yet)
A little update on this, this is how I imagine it'd appear in the reports list when a report has been forwarded to multiple domains.
(this totally conflicts with my redesign of this screen, but oh well)
@thisismissem Would general feedback on the UI be helpful?
@thisismissem @5ciFiGirl is there anyway we can help? Code, funding, coffee???
@Ric @5ciFiGirl you can always financially support my work at: https://support.thisismissem.social
It was an increase in funding that actually allow me to work on this and many other changes over the past month: https://github.com/mastodon/mastodon/pulls/ThisIsMissEm
If you'd like to contribute code & know ruby on rails, there are a few issues that I could help guide a bit on.
@thisismissem My Ruby is way to rusty to be of use, but I've donated to help fund improvements in the moderation tools, it's something very important to a community like this!
@Ric ah, okay! Thanks for your donation!
And yeah, improving the moderation tools and making sure they're understandable is an ongoing project — a lot of things you'll hear about for Trust & Safety also require protocol changes, which makes them slower and more complex to implement.
I am hopeful starting a taskforce to try to coordinate some of the protocol issues that hinder advancing software level features.
@thisismissem Huh. I wonder if GDPR requires that the (anonymised) content of reports about an account be made available to the account owner.
@nikclayton
If you've decided you get to store reports against them for future reference, isn't that exactly what this regulation is for?
ICO not giving an obvious way out here:
https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/online-safety-and-data-protection/content-moderation-and-data-protection/?template=pdf&patch=67#access