One add a larger or additional fuel tank to any conventional truck, or plop a transfer tank with pump in the bed.

People buy trucks to serve their use case, not to serve anyone else's. Invent a form and fit gasser replacement and they'd sell, but paying for inferior performance is absurd.

Arizona

They don't care for reasons they choose not acknowledge.
Their revenue appears unconnected to Slashdot importance, or is sufficient without the effort to restore quality. I find this interesting.

That's why they choose not to respond to (not the same as "ignore") valid criticism. The enshittification of Slashdot is deliberate. It's easy money for minimal effort.

Slashdot owners could easily replace editors with AI and arguably should since the threshold for acceptable "quality" has been so low for so long no one would notice.

There are plenty of places that will take your exposed film, develop, and scan and/or print for you, by mail, or in-person, at least around here. If there's a Hunt's Photo near you, they do a great job.

If you only want digital photos printed, then there are many, many places that will print pro-grade photos for cheap, and the results will be a damn sight better than what you get at the local drug store.

How does one discern the difference between someone hurling an epithet randomly based on topical knowledge versus someone wanting to discuss actual Nazi doctrine from 1930s?

How much influence do you think FDR had on Nazi politics before the bad stuff started? Most Americans have no clue how closely FDR aligned with Adolf before it went sideways.

You're describing the consensus models, and they are better than any individual model, at least thus far.

Calling everyone a Nazi doesn't work any longer, except in the crowds that don't care about diminishing the horrors of 1930's Germany. But you don't care about history, so you hurl epithets all around hoping something sticks.

See: Boy who cried wolf parable.

The second sentence explains it perfectly fine to a layperson, and anyone used to interpreting plots has no real problem even without the supplied explanation. The only points of confusion for someone unfamiliar with the different models are the are the labels.

Canadahelps.org allows you to donate to any registered Canadian charity, if the charity has not set up a Canadahelps.org charity account, they just mail out a cheque for anything that is donated using the registered charity's registered mailing address.

A crucial difference is that Canadahelps.org is itself a charity, subject that the oversight that entails. I think it is a great value to the charities who use it since it can greatly simplify the charity's accounting and official receipt generation requirements, at the cost of losing out at a closer connection to their doners. From the point of view of a doner, it certainly simplifies things to have a single place to do all your donations, potentially combining multiple tax receipts into just one.

"a decision and action appear to takes place milliseconds before the conscious mind is aware of it, but phenomenologically it feels like you made that decision before the event happened."

I certainly don't know, and I don't think the research answers that question yet.

But from what I've read its research that raises many more questions than it REALLY answers.

For example, what if the consciousness feedback loop is not "aware" of the decisions (its "output") until they've been dumped to memory and looped around and come back in as "inputs".

So that doesn't necessarily mean you don't consciously make decisions, it just means you aren't yourself aware you made it until after you made it.

In web programming terms, suppose "consciousness" is the local application state view, which is a reflection of the data on the server "memory" and has all your data labels and field contents showing (including the logs of its decisions). Imagine too that a "decision" is like activating a call to the server to make a an update to the back-end database.

So based on the data in the local state, and the running software, the local app "decides" to calls the server and make an update. Lets just say, it just does it -- in particular it doesn't feed that information back to the local state object, no UI is updated, no labels are changed. Yet.

The local state is not updated with even the record that it made the call until it gets the state update from the server a few milliseconds later.

Then, if you are a brain researcher monitoring the application state (aka consciousness), you'll discover it doesn't "know" it called the server, until after the server has been called and returned.

The point is: just because we don't know what we decided right away doesn't necessarily imply that we didn't decide. The brain is an organic system that evolved over millions of years, perhaps having consciousness run a few milliseconds behind is perfectly serviceable solution for the problems it evolved to solve.

Perhaps its even advantageous, waiting for the awareness of the decision to propagate through consciousness before emitting the decision to the rest of the body might cause enough action latency that we're polar bear or sabre tooth tiger food. Better to get the body acting act as soon as the information is there -- there's simply no survival advantage to waiting for it to get dumped back to memory and updated in the consciousness first.

Or maybe consciousness is an illusion, so we can watch a show that aleady happened with no impact on the world around us... but that seems relatively useless in a world with polar bears and sabre tooth tigers.

Perhaps those railing against high schools, colleges, and even post-graduate education, need to go back and deal with their *own* biases and self-delusions. The institutions and systems are there.

I once had an interesting conversation with an Android OEM. I sat down with them to discuss what security issues they'd like to see the Android security team work on. They asked me "When are you going to fix the USB hole?". I didn't know what they meant and asked for clarification. They explained that in some parts of the world, notably India and China, there were "free" charging stations set up in bus stops, train stations and other public areas. These charging stations allow the public to charge their phones, for free! There's just one catch. On a sign above the charging station there's a set of instructions that tells users how to go about activating the charging. The sign tells them to go into the Settings app, then "About Phone", then scroll down to the build number, tap it seven times, then... it walks them through enabling ADB and accepting the key of the "charging station" computer, which would then proceed to install malware -- and to start charging.

Huge numbers of people used these charging stations every day, to the point that the biggest problem users had (besides the malware) was that they were always occupied. No one had a problem with "activating" charging for their device.

90% of people are capable of following a list of instructions. 100% of people are capable of either following a list of instructions or getting someone nearby to do it for them.

Anyway, this OEM wanted us to disable ADB entirely, or allow them to, because their users were doing it, getting loaded up with malware, and then blaming the OEM for making a crappy phone. I, of course, told them that we were not going to disable ADB and we were not going to remove the compliance requirement that forces them to support ADB.

Unfortunately, the current change still doesn't fix the "USB hole", but it does offer a way to rate-limit malware installation via downloadables.

Anyway, if you really think your users can't follow instructions, or can't get someone else to do it for them, you can always just register for a developer account. As long as you don't distribute malware, people will be able to sideload your APKs without using ADB. If the $25 is too much for you, maybe share the cost with some buddies, or get one of the limited accounts, though your APKs will only be installable on a small number of devices. Except, of course, by people who can follow instructions, or get someone else to.

Yep. It allows them to stop malware. How terrible!

How did you learn this?

I suspect you actually do derive a lot of utility from AWS and Azure, you just don't realize how many of the services you use every day are running on them.