-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Reporting a toot equals NO confirmation - Redirect to getting started. #774
Comments
Perhaps we should display a "success" message but report by itself isn't intended to automatically remove something, it goes to the admin's reports overview where the admins decide what to do. Or do you mean that report should automatically invoke a block as well? |
yes, that's what I mean. I think on other platforms that's what happens. It's debateable, maybe we as an open sourced platform should do things differently, but I for one see no reason not to block at least that single toot that caused distress. |
I think an option, enabled by default maybe, to block might be nice. |
I just tested this out on 2.2.0 and there's no confirmation that the report was sent or received, and the toot I reported doesn't disappear. The way I've seen this done on other sites is like: *reported post disappears* "Thanks for your report. Would you like to block this person? y/n" |
Merge upstream changes
this can probably be closed? |
Why? |
Oh yes, fair enough! Edit: Weird that a post disappears when you report it, until you reload the page. But I think that might need to be a new bug report, if it's still going on. |
I see that the user disappears from the timeline altogether (not just his one toot that I report).
I get redirected to Getting Started.
If I refresh browser window I still see the user and the toot I reported.
The text was updated successfully, but these errors were encountered: