Hacker Newsnew | past | comments | ask | show | jobs | submit | BenjiWiebe's commentslogin

It was pretty rough for me driving through downtown Atlanta - nowhere seemed to have public restrooms.

Around my home every business will have a public restroom, or a not-so-public restroom that's still available if you ask.


It may depend on the milk quality and the dairy. There's definitely a taste difference between our raw milk and our pasteurized milk, and neither one is bottled.

You can even sniff the pasteurizer and smell if it's the raw milk or if it's been pasteurized.

Also when making cheese, the naturally occurring bacteria and enzymes in raw milk make quite a large flavor difference (from a cheesemaker's perspective anyways).


The yield is determined by the components (fat, protein, and other solids) in addition to the process the milk has underwent, and the cheese recipe. In our cheese making there's not a noticeable reduction in yield on pasteurized cheese, but we do a lower/slower pasteurization.

In the US, if you're actually seeking out raw milk cheese, watch out. If the milk is pasteurized but not legally pasteurized (inspected, licensed, documented) it must be sold as raw milk cheese. Even if you boiled it for an hour first.

Then there's also some raw milk cheese that is heat treated for less than the requirement for pasteurization, but still much hotter than required for the cheese process.


When I make raw milk cheese (small commercial, USA) the milk gets only about 1-3 degrees (Fahrenheit!) above the cows body temperature.

Also our family has been drinking raw milk all our lives, and there are a lot of people who come to our farm and get raw milk to drink.

I'm not aware of anyone ever getting sick from our milk (unless lactose intolerant/allergic of course).

If you are heating your milk to 85C, I'm sorry, but that's not really raw milk cheese anymore. When I make pasteurized cheese the milk is heated to only 63C (albeit for 30 minutes).


Is the page actually done downloading 0.3 seconds after it starts? Or is it just (your Internet speed) / 49MB = 0.3 seconds?

No, he's thinking of the "CoCom limits". It's built into the receiver.

There's a lot of room within those 18km/59000ft and 1000kts/1200mph limits.

Clearly the mark of the beast.

So does your boss expect you to go without a driver's license once it expires?

My boss doesn't consider my driver's license his problem, or the company's.

It'll still work. OpenSSH doesn't care about output (for ~ stuff), only input, so if you type <enter>~. it will close the connection.

Does not for me, not even with busybox sh and no funky escape codes in PS1 at all. It does with cat or yes running, so just something being output is not the problem… Hm.

It does not. open ssh linux to mac, typing ~ just types it on fish shell prompt. It works after`cat` followed by ENTER

Just type <enter> without cat, your shell will show you another prompt, and the ssh escape command will also work.

No they are correct, fish seems to intercept this or something like that. Only works with cat.

So you're saying 'fish' intercepts it on the far end? The ssh server on the far end shouldn't be sending it to 'fish' until it knows what's coming next.

Is this a current-ish version of OpenSSH or some other client/server?

EDIT Interesting! I tested it with fish and it does indeed intercept it! Wonder how that works.


In newer versions, it's disabled by default and you have to do something like this to enable in ~/.ssh/config:

    Host *
    EnableEscapeCommandline yes

`EnableEscapeCommandline` only controls the <Enter>~C commandline.

The reason that is disabled in current OpenSSH by default is OpenBSD `pledge` support:

https://security.stackexchange.com/questions/280793/what-att...

On my Linux,

    cat<Enter>~.
closes the connection as expected, and no ~ is shown in the terminal.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: