[-] TootSweet@lemmy.world 3 points 12 hours ago

Saturated fat causes heart disease. Unsaturated fat causes inflammation. Trans fats are basically poison. Protein is bad for your kidneys. Carbs cause cardiovascular disease. Glucose causes diabetes. Fructose is bad for your liver. Alcohol will fuck your liver over but good. Not eating calories at all will make you starve to death.

[-] TootSweet@lemmy.world 6 points 17 hours ago

I don't get it. But he clearly doesn't either. Wait, I think I do get it.

[-] TootSweet@lemmy.world 3 points 17 hours ago

https://en.wikipedia.org/wiki/Ubbi_dubbi

(I'm sorry. I'm being a sarcastic asshole.)

[-] TootSweet@lemmy.world 4 points 17 hours ago

Pabapeber dobolls

[-] TootSweet@lemmy.world 24 points 17 hours ago

More often than not, when I see I've been downvoted, I take pride.

[-] TootSweet@lemmy.world 8 points 1 day ago

Mark NSFW posts NSFW, please.

[-] TootSweet@lemmy.world 7 points 1 day ago

The ingredient that really makes it "kitchen sink" is E. coli.

[-] TootSweet@lemmy.world 2 points 1 day ago

Yeah, but Lineage can just not have the same restrictions. And you can (as I do) run Lineage without Google Play Services or whatever. I get that this change will mean that people with normal Android phones without custom roms will no longer be able to install F-Droid or any of the apps on it, and I get that that means less people will have enough interest in F-Droid to contribute to it or write FOSS apps that I might want to be able to run. But the only reason I can think why that could result in the complete cessation of F-Droid development or package maintenance is if nobody runs custom roms moving forward. (Or F-Droid shuts down completely symbolically as a protest.)

This part of the Register article almost set off my alarm bells:

In March this year, Google also made a change to the way AOSP is developed; the public aosp-main branch is now read-only and development takes place in a private branch, with code published from time to time as android-latest-release.

But it sounds like the AOSP updates still do become FOSS eventually. Just not as soon as they used to.

This might end up being enough to get me to switch to some Linux phone for my next phone, but it's not like I wasn't strongly considering it before this news came out.

I dunno. I still suspect it's not going to affect me directly as badly as most F-Droid users. And don't get me wrong, Google is still complete assholes for doing this. But it's not going to affect my phone for a good while.

[-] TootSweet@lemmy.world 10 points 2 days ago

Sooner we give it a kick, the better.

[-] TootSweet@lemmy.world 26 points 2 days ago

Just when I thought Lemmy was over the trend of talking about stroganoff.

[-] TootSweet@lemmy.world 22 points 2 days ago

No way ChatGPT did this without at least a shit-ton of selection or a really huge prompt or something.

[-] TootSweet@lemmy.world 23 points 3 days ago

Achievement Unlocked: Dissociation

59

!covidconscious@lemmy.world

There are other communities for discussion of COVID-19, but none really on this topic.

As someone who still masks and isolates, I can't imagine I'm the only one, and I'm guessing there are enough people with relevant things to talk about to make an active community.

362

OC

Let no one accuse me of being a competent artist or comedian.

30

Ok. Slight lie. I saw one firefly. It was early in the season and in broad daylight, so not when it should have been blinking. But it was a firefly.

But this year is the first that I haven't seen a single firefly light up. And it's late enough in the season now that I doubt I'll see one before the snow falls.

The planet is fucked, folks. Not that I didn't already know this. The weather has been steadily more severe over the last few years. And hotter. And you steadily hear news about icebergs this and ice shelves that and more hot-habitat species moving further from the equator as the climate warms.

But not a single firefly fireflying? In my area? That's a qualitative shift that has more impact on my outlook than just the abstract knowledge that we're killing the planet and the slow progression of a few known trends.

253

Bonus: and that likely explains why older shows tend to have self-contained episodes while newer shows tend to be serial.

32
submitted 1 month ago* (last edited 1 month ago) by TootSweet@lemmy.world to c/politicaldiscussion@lemmy.world

If you found yourself transported to early 1788 Philadelphia, say about a year before the U.S. Constitution was signed, an if the Founding Fathers were all willing to hear you out, what would be some of the first things you'd say specifically to warn them and try to prevent some of the bad things that have happened in the real-world timeline since then? Basically, what differences would you want to see made to the U.S. Constitution from the beginning and how would you impress specifically on the Founding Fathers the necessity of diverging from their instincts in specifically those ways?

And keep in mind the Founding Fathers' beliefs on things like slavery, "the free market", guns, LGBTQIA+, etc.

7
Project G.e.e.K.e.R. (en.wikipedia.org)
submitted 1 month ago by TootSweet@lemmy.world to c/nostalgia@lemmy.ca

I suspect this may be a lesser-known one. It was on CBS in 1996 and was cancelled after only one season (partially because of the FCC's strengthened requirements for making kids' shows "educational"), but it's very much imprinted on my brain.

You can file this (along with the "Star Tropics" video game franchise) under "underrated media that deserves a reboot but no way in hell is that ever going to happen."

6
submitted 1 month ago by TootSweet@lemmy.world to c/Nerdcore@lemmy.zip
15
submitted 2 months ago by TootSweet@lemmy.world to c/foss@lemmy.world

cross-posted from: https://lemmy.world/post/33915876

This is a California state court case that could drastically change the landscape for Free and Open Source Software moving forward. And particularly that FOSS that is covered by Copylefted licenses like the GPL family of licenses.

The premise of the case is that by selling smart TVs with only the compiled version of GPL'd (and likely forked) code projects such as the Linux kernel, BusyBox, selinux, ffmpeg, etc, Vizio is blatantly violating the "Source Code Provision" of the GPL which requires that they provide along with this compiled code, also the source code or failing that a written offer of source code to any recipients of these compiled versions of these GPL'd applications and libraries.

(Now, of course, anyone can get the source code of the Linux kernel or BusyBox or any of the other applications at issue. But in the process, Vizio and their manufacturers have written kernel drivers for the hardware specifically on the TVs (which are derivative works of the Linux Kernel and therefore covered by the GPL), and probably made modifications to several of the other codebases in order to make them do novel things specifically for the smart TVs in question. Beyond that, the GPL requires Vizio to provide any programs/scripts/signing-keys/etc to compile and install the source code (or a, say, consumer-modified version of the source code) onto the TVs. It's the Vizio-specific/chip-manufacturer-specific modifications/derivative works and compiling/installing code that's most important.)

The "Software Freedom Conservancy v. Vizio Inc." case is seeking to force Vizio to comply with the GPL. Assuming the SFC is successful and the courts rule in their favor, the eventual result is expected to be a fully FOSS OS "distribution" (of, basically, GNU/Linux) that end users can install on their Vizio TVs in place of the factory-installed OS. This FOSS OS distribution, of course, would allow users to remove ads and other antifeatures from the TVs in question. And over time, it's highly probable that this FOSS OS smart TV distribution would expand to other models and brands of TVs. Roughly speaking, the goal of this lawsuit is to be able to create an "OpenWRT but for smart TVs."

But this case could definitely affect the industry not just for smart TVs. Smart phones, game consoles, automobiles, robot vacuum cleaners, sex toys. So many consumer electronics devices run on, for instance, the Linux or Android kernel (both of which are covered by the GPL). And a lot of these devices also include many other programs and libraries covered by the GPL. There's potential for lots of different "OpenWRT but for " sort of distributions. And if SFC v. Vizio succeeds, it could greatly increase the likelihood of all of these coming to fruition.

Vizio has been stalling for strategic reasons. But there's a court date set for 2025-09-22. My understanding is that there will be options to watch a live stream of it via Zoom for Business. (Yes, it's proprietary, unfortunately.) You can even apply for a grant to travel to California to attend the hearing in person (though I think that's kinda mostly for bloggers and journalists and such). Also, a lot of court documents about the case are linked on the page I linked in this post.

Ok. Time for a bit of legal nerd stuff. (IANAL, not legal advice, etc.) Previous GPL enforcement cases have been copyright cases brought by the copyright holders. This case is novel in that it's a contract case. There's a legal concept of a "third-party beneficiary" to a contract. If Alice and Bob make a contract that requires Alice to pay Charlie $100, then Charlie is a third-party beneficiary and thus can bring a suit for enforcement against Alice. In this case, copyright holders of GPL'd code made a contract (the GPL) with Vizio that requires Vizio to make sure anyone they distribute compiled GPL'd code to can get the source code (and compiling/installing scripts etc), so anyone Vizio sells a TV to is a third-party beneficiary and therefore can bring a suit against Vizio to get the court to force Vizio to hold up their obligations under the GPL. At least that's the legal theory under which SFC is bringing the suit.

If you want more info about this, this YouTube video is a panel of SFC folks doing a Q&A specifically about the Vizio case. It'll have some interesting tidbits of info.

I'm hopeful, and the courts have been sympathetic to the SFC's arguments so far. I'm crossing my fingers for sure.

171

This is a California state court case that could drastically change the landscape for Free and Open Source Software moving forward. And particularly that FOSS that is covered by Copylefted licenses like the GPL family of licenses.

The premise of the case is that by selling smart TVs with only the compiled version of GPL'd (and likely forked) code projects such as the Linux kernel, BusyBox, selinux, ffmpeg, etc, Vizio is blatantly violating the "Source Code Provision" of the GPL which requires that they provide along with this compiled code, also the source code or failing that a written offer of source code to any recipients of these compiled versions of these GPL'd applications and libraries.

(Now, of course, anyone can get the source code of the Linux kernel or BusyBox or any of the other applications at issue. But in the process, Vizio and their manufacturers have written kernel drivers for the hardware specifically on the TVs (which are derivative works of the Linux Kernel and therefore covered by the GPL), and probably made modifications to several of the other codebases in order to make them do novel things specifically for the smart TVs in question. Beyond that, the GPL requires Vizio to provide any programs/scripts/signing-keys/etc to compile and install the source code (or a, say, consumer-modified version of the source code) onto the TVs. It's the Vizio-specific/chip-manufacturer-specific modifications/derivative works and compiling/installing code that's most important.)

The "Software Freedom Conservancy v. Vizio Inc." case is seeking to force Vizio to comply with the GPL. Assuming the SFC is successful and the courts rule in their favor, the eventual result is expected to be a fully FOSS OS "distribution" (of, basically, GNU/Linux) that end users can install on their Vizio TVs in place of the factory-installed OS. This FOSS OS distribution, of course, would allow users to remove ads and other antifeatures from the TVs in question. And over time, it's highly probable that this FOSS OS smart TV distribution would expand to other models and brands of TVs. Roughly speaking, the goal of this lawsuit is to be able to create an "OpenWRT but for smart TVs."

But this case could definitely affect the industry not just for smart TVs. Smart phones, game consoles, automobiles, robot vacuum cleaners, sex toys. So many consumer electronics devices run on, for instance, the Linux or Android kernel (both of which are covered by the GPL). And a lot of these devices also include many other programs and libraries covered by the GPL. There's potential for lots of different "OpenWRT but for " sort of distributions. And if SFC v. Vizio succeeds, it could greatly increase the likelihood of all of these coming to fruition.

Vizio has been stalling for strategic reasons. But there's a court date set for 2025-09-22. My understanding is that there will be options to watch a live stream of it via Zoom for Business. (Yes, it's proprietary, unfortunately.) You can even apply for a grant to travel to California to attend the hearing in person (though I think that's kinda mostly for bloggers and journalists and such). Also, a lot of court documents about the case are linked on the page I linked in this post.

Ok. Time for a bit of legal nerd stuff. (IANAL, not legal advice, etc.) Previous GPL enforcement cases have been copyright cases brought by the copyright holders. This case is novel in that it's a contract case. There's a legal concept of a "third-party beneficiary" to a contract. If Alice and Bob make a contract that requires Alice to pay Charlie $100, then Charlie is a third-party beneficiary and thus can bring a suit for enforcement against Alice. In this case, copyright holders of GPL'd code made a contract (the GPL) with Vizio that requires Vizio to make sure anyone they distribute compiled GPL'd code to can get the source code (and compiling/installing scripts etc), so anyone Vizio sells a TV to is a third-party beneficiary and therefore can bring a suit against Vizio to get the court to force Vizio to hold up their obligations under the GPL. At least that's the legal theory under which SFC is bringing the suit.

If you want more info about this, this YouTube video is a panel of SFC folks doing a Q&A specifically about the Vizio case. It'll have some interesting tidbits of info.

I'm hopeful, and the courts have been sympathetic to the SFC's arguments so far. I'm crossing my fingers for sure.

2
Beefy - Crash [Tech] (www.youtube.com)
submitted 2 months ago by TootSweet@lemmy.world to c/Nerdcore@lemmy.zip
56
submitted 2 months ago by TootSweet@lemmy.world to c/asklemmy@lemmy.world

Or anything else concerning, for that matter. (BPA, maybe?)

I eat a tin of these basically every day. Have been doing so for well over a year now.

No, I'm not doing the whole "sardine diet" or whatever it's called where you eat nothing but sardines. I'm proud to say I started eating sardines daily before that fad came up. And I eat a lot more than just sardines.

Anyway, I know "fish" in general tends to have high levels of mercury, but I've heard that basically the amount of harmful heavy metal sort of toxins in fish generally varies directly with the lifespan of the particular type of fish in question. (The longer it's been swimming around in mercury-laden (or whatever-laden) water and eating mercury-laden (or whatever-laden) stuff, the more mercury will build up in its system by the time its caught, cooked, put on a table, and consumed by a human.) And I've heard that sardines in particular are quite low in such harmful toxins. (Maybe anchovies would be even lower? Not sure.)

My googling for an answer to the question of whether the level of harmful stuff in sardines is so low that eating them daily wouldn't be an issue hasn't really yielded helpful results. So, why not ask here?

(I have heard that EVOO is "better for you" (whatever that means, specifically) than non-virgin olive oil. And the particular brand of sardines in "olive oil" I get don't say "virgin" anywhere on the packaging, so that might be a reason to switch brands. Not sure whether it's really worth it or not. And the other brands are always way more expensive.)

4
submitted 2 months ago by TootSweet@lemmy.world to c/Nerdcore@lemmy.zip
view more: next ›

TootSweet

joined 2 years ago
MODERATOR OF