-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Ability to cross submit reports from one Ozone to others. #74
Comments
I would love this feature. 👍 |
Interesting idea, I don't think we'd thought of this. How would you imagine folks would configure which instances they might want to send a report to? It could be configured instance-wide, or try pull the private subscription metadata of the currently-logged in user account, though that account might be an "empty" pseudonym for security reasons. There is also the question of whether the report would be "from" the individual logged-in account, or from the ozone instance service account. The later might make more sense for inter-service communication. An alternative workflow right now would be to use the "peek" links to pop in to the app, and report from there. I agree that having a flow in Ozone itself might be nice. We have some upcoming work around sending notifications and "mail" from ozone instances to PDS admins or user accounts, might have some design overlap with this. |
My wish for this is that it would be instance wide, currently most Ozones are either single user, like mine, or a coop like Aegis. Plus it would make sense for Ozones structured like organizations with rigid procedures and rule sets.
I would personally say, from the instance service account. Purely for the safety of the individual.
Yeah that's what I think a few of us are doing right now. I know I am. |
It would be wonderful to have a feature to submit reports from our Ozone dashboard to other Ozone instances.
Like I run the Taurus Shield instance and would love to be able to submit some posts to Bluesky Moderation or to Aegis.Blue or even to Xblocker as this would help increase the total safety of the network.
The text was updated successfully, but these errors were encountered: