• 0 Posts
  • 26 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • Macklemoore was opening for Ed Sheeran on his tour, and took some time in his set to speak out in favour of not genociding Palestinians, including clarifying statements that he wasn’t blaming Jews in general, just specifically the state of Israel.

    The owner of many of Sheeran’s tour venues phoned him and said he needed to change his opening act or he’d be barred from performing at venues owned by the same company and several other venue-owners who’d agreed to join the threat. Sheeran caved, despite the fact that some of the tour dates were too soon to plausibly book a replacement capable of filling the venues, and Sheeran being a massive ticket-seller in general, so it likely being a bluff.

    P!nk retweeted a message from a pro-Israeli organisation accusing Macklemoore of extreme and vile antisemitism, then when called out for it, doubled down with direct accusations of Macklemoore being an antisemite and wanting to harm Jews.


  • Given that Ed Sheeran is Rupert Grint, and P!nk doesn’t look like P!nk, I suspect that P!nk is not P!nk. Off the top of my head, I think there might be a famous effeminate gay man that vaguely looked like that, and upon using reverse image search, I learned that this is James Charles, who is indeed a famous effeminate gay man, and a YouTuber.


  • Plenty of high-end monitors need more bandwidth than DisplayPort 1.4a can provide if operating uncompressed, but models with a DP 2.x port typically cost a lot more because it needs reasonably expensive hardware to make it work. That means that if you use DP, then you have to compromise between spending more money or using Display Stream Compression. Monitors needing that much bandwidth basically always have an HDMI 2.1 port that can handle it uncompressed, but without this patch, if you used HDMI under Linux with a Radeon GPU, it wouldn’t run in HDMI 2.1 mode, so would give even less bandwidth than DisplayPort 1.4a, and you’d experience even more compression artefacts, despite the same configuration working perfectly under Windows.









  • When governments print banknotes, they can sell them and get money to do things at face value, instead of having to get loans and issue bonds where they’d have to pay interest or charging taxes where their citizens would object. In fact, in countries like the EU, UK and USA, despite normal people and normal companies using cash less and less, for the past couple of decades, the amount of cash printed has increased rapidly because as long as people buy it, there’s a big incentive for governments to print it. Bigger face value notes mean more money for less printing, so are the best thing to issue, as long as people are buying them.

    That leaves a big question of who on earth is buying more banknotes each year than the last. The obvious thing that can be best done by banknotes is storing a large value in a small space with the ability to be moved around without traceability or counterfeiting, which really only matters to money launderers. Things like bank transfers and cryptocurrencies can be traced as long as someone knows who owned the money at some point, but if you buy your bitcoin with cash from someone who doesn’t keep records of who gave them the cash, then your crypto wallet is totally opaque to the authorities.

    The people involved range from minor things like spouses hiding money in a divorce to tax dodgers to drug dealers to people traffickers to sanctioned governments, and when that’s all added up and funneled through opaquely-owned shell companies so it doesn’t look like it’s Russia or Iran’s money buying the cash, there’s enough demand for governments to justify building new money printing facilities and issuing higher denomination banknotes.

    If you want to learn more, there’s quite a lot more detail in Everybody Loves Our Dollars by Oliver Bullough.








  • The exact quote is:

    And this was a debug session from hell, enormously helped by an AI doing much of the grunt-work.

    I’d like to call it my tireless helper, but the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it.

    I suspect those things have been trained by people who may not be quite as stubborn as I am.

    But while the AI was ready to give up several times, it did keep adding debug code and analyzing it faithfully when I pushed. So credit where credit is due and I let the AI write the commit message above.

    This is basically a one-liner fixing a bogus “round_up()” to a “round_down()”, but there were 24 patches adding more and more debug information to this, and 18 kernel boot to finally narrow it down to this. - Linus

    That’s a long way short of finding the bug and pointing it out, and instead is just the tedious work of adding checks and then deciding where to add more checks when you have the result of the previous checks. I suspect if we’d spent a trillion dollars on a tool for that, we could have come up with something much more efficient than an LLM.