Cooper8

I'm not familiar with a temp and flow two handle mixer for a sink faucet. That could work well if the temp valve is full bore.

Single handle faucets dont replicate temps, you have to guess approximate temp each time and they are almost always center biased.

zheres your standard two tap mixer faucet:

At both taps full open you have full flow/pressure from both the hot water and cold water supply only restricted by the valve full open orifice.

Now add an additional valve to the mixed outlet of the faucet with both hot and cold feeding into the line that runs into it. If the valve is sized to accommodate the full flow from both valves feeding into it, the full combined pressure/flow from both cold mains and hot supply is available.

Also, once you set the temperature you like by turning the temp taps, that temp will be available to you at any flow rate on demand. Nothing you do to the mixed valve will change the temperature of the flow. This is especially useful if your hot temperature is very hot, you can have nice warm water to wash your hands every time without worrying you might scald yourself.

And the internet is largely a platform for capitalism, and most available content is from the internet. Capitalism fundamentally relies on the confidence games of profitable pricing and marketing, not to mention speculation on finance.

they set the relative flow/pressure of respectively hot and cold water. The tap sets the total flow from minimum to maximum available based on the pressure supplied from.thenother two, allowing the selected hot/cold ratio to be preserved between on/off cycle, while also allowing for just a small stream of water when you need it, or a full flow of water when you need to fill a vessel or blast a dish.

Because sometimes you want full cold, sometimes you want full hot. Yes you could use a three way valve but you'd generally lose maximum water pressure.

Isn't this thread about sinks?

LLMs and the entire field of reenforcement learning is fundamentally biased towards the production of Influencing Machines. We are training models at the fundamental level to be subtle and devious con artists.

single handles are all well and good, but I'd prefer a hot knob, a cold knob, and a flow knob. I've never been clear why this isn't done, I suppose its probably cost. Maybe there is some wear and tare reason?

Definitely true.

No, but they could be women.

"you could block logged out users but that would impact many lurkers"

"regardless you might not be logged in at all, you should still be allowed to browse content"

Fundamentally, what I'm suggesting is a fork in the road. Either an instance admin can set up to eliminate scrapers by making the instance private to only registered users,

or they can maintain their instance as public and deal with more arcane methods to attempt to eliminate scraping.

The issue is that if the infrastructure isn't in place for the instance operator to decide to make their service private, then everyone is opted in to the Scrapers vs Countermeasures war with no alternative.

Privacy and encryption just work, it seems like not building the infrastructure to enable the network to function with them in place is a mistake.

To me, and to many users, what we want is fast load times, quick federation, and reliable service, all things that benefit from reducing traffic load to only registered users.

Fediseer seems like a good solution, essentially a whitelist vouch system with touching at second hand.

Regarding the media hosting, again it seems like something that could rely on a method of identifying the user request directly with their user account before responding to the request. Cookies could be an option for this, though they are falling out of favor. Alternately, and more securely, it could be a cryptographic handshake where the user's home instance and the instance hosting the post generate a public key using their two private keys for the user, and the user provides the public key when making pull requests from the federated instance. The keys could be batch generated when an instance first federates content with another and then assigned to user accounts the first time the user makes a pull request through a link from their home instance to the federated instance.

Secure Scuttlebutt Protocol already deved the encryption methodology that could be cross applied for a lot of this: https://ssbc.github.io/scuttlebutt-protocol-guide/ though I am of course not suggesting SSP be adopted whole cloth, and there are a bunch of other OS projects with encryption that could be used. This is just the one that comes to mind.

(edit: also I am in favor of finding methodologies that work whether CloudFlare is used by the instance or not, obviously CloudFlare has advantages but as we have seen also is a vulnerability of the network.)