Skip to content
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

Open
HenrickTheBull opened this issue Mar 24, 2024 · 3 comments
Labels
feature New feature or request idea Idea / Suggestion / Request self-hosting Important for folks running independent Ozone instances

Comments

@HenrickTheBull
Copy link

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.

@aendra-rininsland
Copy link

I would love this feature. 👍

@bnewbold bnewbold added the feature New feature or request label Mar 26, 2024
@bnewbold
Copy link
Collaborator

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.

@HenrickTheBull
Copy link
Author

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.

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.

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.

I would personally say, from the instance service account. Purely for the safety of the individual.

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.

Yeah that's what I think a few of us are doing right now. I know I am.

@bnewbold bnewbold added self-hosting Important for folks running independent Ozone instances idea Idea / Suggestion / Request labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request idea Idea / Suggestion / Request self-hosting Important for folks running independent Ozone instances
Projects
None yet
Development

No branches or pull requests

3 participants