not() is a base function that negates what’s inside (turning True to False and vice versa) giving it no parameter returns “True” (because no parameter counts as False)

Actually, not is an operator. It makes more sense if you write not() as not () - the () is an empty tuple. An empty tuple is falsy in Python, so not () evaluates to True.

Oh, really? That’s disappointing to hear; I had no idea he was like that.

Oh hey, it’s the Minecraft guy

Last I heard they want to switch to another platform, and don’t consider it worth upgrading to 0.19 because they’re leaving soon so it wouldn’t be worth the hassle.

This is pure guesswork on my part, but they could be waiting for Sublinks (a Lemmy-compatible backend) to get up to speed before switching to that. They say that the new platform is “compatible with all Lemmy apps”, and Sublinks is the only project I know of that fits that criteria.

It’s a joke.

SponsorBlock automatically skips the entire sponsorship as soon as it starts, so a lot of the time you wouldn’t even know it was there if you didn’t see the green section of the playback bar.

It’s not just for sponsorships, either. You can set it to skip intro animations, reminders to subscribe, self promotion, etc.

BaNaNa

Swift’s extensions system has spoiled me, and I feel the pain of this whenever I have to write Java

Same. I’ve made six accounts since I joined during the exodus, only two of which I actively use now.

This isn’t entirely true, according the article. If a producer in the US was using the name “Champagne” before 2005, they can continue to do so, but producers can’t start using it anymore.

It took two decades of negotiations, but finally, in 2005, the U.S. and the EU reached an agreement. In exchange for easing trade restrictions on wine, the American government agreed that California Champagne, Chablis, Sherry and a half-dozen other ‘semi-generic’ names would no longer appear on domestic wine labels – that is unless a producer was already using one of those names.