Live data from Hacker News

John De Goes indefinitely barred from participating in Typelevel projects

gist.github.com

11–19 of 19 posts

Re: John De Goes indefinitely barred from participating in Typelevel projects

#11

How was this whole thing written without using the verb "sealioning"? https://en.wikipedia.org/wiki/Sealioning

Because sealioning implies malicious intent, i.e., that the guilty party's main intention in engaging in this behavior is to cause strife.

John is certainly engaging in similar behavior, but it does seem like his main problem is that he's overly dramatic and full of himself.

Re: John De Goes indefinitely barred from participating in Typelevel projects

#12
post #4
post #2

So, I have just read the post. And I don't want to be that guy, but why is this on the FP? edit : I will rephrase : why is this interesting?

More generally, why would something that starts “We are contacting you privately “ be posted here?

That might be why it has been taken down already...

Re: John De Goes indefinitely barred from participating in Typelevel projects

#14
post #2

So, I have just read the post. And I don't want to be that guy, but why is this on the FP? edit : I will rephrase : why is this interesting?

> why is this interesting?

Many people here participate in open source development. The evolution of social trends of such development communities is important to members.

There has been discussion here about codes of conduct and what is acceptable behaviour. This case is significant in that the subject is being banned for the intensity of their academic argument and debate, rather than intolerant or plainly offensive behaviour.

Re: John De Goes indefinitely barred from participating in Typelevel projects

#18
post #4
post #2

So, I have just read the post. And I don't want to be that guy, but why is this on the FP? edit : I will rephrase : why is this interesting?

More generally, why would something that starts “We are contacting you privately “ be posted here?

Agreed. The archive appears to show it was meant to be a private/secret GitHub gist; which isn't really protected, because any user with the URL can view the content.

Wasn't meant for public dissemination most likely.

Post reply on HN