danielquinn
Israel has worked very hard to build that assumption everywhere it can, driving home that a lack of support for anything Israel does is somehow antisemitic. They use people like your wife as a shield for their crimes and a disturbing portion of her community is cheerleading their genocide.
They are doing this in her name, whether she "cares about politics" or not, so I would suggest she get out there with her community and remind the world that Israel does not speak for her.
Or just to bring the housing prices down for them to afford.
GitLab. The CI is fantastic.
Please tell me that your username is a reference to Rainbow Rangers. My 5 year old daughter would be tickled pink.
I think what he's missing is that he's approaching the question of "how do I make these people care?" from a liberal position. It just seems like such a weird question to even ask someone who cares about others by default.
If you think of it from the perspective of a self-centred conservative though, you can ask the question as "how can I frame the pain of others as their problem?"
Try talking about solutions in a way that affects them personally:
- You want transit and bike lanes 'cause nothing reduces traffic other than viable alternatives to driving. Get those other people off the road so you can drive.
- You want to stop sending weapons to Israel because we're spending your money on weapons for their war.
- You want to divest from fossil fuels because renewables have better energy security. Your costs don't go up whenever those people start a war over there.
- You want high taxes on the rich because they're festering parasites sleeping on a pile of gold and we want to spend that money on the poor so they aren't so desperate that they steal your shit.
These people do not (cannot?) care about how many children are killed by our bombs or about the fate of some bird, so constantly appealing to emotional arguments meant for liberals will never work on them.
Yeah this isn't a conversation we can have. If you're going to sit there and deny the international criminal court and somehow accept the killing of tens of thousands of children, many by sniper fire like it's comparable to bad tax policy then there's no hope for you.
This is lovely. Thanks for sharing!
So here's the thing. If someone is going to say with a straight face that they "stand with Israel", even when Israel is committing genocide in their name, then those people are effectively throwing in their lot with genociders and frankly I have little sympathy for them. Thankfully, nearly every Jew I've ever met has been very critical of Israel (including the Israeli citizens), many of which have confessed zero interest in an ethnostate, preferring a liberal democracy with no state religion. A secular state for both Jews and Muslims -- from the river to the sea if you will.
These people may well be the minority, but you'll forgive me if I won't accept the assumption that the majority of the 15 million Jews around the world support genocide. Call me a naïve optimist if you like, but I want to believe that most people are better than that.
Actually, this is one of the things that drives me crazy about Jesse's take on this. Putting aside for the moment the base selfishness that would lead someone to ask: "how does your committing genocide affect me?", he's taking Israel's position from the start that their actions are directly tied to the lives of Jews around the world. There are millions of Jews out there who are (a) not Israeli citizens, (b) are not Zionists, and (c) even actively condemn its actions purportedly in their name, but Jesse always starts with the position that Jews == Israel.
It's Israel's favourite shield: to claim that their actions are linked to Jews everywhere. They use it to smear any opposition to their war crimes as antisemitism, and lines of questioning like this only reinforce this link. You just can't bemoan how Jews are being linked to war crimes while starting from the position that Israel is inherently linked to Jewish identity. What you get is a conversation where both parties agree that Israel is both inexorably linked to Jews everywhere but that they're also not responsible for their safety because they can't be -- they're not Israelis.
To put it another way, no one would do an interview with the Iranian ambassador and suggest that they're somehow responsible for Islamophobia in Canada. That would be absurd, but because it's in Israel's interest to claim representation of all Jews everywhere, you get this ridiculous session where both parties agree on a distorted version of reality. Since journalism is supposed to be about distributing factual information, beginning an interview on such a flawed position is both illogical and irresponsible.
The former.
Responsible journalism is more than simply showing up for an interview and broadcasting whatever lie the subject wants you to share for them. If he's not going to fact-check the ambassador immediately, then he's operating as a defacto mouthpiece for his subject. Attaching a fact-checking document, after the fact, in an entirely different medium that outlines just how much of the interview was obvious propaganda is not journalism.
The worst part is that Jesse has levelled this very criticism in the past against other journalists! Specifically in reference to how Trump is covered, but others as well. You can't just hand your mic, your platform over to a 3rd party and claim that you're doing journalism when you're really being complicit in the distribution of propaganda.
So let's get the licensing bit out of the way first. I am 100% confident that you're wrong on this. The GPL is a copyright license and like all copyright licenses, it applies to the work and your rights to copy it. If you choose to copy the contents of a GPL project's code into your own project, the license dictates that you must license your project under the GPL. For example, if you were to build a new kernel for your own special operating system and copy out significant portions of the Linux kernel to do it, your new kernel will be covered by the GPL.
You may be confusing the GPL with the LGPL here, which specifically has an exemption for linking. Under that license, you can link to a GPL project (it's not clear if a Python import would qualify as this was originally written for external modules in C projects) without your project being covered by the GPL.
You're also misunderstanding "distribution" here. While it's true that there's a distinction between the GPL and AGPL in how this word is defined, it does not affect how the license applies. To use another example, the fuzzywuzzy project is GPL-licensed, so if you were to use it in your Django project, it would necessarily make your Django project GPL. However, as "distribution" under the GPL applies only to sharing copies of the project with others and not to services provided over the web, your project will be GPL, but you'll be under no obligation to share the source with anyone unless you were to copy the project onto someone's laptop. So long as your project is just a webserver sending HTML to the user, you're under no obligation to share the source code for your server.
The AGPL on the other hand includes accessing the software over a network under its definition of "distribution" and so if fuzzywuzzy were AGPL licensed, this would require you to publish your Django project's source publicly.
Source: I too have been reading heavily on this front for about 23 years, so much so that I married a copyright lawyer. We talk about this stuff a lot.
Regarding the secrets in-repo, I'm not going to fight you on this. In my experience it's a Great Big Pain In The Ass to manage these things and I think you may be overlooking just how many of the devs on your team may need the rights to read/write production values.
As for the making the distinction between settings and configuration, again I think you're going to live to regret this as every company I've started at that employs this pattern has. You simply can't have your development, testing, and production environments running different middleware classes (as your example suggests) and not be due for a surprise in production. No, your settings should be as close to production in all environments as possible, and breaking your settings up like this is just begging for deviation.
As for the claim that only 99% of problems in production are data-related, that too is not my experience with such systems. If you're talking to S3 in production and local folders in development, or SQS in production and synchronous execution in development, you will have problems, and you won't be able to detect them, let alone debug and fix them in an environment that doesn't match the place you're deploying to.