Yes, in my experience, this is the most likely reason that this article disappeared.
I have a hard time deciding if this is a good policy or not.
On the one hand, it does tend to mean that there are fewer flamewars showing up on the front page, and getting people sucked into endless debates that go nowhere.
On the other hand, I feel like this works to sweep under the rug real problems that occur in this community. Rather than being able to expose and deal with such problems, once things become contentious they just disappear, leaving only the things that the community has more consensus on.
PyCon staff of course will be sycophantic with upset
guests because they hate bad press.
All the PyCon staff did was talk to the developer in question, mention that the comments had offended someone, and left it there. That's pretty much exactly what I would expect them to do. That was confirmed by the developer in question:
There were plenty of overreactions in that case; Adria Richards for choosing to publicly shame rather than either talk privately with the developers in question or simply bring it to the PyCon organizers' attention, Play Haven for choosing to fire him over such a minor incident rather than simply giving him a warning, SendGrid for choosing to fire Adria rather than try to work with her to try and bring her behavior more into line with acceptable public relations, and a large number of people on the internet for going way beyond the boundaries of civil behavior in harassing people on both sides of the debate.
But among all of those over-reactions, from all accounts, the PyCon organizers behaved eminently reasonably.
I want to date your daughter, I want to take your
daughter to prom, I want to hit on your daughter etc.,
those? Those are guys being dopes and saying what guys
say. This stuff? This is so far off the radar it’s
pathetic.
It's pretty easy to read his "i have many friends that are in or former special forces....." in the same light; joking around, maybe pushing the boundaries a bit but nothing that's egregious. It's a pretty normal response from a father to someone who's being a bit too forward with his daughter.
Graphic descriptions of rape and violence against a minor are a completely different ballpark.
Should he not have made the "special forces" comment? Maybe. That's what showed people that they could get under his skin by making comments about his daughter, so some people took that and escalated quickly. But I don't think anyone would read that as any actual threat, and the people who escalated and graphically described raping his daughter are fully responsible for their own actions.
Most of these people, I'm sure, had their real name on the account, or had their account linked to from some page with their real name, so Googling for their handle would easily find it.
At that point, as he mentioned, many of these people were college athletes, so their names would also show up on rosters and various campus newspaper accounts of games.
While it is possible to harass anonymously if you try, it's pretty likely that many of these people didn't even try; they just didn't think and said the first thing that came to mind that they knew would get a rise out of Curt Schilling.
What's kind of chilling and awful is the thinking apparently at work: "I want to get a rise out of this guy, so I'll make repeated menacing/disgusting sexual remarks about his teen daughter."
There is a pretty clearly defined set of safe behaviors under the GPL. If you do not link to a program, run it in the same address space as your proprietary code, or use any internal data structures of that program, that is safe.
No one can force you to open your whole code base. They can only make you choose between opening the parts that do the unsafe things listed above (linking, running in the same address space, utilizing private data structures via some kind of shim that is supposed to work around the GPL), or they can force you to stop distributing the GPLed software.
Until then, my company is solidly in the "Absolutely no
GPL" camp.
It's so stunningly easy to use GPLed software properly, and there are thousands of companies doing it. Just don't link it to your code, or try to do some kind of hack that avoids linking it while giving you all of the same benefits of doing so.
The problem with VMware is that they have been pushing all of the boundaries; rather than just taking the easy road and doing known safe things like ensuring that there's a clear separation between GPLed code and their code, or just releasing their code that is linking to the GPLed code.
Take MediaWiki, it is GPL licensed (not AGPL), so you can modify it and run an instance of it without sharing your changes. Except, when someone accesses it, you are redistributing MediaWiki's GPL-licensed JavaScript files to their browser, so you do have to share your changes[0]. Think how many sites there are violating that without even realising.
Now think how you configure MediaWiki; you modify LocalSettings.php to (at the bare minimum) add the database username/password, and set the secret key.
This means essentially every site running a MediaWiki installation (or Wordpress, or effectively any other GPL-licensed web application) is violating the GPL, and are only getting away with it because no one has bothered to take legal action over it.
That is not a problem with MediaWiki, but that copyright on JavaScript has not been acknowledged or enforced since it was created. Site like archive.org, spiders, and scrapers are regularly copying JS, and most JS libraries I have seen lacks any copyright information whatsoever. Many media sites gives out JS snippets for users to include (for inline video, images and so on), but do not add a license permission to include (copy) the JS.
You modify LocalSettings.php which creates a derivation of MediaWiki, or as the GPL puts it, "thus forming a work based on the Program". At this point you don't have to share the changes.
However, once you distribute the JavaScript files:
"You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License [...] These requirements apply to the modified work as a whole."
By modifying LocalSettings.php you have created a derivation. By redistributing the JavaScript files you have distributed part of the work and therefore must make the whole derived work available under the GPL.
How does that help if the code we want to use is a library? A recent example was an image manipulation need. We found a great library that met all our requirements, but was GPL. Our other options were an inferior MIT-licensed library, an inferior commercial library, or spending the time to write our own.
If the thing you want to use is a DLL, how do you use it without linking to it? Writing some sort of external process and using IPC to talk to it might fulfill the letter of the license, but it's more work and less robust, and still violates the spirit of the GPL.
In the end, we picked the MIT licensed component and worked around the issues.
You either decide not to use it, using another component with a different license or writing it yourself, or you release you code under the GPL.
That's not so hard, is it?
It's just like the question you get when using proprietary software. If you don't want to pay the license fee or abide by its terms and conditions, you find an alternative or write an alternative yourself.
The obligation to release your code is just the license fee for the GPL. If that's too steep for you, look somewhere else.
I don't know of any other companies who control as many display ads on the web, which can be replaced by a "thank you for donating."
There already are other similar services, like Flattr, but it becomes hard to ensure that you get a steady revenue stream by serving ads to some people and getting donations from others, and being able to turn off the ads for those people who donate.
Google runs the largest advertising network on the web.
They already pay for much of the content you see online.
Only they have the ability to say "pay $1-$3 a month, and we'll replace those ads with a thank you", and have it actually affect a significant fraction of what you see.
No, the subscriber links are for exactly this kind of situation. They are to allow you to link to articles when it's relevant to a discussion, as long as you don't abuse them by doing something like posting a regular feed of all LWN articles or submitting every single one to Reddit/HN.
Jonathan Corbet, editor of LWN, frequently posts his own subscriber links to LWN articles:
You missed the next paragraph, in which it says that as they looked further into it, they discovered Linux kernel violations as well.
LWN has some more detailed coverage, describing the proprietary vmkernel component that gets loaded into the kernel as a kernel module, and the specific files from the kernel that are included in this: http://lwn.net/SubscriberLink/635290/d7304b50a2ef15b0/
This is much deeper than simply a binary kernel module that uses the exported interfaces; it also appears to copy wholesale large parts of kernel internals, not just access the kernel via defined interfaces.
My approach avoids recompiling the program every time you run it, and it also makes it much easier to debug crashes. At least when I was doing this, running `swift` directly produced really bad crash info when things went wrong.
I have a hard time deciding if this is a good policy or not.
On the one hand, it does tend to mean that there are fewer flamewars showing up on the front page, and getting people sucked into endless debates that go nowhere.
On the other hand, I feel like this works to sweep under the rug real problems that occur in this community. Rather than being able to expose and deal with such problems, once things become contentious they just disappear, leaving only the things that the community has more consensus on.