It's really easy! If you imagine that a black person and a white person could never be friends or spend positive time together, and then you saw a show that had them together, you might conclude the show is trying to convince you something is okay that you know is not. Propaganda.

If you imagine that a gay person is inherently wrong, and that bad things deserve to happen to them as punishment for their choices, and then you watch a show where a gay person is happy and normal and respected, you might conclude the show is trying to push an idea on you that you already know isn't right. Propaganda.

It's sad, and dangerous, but it's not complicated.

I know it doesn't matter, and is fully a side issue to this post, but I hate that "blacklist" gets brought into this. It's never been used to be "a list of black people" or something; that wasn't the original meaning, and that's not the modern intention. It's just a word that sounds like maybe it could have been racist in origin, but it wasn't. And that one makes me grumpy just as an annoying word person.

The real hot take was that we used the term black and white for people at all! If we could go back to the past and make it so we call it, like, Affo and Euro or something, whatever, it would have cleared up a lot of unrelated term confusion.

I mean, if we could go back and change things there's maybe some other stuff that would be more important to change... but among the changes I would make are those!

Yeah, typically per year. And usually it's called Total Compensation because some of it is in salary, some in stock, some in stock options, sometimes even some kinds of perks, etc.

So all of that gets balled up into Total Compensation, which is different than annual salary

I can least kinda appreciate this guy's approach. If we assume that AI is a magic bullet, then it's not crazy to assume we, the existing programmers, would resist it just to save our own jobs. Or we'd complain because it doesn't do things our way, but we're the old way and this is the new way. So maybe we're just being whiny and can be ignored.

So he tested it to see for himself, and what he found was that he agreed with us, that it's not worth it.

Ignoring experts is annoying, but doing some of your own science and getting first-hand experience isn't always a bad idea.

Highly basic answer, let's say the strength of the vocals wave over time is:

5, 4, 3, 2, 3, 4, 5, 4

And drums is:

4, 0, 2, 0, 4, 0, 2, 3

Then you add them together for each time slice and get:

9, 4, 5, 2, 7, 4, 7, 7

And you put that on a record, or out to a speaker, and our ears are able to break that up into the two parts when it hears it. This is the same as when two things are in the room making sound, there may be two sources, but my ear only has one hole, and that hole has one eardrum behind it. The different sounds just add their powers together and hit my ear as one mixed wave.

Alternative answer: magic

You mean the AI trained on Twitter users and intentionally guided to be right-wing has learned that sometimes talking about soccer is a way to lure a 12 year old boy into child abuse? The resemblance is uncanny...

Maybe I'm just a wizard, or I don't know what y'all are talking about, but rebases aren't special. If you use git reflog it just tells you where you used to be before the rebase. You don't have to fix anything, git is append only. See where the rebase started in reflog, it'll say rebase in the log line, then git reset --hard THAT_HASH

Pushing without fetching should be an error. So either they got the error, didn't think about it, and then force pushed, or someone taught them to just always force push. In either case the problem is the force part, the tool is built to prevent this by default.

Continuing after merge should be pretty easy? I'd assume rebase just does it? Unless the merge was a squash merge or rebase merge. Then yeah, slightly annoying, but still mostly git rebase -i and then delete lines look like they were already merged?

I'm not an ffmpeg maintainer, but it's actually not as hard as you think. You know how when you get an email it shows up in your list of emails? That's your list of issues.

You know how when you get a reply to an email, all email clients that aren't the most absolutely basic will put the original emails and its replies into a thread together? That's the conversation about an issue, in context, with threading.

You know how emails can have attachments? That's attachments. You can put screenshots in there, or patches, lots of stuff.

Now you may be wondering, that sounds like a lot of emails. That's true! But most people who live the mailing list life have filters and stuff setup to expect a lot of unsolicited emails. Like there are headers in the emails from mailing lists that tell you which list it was from, so it's really trivial to have a thing that puts all mail from this list into a folder or something and then not notify on emails in that folder. So, like an issue page, you can check it periodically, maybe mark certain ones as notification worthy, and ignore the rest.

The main upside to this is that the theoretical barrier to entry is relatively low, because every human who has touched a computer basically has an email. And you can have ultimate control of your experience because really it's all about what features your mail client has. And even if the mailing list server goes down you won't get any new emails, but you already have all the emails you've received before, so it's distributed! And you can still send replies while it's down, and they'll just spool until things come back up. Magic!

The main downside is that the practical barrier to entry is relatively high because people aren't used to joining mailing lists and aren't setup for it, and so it ironically feels like a much bigger deal, if you're any "normal" kind of email user, than creating a new username and password account. So for casual users, it's kind of a nightmare.

Also, because mailing lists are usually public, it's really easy to make a web frontend that contains the archive for non-subscribers and search engines and stuff, but while these could look like anything, in practice they look like ass, because mailing list people don't really care about what web stuff looks like a lot of the time. Which makes sense, they're not looking at the web frontend, they're ssh'd into a jump box using mutt through screen, or some set of emacs plugins 😛

Knowing the folks at IA I'm sure they would love a backup. They would love a community. I'm sure they don't want to be the only ones doing this. But dang, they've got like 99 Petabytes of data. I don't know about you, but my NAS doesn't have that laying around...

a spokesperson for the honeyseller, Vladimir Dmitriev

Listen, obviously people with names like that can be totally normal and great people. For sure. But this name, connected financially to this candidate, at this time. Guys... It's not a good look...

Similar to other people, I think you should own it. Try to think of it not as "I betrayed my character" but rather "my character gave in to temptation and regrets it but has to live with the consequences", then use that. Play the character as though they are unhappy with the changes, they regret it, but they must soldier on.

People aren't all perfect archetypes, and characters can have flaws and nuances. And the best part is, if your character up until now had no reason to make the choice you made, maybe it's time for an out of game flashback. Work backwards... what thing could have happened in their backstory that would explain why they made this seemingly incongruous choice? Why did this tempt them when so many other things did not, and why does this cause them so much shame now. That kind of stuff.

Or don't! Just some suggestions, since it sounds like you've got nothing to lose, may as well try some character development!

Well... That's actually probably fair as stated.

BestBuy etc don't sell Apple's products on commission, they bought them from Apple for a wholesale price, they've got them in a warehouse and on shelves right now on their dime, and the only way they make that money back is by selling them.

And the only way Apple makes money from a product being sold at Best Buy is that Best Buy will likely buy more stock to replace the stuff they sold, and they'll buy that from Apple.

So if it was banned everywhere it would be unfair to the retailers that already paid Apple for a product they now can't recoup, and it wouldn't impact Apple at all because they already made their money from Best Buy.

This way the retailers can get their money back, but can't get any more, which means only Apple is impacted.

The only other way that's semi-fair (but would be extreme) would be for Apple to be forced to do a recall or something and reimburse all the retailers the money they had already spent. Doable, and definitely more of a punishment for Apple, but a lot of extra work for everyone if the outcome of this is that Apple settles and then everyone can just go back to ordering more again.