scrion

Didn't I just say that in the comment you replied to?

Also, ultraprocessed food is a fixed term that refers to

[...] foods [...] ready-to-eat or ready-to-heat industrial formulations made mainly with ingredients refined or extracted from foods and contain additives but little to no whole foods.

It's used as such in studies and reports.

https://pmc.ncbi.nlm.nih.gov/articles/PMC10261019/

I agree. When I was talking about "processed food", I was talking about food that has been processed too much, i. e. cooked to oblivion, loaded up with preservatives, artificial flavor, colors etc. to maximize profit by making it last longer, be more attractive / "tasteful" to the point of addiction (think chips) no matter the nutritional value.

Food is of course processed even in the home kitchen, and there are processing methods that are totally fine (let's say freezing, canning) and that have a long cultural tradition without adverse effects.

However, I think it's hard to dispute that industrially processed (fast) food, convenience food, snacks, super high calorie foods etc. are a real problem. I honestly also blame e. g. the expectation society has with respect to its workers who can't necessarily afford (money, time) to regularly prep healthy food at home, given the schedule imposed on them.

Oh, please skip it. I watched the first season and I wish I could erase that experience from memory.

What are your requirements? I liked CalenGoo, I can live with aCalendar and BusinessCalendar.

Yeah, thanks, that comic was a little too black and white in 50% of the panels - acknowledging women's rights and their role in society and abolishing child labor doesn't mean that we did not process the shit out of food and invented the unholiest abominations as substitute for actual nourishment, or that it's suddenly healthy to live in a concrete block after spending 10 hours in cloned cubicle #7.

Yeah, no lubricants and the look / style factor - that was my conclusion as well.

As for maintenance, while a belt might last 3 times as long, that's not really a factor, given the price difference between belts and chains.

Exactly, which is why I was trying to think of any actual reasons I might want a belt, except style.

Are there any other reasons I'd want this apart from the lack of oil and the decreased noise levels, the coolness factor and the tinkering itself?

Every single one is a valid reason in itself of course, but maybe there is more.

I'll post some links, but it's a pretty busy week for me already, so give me some time.

An interrupt is an input that can be triggered to interrupt normal execution. It is used for e. g. hardware devices to signal the processor something has happened that requires timely processing, so that real-time behavior can be achieved (for variable definitions of real-time). Interrupts can also be triggered by software, and this explanation is a gross oversimplification, but that information is what is most likely relevant and interesting for your case at this point.

The commands you posted will sort the interrupts and output the one with the highest count (via head -1), thereby determining the interrupt that gets triggered the most. It will then disable that interrupt via the user-space interface to the ACPI interrupts.

One of the goals of ACPI is to provide a kind of general hardware abstraction without knowing the particular details about each and every hardware device. This is facilitated by offering (among other things), general purpose events - GPEs. One of these GPEs is being triggered a lot, and the processing of that interrupt is what causes your CPU spikes.

The changes you made will not persist after a reboot.

Since this is handled by kworker, you could try and investigate further via the workqueue tools: https://github.com/torvalds/linux/tree/master/tools/workqueue

In general, Linux will detect if excessive GPEs are generated (look for the term "GPE storm" in your kernel log) and stop handling the interrupts by switching to polling. If that happens, or if the interrupts are manually disabled, the system might not react to certain events in a timely manner. What that means for each particular case depends on what the interrupts are being responsible for - hard to tell without additional details.

It's not like Bluetooth started demanding location permissions, the conceptual model of the permission was revised: having access Bluetooth means an app could determine your location via a form of lateration.

In earlier versions of smartphone operating systems, this was not transparent to users lacking the technical background, so Bluetooth also requiring location access is actually an attempt at making users aware of that. I'm not an iOS developer, so I can't comment on iPhones, but on Android versions prior to 11, having access to Bluetooth meant an app would be able to determine your location.

Today, you can require the permission ACCESS_FINE_LOCATION, which expresses that your app might use Bluetooth to obtain location information on Android. Also, if you're just scanning for nearby devices to connect your app to, but don't want users to be confused why your smart fridge app needs to know your precise location, you can declare a permission flag (neverForLocation) and Android will strip beacon information from the scan results, better asserting your intentions.

So, overall: no, there is nothing nefarious going on, it was always possible to determine your location via Bluetooth, and the update to the permission model was an honest improvement that actually benefits you as user.

Now, there are still plenty of shady apps around, and apps that are poorly written - don't use those.

https://launchpad.net/safe-rm

https://github.com/kaelzhang/shell-safe-rm

etc.