Because the alternatives are Bash and Perl.
And because Python is awesome for writing scripts. (I'd never use it for anything else, though.)
Because the alternatives are Bash and Perl.
And because Python is awesome for writing scripts. (I'd never use it for anything else, though.)
Ooooo this puts them a cut-above most open source projects! They read the bugs before ignoring them for years at a time!
Your definition of "above" is disturbing. They pretend to care and then leave you waiting for years. That's way more cruel than closing bugs as WONTFIX or just ignoring their existence.
Okay, I was wrong. They actually read the bug tracker and assign people to those bugs, they just don't fix them.
I don't know, but they seem to have stopped reading the Linux bug tracker as well a long while ago. Several annoying and easy-to-fix bugs have been open for a long, long time.
I'm sure this code works just fine on Linux.
I can't test that right now since I have only one monitor, but I can assure you that the Linux client is buggy as hell as well. Just look at the number of open issues.
Couldn't really say. It would mean the user is telling Discourse to make that copy for him/her, but since Discourse is providing the button, it could also mean that Dsicourse is actively aiding the user making that copyright infringement. I think Napster was sued for exactly that, so no, I wouldn't think such a button would be a solution.
IANAL, but I think it would be legal if you tell the user that he needs to hold the right to upload the image (footnote, link to FAQ, etc.). That way, it becomes the user's responsibility to check whether the upload infringes someone else's copyright.