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

Unwatched instances (comment, question, answer) #51

Open
sbabashahi opened this issue Jun 9, 2021 · 2 comments
Open

Unwatched instances (comment, question, answer) #51

sbabashahi opened this issue Jun 9, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@sbabashahi
Copy link
Member

Currently review and interview comments, company questions and answers are not under any process to check the contents.

For example:
Reviews and interviews have a field is approved, default is false, after creating and updating a message containing data about review or interview will send to telegram bot. Telegram bot will notify moderators and they will check contents and will decide to approve it or not. They check contents against the site rules.

We need a process to check contents of these instances as review and interview.

Suggested solution:
Add a boolean field named reported to these instances.
An API that from frontend instances could be reported by users.
Request data are id of instance and type of instance. Currently type of instance choices are review_comment, interview_comment, question and answer.
After reporting API called we could check if instance reported before or not by using reported field.
If it's not reported before we could send content of instance to telegram bot for moderators decision,
And we need an API like approving review and interviews from telegram to delete instance by moderators.

Any other suggestion?

@sbabashahi sbabashahi added the enhancement New feature or request label Jun 9, 2021
@MAM-SYS
Copy link
Contributor

MAM-SYS commented Jun 10, 2021

hello @sbabashahi
i hope you ok
this is an excellent feature
At first i was thinking about the report itself and i think it could be more than a boolean field. it could be design as a model
with report_type field( Abusive or Harmful ), number_of_report_times (for example more than 4 times the instance delete temporarily for final moderators decision), report_level_hierarchy( it help moderators to find more important reports sooner), description (it can be fill by user who is reporting something), etc.....
i think before the designing the API its better to think about the report it self
but the final decision is yours
hope it can help
sorry if i did not explained so good
✌️

@sbabashahi
Copy link
Member Author

Thanks for your suggestion, it could be great to have a complete app on reporting and it's related features, currently we are waiting for other suggestions. But one thing we need to have in our mind is we suffer from lack of human resources. So any work around should try to maximize the automation and minimize human related works. thanks again good call

@sbabashahi sbabashahi changed the title Unwanted instances (comment, question, answer) Unwatched instances (comment, question, answer) Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants