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

User Profile: hide profile of banned user #44

Closed
ShawnMcCool opened this issue Sep 22, 2013 · 6 comments
Closed

User Profile: hide profile of banned user #44

ShawnMcCool opened this issue Sep 22, 2013 · 6 comments
Milestone

Comments

@ShawnMcCool
Copy link

In some ways it sucks, but it probably needs to happen anyway.

@driesvints
Copy link
Member

Perhaps we can add a large red stamp that says "Banned" ;)

On 22 Sep 2013, at 21:10, Shawn McCool notifications@github.com wrote:

In some ways it sucks, but it probably needs to happen anyway.


Reply to this email directly or view it on GitHub.

@driesvints driesvints mentioned this issue Sep 22, 2013
44 tasks
@ShawnMcCool
Copy link
Author

My concern is that the user has unfortunate content (which is why they're banned) and we don't want to propagate it through Google.

@taftse
Copy link
Contributor

taftse commented Sep 23, 2013

well why not remove the questionable content but leave the profile and stick the banned stamp on it as diesvints suggested
and only remove the actual porn spammers

@ShawnMcCool
Copy link
Author

I really doubt that we'll have porn spammers as they'd have to first authenticate through GitHub.

But, I think that the suggestions from @driesvints and @taftse are appropriate. Anyone have proposals on how best to approach the concept of banning users?

My first thought is that there might be escalating time-oriented bans for behavior problems. First strike is a day, second is a week, third is a month. This prevents users from having to create a new GitHub account to get back in.

Additionally, users are probably less likely to be a pain in the ass in some small capacity due to the fact that their whole GitHub profile is publicized.

Normally, I wouldn't want to put much thought into this sort of thing until it was needed. But, due to the scale of the current laravel.io and the Laravel community. I know that this is going to come up. We're going to need a solid policy in place when it does.

@anlutro
Copy link
Contributor

anlutro commented Sep 28, 2013

Isn't it possible to send a custom Response::view with a HTTP response code that discourages google from indexing the page, but still allows normal users to browse normally?

@jasonlewis
Copy link

Just a simple ban with the ability to hide any of their posts for the duration of said ban? So, for example, a reply on a discussion would simply be replaced with a "User X has been banned."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants